Unnumbered use cases

[andrefoo]

Use cases in the documentation guide are not numbered.

[nus-pe-bot]

Team's Response

It is useful to give a unique ID to each use case but there is no such requirement

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: I agree that this is not a requirement, but perhaps I could have been clearer in my explanation of why this is a documentation bug!

Here's a non-exhaustive list of reasons:

• Without numbering, locating specific use cases within a guide can become time-consuming and frustrating, especially in extensive documents. Readers might have to rely on lengthy descriptions or titles to find what they need, slowing down their workflow.
• Developers often scan through documentation to quickly find relevant information. A lack of numbering system makes this process less efficient, as readers cannot quickly jump to numbered sections or easily identify the hierarchy and organization of content.
• For those who regularly consult the developer guide, identifying changes, updates, or additions can be more challenging without a clear, sequential numbering system. This can be particularly problematic in dynamic projects like this, which happened in the span of 3 weeks, where use cases were frequently modified.

---