SpendWise

SpendWise

1. Success Criteria

   • Functionality: The solution provides the user with the opportunity to save money, and track expenses and therefore meets the users’ needs of receiving an expense tracking app.
   • Usability: Solution is easy to navigate and has a user-friendly interface. It has clearly labelled buttons, is suitable for all ages and feedback is shown instantly.
   • Performance: Solution responds quickly to inputs and doesn’t have lags. Runs smoothly on devices that have the code installed.
   • -Security: User data is stored safely in databases. Expense records are stored safely and are shown on the home page.
   • Scalability: Code can be expanded further in the future, it can be made more interactive and online, to hold more users and to allow users to use the app.

2. Constraint and Limitations

   • Hardware constraints: The solution is limited to a device that has software which can run the code for the solution, so it is likely limited to a computer.
   • Budget constraints: Development of the solution must be built on a budget, so there is currently no money for maintenance costs. All technology and deployment costs must fall within the budget.
   • Time constraints: The solution must be built over a span of 4 weeks so this may affect the thoroughness of testing and inclusion of additional features.
   • Legal constraints: The solution must abide by all data laws regarding data protection and collection.
   • Ethical constraints: All data must be stored securely and protected. Users must be made aware that by signing up, their data will be stored, to ensure user consent. Social impacts may include help with stress management as it helps manage expenses and helps reduce spending.

3. User Requirements

   • User Personas: Specific user persona for this solution is a 16-year-old student that wants an app to help her with her spending problem, by helping her track expenses and save money.
   • Functional Requirements: Users require user registration. Users must be able to create records, read records, edit records and delete records. Interface must include all the buttons, numbers, info and records that the user needs to solve their frustration and meet their needs.
   • Non-Functional Requirements
     • Performance: Solution should respond quickly to user inputs.
     • Security: Solution requires a username and password to play.
     • Usability: Simple and functional design, accessible with contrasting colours and has easy navigation and readability.
     • Reliability: Solution should load quickly and function consistently without crashing. Any invalid inputs should not crash the solution. If the solution encounters an error, it should reload or reset to the home page. User data should also not be lost due to minor system errors.
     • Support: Captions can be added to help the user navigate the application.

4. Programming Requirements

   • Languages: The coding languages of Python, CSS, SQL and HTML will be used.
   • Frameworks: The flask framework will be used.
   • Scalability: The solution can handle increased input loads and more users using the solution. It can handle future growth and expansion to the code as it is a simple solution that can store a lot of data
   • Performance: The solution has a speed which allows for ease of use, and has a low latency, which allows for quick responses to the user’s inputs, creating a smooth experience.
   • Testing: Usability was tested, and existing solutions were taken into consideration when building the solution, to improve overall user experience.

5. System Requirements

   • Operating Systems: All operating systems will be able to play this solution if code running systems are installed such as Thonny or VS code.
   • Software Dependencies: Libraries such as Flask and SQLite are required.
   • Hardware Specifications: Memory required for the solution is relatively low, no storage is required as the solution is browser only, and any processor will do as no animations are used in the solution.
   • Network Requirements: Connection to the internet is required but the bandwidth does not need to be extremely high, only high enough to have a quick system response when inputting actions, so around a 3G mobile connection or over.
   • Accessibility Requirements: The background can be made a different colour to contrast to the black and white table of expenses, to help users with low vision. Font sizes can be made bigger to also help with readability. For accessibility requirements regarding the system, the solution is only available for those who have the files and code from the developers and is not open to the public such as a public website. This limits the public from playing the solution.

6. Data that is required

   • Real World Data Sources: Databases will be used to track user profiles and user expenses.
   • Data Types: Structured Data will be used for the UserID, expenses and passwords. Unstructured data will be used for images.
   • Data Volume: Initially, the solution will have a small volume of data with around 500-1000 rows of data. This can be scaled up if the app expands in the future.
   • Data Cleaning and Transformation: The solution will remove invalid user inputs by asking the user to redo them.
   • Data Security and Privacy: Data will be kept secure and will be anonymized if shared.

7. Scope of Problem

   • The problem that needed to be solved was a CRUD Web Application that needed to be created in relation to money and tracking expenses, called SpendWise. This solution needs to be able to be used by multiple users, and allow the users to create, read, update and delete records, such as logged purchases and a sign in and log in function. The solution may help stakeholders by providing an easy to use, simple design and functional solution to their problem.

8. Impacts of storing data in databases for individuals, governments and organisations

   • Social
     • The solution has a positive social impact as it could result in improvement in money-managing skills and better spending habits.
   • Personal
     • Users must be aware that their data is being collected and are able to use anonymous data to help with privacy. Users should also be able to have control over their data, such as being able to delete their data.
   • Economic
     • The solution uses local storage, so no money is needed for that. The solution will be kept free and private so data will not be monetized. Local databases will be used, which aligns with the low budget provided for the solution.
   • Government
     • The solution needs to apply with the data security and privacy laws. Data handling must be secure and safe.

9. User Interface Design

   • Layout: Solution has a clean and clear design, expenses are easy to see however could be made to be seen easier with a contrasting colour to the background (such as a dark background and a light records colour). Navigation is predictable which allows for ease of use for the user.
   • Colours and Fonts: Colour theme and font is consistent, with buttons having larger fonts and the background contrasting with the record colours. Allows for easy readability for the user.
   • Responsive Design: Solution is only compatible with a desktop screen and would not be easy to play on a mobile device.
   • Interactivity: Solution uses buttons and real-life feedback to allow for interactivity.

10. Proposed Digital Solution Components

    • Core functionality: Solution has core functions of a login, signup, home and create record.
    • Programming Logic: Solution uses algorithms, for example to add an expense.
    • Database Integration: Solution uses databases to store user data and expenses.
    • APIs and Web services: No external APIs used but could be implemented for future online features.

11. User Feedback and Testing

    • Prototyping: Mockups were made to ensure a perfect user experience.
    • Usability Testing: Mockups were based on existing solutions, to allow for the system to meet to all common user needs and common web functions.
    • Iterative Development: Code was edited to meet user feedback throughout the development process.