Software Requirement Specification (SRS)

Updated 22 Jul 2026

•
def
- •
  a formal, comprehensive document containing exact details of system functionality
- •
  defines both functional and non-functional requirements
- •
  the official statement of what is required of the system developers
- •
  the primary output of the Requirements Specification process
•
note
- •
  is NOT a design document — specifies WHAT the system should do, not HOW it should do it
•
uses
- •
  for developers — absolute guide for coding and implementation
- •
  for QA — main basis for designing test scenarios and acceptance criteria
- •
  for management — prevents scope creep (pembengkakan ruang lingkup proyek)
•
document structure (IEEE Std 830-1998)
- •
  Introduction
  - •
    purpose of the document
  - •
    scope of the system
  - •
    definitions, acronyms, and abbreviations
  - •
    references
  - •
    document summary
- •
  Overall Description
  - •
    product perspective
  - •
    main functions
  - •
    user characteristics
  - •
    general constraints
  - •
    assumptions and dependencies
- •
  Functional Requirements
  - •
    list of system functions with use case scenarios
- •
  Non-Functional Requirements (Kebutuhan Non-Fungsional)
  - •
    performance, security, usability, reliability, etc.
- •
  Appendices and Additional References
  - •
    external regulations, traceability matrix, etc.

broader SRS document structure (Sommerville)

Section	Description
Preface	Expected readership, version history, rationale for new versions
Introduction	System need, brief function summary, how it fits business objectives
Glossary	Technical terms defined; no assumption of reader expertise
User requirements definition	Services provided for the user; non-functional requirements; natural language or diagrams
System architecture	High-level overview of anticipated system architecture; reused components highlighted
System requirements specification	Functional and non-functional requirements in detail; interfaces to other systems
System models	Graphical models (object, data-flow, semantic data, state machine models)
System evolution	Fundamental assumptions and anticipated changes due to hardware, user needs, etc.
Appendices	Hardware and database descriptions; min/optimal configurations
Index	Alphabetic, diagram, and function indexes

Linked references 12