Description of Issue
While most requirements have an included rationale, sections 12, 13, 15, and 17 do not have any.
While some do not inherently require a rationale as per the rubric (Requirements whose rationale is obvious, such as Release Requirement 13.5.3 "Products must be tested before each release.") many other requirements, particularly from section 12, include numeric values in the requirement but fail to discuss how these values were arrived at or why they are valid.
E.g. 12.4.2 "The system shall provide 10 minutes of emergency operation..." or 12.6.3 "The product shall be capable of processing up to 500 000 customers within 3 years of launch..."
Providing rationale for why you chose these numbers or how you calculated/arrived at them will greatly improve the unambiguity of your SRS document.
Artifact Under Review SRS
Team Number for Team Doing the Review 12
Description of Issue While most requirements have an included rationale, sections 12, 13, 15, and 17 do not have any.
While some do not inherently require a rationale as per the rubric (Requirements whose rationale is obvious, such as Release Requirement 13.5.3 "Products must be tested before each release.") many other requirements, particularly from section 12, include numeric values in the requirement but fail to discuss how these values were arrived at or why they are valid.
E.g. 12.4.2 "The system shall provide 10 minutes of emergency operation..." or 12.6.3 "The product shall be capable of processing up to 500 000 customers within 3 years of launch..."
Providing rationale for why you chose these numbers or how you calculated/arrived at them will greatly improve the unambiguity of your SRS document.
Good work, and good luck!