[docs-dg] MSS for Add

[yusufaine]

---

I might be wrong but shouldn't this process be 2 steps?

Such as:

1. User requests to add new candidate with their details.
2. TA... adds the new candidate

Extension:
2a. Command is invalid
    2a1. Shows error message
    Use case ends
2b. Candidate already exists
    2b1. Shows duplicate message
    Use case ends

[soc-se-bot]

Team's Response

Our use case is still valid and follows the standard for use cases. The intention of each step is to highlight that the system will respond with the feedback message indicating the rest of the details that need to be filled.

See the following screenshots for further examples on standard of use cases provided within the scope of the module:

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: As what was pointed out in the screenshot:

A use case describes only the externally visible behaviour, not internal details, of a system

The external behaviour here is only what the user enters and what the application gives as a feedback (successfully added/invalid command or format)

However, based on how I'm understanding this MSS, it seems like there are 2 steps from the user to add a candidate as the user would first have to request to add, followed by providing the details after being prompted -- this is different from the behaviour that the app is currently showing where the user specifies what they want to do along with the details of what they want to do (add id/STUDENT_ID n/NAME p/PHONE e/EMAIL c/COURSE yr/SENIORITY avail/AVAILABILITY).

---