Repeated use case of "list person"

[waynezsy]

Multiple use cases start with the same first 2 steps of listing persons. This should perhaps have been extracted into a separate use case, and then the existing use cases can include the list person use case.

[nus-se-script]

Team's Response

It could have been extracted but that would only save us one step, thus we decided to keep it in to improve our clarity.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: The DG is actually more cluttered as a result of not extracting the list person use case as an inclusion in subsequent use cases, since it distracts readers from the key differences between each use case that can include the List Person use case. By leaving the list person use case embedded, it does not improve clarity.

The following is from the 2103 textbook on when to use inclusions:

The same steps being repeated also makes the DG seem less unified, as if it were written by multiple authors.

The following is from 2103 DG deliverable, highlighting the need to reduce repeated information:

---