Easy Budget

08 May 2017

User Stories

Main Page

As a user, I want to see:

  • Current balance
  • Previous 5 transactions
  • Limit remaining of the current balance

Transactions

With the mobile application, the users will be able to control their incomes and outcomes. A numeric keyboard will be used to enter the amount. The result will be based on the criteria the user inputs. There are several entry form criteria and it will be also possible change the date of new transaction. User can choose an exist categories for transactions or create new. It will be possible to comment any transactions.

Methods of payment

The users would be able to use main different payment systems: Cash, Bank Card, Credit Card and so on. Otherwise they may use different currency: EUR, USD, CNY, UAH, RUB and so on.

Icons

As a user, I can recognize some of the features with the help of relevant icons.

Security

A user should be able to enter pin as a numeric value. When a selection is wrong, there will be no alternate way for login. The user should then create a new login. The user can enter a pin code from the setting to unlock the application. Pin code includes a numeric value and it can be set five digit long numbers.

Recurring Transactions

It will be possible to add recurring transactions that will be added automatically. Also recurring transactions are customizable and same entry transaction form should be used with a slight option for recurring transactions. Every user can check the frequency occurrence and this feature include daily, weekly, monthly. In addition to recurring layout is checking option for type transaction.

Review

On the mobile application, a user can:

  • Make a budget plan
  • Check the reviews which is depending date
  • Label payment

Use Case

How did your team gather requirements??

We gathered all our requirements from the user through questions and answers through which we are able to prioritize the tasks and divide this task between team members.

How did your team analyze requirements?

We use the next means for requirements analysis

  • Brainsorm
  • Prioritizing the requirements
  • Idea collection
  • SCRUM

How did your team specify requirements? How did you map requirements to user stories/use case?

We are able to specify the requirement through the user's priority which also helped us to map them to the user stories and use case based on relationship or dependencies that exists among them.

How did your team identifies wrong assumptions?

We also had the initial that the application should be a multi-user which will require registration of user but this was also filtered out as the user said its going to be a single user application . Therefore, there is no need for registration.