Oen Qi Han, Kenson - Project Portfolio

As befitting a finance tracker, THRIFT allows its users to set a budget for each month and track incoming and outgoing transactions by adding and deleting them. Showing the remaining budget clearly in the user interface reduces the possibility of our users overspending their budget.

THRIFT helps our users better keep track of each transaction by allowing the transactions to be tagged. Tagging transactions with tags such as Food or Transport will improve visibility and help to categorise the transactions.

THRIFT is able to filter transactions by month. This enhances our users' ability to keep track of their spending over a long period of time, and allows them to compare monthly expenses. The find command is also very helpful in locating specific transactions, if a user wishes to do so.

Thrift is very user friendly, and users can make use of the undo and redo feature to help with any mistakes that have occurred when they use a command wrongly. Thus, even mistake-prone users are able to use THRIFT efficiently to track their finances.

As part of the project requirements, we had to work under the constraint that the application required the use of a command line interface (CLI). As such, the user would be able to interact with our app using a single line of text to execute any single command.

The following image shows how THRIFT’s user interface looks like:

To execute the list command, you have to use the following syntax:

list [m/MONTH]

Imagine that you wanted to take a look at how much you spent and saved the previous month! For example, you want to show only the transactions that occurred in Oct 2019.

To list the transactions of Oct 2019:

{End of extract}

ListCommand is instantiated by ListCommandParser#parse(String args), which attempts to parse the various parameters supplied in args and return a ListCommand object.

The sequence diagram below shows how the execution of the list is like:

The following conditions will cause a ParseException to be thrown by the parser:

The scenario below shows an example of how the feature works:

Step 1. The user executes list m/10/2019 to filter the list to bring up transactions of October 2019.

Step 2. The ListCommandParser will parse the arguments using the method ListCommandParser#parse(String args).

Step 3. Since user input is correct and the arguments have been parsed, a new ListCommand object will be created by the ListCommandParser.

Step 4. This ListCommand object will use a Predicate based on the specified month which is used to filter through each Transaction.

Step 5. The final list of filtered transactions will be brought up. The income, expense, and balance values in the UI will be updated accordingly as well, to reflect the correct values for the filtered month.

The activity diagram below will give an overview of what is happening when the command is executed.

In the near future, we plan to enhance the filtering feature. We want to improve the list command to take in tags as a possible argument similar to month, and thus allow for the possible filtering by tags as well. The design considerations mentioned earlier was to facilitate this proposed extension, since we would require the use of a Predicate which will be created using the tag in the argument as well. By doing so, we reduce the difficulty of enhancing the filtering feature in the future. This would benefit the simplicity of the command and further enhance the user experience, for them to be able to filter by a combination of both months and tags.

The image below shows how a possible future implementation of this feature could look like:

{End of extract}