Systems Engineering Glossary
An asset, such as people, equipment, facilities, technology, and budget used to perform project tasks.
|Risk - Informed Decision Making Process (RIDM)||
A process to develop decision alternatives with an explicit consideration of the risk associated with those alternatives.
The examination of the probability that a given risk will occur and the seriousness of the impact.
The process of identifying all system (product) and programmatic risks.
A systematic, continuous process that identifies, assess, plans, mitigates, tracks, controls, and documents project risks throughout the life cycle.
|Risk Management Framework (RMF)||
The process for applying cybersecurity to systems throughout the product life cycle.
|Risk Mitigation Plan (RMP)||
A document that details anticipated risks and identifies strategies to ameliorate those threats or hazards that can adversely affect the project.
A time-based plan of milestones/ activities for performing work or achieving an objective.
A group of functionally related items in the system hierarchy.
|Service Component Architecture (SCA)||
A developer framework for building Service-Based Architecture services. It provides both multi-protocol and multi-language support.
|Service-Based Architecture (SBA)||
The principles, structures, and methodologies for linking together loosely coupled systems/ services, typically through shared data or common logic/ direction.
|Service-Oriented Architecture (SOA)||
Principles, structures, and methodologies for linking together loosely coupled systems/ services, typically through shared data or common logic/ direction. Also known as Service – Based Architecture.
|Soft Systems Methodology (SSM)|
|Software Architecture Document (SAD)||
Documentation of a project’s architectural overview, architecture specifications, and design rationale.
The application of a systematic approach to the development, operation, and maintenance of software.
|Software Requirements Specification (SRS)||
An artifact of he definition process that contains all of the requirements for a software product. It is the starting point for software architecting.