Appendix B

IDEF0 Model of the

Engineering of a System

The Engineering Design of Systems: Models and Methods, Second Edition. By Dennis M. Buede
Copyright r 2009 John Wiley & Sons, Inc.

455
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
456

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering None
RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Stakeholders' Needs

Inputs of Stakeholders
APPENDIX B

Perform
Stakeholders' System Design & Qualification
Integration System Design
Activities
A-11
Documentation Documentation

Perform
Systems
Engineering
A-0
Design & Test
Configuration
Items (CIs)
Operational
System Design &
A-12 Qualify the
Materials Qualification
and Parts "Built-to" System
Configuration A-13
Items & Pre-
Production Qualification
Prototypes System
Stakeholders
Note 1: This model only addresses Qualification
the operational phase of the system.
Discipline
Consider SE teams for other phases SE Team Engineers System Discipline
(e.g., manufacturing) to be part of Engineers
the Stakeholders.
NODE: A-1 TITLE: External Systems Diagram for the SE Team NUMBER: P. 1
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a System REV: DRAFT
Engineering Top
RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Inputs of Stakeholders

System Design &

Integration
Documentation

"Built-to"
Configuration
Perform
Items & Pre-
Systems Operational
Production Engineering System
Prototypes

A0

Qualification
System Design
Qualification Documentation
System

PURPOSE: To describe the systems engineering process

VIEWPOINT: The Systems Engineering Team

APPENDIX B

NODE: A-0 TITLE: Perform Systems Engineering NUMBER: P. 2

457
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
458

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Inputs of Stakeholders
APPENDIX B

System Design
Phase
Documentation System Design &
Perform Integration
Qualification Documentation
Design
System Design
Activities
Documentation Qualification
A1
System Design
Documentation
Qualification Procedures,
Activities, & Models System
Integration
"Built-to" Phase
Configuration Perform Documentation
Items & Pre- Qualification
& Integration Operational
Production System
Activities
Prototypes
A2

Design
Changes
Qualification
System

NODE: A0 TITLE: NUMBER: P. 3

Perform Systems Engineering
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a System REV: DRAFT
Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Inputs of Stakeholders

Qualification
Perform
System Design
Design System- Originating System's
Level Subsystem Stakeholders Qualification Documentation
Changes System
&& System
Design Design Requirements System
Requirements, Requirements Documentation
Activities Documents Component & CI
Boundaries, Documents
Qualification System
Missions, Subsystem
Subsystem- Documentation
Objectives Qualification
A11 Level
& Constraints System
Subsystem Documentation
Documentation
Design System Design
Changes Perform Phase
Subsystem- Documentation
Level
Lower Component Design
Design Requirements,
Layer
Activities Boundaries, Missions,
Changes to
Require- Objectives
ments A12 & Constraints
Component-Level
Perform Documentation
Subsystem Component
Changes to Component-
Changes Design
to System Subsystem Changes Level
Requirements Requirements Design
Activities Component
A13
Changes
to System
APPENDIX B

Requirements

NODE: A1 TITLE: Perform Design Activities NUMBER: P. 4

459
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
460

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
Inputs of Stakeholders Stakeholders
& System
Requirements Stakeholders
Design Define & System
Changes
APPENDIX B

System- Stakeholders & System System-level Requirements

Lower Level Requirements, Objectives Physical Documents
Design Hierarchy, Boundary & Architecture
Layer
Problem Qualification System Requirements
Changes to
Require- System-level
A111 Risk Analysis,
ments Develop Functional
System Architecture System Design
Functional Document,
Architecture Allocated
System-level Design Architecture,
Operational A112 Candidate
System Physical System Interface
Concept
Physical Architectures Control Document
Candidate Architecture Subsystem
Generic Design
Physical A113 Develop
Requirements,
Architectures System
Allocated
Boundaries,
Architecture Allocated System Missions,
Architecture Requirements Objectives
A114 & Constraints
Physical
Architecture Architecture Develop
Changes Changes Interface
Architecture
A115

Functional Interface
Interface
Architecture Architecture
Architecture System's
Changes Changes
Requirement Develop Qualification
Changes Qualification System
System Documentation
A116
Qualification
System
Allocated Architecture, Changes
Changes to Requirements
NODE: A11 TITLE: Perform System-Level Desi gn Activities NUMBER: P. 5
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a System REV: DRAFT
Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
Inputs of Stakeholders
Approval or
Stakeholders' Stakeholders' Stakeholders' Qualification
Stakeholders' Disapproval
Jurisdiction Objectives Constraints Constraints
Uses

Requirements System-level
Issues
Develop Operational
Design Concept
Operational Engineers'
Changes Requirements
Concept System
Boundary Issues
A1111
Define
System Stakeholders & System
Qualification Qualification Requirements,
Boundary
System Issues System Objectives Hierarchy,
with an Requirements Boundary & Qualification
External Objectives System Requirements
Systems Hierarchy
Define
A1112 Qualification
System Stakeholders'
Requirements Requirements
Develop Issues
System A1116
Objectives Proven Requirements
System
Hierarchy Boundary & Infeasibility
A1113 Objectives
Hierarchy Obtain
Approval of
Develop, Requirements Stakeholders
Lower Analyze and Documentation & System
Layer Ensure
Refine Requirements
Changes to Requirements A1117
Require- Requirements Feasibility
ments A1114 A1115
APPENDIX B

Allocated Architecture, Stakeholders & System Proven Requirements

Changes to Requirements Requirements, Feasibility

NODE: A111 TITLE: Define System-Level Design Problem NUMBER: P. 6

461
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
462

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Stakeholders & System

Requirements,
Objectives Hierarchy,
Boundary & Qualification
APPENDIX B

System Requirements

Functional
Create Simple Simple
Boundary Inputs,
Requirements, Boundary Inputs,
Functionalities Functionalities Controls, and
System-level Inputs, and Controls, and Input/Output
for Operational Outputs Outputs Outputs and Requirements
Operational
Concept Objectives
Concept
Draft &
A1121 Evaluate Architecture
Functional Issues
Candidate
Generic
Model
Physical A1122 Draft Data
Model for Data
Architectures
Functional Model
Draft
Functional
Model
Model A1123
Functional
and Data
Complete Models
Functional
and Data
Functional Models
Architecture
Changes A1124 Trace
System-level
Input/Output
Functional
Requirements Architecture
to Functions
and Items
A1125

NODE: A112 TITLE: Develop System Functional Architecture NUMBER: P. 7

USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a System REV: DRAFT
Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
System-level Stakeholders & System
Functional Requirements,
Architecture Objectives Hierarchy,
Boundary & Qualification
System Requirements

System-level Brainstorm and Candidate

Operational Select a Generic Generic
Concept Physical Physical
Architecture Architectures

A1131
Generate a
Generic Morphological Box
Physical for Alternate
Architecture
Physical Instantiated Physical
Architecture Architecture
Changes
A1132
System-level
Physical
Morphological Architecture
Box
Select
Alternate
Instantiated
Physical Candidate
Architecture Physical
Architectures
A1133
APPENDIX B

NODE: A113 TITLE: Design System Physical Architecture NUMBER: P. 8

463
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
464

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
Stakeholders & System-level
System Requirements, Functional
Objectives Hierarchy, Architecture
Boundary & Qualification
APPENDIX B

System Requirements

Discrepancies in the
Specifications,
Interface Control,
Suggested and Acceptance
Allocate Test Plan
Revisions
Functions &
Candidate System-wide
Document Risk Analysis,
Physical Requirements System Design
Architectures to Physical Alternative Architectures
System-level Document,
Subsystems Define & & Obtain
Allocated Allocated
Analyze Architectures
Approval
A1141 Architecture,
Functional System Interface
Function to Activation & Control Document
Subsystem Control Analysis A1144
System-level Allocation
Structure Results
Operational
Architecture
Concept A1142
Conduct Changes
Performance
Interface & Risk
Architecture Analyses Allocated
A1143 Architecture
System's
Qualification System-level Subsystem
System Architectures Design
Documentation Document Requirements,
Subsystem Boundaries,
Specifications Missions,
Objectives
A1145 & Constraints

NODE: A114 TITLE: Develop

DevelopSystem Operational
SystemAllocated Architecture
Architecture NUMBER: P. 9
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a System REV: DRAFT
Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
System
Requirements

Interface
Allocated Define Requirements
Architecture Interface
Requirements
A1151 High Level Draft Interface
Evaluate & Interface Physical
Interface Architecture Decomposition
Architecture Interface
Select High
Changes Requirements Level
Modifications Interface
Architecture Draft Interface
A1152
Functional
Develop Decomposition
Functional
Architecture
for Interface
A1153 Interface
Develop Physical
Physical Architecture
Architecture
for Interface
Interface
High Level A1154
Functional Develop
Interface Architecture Interface
Architecture Allocated
Modifications Functional
Modifications Architecture Architecture Interface
for Interface Architecture
A1155
Interface Interface
Physical Architecture
APPENDIX B

Architecture Modifications
Modifications

NODE: A115 TITLE: Develop Interface Architecture NUMBER: P. 10

465
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
466

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Stakeholders & System

Requirements,
Objectives Hierarchy,
Boundary & Qualification
APPENDIX B

System Requirements

Qualification System
Allocated Define Requirements,
Architecture Objectives Hierarchy,
Qualification Boundary & Validation
Requirement System Requirements
Changes Design
Qualification
A1161
Develop System
Functional Functional
Qualification Architecture
System Architecture of
Operational Qualification Candidate
Concept System Qualification
Develop
A1162 System
Physical Physical
Architecture of Architectures System's
Changes to
Qualification Qualification
Candidate Generic
Functional Physical Architecture
System Develop System
Architecture of of Qualification System A1163 Qualification
Allocated Documentation
Qualification System
System Architecture of Allocated
Qualification Qualification Architecture
System System System Models,
Changes Changes to Develop Models of
Physical Architecture A1164
Interfaces of Environment,
of Qualification System Changes External Systems,
Qualification
& Test Equipment
Changes to
System
Changes to Qualification Interface Architecture A1165
Requirements System of Qualification System
of Qualification
Define
Interface
System Architecture Models for
Qualification
A1166

NODE: A116 TITLE: Develop Qualification System NUMBER: P. 11

USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a System REV: DRAFT
Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
Subsystem
Design
Requirements,
Boundaries,
Subsystem-
Missions,
Level
Objectives
Subsystem Documentation
& Constraints
Design
Changes
Subsystem Allocated
Define Architectures, Design
Changes to Subsystem Specifications,
Subsystem Subsystem Subsystem Trade Studies,
Design
Requirements, Functions, Implementation Plans,
Requirements Problems
Boundaries Performance Subsystem Interface
A121 Specification Control Documents &
Develop
Qualification Plans
Subsystem Subsystem
Subsystem Functional
Functional Candidate Subsystem
Operational Architectures
Architectures Physical Architectures Subsystem
Concepts Design
A122 Approvals
Design
Subsystem Subsystem
Physical Component Design
Physical
Architectures Requirements,
Architectures
Subsystem Boundaries, Missions,
Functional A123 Objectives
Develop
Architecture & Constraints
Subsystem Subsystem
Changes
Physical Allocated
Architecture Architecture
Changes Subsystem
Obtain
Subsystem A124 Subsystem Qualification
Requirements Subsystem Design System
Changes Architecture Approval & Documentation
Changes Document for
Next Lower Subsystem
Changes
APPENDIX B

Level
A125 to System
Requirements

NODE: A12 TITLE: Perform Subsystem-Level Design Activities NUMBER: P. 12

467
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
468

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
Component Design
Requirements,
Boundaries, Missions, Subsystem Test Procedure
Objectives Component Valid Plan
APPENDIX B

& Constraints Operations Manual

Component-Level
Component Define Documentation
Design Component
Design Component Component
Changes Requirements Functions, Component Allocated
Problems
& Boundaries Performance Architectures, Design
A131 Specification Specifications,
Develop Trade Studies,
Component Component Implementation Plans,
Functional Candidate Component Interface
Component Functional
Architectures Component Control Documents &
Operational Architectures Architectures
Concepts Qualification Plans
A132
Design Component Component
Component Physical Design
Physical Architectures Approvals
Architectures
Component
Functional A133
Develop Component & CI
Architecture Component
Physical Component Qualification System
Changes Documentation
Architecture Allocated
Changes Architecture
A134
Component Obtain
Requirement Component
Changes Design Component
Component Approval & Changes
Component
Operational Document to System
Architecture
Changes Architecture for Next Requirements
Lower Level Changes to
A135
Subsystem
Requirements
NODE: A13 TITLE: Perform Component-Level Design Activities NUMBER: P. 13
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a Syste REV: DRAFT
Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Qualification Procedures, System Design

Operational Concept, Inputs of Stakeholders
Activities, & Models Phase
Stakeholders Requirements,
Derived Requirements Documentation
Acceptance
or Rejection

Early Acceptance
Validation Operational Criteria &
Derived &
Changes Concept Thresholds
Conduct Stakeholders
Early Requirements
Design
Validation Changes
A21
Early Verification
Validation Changes System
"Built-to"
Conduct Document Integration
CIs
"Built-to" Integration & Phase
Configuration Verification Documentation
Items & Pre- Verification
A22
Production Document Validation
Prototypes Changes
Pre-Production
Prototypes Verification
Data Conduct
Validation
Validation Acceptance
Document Acceptance Testing
A23 Changes Document

Validation
Data Conduct
Acceptance
Testing Operational
A24 System
APPENDIX B

NODE: A2 TITLE: Perform Qualification & Integration Activities NUMBER: P. 14

469
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
470

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Inputs of Stakeholders Qualification Procedures,

Activities, & Models
APPENDIX B

Conceptual
Validity
Changes
Conduct
Conceptual
Validation
Operational A211
Concept Conceptual
Validation
Document Requirements
Validity
Changes Early
Conduct
Operational Concept, Validation
Requirements
Stakeholders Requirements, Changes
Validation
Derived Requirements
A212
Operational
Concept, Requirements
Validation
Stakeholders
Document
Requirements Design
Validity
Changes
Stakeholders
& Derived
Requirements Conduct
Early
Design
Validation
Validation
Document
A213
Design
Validation
Document

NODE: A21 TITLE: Conduct Early Validation NUMBER: P. 15

USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a System REV: DRAFT
Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
Qualification Procedures, Derived &
Activities, & Models Stakeholders
Requirements

Stakeholders
& System
Component Level Subsystem Level Requirements
Design Documents Design Documents Documents
Perform Verification
Component CI Verification Changes
"Built-to" Changes
CIs Integration &
Verification CI Test
Results
Component Component Subsystem
A221 "Built-to"
Components Verification Verification Verification
Changes Documents Documents

Perform
Subsystem- Subsystem
Generated
Verification
Component Integration & Document
Regression Verification
Component Subsystem
Qualification
Test Verification
A222 Changes
Results

Perform
"Built-to" System
Subsystems System
Integration & Verification
System- System- Verification
Generated Document
Generated Verification
Component Subsystem
Regression A223 Data
Regression
Qualification Qualification Subsystem
Test
Results
System-Level
APPENDIX B

Reqression
Qualification

NODE: A22 TITLE: Conduct Integration & Verification NUMBER: P. 16

471
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
472

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
Component Level Qualification Procedures,
Design Documents Activities, & Models
"Built-to"
APPENDIX B

CIs

Inspect
Subsystem- CI Test
&
Generated Deficient
Results
Verify CI
Component CI Discrepancy
Regression Reports
Qualification Identify & Fix
Correctable Impact
A2211
CI Statement
System-
Deficiencies
Generated Assess Acceptable
Component A2212 Impact
Impact of
Regression Uncorrectable
Qualification CI
CI
Deficiencies Engineering
Uncorrected CI
Corrected CI Changes
A2213

Unacceptable
Cleared Impact Redesign CI Verification
CI CI Changes
Baseline
Redesigned CI Changes
A2214
Modify CI Component
Baseline
Verification
Documents
Approval to A2215
Continue
Integration Cleared CI Integrate
with
"Built-to"
Next CI Components

A2216

NODE: A221 TITLE: Perform Component Integration & Verification NUMBER: P. 17

USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
GMU Systems PROJECT: Engineering Design of a System REV: DRAFT
Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION
Subsystem Level Qualification Procedures,
Design Documents Activities, & Models
"Built-to"
Components

System- Component
Generated Inspect Test
& Deficient Results
Subsystem Component
Regression Verify
Component Uncorrectable
Qualification
Identify & Fix Component Impact
A2221 Correctable Statement
Component
Deficiencies Assess Impact Acceptable
of Impact Subsystem-
Cleared A2222 Uncorrectable Generated
Component
Component Component
Deficiencies Regression
A2223 Qualification
Corrected Unacceptable
Component Impact Redesign
Component Component
Redesigned Verification
Component A2224 Changes
Baseline
Changes
Component
Engineering
Changes Modify Subsystem
Component Verification
Approval to
Baselines Documents
Continue
Integration A2225 Integrate
Cleared with Next "Built-to"
Component Component Subsystems
APPENDIX B

A2226

NODE: A222 TITLE: Perform Subsystem Integration & Verification NUMBER: P. 18

473
USED AT: AUTHOR: Dennis Buede DATE: 05/24/99 WORKING READER DATE CONTEXT:
474

GMU Systems PROJECT: Engineering Design of a System REV: DRAFT

Engineering RECOMMENDED
Program NOTES: 1 2 3 4 5 6 7 8 9 10 x PUBLICATION

Stakeholders Qualification Procedures,

& System Activities, & Models
Requirements
Documents
APPENDIX B

"Built-to"
Subsystems
Subsystem
Inspect & Test
Verify Deficient Results
Subsystem Uncorrectable
Subsystem
Subsystem Impact
A2231
Statement
Identify & Fix
Correctable
Assess Acceptable
Subsystem
Impact of Impact
Deficiencies
Uncorrectable
Cleared A2232 Subsystem
Subsystem System-Level
Deficiencies
Reqression
A2233 Qualification
Redesign
Corrected Unacceptable
Subsystem Subsystem
Impact Subsystem
Redesigned Verification
Subsystem Baseline Changes
A2234 Changes

Subsystem Modify
Subsystem System
Engineering
Changes Baselines Verification
Document
A2235

Approval to Cleared Integrate

Continue Subsystem with Next
Integration Subsystem
A2236

NODE: A223 TITLE: Perform System Inte gration & Verification NUMBER: P. 19