two different input types for `edit savings`

[nidhi-nayak]

in the UG, there are 2 different kinds of inputs for the edit savings command that will confuse the user on which to use.

[nus-se-bot]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Thank you for bringing the mismatch in the user guide to my attention. I understand the concerns about the incorrect command format example and its classification as a High severity bug. However, I propose that it is more appropriately classified as Medium severity for several reasons:

1. The erroneous command format, while leading to an exception, does not affect the application's core functionality or security—it's specific to one test case.

2. The error is limited to the user guide. Additionally, the correct command syntax is outlined in the guide itself, just above the Example of Usage section, which users can follow for successful operation.

3. The Documentation Guide for the edit savings feature under Section 3.5 has been updated correctly with the appropriate command format.

4. Test cases provided in the Documentation Guide under Appendix F Section 2.5 are accurate and yield the correct expected outcomes when the proper command format is used.

5. Additionally, invoking the menu command in the application provides users with accurate usage information, offering an immediate alternative to the user guide.

Since the cause of the issue can be pinpointed to a documentation inconsistency and considering the edit savings command is correctly documented elsewhere, a reassessment of the severity to Medium is suggested.

These points indicate mitigating circumstances that could justify a reduction in the severity rating from High to a Medium.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Medium] Originally [severity.High]

• [ ] I disagree

Reason for disagreement: [replace this with your reason]

---