Work Product (Artifact): Subsystem Requirements Specification

This artifact represents the system and derived requiremetns allocated to a subsystem or to an engineering discipline within the system or subsystem scope.

Purpose

The purpose of the work product is to hold the subsystem or engineering discipline-specific requirements in an accessible and controllable fashion.

Relationships

Roles	Responsible: Architect Control Engineer Electrical Engineer Mechanical Engineer Miscellaneous Engineer System Architect	Modified By: Control Engineer Developer Electrical Engineer Mechanical Engineer Miscellaneous Engineer System Architect
Output From	Allocate Requirements to Engineering Disciplines Gather Subsystem Specification Data

Main Description

Properties

Optional
Planned

Illustrations

Templates	System Requirements Specification

Tailoring

Impact of not having	The impact of omitting this work product is the increased likelihood of requirements being missed or ignored because the could not be easily found.
Reasons for not needing	If a system is sufficiently simple, it may be possible to add an "allocated to" field to clarify the requirements allocations.
Representation Options	The system requirements specification may be represented as a document created in a word processing tool, as a report from a database or as a report from a commercial requirements management tool.

More Information

Checklists	Requirements Specification Stakeholder Requirement