Feedback for V0.3 - Githubissues

Admin

@aanshul20 please update your photo to show your full face clearly (and rotate the image properly!)

you need to add a screenshot of your application in the user guide
3.0 Features
- I feel the first quoting is unnecessary
3.2 Add
- Think if you can make add easier for the user rather than have the e and t every time.
- in the command format, it is better to spell out the full thing rather than use ellipses
- how will the user add a floating task, the one without either start or end times?
3.3 List
- how does c relate to expired tasks?
- can c or o be combined with e or t? as a user, I would like to use just one variant in the first place!
- 3.4 Edit
- it is quite strange that add and list requires you to specify the task type, but edit doesn't need that information.
3.6 Find
- you may want to list restrictions/features of the find command, like search behavior
3.10 Undo
- need to explain the undo behavior, how many levels of commands can be undone, what commands can be undone etc.,
3.11
- what is the difference between edit and recycle?

please take a look at the project requirements and scope and see if you have missed something. please update the user guide accordingly.
you may want to use some screenshots to show the behavior of the product.
The 'Command summary' section will be used heavily by our testers. Try to make it easy to use as possible. e.g. give examples for each command.
some parts of your user guide are terse, please try to improve on that.

you have some references to addressbook, please correct it.
2.1 Architecture
- are you using the web component in the project? if so you may need to explain how; if not, please update the architecture diagram
please refer to your handouts to check how sequence diagrams are written, there are minor errors in your sequence diagrams, please fix those.
2.4 Model
- please un-mess the diagram
- UserItem is probably not the best of the names for the class related to task manager.
4.0 Testing
- It may be more practical to give a few examples of interesting test cases and explain the thinking behind how you arrived at those test cases, rather than try to give a comprehensive list of all test cases.
Suggested additions
- Explain how your design support undo/redo. There are multiple ways this can be done, so it will be useful to explain how you do it and why you chose to do it that way.
- Similarly, you can explain other interesting design decisions you made.

@bdioni @aanshul20 @yoshi-1224 for your action!