Overview

FastTrack is a desktop application to help you keep track of daily expenses, optimised for use via a command line interface (CLI). With this app, you can easily add expenses by category, view a summary of what has been spent in total, by category or for the week. The user interface is intuitive and easy-to-use. Overall, FastTrack aims to speed up the time taken to log expenses, saving valuable time for the user.

Summary of Contributions

Enhancements implemented:

  • Helped with implementation of Category class.

    • Defined the Category class with its fields. (Pull request #30)
    • Edited storage system to accommodate Category class. (Pull request #29)

  • Helped with the implementation of RecurringExpenseManager class.

    • Edited storage system to accommodate Category class. (Pull request #95)

  • Implemented edit function for all 3 main classes used (Category, Expense and RecurringExpenseManager)

    • Implemented EditExpenseCommand along with its necessary helper parser class. (Pull request #77)
    • Implemented EditCategoryCommand along with necessary parser class. (Pull request #78)
    • Implemented EditRecurringExpenseManagerCommand along with necessary parser class. (Pull request #130)

  • Added basic startup data that was adapted for FastTrack’s usage. (Morphed from AB3’s given sample data) (Pull request #107)

  • Added functionality that causes list of Expense in FastTrack to be sorted by date upon any operations (adding/deleting expenses) (Pull request #136)

Contributions to the UG:

  • Wrote about features in initial draft and added tables denoting the parameters used as well as simple explanations.

Contributions to the DG:

  • Worked on the Implementations portion of the DG.
  • Wrote about the Effort section of the DG.
  • Sketched multiple sequence diagrams that were translated through PlantUML to be used in the DG.

Contributions to team-based tasks:

  • Participated in weekly (sometimes biweekly) meetings to discuss project structure and direction.
  • Took part actively in debugging other teammate’s issues.
  • Fixed several bugs reported from PE Dry Run (#167, #170, #179).
  • Helped to regulate pull requests from team-mates and merged them only when they passed CI and internal test cases.

Review/Mentoring Contributions:

  • Reviewed multiple PRs made by teammates (#101, #90, #72).

Contributions beyond team project:

  • Reported bugs for another team during the PE-Dry run (T11-4): HospiSearch.