test

Most if not all sequence diagrams provided in the UG are almost one page long. Which makes it hard to read for the developer reading it.

We can use ref to seperate them, for example for the goal feature, we can use one ref for goal /add and goal /remove rather then adding both into one extremity large sequence diagram.

As the goal of the developer guide is to allow the developers to understand the flow of the features within the codebase, which was not achieved due to the lengthiness of the sequqnece diagram, I have rated this bug as high.

More effort can be put in to check whether the diagram is split in the PDF. As this affects comprehensibility of the Sequence Diagram

In page 9 of developer guide. Not very sure why the month is capitalised while the day and year isn't.

Currently, all transaction are already stored and updated in the data folder under income-store and expense-store. Hence could a Transaction-store be already created under the data folder? Why must there be a 'seperate' feature just for transactions

User guide examples should be valid and used in the application, which definitely includes newlines.

In Image above, the example in the user guide includes a newline. Which returns invalid in the application shown below.

In the application, text related arguments are all lowercased. Hence its not very clear why in the example above(command summary) we use a lower case ps5 in edit and a uppercase ps5 in adding of a goal.

The correct code is suppose to be
delete 1 /type in. However when I type in
delete 1 in, it says above, Please enter a valid index. Which is a misleading error message as the argument '/type' is missing rather than there being a invalid index

Not really clear what unused goals means? Not stated in the user guide as well. In my opinion if the developers come up with their own terms, it should be explained clearly to beginner users using the application for the first time.

The command for initialisation is unclear, am I suppose to type in my name or my command?
Should be more explicitly stated at the start

I think for examples as shown above, e.g out dinner /amount 10.50 /category food. We can write it as

Example: out dinner /amount 10.50 /category food. When the reader reads the user guide, it can clearly see which is the example and which is the explanation

Error messages should be clear and intuitive to the user.

The error message above is unclear, and can definitely be more specific. For example 'you have entered a goal that does not exist yet.' As invalid goal can mean invalid characters, doesnt exist etc....

I added a date of 31st Feb and instead of rejecting the input as invalid date, the application rounds down the date to 28th February instead which is not ideal.

Numbers in this diagram are getting cut off by the arrows, making the numbers hard to see

According to documentation:

User Guide has explained the use of [ ] but not ( ). As shown below

It is unclear what (goal | category) means. Explanation of this symbol would be helpful.

Initial description gets placed under amount and date and amount gets jumbled up.

Furthermore, same bug will be displayed in list feature with no rectification.

Anchor Tags in the website leads outside of the website. Which makes the using user guide PDF a bad experience