More elaboration in use case 09

[nus-se-script]

Step 1 could most likely be separated into 2 steps, and more extensions could be added to this use case.

Example:

1. User selects a client and select an insurance plan
2. User requests to add a claim to selected insurance plan
3. System adds claim to the insurance plan

2a. The claim id is in the wrong format 2a1. System shows an error message 2a2. User inputs the claim id Use case repeats until user enter it in the correct format Use case resumes from step 3

This is just a rough example, and more extensions could be added, for example the claim amount is in the wrong format.

---

_{[original: nus-cs2103-AY2425S1/pe-interim#3170] [original labels: severity.Medium type.DocumentationBug]}

[RezwanAhmed123]

Team's Response

Thanks for bringing up the issue. While we agree that we can add more information to the documentation, currently we went with the most basic externally visible behaviour for the system in the MSS. As such, we kept all of the inputs to step 1 which is what the command entails (externally visible behaviour).

Duplicate status (if any):

--