search

AY2324S2-CS2103T-W12-1 / tp

https://ay2324s2-cs2103t-w12-1.github.io/tp/
MIT License
0 stars 4 forks source link

Update Use Cases in DG #184

Closed yorklim closed 7 months ago

yorklim commented 7 months ago

I changed some things in the DG,

  1. Removed reference to (view client) in add, cause its weird in the sense that view client is initiated by the user according to the use referred to but i think in this sense it was the system updating it automatically
  2. References to how UI updates, person is shifted from Last Met Display to Schedule Display. This is too specific and i think is pretty much talking about how its implemented already so i think cannot. So i think just saying like add is sufficient
  3. Added missing shows success messages
  4. Make extensions consistent
  5. I dont think we need to be specific about what the system should tell the client if a certain part fails so i think we just have to say shows a error message
  6. Removed extensions which would be covered by another extension eg parameter format issues (this does not include invalid values)
  7. Edited extension to end if client intended action completes, eg thing client is trying to delete is already deleted/ not even there in the first place, client put invalid inputs (This does not include scenarios where client does not know how to use the command/ uses the command incorrectly)
  8. Fixed find extension wrong numbering
  9. For UC6 MSS 3 im not sure if that is correct as it shows the client details of the first person in the list, but then idk if we say first person is it too specific. Idk if ppl will say then if got multiple ppl in the list will they show all the client details (Ill leave this untouched for now, PLEASE HELP!)
  10. Removed UC4 extension 1b cause it doesnt do that
  11. UC3 cause is was literally the same as list