Sornsornah / pe

0 stars 0 forks source link

DG Unnecessary extension of UC1 #8

Open Sornsornah opened 2 weeks ago

Sornsornah commented 2 weeks ago

image.png

Extension 2a is technically the same as MSS 3, considering that viewing between the different sections is part of reviewing the instructions

nus-se-script commented 1 week ago

Team's Response

Thank you for your feedback.

While we understand the concern regarding the relevance of extension 2a in UC01, we believe this is not an unnecessary extension but a valid addition based on what we have learnt in CS2103.

1. Definition of Extensions:

As outlined in the CS2103 Textbook: “Extensions are add-on’s to the MSS that describe exceptional/alternative flow of events. They describe variations of the scenario that can happen if certain things are not as expected by the MSS.”

In this case, extension 2a describes an alternative scenario where the user interacts further with the instructions by switching between different sections (e.g., FAQs, How-to sections). While this may be considered part of the reviewing process by the tester, it adds clarity by explicitly addressing this variation in user behaviour.

2. Encouraging Comprehensive Coverage:

The CS2103 Textbook also highlights: “Identifying all possible extensions encourages us to consider all situations that a software product might face during its operation.” Including extension 2a ensures that this common and expected user action—navigating different sections — is explicitly documented, providing better coverage of all possible scenarios within the use case. This is especially important for a feature like “Help,” which might cater to a variety of user needs.

3. Purpose of Documentation:

Extensions like 2a enhance the documentation’s usefulness by acknowledging specific user actions that might not be immediately obvious in the MSS. Removing this extension would reduce clarity for stakeholders trying to understand the full scope of how the “Help” functionality is used.

In conclusion, extension 2a is not redundant but serves as a detailed consideration of a potential variation in user interaction with the instructions. Therefore, we respectfully retain this extension and classify this issue as response.Rejected.

Best regards, The SpleetWaise Team

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your explanation]