jieqiboh / pe Goto Github PK

The 5th requirement pertains to the user and not the system, which is not a non-functional requirement.

There are repeated references to AddressBook, the name of the original application throughout the User Guide. Users may find this confusing since RainbowDragon is the new name.

To reproduce:

After executing the command, the app works successfully to delete the category 'Clan' as can be seen from the screenshots, and no error message regarding multiple prefixes is shown.

There is no tutorial guiding a new user through a simple example on how to use the app to do a basic add, edit and deletion of a new contact, which would be useful for new users to the application.

To resolve:
Add a tutorial section to the User Guide

To reproduce:

Run the above command, given 2 persons named "John Doe", with 1 having the category class of warrior already.

This is an issue if users have multiple friends of the same name who might share the same category class.

To reproduce:

Do group c/CATEGORY in the cli with a few contacts present.
There is a notable cutoff in the UI, and no way to scroll to see the rest of the words in the group.

Currently, the instructions only contain steps to launch the application and delete a person, and the steps to launch the application are not accurate to what was stated in the User Guide.
This is insufficient for developers who want to test the main features of the application.

To resolve:
Add manual instructions for adding, deleting and editing persons

To reproduce:

Duplicate prefixes of "clan" should result in an error and halt execution of the command, but it gets carried out and the category is deleted anyway.
Additionally, the wrong error message is displayed which may be misleading.

To reproduce:
The documented example commands in the application don't work and cause errors.

The example Find command fails when it is run, which may cause users confusion.

To resolve:
Change the provided examples

To reproduce:
Run addCategory 2147483647 c/Clan d/rainbow

The command format is valid according to the prompts, but the error message says it is invalid, which may mislead users who might not know how to resolve it.

To Resolve:
Change error messages to index out of bounds for this case

Users may want to jump between commands quickly without having to scroll back and forth. The lack of links back to the Command Reference so they can easily navigate the document is a little inconvenient.

To resolve:
Add links to the Command reference at the bottom of each feature description.

For some feature descriptions, there is a cutoff between pages that makes it a bit jarring for the user to read.

To Resolve:
Resize the sections such that every feature is on its own page.

There are some instances such as the above where the diagram is too big and gets shifted to the other page, causing a large amount of whitespace in a page, reducing readability.

To resolve:
Resize the images to fit in 1 page and reduce the whitespace

To reproduce:

Run the above command, and all partial matches are shown, which isn't a behaviour of the find command clearly defined in the documentation

To Resolve:
Update the documentation to mention how the find command behaves for partial matches as well.