1
Problem Statement
Are you always running out of money before the end of the month? If yes, it's about time you need to start thinking about how to manage your money. The first step is to create a budget list. The budget list can help you to manage cash flow. It's quick, easy and will give you a good idea of where most of your money goes each month. However, there are some problems in creating a budget list. In particular one needs a lot of time to organize the budget lists and calculates remaining balance by himself. In order to maintain our budget lists more efficiently, you can use a personal finances management tool to help you manage budget list.
MMM (Mobile Money Manager) is a mobile application that combines an expense manager, a budget manager and a bill reminder! To more effectively manage your budgets, MMM provides a budget manager that makes keeping track of your expenses easily. Business expenses, personal expenses, travel expenses etc. can all be managed rapidly using expense manager. Track and manage daily expenses quickly and easily! The integrated expense manager within MMM lets you set monthly budgets on specific accounts and/or categories and monitor them via color-coded budget health bars that warns you when you are about to exceed your budgets. Interactive reports let you analyze income, expenses, cash flow and balance over various date ranges and accounts. Also integrated is a bill reminder that helps you avoid nasty late fees by issuing you timely reminders to pay your bills. You can even take a picture of your bills or invoices to keep a digital record.
User
Mobile Money Manager Spend money Account Report View Input data、 command Display
2 Use Case Diagram
Figure 2 Use Case diagram
3 Use cases
3.1 Create Account
Scope Mobile Money Manager System
Level User
Primary Actor User
Stakeholders and Interests
Preconditions The application is active.
Success Guarantee
1. A new account has been created in Mobile Money Manager
Create account
Add transaction User
Mobile Money Manager System
View report
Main Success Scenario 1. User chooses to create a new account. 2. System asks account information.
3. User fills out “name”, “currency”, “description”, “starting balance”, “monthly budget”, “default transaction status”, and “is excluded from total balance.”
4. The system validates the entered user account
information, and notifies the user that the account has been created.
Extensions 3a. User cancels request
1. User chooses cancel option to cancel the account creation
2. System notifies that the account management request has been cancelled.
4a. User enters invalid user account information
1. The system describes the entered data that were invalid, and prompts the user to re-enter the information.
2. The system validates the entered user account information, and notifies the user that the account has been created.
Special Requirements: None
Technology and Data Variations List
None
Frequency of Occurrence
Sometime
Open Issues None
3.2 Add Transaction
Scope Mobile Money Manager System
Level User
Primary Actor User
Stakeholders and Interests
2. An account exists in the account list.
Success Guarantee
1. A new transaction has been added in Mobile Money Manager.
2. The user entered data is stored in the transaction.
Main Success Scenario 1. User chooses an existing account in the account list. 2. System lists all transactions in the account.
3. User chooses to add a new transaction. 4. System asks transaction information (“name”,
“amount”, “category”, “type”, “date”, “notes”, “is repeat?”, and “status”).
5. User chooses to take a photo for the bill or item. 6. System presents the camera view and waits for user
to take a photo. 7. User takes the photo.
8. System stores the photo information (width, height, date, and photo file) and asks the transaction information.
9. User choose to set transaction type to repeat transaction.
10. System shows extract transaction information for user to enter.
11. User fills out extract transaction information
(“repeat times”, “every day/week/month/year”, and “next transaction date”).
12. The system validates the entered user account information, and notifies the user that the account has been created.
Extensions *a. User cancels request
1. User choose cancel option to cancel the transaction creation
2. System notifies that the transaction management request has been cancelled.
5a. User doesn’t want to take a photo for the bill or item.
1. Go to Main Success Scenario step 9
9a. User choose to set transaction type to non-repeat transaction.
12a. User enters invalid user transaction information 1. The system describes which entered data was
invalid, and prompts the user to re-enter the invalid information.
2. The system validates the entered transaction information, and notifies the user that the transaction has been created.
Special Requirements: None
Technology and Data Variations List
None
Frequency of Occurrence
Usually
Open Issues None
3.3 View report
Scope Mobile Money Manager System
Level User
Primary Actor User
Stakeholders and Interests
Preconditions 1. An account must exist on system
Success Guarantee
1. System shows the personal finance report
Main Success Scenario 1. User wants to view personal finance report.
2. System asks user to select types of report (“Expense by Category Report”, “Income by Category Report”, “Monthly Expense Report”, “Monthly Income Report”, “Monthly Cash Flow Report”, and “Daily Balance Chart”).
3. User wants to watch expense by category report. 4. System lists account list, and asks user to select an
account.
5. User selects an account.
6. System uses bar chart to show expense (with
percentage and amount) by category, and total spent.
1. User choose cancel option 2. System lists account list.
3a. User wants to watch income by category report. 1. System lists account list, and asks user to select an
account.
2. User selects an account.
3. System uses bar chart to show income (with percentage and amount) by category, and total received.
3b. User wants to watch monthly expense report.
1. System lists account list, and asks user to select an account.
2. User selects an account.
3. System uses bar chart to show expense (with amount) by month.
3c. User wants to watch monthly income report.
1. System lists account list, and asks user to select an account.
2. User selects an account.
3. System uses bar chart to show income (with amount) by month.
3c. User wants to watch monthly cash flow report.
1. System lists account list, and asks user to select an account.
2. User selects an account.
3. System uses bar chart to show income (with green color) and expense (with red color) by month. 3d. User wants to watch daily balance chart.
1. System lists account list, and asks user to select an account.
2. User selects an account.
3. System shows the daily changes of an account's balance.
Special Requirements: None
Technology and Data Variations List
None
Frequency of Occurrence
