ay2122s1-cs2103t-t10-4 / tp Goto Github PK

Status:
TOWATCH,
WATCHING,
FINISHED

• Update help command to include every command
• Update user guide

Complete refactor of developer's guide to match that of our project

As an organized user, I want to organize my anime by status so that I can better keep track of which anime I am watching

As a user, I want to quickly remove all animes that matches a particular criteria, for more convenience.

Rename code to follow the updated glossary in the DG.

Update the target user profile and value proposition to match the project direction you have selected. Give a list of the user stories (and update/delete existing ones, if applicable), including priorities. This can include user stories considered but will not be included in the final product.

Remove EditCommand and related tests / code

Need to update testcases for commands such as add and genre to include names that includes prefixes.
Replace magic strings with constants

Give use cases (textual form) for a few representative user stories that need multiple steps to complete. e.g. Adding a tag to a person

I want to be able to delete anime that I no longer want to be shown on the list

As we are changing the whole app, there is a need to change address book code into one suitable for starting the development of AniList.

As a user, I want to find an anime by some criteria, so that I can access anime(s) of a certain criteria quickly.
Format: find g/genreName

Define terms that are worth recording.

Need to clarify terms so that we can be uniform about what to use in our code.

• Mention that leading and trailing whitespace are ignored
• Miscellaneous grammar issues, eg Genres deleted from anime -> Genre(s) deleted from anime
• Explain the tabs
• Since we are not enforcing the episode of an anime to be at 0 for it to be moved to TOWATCH, we shd mention that TOWATCH can also mean an anime has been put on hold temporarily. Same for FINISHED
• Add hyperlink in each section to go back to TOC

As a user, I can read more about the application, so that I can understand what I am using.

As a user, I can read more about the developers.

As a developer, I can look at a nicer site for all of my project websites.

As an anime watcher, I want to view the statistical breakdown of the animes in my list, so that I get a sense of my own preferences and progress.

• Implement pie chart for status breakdown, bar graph for top genres watched and episode count and wrap them in a panel

Below are the things to refactor:

• src/main/resources/view/MainWindow.fxml line 336
• src/main/resources/view/MainWindow.fxml line 33 and line 40

As a picky user, I want to be able to change into different themes, to better personalize the app to my taste.

As a careless user, I want to confirm clearing the anime list, so that I won't accidentally delete everything.

Write documentation in the format of javadocs to aide test case writing

As a new user, I want to see usage instructions, so that I can refer to instructions when I forget how to use the App

Update AddCommand to use status and episode

As a user, I want to list all anime, so that I can see all anime that I have added.

Update Help Command and docs

As an organized user, I want to see more animes with different status in different tabs, so that I can immediately know which animes are of which status.

Update names and tags of anime objects used for testing. Update name validation criteria to include new characters.

As an organized user, I want to specify the genre of the animes, so that I can keep track of which anime is of which genre.

As a user who prefers keyboard over mouse, I want to have a shortcut to access different lists on the keyboard, so that I won't have to use the mouse.

• Currently adding a genre that already exists or deleting a genre that doesn't exist in an anime displays a success message even though nothing actually happens

• Possible fix as suggested by Minhong: only proceed when all genres input are valid, otherwise output invalid genres provided.

Example for delete genre (same goes for add genre):

Note: Many of the given project constraints can be considered NFRs. You can add more. e.g. performance requirements, usability requirements, scalability requirements, etc.

As a user, I can read the user guide and understand how to use the program.

As a user, I want to update anime episode, so that I can ensure I am on the right episode of the anime.

As a user, I want to add a new anime, so that I can keep track of the anime.