Personal Financial Management and Prediction Tool

Personal financial management and prediction tool for personal use
Name
Institution
Professor
Course
Date

Part A – Requirements
Functional requirements
R1. System would allow user to determine expenses over a given period of time.
R2. The tool should allow setting of a new user and update relevant details.
R3. The tool would be used to determine or predict future expenses.
R4. It should provide an opportunity to enter and evaluate recurrent personal expenditures.
R5. System should be able to produce a report that suites individual needs.
R6. The tool should provide an opportunity to compare expenses over a given period of time in
months.
R7. The system should provide individual with an interactive interface which is simple and easy
to use. System is required to provide users with simple and robust interface that is attractive as
well as simple to use. It has to meet some requirements such as usability, reusability and
R8. System should provide user with validations which minimize possibility of incorrect data.
Validation determines the nature of data captured by the system in terms of characters and
numbers. Where integers are required, no other values should be accepted by a specific field.
Proper validation makes sure data captured into the system is consistent and accurate.
R9. The tool should offer required security to any data captured by the system. The data can be
protected through several mechanisms such as; data encryption which can be initiated from data
entry point while on forms. The next data protection mechanism is through authentication and
authorization. Both authentication and authorization are quite important as they determine who
access the data and manipulation accorded to each user.
Non-Functional requirements
NF1. The application specification is to run on windows systems which is common platform to
many system users.
NF1. The tool would be used to generate desirable reports as instructed by the user. User can
generate report for different uses in regard to available options.

NF1. Implementation would developed on Vb.Net framework and its associated windows forms.
Part B – Use Case Diagrams
1. Use cases
2. Use cases description
Use case Register Expenses
Id UC_001
Description Enter personal recurrent expenditure
Primary Actor System owner
Supporting actor None
Stakeholders and Interests System owner
Pre-conditions Expenses must be recorded
Post conditions Capturing expenses and generating reports
Triger Register expenses, Print report
Main scenario (steps) 1. Login to the system
2. Enter date of the expenses
3. Register/Update expenses
4. Systems updates/saves new records
5. Total expenses gets updated
Variations Users can register single expense at a time