Adi-Kesava Das’ - Project Portfolio Page

Project: NUS Expenses Tracker (NET)

NET is an app for managing expenses, optimized for use via a Command Line Interface (CLI) while still having the benefits of a Graphical User Interface (GUI).

Contributions to the project.

• Initial Code Skeleton / Baseline(#1, #9)

• New Feature: User Interface (UI)(#14)
  • What it does: Provides a interface layer for the user to interact with. Handles inputs from the user and displays outputs.
  • Justification: Prompts users on when to input commands with feedbacks.
  • Credits: Logic and design adapted from addressbook-level2 (TextUi)
• New Feature: Regular Expressions (Regex) for different commands. E.g. Add, Update, Search, View, (#21, #39, #43, #45).
  • What it does: User input is parsed and matched by Regex to determine the commands and arguments input
  • Justification: Pattern matching of inputs allows for optional inputs and to isolate arguments for processing and exception handling.
  • Credits: Some minor reference taken from addressbook-level2 (Parser)
• New Feature: Added a Search Function (#21)
  • What it does: Allows the user to search for transactions with a specified keyword.
  • Justification: Allows for the user to search and view specific past transactions.
  • Credits: Logic and design adapted from addressbook-level2 (FindCommand)
• New Feature: Added the Category Functionality (#39)
  • What it does: Allows for the user to specify the category for a transaction when adding and or modifying.
  • Justification: Categorizes transactions with a String tag. Allows for a more insightful look at past transactions.

• Code contributed: RepoSense Link

• Project management
  • Managed releases v1.0 - v3.0 (3 releases) on Github
• Enhancements to existing features:
  • Enhanced the View functionality to allow filtering to display only transactions of a specified category(#43)
  • Enhanced the Update functionality to allow updating of a transactions category.(#45)
• Documentation:
  • User Guide:
    • Added documentation for the view (#52)
  • Developer Guide:
    • Added Component diagram. Added plantUML Architecture.puml (#67)
    • Fixed UG and DG grammar, markdowns… (#68)
    • Added SearchCommand Sequence diagram (#79)
    • Added SearchCommand Object diagram. Added NUS Expense Tracker Use Case diagram. (#84)
• Community:
  • Our application was developed using a combination of pair-programming and adhoc coding sessions. During each session lasting between an hour to four or more, all group members sat in a meeting session while coding/ implementing their assigned components. If a concern was raised or support was needed, they shared their screen via the meeting session and everyone participated or assisted to clear the obstacle. Using this method we’ve successfully cleared v1.0 to v3.0 of our project milestones.
• Tools
  • All Regular Expression created with aid of RegExr by gskinner.
  • Diagrams drawn using draw.io / diagrams.net