ICT602 SRS Tip: Make Every Non-Functional Requirement Measurable
Groups writing the ICT602 Software Engineering SRS for Greenfield City Council's Smart Community Services Platform at VIT often lose marks in one place: non-functional requirements that cannot be tested.
Compare these:
- Weak: "The system shall provide fast response times."
- Strong: "95% of pages shall load in under 2 seconds with 1,000 concurrent users."
- Weak: "The platform shall be accessible."
- Strong: "The platform shall meet WCAG 2.2 Level AA."
- Weak: "High availability."
- Strong: "99.5% monthly uptime, excluding announced maintenance."
Two more quick wins: put the external GIS, payment, authentication and SMS services on your use case diagram as secondary actors, and show multiplicities on your class diagram (for example, Resident 1 to 0..* ServiceRequest).
Our full ICT602 guide has example functional requirements, an interface table and UML hints: ICT602 Assessment 2 SRS guide. Need a review? See our IT assignment help.
Comments
Post a Comment