How to Write Software Requirements Specification (SRS) Document

An SRS document, short for software requirements specification, states what a piece of software must do and how well it must do it, in language precise enough to test against. It exists to stop requirements like “the system should be fast” from reaching development.

Fast to whom, and under what load? When nobody settles it, everyone assumes, and the disagreement surfaces in user testing, when it is expensive to fix.

This guide gives you a template and a worked example, then covers the standard to follow and how to write the document for a custom software development project.

What is a Software Requirements Document?

A software requirements document describes what the software must do, how it should perform, and the constraints it works under. The SRS is the shared agreement between clients, developers, testers, and stakeholders about what is being built.

The value is agreement. The SRS document makes disagreement visible during the requirements phase of the SDLC, when a misunderstanding is cheapest to fix. Developers read it to know what to build, testers write test cases from it, and the client confirms it matches what they asked for.

The SRS is not a design document. It defines what the system must do and leaves the how to engineers. Mixing the two can lock engineers into technical decisions before they have compared the options.

What types of requirements does a software requirements document cover?

A requirements document covers four requirement types: business requirements explain why the project exists, user requirements describe what people need to accomplish, functional requirements define what the system does, and non-functional requirements set how well it must do it.

The four requirement types in an SRS document: business, user, functional, and non-functional

The types sit at different levels of detail, and confusing them is where documents go wrong. The examples below are illustrative.

Type Question it answers Example
Business Why are we building this? Cut the time spent on manual stock counts
User What must a person accomplish? A warehouse manager needs to see live stock across three sites
Functional What must the system do? The system shall display current stock quantity per SKU per location
Non-functional How well must it do it? Stock data shall refresh within 3 seconds of a change

A statement like “the system should be fast” is a non-functional requirement, and it needs a measurable target. Performance, reliability, and security cannot be tested without specific criteria, which is why teams forget them most often.

What should a software requirements document include?

A requirements document should include an introduction, an overall description, specific functional requirements, non-functional requirements, and appendices. Each section answers a different question, and skipping one creates ambiguity later.

SRS document template outline with five numbered sections

Copy this outline, delete what does not apply, and fill in the rest.

  • Introduction. Purpose, intended audience, product scope (including what the software does not do), definitions and acronyms, and references.
  • Overall description. Product perspective, major functions, user characteristics, operating environment, constraints, and assumptions and dependencies.
  • Specific requirements. Functional requirements, external interface requirements, and data requirements, one testable statement at a time.
  • Non-functional requirements. Performance, security, reliability and availability, usability and accessibility, scalability, and compliance (GDPR, HIPAA, PCI DSS, or whatever applies), each with a number or a named standard.
  • Appendices. Glossary, use cases or user stories, diagrams, and open items with an owner and a date.

Give every requirement a unique ID (FR-001, NFR-014) so you can trace it through design, code, and tests. Add a priority too, using a common convention such as must, should, or could, so the team knows what to cut first. That priority convention is a judgment call.

What does a good SRS document example look like?

A good requirement is specific, testable, and written as a single unambiguous statement. It uses “shall” for obligations, avoids vague adjectives, and includes a measurable threshold wherever performance or quality is involved. The thresholds in this example are illustrative.

Weak requirement Rewritten properly
The system should be fast. The system shall return search results within 2 seconds for up to 500 concurrent users.
Users can manage their profile. A registered user shall be able to edit their name, email, and phone number, and changes shall be saved within 1 second.
The app should be secure. All passwords shall be hashed using bcrypt, and sessions shall expire after 30 minutes of inactivity.
The system will handle lots of users. The system shall support 10,000 concurrent users with response times under 3 seconds at the 95th percentile.

Every rewrite added a number, a condition, or both, so someone who was not in the room can turn it into a test case. Use “shall” for obligations, since “should” and “may” invite negotiation later. Keep one requirement per statement, because a sentence that joins two behaviors with “and” is two requirements.

What does a sample SRS excerpt look like?

A sample excerpt shows how scope, IDs, priorities, and tests fit together. The excerpt uses a fictional product, StockView. Its figures are illustrative.

1.3 Product scope. StockView shows warehouse staff live stock levels across three sites. It does not create purchase orders.

ID Requirement Priority How it is verified
FR-001 The system shall display current stock quantity per SKU per location. Must Compare the screen with a database count for a sample of SKUs.
FR-002 A warehouse manager shall be able to filter stock by site. Should Select each site and confirm that only that site’s stock appears.
NFR-001 Stock data shall refresh within 3 seconds of a change. Must Change a quantity ten times and time each screen update.
NFR-002 Only users with the Manager role shall be able to edit stock quantities. Must Attempt an edit as a staff user and confirm it is refused.

Every row has an ID, a priority, and a test. A row that cannot name its test is not finished.

Which standard should a software requirements document follow?

A requirements document should follow ISO/IEC/IEEE 29148:2018, the current requirements engineering standard. Many templates online still copy the outline of IEEE 830-1998, which the IEEE now lists as superseded.

The IEEE Standards Association page for IEEE 830-1998 states “Superseded by ISO/IEC/IEEE 29148:2011.” That standard was itself replaced by ISO/IEC/IEEE 29148:2018, published in November 2018. ISO’s page for 29148:2018 lists the standard as ‘to be revised.’

IEEE 830-1998 ISO/IEC/IEEE 29148:2018
Status Superseded by the 2011 edition of 29148 Current edition
Focus A recommended practice for writing the SRS Requirements processes and the information items they produce, for systems and software
Outlines One outline for the SRS Example outlines for stakeholder, system, and software requirements documents

The practical difference is scope. 29148 separates requirements by level, from stakeholder needs down to software requirements, and its contents include verification activities as well as writing guidance. 29148 also provides guidelines for applying the requirements processes in ISO/IEC/IEEE 15288 and 12207.

The IEEE 830 outline is still a reasonable, familiar structure, and the template above draws on it. If you work in a regulated sector, or a client asks which standard you conform to, cite 29148:2018 and not a document the IEEE lists as superseded.

What is the difference between BRD, FRD, and SRS?

The difference between a BRD, an FRD, and an SRS is scope and audience. A BRD (business requirements document) explains why the project exists in business terms, an SRS defines what the software must do and how well, and an FRD (functional requirements document) details how each function behaves.

They are sequential documents. Teams define these documents differently, so the table reflects TekRevol’s judgment.

BRD SRS FRD
Answers Why are we doing this? What must the software do? How does each function behave?
Written by Business analyst, stakeholders Business analyst with technical input Business analyst or systems analyst
Read by Executives, sponsors Developers, QA, client Developers, QA
Detail level High Medium to high Highest

In TekRevol’s judgment, the SRS is the pivot document. Everything above it is written in business language, and everything below it moves into technical detail. If you create only one requirements document, make it the SRS.

How do you write a software requirements document?

Write a requirements document in six steps: gather requirements from stakeholders, organize them by type, write each as a testable statement, review with business and technical readers, get formal sign-off, and version the document as things change.

Step 1: Gather information. Interview stakeholders, observe how work happens today, and review any existing system. Ask what people do, because users describe solutions and your job is to find the problem underneath.

Step 2: Organize by type. Sort everything into business, user, functional, and non-functional requirements. Anything that does not fit is usually a design decision that snuck in, or a wish nobody owns.

Step 3: Write each requirement testably. Use one statement, one behavior, a unique ID, and a number wherever quality or performance is implied.

Step 4: Review with both sides. Business readers confirm it is what they meant, and technical readers confirm it is buildable. Doing only one is how documents get signed and then argued about.

Step 5: Get formal sign-off. Name the person and date it, because sign-off forces people to read the document.

Step 6: Version it. Requirements change, and that is normal. Changing them silently is the problem, so log each revision. The revision log also keeps software development cost conversations factual.

Does an Agile team need a requirements document?

Yes, but a lighter and versioned one. In TekRevol’s paraphrase, the Agile Manifesto values working software over comprehensive documentation and still values documentation.

In TekRevol’s judgment, Agile teams keep the upfront SRS short, covering scope, non-functional requirements, and constraints. They then write functional details as backlog items with IDs and acceptance criteria. TekRevol’s agile vs waterfall guide compares the two approaches.

What mistakes make a requirements document useless?

The mistakes that make a requirements document useless are vague language, mixing requirements with design decisions, omitting non-functional requirements, and writing it once and never updating it. A document nobody maintains stops being a reference and becomes a liability.

  • Untestable statements. If QA cannot turn a statement into a test case, it is not a requirement.
  • Design decisions disguised as requirements. “The system shall use PostgreSQL” is a design choice unless something genuinely mandates it. Specify the need and let engineers pick the tool.
  • Missing non-functional requirements. Teams document features thoroughly and skip performance, security, and availability, and the gaps surface at load testing.
  • Ambiguous words. Fast, simple, seamless, robust, and intuitive each mean something different to every reader.
  • Writing it once. A specification that reflects month one of a nine-month project becomes wrong while people still trust it.
  • No traceability. Without IDs linking requirements to tests and code, nobody can say whether a requirement was delivered.

TekRevol’s software development best practices guide covers the habits that keep requirements and delivery aligned.

How does TekRevol write software requirements?

TekRevol is a software development company that writes the requirements before it writes code. The team interviews the people who will use the software, turns each requirement into a testable statement with an ID and a measurable target, and logs every later scope change as a change request with a cost and a date.

Turn your project idea into a testable SRS before development starts! Book Free Consultation Today →

Summerize with AI

  • AI
  • AI
  • AI
  • AI
  • AI

Get In Touch

    Summarize with AI

    Frequently Asked Questions:

    A business analyst usually prepares the requirements document, working with stakeholders, product owners, and technical leads. On smaller projects, a product manager or senior developer often writes it. The document needs review from business and technical readers and sign-off from whoever controls the budget.

    Often, yes. SRD usually stands for software requirements document, which most teams use interchangeably with SRS. SRD can also mean system requirements document, which covers a whole system, so check which one a template means.

    The four types are business, user, functional, and non-functional requirements. They cover why the project exists, what people must accomplish, what the system does, and how well it does it.

    The BRD answers why the project exists, the SRS answers what the software must do and how well, and the FRD answers how each function behaves. The three are sequential documents.

    A software requirements example is a single testable statement that names the system, uses “shall”, and includes a measurable threshold. The thresholds in this example are illustrative. One such statement is “The system shall return search results within 2 seconds for up to 500 concurrent users.”

    Asim Profile Image

    About Author

    Asim Rais

    CTO

    Asim Rais Siddiqui co-founded TekRevol and has led its tech ever since. He started out writing code, and 17+ years later he’s still the one pushing the team to build AI into everything they ship. Along the way, TekRevol made the Inc. 5000 list with 829% growth. His writing has appeared in Inc. and Entrepreneur, and he’s spoken at keynote and TEDx events. He studied Computer Engineering at SSUET and later earned an MBA in MIS. When he’s not thinking about tech, he’s playing padel.

    Rate this Article

    0 rating, average : 0.0 out of 5

    Let's Connect With Our Experts

    Get valuable consultation form our professionals to discuss your projects. We are here to help you with all of your queries.

    Revolutionize Your Business

    Collaborate with us and become a trendsetter through our innovative approach.

    5.0
    Goodfirms
    4.8
    Rightfirms
    4.8
    Clutch

    Get in Touch Now!

    By submitting this form, you agree to our Privacy Policy

    Unlock Tech Success: Join the TekRevol Newsletter

    Discover the secrets to staying ahead in the tech industry with our monthly newsletter. Don't miss out on expert tips, insightful articles, and game-changing trends. Subscribe today!

    X

    Do you like what you read?

    Get the Latest Updates

    Share Your Feedback