Software Requirements Specification

6 weeks · 0 milestones

Produce a Software Requirements Specification (SRS) for a real or realistic software system using IEEE 830 or an equivalent structured format. The SRS must cover: functional requirements (at least 15 numbered, testable requirements with input, output, and boundary conditions), non-functional requirements (performance, security, availability, maintainability — each with a measurable acceptance criterion), assumptions and constraints documented explicitly, and use-case or user-story mapping to each requirement. The system described must be real or realistic enough that the requirements can be verified against it. Proof artifacts: the SRS document (design artifact) and a review record in which a software engineer challenges at least 3 requirements for completeness or consistency — with your written responses (documentation artifact). Accessible: no special software required — the SRS is a document artifact. Verification: a software engineer or systems architect who challenges 'this requirement is ambiguous — how would you test it?' for at least 3 requirements before endorsing. Generic fictional systems are not accepted; the reviewer must be able to ask grounding questions about real constraints.

Sign in to start this outcome and track your progress publicly.