Requirements Specification and Sprint 1 Plans - coconutbmp/leash GitHub Wiki

Requirements

Here we will document the refined requirements based on what was given by the client during our first client meeting for sprint 1. The following 6 requirements were given by the client for this sprint:

-Implement login and sign in features, allow for logging in with a third party such as google

-Implement a create budget button such that when clicked, a mini page should pop up. This mini page should contain fields allowing the user to input their details

-Implement a page showing a summary of financial activity.

-Add a page called 'loans/liabilities' (display details of loans taken out).

-Based on the repayment/payment amounts, the app should calculate what remains from what is set aside (in the budget) to pay for the loan/debt.

-Make the app look really nice (must contain buttons with rounded edges)

Sprint Planning

Roles

In the sprint planning, we divided the project into several categories, with each team member choosing which category they would like to take up as their role. The list of the categories and the corresponding members is as follows:

• Back-end: Hewitt Nyambalo (2362907); Liam Carstens (2304903);

• Database: Ama Commey (2312836); Michael Coker (2277795);

• Front-End: Liam Carstens (2304903)

• Admin: Michael Coker (2277795);

• Testing: Liam Carstens (2304903); Hewitt Nyambalo (2362907);

• Server: Liam Carstens (2304903);

We may change roles in later sprints depending on the amount of assistance required. The roles aren't strict and mainly serve as our expectations of what part of the project we will be mainly working on.

We decided to divide the requirements into tasks that all of us will work to accomplish mainly within our roles. We also established the user stories we will accomplish and the acceptance tests to be conducted.

User Stories

The first 4 user stories we derived are the ones we wanted to finish within the sprint. We planned to achieve the remaining ones if we had the time and they may spill over into the next sprint.

  1. As an unauthorised user, I can sign up to gain subsequent access to the remaining pages of the app.

  2. As an authorised user, I can add my budget details and submit them to store them for later use.

  3. As an unauthorised user, I can log in using a third party such as Google to avoid using a custom password for the app

  4. As an unauthorised user, I can see prompted messages explaining invalid input upon registration to correct erroneous sign-up details

  5. As an authorised user, I can access a summary page to view a summary of my financial activity.

  6. As an authorised user, I can enter details of my loans and liabilities to view them later on and keep track of how much money I have access to.

User Acceptance Tests

  1. Given I am an unauthorised user, when I sign up or log in, I will gain access to the remaining pages of the app.
  2. Given I am an authorised user, when I add my budget details and submit them, then they will be stored for later use.
  3. Given I am an unauthorised user, when I attempt to log in via a third party, then I'll be redirected to an authentication page.
  4. Given I am an unauthorised user, when I enter the wrong details, then I'll be prompted to correct them.
  5. Given I am an authorised user, when I access a summary page, then I will view my financial activity.
  6. Given I am an authorised user, when I enter details of my loans and liabilities, then I will view them later on and keep track of how much money I have access to.