Artifact: System Requirements Specification |
 |
The System Requirements Specification is a composite of the Use-Case Model and the Supplementary Specifications. Its purpose is to provide a formal delivery vehicle for these artifacts, in document form. If the project does not produce these artifacts, then the System Requirements Specification provides equivalent content. |
Domain:
Systems Engineering
Work Product Kinds:
Specification
Extends:
Software Requirements Specification |
|
Purpose
The purpose of the System Requirements Specification is to provide a single formal delivery vehicle
(if required) for the Use-Case Model and Supplementary Specifications artifacts, in document form.
If the project does not produce these artifacts, then the System Requirements Specification provides
equivalent content.
|
Relationships
Roles | Responsible:
| Modified By:
|
Tasks | Input To:
| Output From:
|
Description
Brief Outline |
The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion
of the system.
Many different arrangements of an SRS are possible. Review the tailoring section for additional guidance.
|
Illustrations
Key Considerations
Refer to the Requirements Management Plan to determine the correct location and
organization of the requirements. For example, it may be desired to have a separate SRS to describe the complete software
requirements for each feature in a particular release of the product. |
Tailoring
Representation Options | UML Representation:
Tailoring of this artifact is driven by the same considerations that apply to the Use-Case Model and Supplementary
Specifications. If it is simply a composite artifact, then the tailoring is subsumed in those artifacts. If the System
Requirements Specification is produced in its own right, then its tailoring depends on the nature of the system under
development and the formality ("ceremony") attending the development process. For example (using the template as a
reference):
-
There must always be a capability section which describes the functional requirements (and associated performance
demands) for the system.
-
The external interface requirements section depends on the context for the system. For example, does it have to
interface with other external systems or hardware?
-
Other non-functional requirements sections must be retained as needed. For example, if the environment in which the
system must operate is entirely benign, the section on system environment requirements is probably not needed.
|
More Information
Checklists |
|
Concepts |
|
Guidelines |
|
© Copyright IBM Corp. 1987, 2006. All Rights Reserved.
|
| |
|