Strategy Bridge

Systems Engineering Glossary

Term Main definition
Product Baseline

Approved documentation and configuration describing the functional and physical characteristics of a Configuration Item as delivered.

Product Breakdown Structure (PBS)

The hardware and software entities of the program/ project decomposed and expressed in a hierarchical structure.


A defined and planned effort to achieve a common objective across a number of projects.


An activity with a defined beginning and end that consumes resources and produces a product or service.

Proof of Concept

A demonstration that an idea or technology is feasible for use in developing a solution.


The verification process to prove that an entity meets environment requirements, usually with a defined risk margin.

Qualification Test

A test of a representative production unit to demonstrate that the design withstands defined environmental qualifications.

Quality Assurance (QA)

A systematic and independent process to assure a system is produced and delivered in accordance with applicable policy, processes, procedures, and its performance specifications.


A software Configuration Management action that groups items and enters them into the process to deliver them to another phase in the development cycle or to users.

Release Managements

A software process to plan and manage the contents of a release – what is contained, the version numbers, the status of the contents, and any open Problem Reports.


The ability of a system (and its components) to perform its function without failure or degradation within a specified period of time under stated conditions.

Request For Change (RFC)

The Configuration Management process to initiate changes to formally controlled Configuration Items.


A statement that identifies a system need that is unambiguous, clear, unique, consistent, and verifiable.


The process of understanding, documenting, approving, and managing the parent/ child relationships of system requirements during system decomposition.

Requirements Allocation

The process of deriving, decomposing, and assigning the requirement to lower-level architecture elements in the evolving design architecture.

Requirements Analysis

The process of analyzing requirements statements to determine if they have the necessary properties for effective management and implementation.

Requirements Development

The process of generating, analyzing, allocating, and tracing requirement statements.

Requirements Development Plan

A document that describes the scope, resources, constraints, products, and process tailoring of a requirements development activity.

Requirements Generation

The process of translating needs, constraints, and higher order requirements into specifications.

Requirements Verification Traceability Matrix (RVTM)

A document showing the source and parent/ child relationships among requirements and how they cascade from the system level to the lowest level of the system architecture.  The verification method, result, and resolution for each requirement are included.