The SRS (Software Requirements Specification) block follows IEEE 830 patterns to document complete software requirements. It separates functional requirements from non-functional requirements (NFRs), documents external interfaces, and captures system constraints.
When to Use
Block Properties
| Property | Required | Description |
|---|
| Title | Yes | SRS document title |
| Version | No | Document version number |
| Status | No | Draft, In Review, Approved, or Obsolete |
| Author | No | Document author |
| Date | No | Creation or last update date |
| Purpose | No | Why this document exists |
| Scope | No | System boundaries and capabilities |
| Definitions | No | Terms and definitions |
| Functional Requirements | No | What the system does |
| Non-Functional Requirements | No | Quality attributes |
| External Interfaces | No | System interfaces |
| Constraints | No | Design and implementation constraints |
| Assumptions | No | Conditions assumed true |
Functional Requirement Properties
| Property | Required | Description |
|---|
| ID | Yes | Unique identifier (SRS-FR-###) |
| Description | Yes | The requirement statement |
| Priority | No | High, Medium, or Low |
| Source | No | Where the requirement originated |
Non-Functional Requirement Properties
| Property | Required | Description |
|---|
| ID | Yes | Unique identifier (SRS-NFR-###) |
| Category | Yes | Performance, Security, Reliability, etc. |
| Description | Yes | The requirement statement |
| Metric | No | What is measured |
| Target | No | The measurable target |
NFR Categories
Example: Payment Processing System SRS
A complete SRS for a payment processing system.
Best Practices
| Practice | Description |
|---|
| Separate FR and NFR | Separate functional from non-functional requirements clearly |
| Measurable NFRs | Make NFRs measurable with specific metrics and targets |
| Document Sources | Document the source of each requirement for traceability |
| Interface Documentation | Include all external system interfaces |
| Consistent ID Schemes | Use consistent ID schemes across requirement types |
| Team Reviews | Review NFRs with operations and security teams |
| SLA Alignment | Align NFR targets with business SLAs |
