[Developer Guide] NFR pertaining to sorting maximum time is not scoped clearly

[vigonometry]

Details

• The developer guide solely mentions the time complexity taken to perform sorting operations.
• Furthermore, the use of the term "maximum time of O(nlogn)" leads readers to perceive that the time taken is O(nlogn) units which is not a number but rather a time complexity.

Expected behavior

• The developers quantify a way to verify the time complexity of their sorting algorithm/maximum time.
• Mention this corresponds with an average time complexity of O(nlogn)

Screenshots / Screen recordings

System Details

• Desktop OS: Mac OS Ventura 13.1
• JDK: OpenJDK 11/Azul
• Build Resolution: 1920 x 1080

[nus-se-bot]

Team's Response

It should be clear that we are talking about time complexity ...

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement:

Referring to the quality of requirements section on the CS2103/T module website a well-defined requirement should be testable. Simply stating "has a time of O(nlogn)" does not make this verifiable. It has to be associated with a quantifiable/testable metric that makes it easy to ascertain the verity of their assertions.

As such I will not be accepting this response as their NFR has been poorly scoped resulting in testers finding it tough to verify their claims. It should thus remain a DocumentationBug.

---