The physical architecture is the physical layout of a system and its components in a schema. It refers to some representation of the structure or organization of the physical elements of the system. The physical architecture should be part of the Allocated and Product Baselines. Definition: A physical architecture is an arrangement of physical elements […]
An Operational Requirements Document (ORD) was replaced by the Capability Development Document (CDD). The ORD described the overall requirements for one system, how it interacts with other systems, and a system’s performance goals. An ORD is generally more detailed than a Concept of Operations (CONOPS). Older programs will have an ORD. The Mission Needs Statement
A requirement is an attribute of a product, service, or system necessary to produce an outcome(s) that satisfies the needs of a person, group, or organization. Operational Requirements are capabilities, performance measurement (Measures of Effectiveness, Measures of Performance, Measures of Suitability & Technical Performance Measurements), and processes needed to address mission area deficiencies, evolving threats,
Modular Open Systems Approach (MOSA) is an integrated business and technical strategy for the assessment and implementation of open systems in the DoD. An open system is a system that employs modular design tenets, uses widely supported and consensus-based standards for its key Interfaces, and is subject to Validation and Verification, including Test and Evaluation,
An Open-Standard System Architecture (OSSA) is an architecture development approach that utilizes open standards to reduce the cost/risk of ownership of weapons systems, delay system obsolescence, and allow the fielding of capability more quickly. An open systems approach reduces weapon system cost by facilitating the use of widely accepted standard products from multiple suppliers in
Modeling and Simulation (M&S) is the use of models, including emulators, prototypes, simulators, and stimulators, either statically or over time, to develop data as a basis for making managerial or technical decisions. The terms “modeling” and “simulation” are often used interchangeably. [2] M&S is a tool used in systems engineering to gather information to make
Measures of Effectiveness (MOE) are measures designed to correspond to the accomplishment of mission objectives and the achievement of desired results. They quantify the results to be obtained by a system and may be expressed as probabilities that the system will perform as required. The Capability Based Assessment (CBA) defines the MOE’s and articulates them
Interfaces are the functional and/or the physical interface between two components with a system. The components can be internal or external to the system. It’s key to understand these interfaces in systems engineering to make sure systems components work properly with each other. See Interface Management Interface definition and control Interface definition and control are
Interface Management identifies, develops, and maintains the external and internal interfaces necessary for system operation. It supports control measures (Configuration Management) to ensure that all internal and external interface requirement changes are properly documented in accordance with the configuration management plan and communicated to all affected configuration items. Definition: Interface management includes the activities of defining,
A Functional Architecture is an architectural model that identifies system function and their interactions. It defines how the functions will operate together to perform the system mission(s). Functional architecture can be used as a framework to arrange information, processes, or other solution modules in an enterprise system. Definition: A functional architecture is a set of functions
The Initial Capabilities Document (ICD) documents the need for a materiel approach or an approach that is a combination of materiel and non-materiel, to a specific capability gap. A capability gap derived from an initial analysis of materiel approaches executed by the operational user and, as required, an independent analysis of materiel alternatives. It defines
A Configuration Baseline is the performance documentation and standards that comprise a product at a certain moment during its development. It is a set of documented specifications for a configuration item within a system that has been formally examined and agreed upon at a given time and can only be amended via change control procedures.
Note: The CPD has been eliminated from the JCIDS process. The Capability Production Document (CPD) captures the information necessary to support the production, testing, and deployment of an affordable and supportable increment within an acquisition strategy. The CPD identifies, in threshold/objective format, the specific attributes that contribute most significantly to the desired operational capability. The
A Concept of Operations (CONOPS) is a document that describes a proposed system concept and how that concept would be operated in an intended environment. The user community develops the CONOPS to communicate the vision for the operational system to the acquisition and developer community with quantitative and qualitative system metrics. A CONOPS can also
The Capability Development Document (CDD) specifies the operational requirements for the system that will deliver the capability that meets the operational performance criteria specified in the Initial Capabilities Document (ICD). It outlines militarily useful increments of capability with its own set of attributes and development performance values (i.e., thresholds and objectives) in terms of Key
Design Synthesis is the process of taking the functional architecture developed in the Functional Analysis and Allocation step and decomposing those functions into a Physical Architecture (a set of product, system, and/or software elements) that satisfy system required functions. SMC Systems Engineering Handbook, Figure 17 Synthesis is the process whereby the Functional Architectures and their
System Analysis and Control manages and controls the overall Systems Engineering Process. This activity identifies the work to be performed and develops the schedules and costs estimates for the effort. It coordinates all activities and assures that all are operating from the same set of requirements, agreements, and design iteration. It’s the center for configuration
Functional Analysis and Allocation is a top-down process of translating system-level requirements into detailed functional and performance design criteria. The result of the process is a defined Functional Architecture with allocated system requirements that are traceable to each system function. SMC Systems Engineering Handbook – Figure15: Functional Analysis and Allocation The Functional Analysis and Allocation
Requirements Analysis (Step 1) is one of the first activities of the System Engineering Process and functions somewhat as an interface between the internal activities and the external sources providing inputs to the process. It examines, evaluates, and translates the external inputs into a set of functional and performance requirements that are the basis for
The Verification Process confirms that Design Synthesis has resulted in a physical architecture that satisfies the system requirements. Throughout a system’s life cycle, design solutions at all levels of the physical architecture are verified to meet specifications. Definition: Verification is a test of a system to prove that it meets all its specified requirements at a
The Systems Engineering Process is a comprehensive, iterative, and recursive problem-solving process, applied sequentially top-down by integrated teams. It transforms needs and requirements into a set of system product and process descriptions, generates information for decision-makers, and provides input for the next level of development. The process is applied sequentially, one level at a time,
The Systems Engineering Plan (SEP) is a living document that details the execution, management, and control of the technical aspects of an acquisition program from conception to disposal. The SEP outlines how the systems engineering process is applied and tailored to meet objectives for each acquisition phase. The SEP captures a program’s current and evolving
The table below represents activities and tasks that systems engineering must be aware of, participate in or be responsible for. The table is a good point of reference for planning purposes and should be addressed in the Systems Engineering Plan (SEP). Activity Systems Engineering Responsibility Awareness Participant Write Review Acquisition Strategy X
Systems Engineering (SE) is the engineering discipline that focuses on integrating all the key elements of a system into one overall system and managing it throughout its lifecycle from cradle to grave. It focuses on the overall development process of a system that is based on established processes, documented needs, and traceable communications or interaction
A Functional Configuration Audit (FCA) examines the functional characteristics of the configured product. It verifies that the product has met the requirements specified in its Functional Baseline documentation approved at the Preliminary Design Review (PDR) and Critical Design Review (CDR). It has to do more with systems engineering and program management than official auditing. The
