Austin Santoso - Project Portfolio

The current Budget component keeps track of three variables:

The budget amount and the month the budget is set are saved in the save file, whereas the sum is not. Upon initialization, if a save file is found it will automatically set the monthly budget based on the save file’s options. Once the save file is loaded, the program will check today’s month. If the month has changed, the budget’s set month will change to the current month, and the budget amount will carry over. Once the month has been set, it will go through all spending available and sum up all the spending that are in the set month. It will then keep track of this sum.

Once done initializing, users can set a new monthly budget by executing the budget command. The sequence diagram below demonstrates how the budget command is executed:

The figure above shows the sequence of events that occur to set the monthly budget:

Budget also keeps track of the sum of all spending in order to show the user how much budget the user has left. Initially, it has totaled up all spending in the save file, and then the value is modified when the add, delete and edit commands are called.

The following sequence diagram demonstrates how Budget modifies its value when the add command is used:

The diagram above shows what happens when an addCommand is being executed. It focuses only on the components that affect Budget.

When adding a new Spending the following steps happen:

The same applies to delete commands, instead of adding to the sum, it is subtracting from the sum. As well as edit command, which utilizes both add and delete.

A combination of the two was chosen. During the initialization phase, we read through all spending available, but we handle add, delete and edit commands using option 1.

The up and down key mechanism is facilitated by the logic component of MoneyGoWhere. Whenever a user inputs a command, it is stored internally in a list in CommandHistory component of Storage. CommandHistory has an internal index to keep track of its current position in the list.

Additionally, it implements the following operations:

The index is initially set to -1, to indicate that there has been no user input. Whenever a user inputs a command, the command is stored at the end of the list and the index is set to the size of the list, to indicate that there are no commands beyond after this point.

Calling getPrevCommand() will cause the index to decrement by 1 and show the user input command stored at that index. When the index is currently 0, or the first user input, pressing the up key will cause the index to result in -1. This returns the empty string, since there are no commands before this point. Any further up key press will have the same outcome, but the index will stay at negative one.

Calling getNextCommand() will cause the index to increment by 1 and the user input at that index will be returned. If the index is currently the last possible value, the last user input, pressing the down key will cause the index to increment by 1, which is outside the list, the empty string will be returned. Any further down key press will have the same outcome but the index will stay at the list size or one after the last possible index.

The following sequence diagram shows how the up/down key mechanism works:

The following steps explain the sequence diagram:

To summarize what determines the output when the user presses the down key:

The following steps explain the activity diagram:

The sequence diagram and activity diagram for getPrevCommand() are similar to the sequence and activity diagram of getNextCommand() as shown above. The only difference is whether it returns the next command or the previous command.