System Requirement Specification

A System Requirement Specification is a requirement specification that defines specific capabilities, conditions, or constraints needed for a system to meet stakeholder needs.

AKA: Technical Requirement, Formal Requirement.
Context:
- It can transform stakeholder needs into technical specifications through requirement engineering.
- It can specify system behaviors through system functional requirements.
- It can define system quality through system non-functional requirements.
- It can support system verification through system requirement testing.
- ...
- It can often guide system architecture through system constraints.
- It can often enable system integration through system interface requirements.
- It can often enhance system maintainability through system documentation requirements.
- ...
- It can range from being a High Level System Requirement to being a Low Level System Requirement, depending on its abstraction level.
- It can range from being a Mandatory System Requirement to being an Optional System Requirement, depending on its implementation necessity.
- It can range from being a Business System Requirement to being a Technical System Requirement, depending on its requirement focus.
- ...
- It can have requirement verifiability through system testing methods.
- It can have requirement traceability through requirement management processes.
- It can have requirement measurability through system performance metrics.
- ...
Examples:
- Computing System Requirements, such as:
  - Computing System Performance Requirement for processing efficiency.
  - Computing System Security Requirement for data protection.
- Mechanical System Requirements, such as:
  - Mechanical System Load Requirement for structural integrity.
  - Mechanical System Safety Requirement for operational safety.
- Electrical System Requirements, such as:
  - Electrical System Power Requirement for energy consumption.
  - Electrical System Protection Requirement for circuit safety.
- ...
Counter-Examples:
- a Design Decision, which implements rather than specifies capabilities.
- a User Preference, which suggests rather than requires system features.
- a System Description, which documents rather than prescribes system behaviors.
See: System Specification, Requirements Engineering, System Development Process, Requirement Management, System Architecture, System Integration, System Testing, System Documentation.