Software requirements specification (SRS) generator
An SRS lists every requirement of a software product with an ID, a priority and a way to check it. This generator turns your features, quality needs and constraints into a Markdown SRS laid out after the section titles of ISO/IEC/IEEE 29148, with acceptance criteria stubs and a goal-to-requirement traceability table.
Updated
Your SRS draft
6 functional, 8 non-functional
FR-1 to FR-6 · 1 deferred · 1326 words
- Pass · Every goal has a requirement3 of 3 covered
- Fail · Every requirement traces to a goalnot linked: FR-6
- Pass · Performance, security and availability statedall three present
- Pass · Priorities are spreadmix of Must, Should and Could
Software Requirements Specification (Markdown)
# PhysioBook: Software Requirements Specification | Item | Value | | --- | --- | | Document status | Draft 0.1 | | Date | [fill in] | | Owner | [fill in] | | Approved by | [fill in] | > Outline follows the section titles of ISO/IEC/IEEE 29148:2018, clause 9.6 (SRS content), tailored. Clause numbers are shown in brackets. This is a working draft, not a claim of conformance to the standard. ## 1. Introduction ### 1.1 Purpose [9.6.2] This document specifies the software requirements for PhysioBook. It is written for the product owner, the development team and whoever tests the product. ### 1.2 Scope [9.6.3] Lets patients book and pay for physiotherapy sessions at independent clinics, and gives clinics one calendar for every therapist. Out of scope for this specification: - Insurance claims - Therapist payroll ### 1.3 Definitions, references and acronyms [9.2.3 to 9.2.5] _Add domain terms, acronyms and referenced documents here._ ## 2. Overall description ### 2.1 Product perspective [9.6.4] PhysioBook is a web application and iOS and Android apps. **Interfaces with services [9.6.4.9]** - EI-1: Razorpay for payments - EI-2: An SMS or WhatsApp provider for reminders - EI-3: Google Calendar sync for therapists ### 2.2 Product functions [9.6.5] Summary of what the product does, in priority order: - FR-1 (Must): Patient sign-up with phone OTP - FR-2 (Must): Book a slot with a chosen therapist - FR-3 (Must): Pay online when booking - FR-4 (Must): Clinic calendar showing every therapist's slots - FR-5 (Should): SMS or WhatsApp reminders before a session - FR-6 (Could): Session notes and exercise plans ### 2.3 User characteristics [9.6.6] - Patient: books and pays for sessions - Therapist: manages their day and session notes - Clinic admin: sees bookings, payouts and reports ### 2.4 Limitations [9.6.7] - CON-1: First release live within 4 months - CON-2: Hosted in an India region ### 2.5 Assumptions and dependencies [9.6.8] - Clinics supply their therapist list and timetables before launch ### 2.6 Apportioning of requirements [9.6.9] Requirements deferred beyond the first release: | ID | Deferred requirement | Priority | | --- | --- | --- | | DEF-1 | Video consultations | Won't (this release) | ## 3. Specified requirements [9.6.10] Requirement statements use "shall". Priority follows MoSCoW: Must, Should, Could. Rephrase each statement until it is singular, testable and unambiguous. ### 3.1 External interfaces [9.6.11] | ID | Interface | Requirement | | --- | --- | --- | | EI-1 | Razorpay for payments | The system shall exchange data with razorpay for payments. [Define the data, direction and failure behaviour.] | | EI-2 | An SMS or WhatsApp provider for reminders | The system shall exchange data with an SMS or WhatsApp provider for reminders. [Define the data, direction and failure behaviour.] | | EI-3 | Google Calendar sync for therapists | The system shall exchange data with google Calendar sync for therapists. [Define the data, direction and failure behaviour.] | ### 3.2 Functional requirements [9.6.12] | ID | Requirement | Priority | | --- | --- | --- | | FR-1 | The system shall support: patient sign-up with phone OTP. | Must | | FR-2 | The system shall support: book a slot with a chosen therapist. | Must | | FR-3 | The system shall support: pay online when booking. | Must | | FR-4 | The system shall support: clinic calendar showing every therapist's slots. | Must | | FR-5 | The system shall support: SMS or WhatsApp reminders before a session. | Should | | FR-6 | The system shall support: session notes and exercise plans. | Could | ### 3.3 Usability requirements [9.6.13] | ID | Requirement | | --- | --- | | NFR-8 | The system shall meet this usability target: a first-time patient can book a session in under 3 minutes without help. | ### 3.4 Performance requirements [9.6.14] | ID | Requirement | | --- | --- | | NFR-1 | The system shall meet this performance target: booking pages respond in under 2 seconds for 95% of requests at 500 concurrent users. | ### 3.5 Logical database requirements [9.6.15] _To be defined with the data model during design. List the main entities and retention rules here._ ### 3.6 Design constraints [9.6.16] - CON-1: First release live within 4 months - CON-2: Hosted in an India region ### 3.7 Standards compliance [9.6.17] | ID | Requirement | | --- | --- | | NFR-6 | The system shall comply with: Personal data handled under India's Digital Personal Data Protection Act, 2023. | | NFR-7 | The system shall comply with: Payments through a PCI DSS compliant gateway. | ### 3.8 Software system attributes [9.6.18] **Security** | ID | Requirement | | --- | --- | | NFR-2 | The system shall meet this security requirement: all traffic over TLS. | | NFR-3 | The system shall meet this security requirement: role-based access so therapists see only their own patients. | | NFR-4 | The system shall meet this security requirement: card details never stored by the system. | **Availability** | ID | Requirement | | --- | --- | | NFR-5 | The system shall be available at least 99.5% of each calendar month, which allows about 3 h 36 min of downtime in a 30-day month. | ## 4. Verification [9.6.19] Acceptance criteria stubs. Replace each placeholder with a concrete, observable check before sign-off. | ID | Acceptance criteria stub | | --- | --- | | AC-FR-1 | Given [starting state], when [action], then [observable result] for: patient sign-up with phone OTP. | | AC-FR-2 | Given [starting state], when [action], then [observable result] for: book a slot with a chosen therapist. | | AC-FR-3 | Given [starting state], when [action], then [observable result] for: pay online when booking. | | AC-FR-4 | Given [starting state], when [action], then [observable result] for: clinic calendar showing every therapist's slots. | | AC-FR-5 | Given [starting state], when [action], then [observable result] for: SMS or WhatsApp reminders before a session. | | AC-FR-6 | Given [starting state], when [action], then [observable result] for: session notes and exercise plans. | | AC-NFR-1 | Pass when, measured by [method and tool] on [environment]: Booking pages respond in under 2 seconds for 95% of requests at 500 concurrent users. | | AC-NFR-2 | Pass when, measured by [method and tool] on [environment]: All traffic over TLS. | | AC-NFR-3 | Pass when, measured by [method and tool] on [environment]: Role-based access so therapists see only their own patients. | | AC-NFR-4 | Pass when, measured by [method and tool] on [environment]: Card details never stored by the system. | | AC-NFR-5 | Pass when, measured by [method and tool] on [environment]: availability of at least 99.5% per calendar month. | | AC-NFR-6 | Pass when, measured by [method and tool] on [environment]: Personal data handled under India's Digital Personal Data Protection Act, 2023. | | AC-NFR-7 | Pass when, measured by [method and tool] on [environment]: Payments through a PCI DSS compliant gateway. | | AC-NFR-8 | Pass when, measured by [method and tool] on [environment]: A first-time patient can book a session in under 3 minutes without help. | ### 4.1 Traceability Each business goal should map to at least one requirement, and each requirement to at least one acceptance check. | Goal | Functional requirements | Acceptance checks | Status | | --- | --- | --- | --- | | G1: Cut double-bookings at partner clinics to near zero | FR-2, FR-4 | AC-FR-2, AC-FR-4 | Open | | G2: Let patients pay online when they book | FR-1, FR-3 | AC-FR-1, AC-FR-3 | Open | | G3: Reduce no-shows with reminders | FR-5 | AC-FR-5 | Open | Requirements not linked to a goal: FR-6. ## 5. Supporting information [9.6.20] _Attach prototypes, flow diagrams, research and decisions that explain the requirements above._
- The requirement sentences are scaffolding built from your lines. Read each one and rewrite it as a single testable statement.
Discovery Sprint: ₹1,50,000 / $1,600
An SRS draft lists what you want. A Discovery Sprint turns it into a prioritised scope, user flows including unhappy paths, a clickable prototype, the architecture, a risk list and a fixed-price quote in milestones.
What is in a software requirements specification?
An SRS is the document a development team, a tester and the person paying all read to agree what the software must do. ISO/IEC/IEEE 29148 describes the content of an SRS in clause 9.6, from an overview, purpose and scope, through product perspective, product functions, user characteristics and limitations, to the specified requirements: external interfaces, functions, usability, performance, logical database, design constraints, standards compliance and software system attributes, then verification and supporting information.
This tool follows those section titles as a tailored outline and fills them from your answers. Features become functional requirements (FR-1, FR-2) ordered by MoSCoW priority. Performance, security, availability, compliance and usability needs become non-functional requirements (NFR-1, NFR-2). Integrations become external interfaces, constraints become design constraints, and Won't-have features are listed as deferred rather than numbered as requirements.
Each requirement gets an acceptance criteria stub, and tags such as [G1] link features to your business goals so the traceability table can show which goals have no requirement yet. That gap check is the part a one-page brief cannot do.
An SRS is longer and more exact than a project brief. A brief says what the product is for; an SRS says what every requirement is, how it is identified and how it will be checked. The standard allows tailoring, so treat the output as a draft outline, not as a conformance claim.
Not ready for a full specification? Start with the one-page app project brief generator.
How do the form fields map to the SRS sections?
| You enter | Becomes | Clause | ID |
|---|---|---|---|
| Product name and one-line purpose | Purpose and scope | 9.6.2, 9.6.3 | none |
| Platforms and integrations | Product perspective, external interfaces | 9.6.4, 9.6.11 | EI-n |
| Users and roles | User characteristics | 9.6.6 | none |
| Features with Must/Should/Could | Product functions, functional requirements | 9.6.5, 9.6.12 | FR-n |
| Won't-have features | Apportioning of requirements | 9.6.9 | DEF-n |
| Performance, usability | Performance and usability requirements | 9.6.14, 9.6.13 | NFR-n |
| Security, availability | Software system attributes | 9.6.18 | NFR-n |
| Compliance and legal | Standards compliance | 9.6.17 | NFR-n |
| Constraints and assumptions | Design constraints, limitations, assumptions | 9.6.16, 9.6.7, 9.6.8 | CON-n |
| Goals and [G1] tags | Traceability table | 9.6.19 (verification) | G1, G2 ... |
How to write a software requirements specification
- 1Describe the product and its usersA name, one or two sentences on what it does, the platforms, and one line per role.
- 2List business goals, then features with a priorityPut a goal number in square brackets after each feature, such as [G2]. Mark each Must, Should, Could or Won't.
- 3Add the quality needsPerformance targets with numbers, security rules, an availability percentage, legal obligations and usability targets. Vague words like fast or secure do not give a tester anything to check.
- 4Generate, then rewrite and reviewCopy or download the Markdown, rewrite each requirement as one testable statement, fill in the acceptance stubs and review the traceability gaps with whoever will build and test it.
Frequently asked questions
What is the difference between an SRS and an app project brief?
What does ISO/IEC/IEEE 29148 say an SRS contains?
How do I write a requirement that can be tested?
What do Must, Should, Could and Won't mean?
How much downtime does 99.9 percent availability allow?
Why do some of my goals say Gap in the traceability table?
Does this tool store my specification?
Sources
Building a SaaS product?
We design, build, and scale SaaS platforms — from auth and billing to dashboards and APIs.
Built by CountryDevs · No signup · No ads · We count visits, never what you enter