"A goal without a plan is just a wish," as the saying goes. Nowhere is that truer than in software, where a System Requirements Specification, or SRS, sets out what the client expects and what's expected of the software system being developed. It's a mutual agreement and insurance policy between client and developer, and a vital part of the software development lifecycle.
What is an SRS?
The SRS is a technical document that provides a framework for the development process. It gives an overview of the software, including what it should do and its parameters, how it interacts with its environment and end users, and its hardware and software requirements. It should be readable and understandable by everyone involved in producing the software: clients, designers, coders, testers and end users alike.
Can you do without one?
You can, if you don't want an overview of the project available to the whole team, don't want to know what the software is supposed to do, aren't interested in inspiring confidence in stakeholders and users, are happy to leave things open to a variety of interpretations, or aren't worried about expected costs and time implications. For most projects worth doing properly, the answer is that you do want one.
Who writes it, and to what standard?
Many people can be involved, not least the client. The project manager is usually at the forefront, but system analysts, programmers, technical writers and product marketers often contribute too. It's good practice to use project-unique identifiers so the document, and references within it, can be traced in a hierarchical way, and to record how requirements will be tested so quantitative elements are built in. The language should be clear, concise and consistent, avoiding ambiguity and passive phrasing.
A generic SRS structure
Before the introduction, it's good practice to keep a revision history, so you can see how the document has evolved. The introduction should cover the purpose of the software, the reasons it needs to be built, its parameters, standardised terms, and any references used in preparing the specification.
The description section covers a general overview of the software, who will use it, the environment it will work in, any constraints on development, and assumptions about dependencies. An interfaces section describes how the software presents to the end user, alongside hardware, software and communication interfaces. Functional requirements describe how the software behaves in response to business needs, telling the developer what to build. Non-functional requirements cover performance, quality attributes, business rules and security. A user documentation section lists supporting materials such as manuals and tutorials, and an appendix holds a glossary and any supporting diagrams.
It's worth the time to produce a full and clear SRS. It lets the client see what they're getting, and lets the development team understand the client's needs well enough to produce something genuinely valuable. If you have any concerns about compiling one, or need a hand, get in touch.