Systems Engineering Glossary
Approved documentation and configuration describing the functional and physical characteristics of a Configuration Item as delivered.
|Product Breakdown Structure (PBS)|
A defined and planned effort to achieve a common objective across a number of projects.
|Proof of Concept||
A demonstration that an idea or technology is feasible for use in developing a solution.
|Quality Assurance (QA)|
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.
|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 analyzing requirements statements to determine if they have the necessary properties for effective management and implementation.
The process of generating, analyzing, allocating, and tracing requirement statements.
|Requirements Development Plan|
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.