The Boeing System of Systems Engineering (SoSE) Process and Its Use in Developing Legacy-Based Net-Centric Systems of Systems

(1)

Advanced Network & Space Systems

Information & Knowledge Systems

The Boeing System of Systems Engineering

(SoSE) Process and Its Use in Developing

Legacy-Based Net-Centric Systems of

Systems

Copyright © 2009 by Boeing. All rights reserved. This document does not contain technical data within the definition contained in the International Traffic in Arms Regulations (ITAR) and the Export Administration Regulations (EAR), as such is releasable by any means to any person whether in

the U.S. or abroad. The Export Compliance log number for this document is Export Approval # ACK219 (assigned IAW PRO-4527, PRO-3439).

Marion L. Butterfield, Alaka Shivananda, and

Dennis Schwarz (The Boeing Company)

National Defense Industrial Association (NDIA) 12th Annual

Systems Engineering Conference, October 26-29, 2009

(2)

Advanced Network & Space Systems | Information and Knowledge Systems

Systems to Systems of Systems:

The Evolving Challenge of Complexity

For example, many future military SoS’s

will be comprised of legacy systems

from the Air Force, Army, Marines, and

Navy. Effective approaches are required

to transform these legacy systems into

net-enabled systems capable of

performing effectively as a part of these

net-centric SoS’s.

Weapon System Effectiveness, for

single systems, in a standalone

platform-centric environment is

directly proportional to Mission

Effectiveness of the system

THE BATTLEFIELD

Net-Enabled System of Systems

Boeing’s role as a developer of commercial

and military net-centric enterprise systems

of systems (SoS) has resulted in the

requirement to perform Systems of

Systems Engineering (SoSE) over a wide

range of mission and system domains.

Single System

(3)

Advanced Network & Space Systems | Information and Knowledge Systems

System of Systems Engineering (SoSE) Process

What it is and What it does

An Enterprise (SoS)

Engineering Process

for development of both

commercial and military

complex systems and

systems of systems

• Provides a disciplined and

more detailed SE process

• Follows industry standards

• Applicable to all system

development programs

An architecture-centric,

model-based approach

that results in a single

SoS/Systems Architecture

Model when used in a

collaborative environment

• Horizontally integrates program

engineering disciplines

• Results in a single truth-model

• Incorporates a common modeling

language for architecture dev.

A methodology that

provides detailed

guidance on the

net-enablement of legacy

systems and their use in

net-centric systems of

systems

• Supports industry NCO

standards and strategies

• Improves implementation of

acquisition strategies

(4)

Advanced Network & Space Systems | Information and Knowledge Systems

What is a System?

A collection of components organized to accomplish a specific

function or set of functions.

(5)

Advanced Network & Space Systems | Information and Knowledge Systems

What is a “System of Systems?”

A network-centric Air Transportation

Management system



Definition:

A System-of-Systems (SoS) is a “super-system” comprised of elements that are themselves

complex, independent systems which interact to achieve a common goal.

*After Maier, Sega, Levis



Common Characteristics:

–

The component systems achieve well-substantiated purposes in their own right even if

detached from the overall system

–

Constituent systems and functions may be added or removed during its use

–

It exhibits behavior, including emergent behavior, not achievable by the component

systems acting independently

–

The component systems are managed in large part for their own purposes rather than

the purposes of the whole

(6)

Advanced Network & Space Systems | Information and Knowledge Systems

SoSE Process is the Boeing Model-Based Best-Practices

Approach to Developing a SoS/System Architecture Model

Identifies requirements, system elements, and interfaces

at each level

to support early design activities for all of a

program’s engineering disciplines

SoS/System Architecture Model: A description of the structure of a system’s components, the

relationships between those components, and capabilities assigned to those components.

SoSE System

Architecture

Model

SoSE is Architecture-Centric:

The system’s architecture

model is used as the

primary artifact

for conceptualizing,

constructing, managing, and evolving the system

Provides a continuous

model stream

from the

Stakeholder-Goal level

to the architecture

base level

Improves traceability

by

defining functional

requirements and system

objects at each system

development level

(7)

Advanced Network & Space Systems | Information and Knowledge Systems

Capabilities

Description

Stakeholder

Views

SoS/System

Specifications

Architecture

Description

Extraction Methods

Analysis, Modeling &

Simulation

SoS/System

Architecture Model

System of Systems

Engineering (SoSE) Process

System

Architecture Team

Program

Stakeholders Inputs

Standards &

Strategies

SoSE Process Transforms the Stakeholders’ Goals into a

Balanced SoS/System Architecture Model

(8)

Advanced Network & Space Systems | Information and Knowledge Systems

SoSE Architecture Model Includes Required Architectural Levels of

Commercial and/or Government NCO SoS/Systems

SoSE Operational Approach Supports all Commercial and/or Government Missions

Force (SoS-Level)

Capability Goals

Force

Operational Capabilities

Node (System-Level)

Operational Capabilities

System

Functional Capabilities

Example – Force SoS

Capability Levels

Force SoS Goals (policy objectives) that drive the

SoS level mission.

Measurable results that have

value to mission stakeholders of the SoS.

SoS/System Level Definitions

Force SoS operational capabilities required to achieve

the SoS goals.

Measurable results that have value to

the operational level authorities of the SoS.

Force Node/System operational capabilities required

to achieve SoS Capabilities.

Measurable results that

have value to the operational level authorities of the

Node/System/Organization.

System/Organization functional capabilities

(behavior) required to achieve the Node operational

capabilities.

Measurable results that have value to

the functional authorities of the System/Organization.

Sub-System

Functional Capabilities

Sub-System/Organization functional capabilities

(behavior) required to achieve the System/Organization

capabilities.

Measurable results that have value to the

functional authorities of the sub-System/Organization.

(9)

Advanced Network & Space Systems | Information and Knowledge Systems

Legacy Constraints Can Drive the SoS Architecture Model

at all SoS and/or System Capability Levels

DoD NCO SoS

Capability Levels

NCO SoS Development

Analyses

Example Architectural Decisions

Affected by Legacy Constraints

Legacy doctrines

can constrain the

selected Objective Capabilities and the

constituent operational capabilities

Legacy force structure

, operational

doctrine, and systems can constrain the

operational nodes selected and their allocated

operational requirements

Legacy systems technology

,

standards, and support systems constrain

the identified functional requirements and

services provided and/or consumed

Legacy design features

, software, and

subsystems constrain the subsystems

selected and their allocated functional

requirements and services provided and

/or consumed

Subsystem Behavior

(Functional Capabilities)

Force SoS

Operational Capabilities

Force SoS Goals

(Mission Objectives)

Functional

Decomposition

Functional

and Structural

Decomposition

Node/System

Operational Capabilities

Functional

Decomposition

System Behavior

(Functional Capabilities)

Functional

and Structural

Decomposition

(10)

Advanced Network & Space Systems | Information and Knowledge Systems

Both New and Legacy Systems are Expected to be used to

Develop Net-Centric Systems of Systems

NCO

Infrastructure

Components

▲

Legacy

System #1

Transceivers

Sensors

Command

and

Control

Processors

▲

Legacy

System #2

New

System #5

▼

Legacy

System #4

Legacy

System #3

Net-Enabled

New System #5

▼

Legacy

System #3

▼

Legacy

System #4

Net-Enabled

System #2

Net-Enabled

System #1

▼

Legacy system required for SoS, but cannot be modified

Legacy system required for SoS and it can be modified

(11)

Advanced Network & Space Systems | Information and Knowledge Systems

SoSE Architecture-Centric Approach Extends Legacy

Methods for Verification & Validation

Legacy Verification Approach

SoSE Integrated Verification and Validation Approach

Generate System(s)

Operational Concept &

Requirements Documents

Generate System(s)

Specifications

& Verification Plan

Generate Subsystem(s) “Design to” Specifications

Verify CIs to “Build to” Documentation

Integrate Subsystem(s) and Verify to “Design to”

Specifications

Evolve CIs “Design to” Specifications into “Build

to” Documentation & Verification Procedures Validate System(s) Architecture Verify System(s) Requirements Validate Subsystem(s) Architecture

Verify Service(s) Needs Validate SoS Architecture Verify Subsystem(s) Verify System(s) Verify SoS Validate SoS

decompose

extract

validate

Verify Subsystem(s) Requirements Verify CIs Requirements Verify CIs

Design Details Verify CIs

Integrate SoS and Perform

Verification to Operational

Concepts & Requirements

Documents

Subsystem(s)

Architecture Model

System(s)

Architecture

Model

System of Systems

Architecture Model

requir emen ts

Model System of Systems

(SoS) Architecture to

Identify Systems

Customer

Enterprise/Mission

Goals & Valuation

validate

Model Customer

Enterprise/Mission

Goals & Valuation

Model Customer

Enterprise/Mission

Service(s) Needs

decompose decompose Validate Subsystem(s) Architecture decompose

Model Subsystem(s)

Architecture to Identify

Component(s)

extract

Baseline Architecture

Description Document

(ADD)

verify

Model Configuration Items

(CIs) Architecture with

design patterns

Document Architecture

CI (s)

Architecture Model

validate

Design

Architecture

Model

validate

Code/Fabricate and Assemble CIs to “Build to” Documentation

Customer Deployment

& Validation of SoS

Enterprise/Mission

Goals

Integrate System(s) &

Perform Verification

to Specifications

verify

Model System(s)

Architecture to Identify

Subsystems

(12)

Advanced Network & Space Systems | Information and Knowledge Systems

A Net-Enabling Architecture Framework (NEAF) was created to

Augment the SoSE Process to Assist Net-Enabling Product Teams

NEAF Provides Product Teams Best-Practices Guidance on how to

–

Develop System Architecture models using the Boeing SoSE Process

–

Implement Net-Centricity and net-enable systems

–

Organize and present the net-enabling aspects of the system architecture

–

Develop and use a Net-Enabling Reference Architecture (NERA)

–

Incorporate SOA principles

DOD NCO SoS

Development Levels

Functional Decomposition Technique Functional Functional Decomposition Decomposition Technique Technique Functional Decomposition Technique Functional Functional Decomposition Decomposition Technique Technique System Decomposition Technique System System Decomposition Decomposition Technique Technique

Force SoS Goals

(Mission Objectives)

Force SoS Goals

(Mission Objectives) (Mission Objectives)

Subsystem Behavior

(Functional Capabilities)

Subsystem Behavior

(Functional Capabilities) (Functional Capabilities)

Force SoS

Operational Capabilities

Force SoS

Operational Capabilities

Node/System

Operational Capabilities

Node/System

Operational Capabilities

System Behavior

(Functional Capabilities) (Functional Capabilities) System Decomposition Technique System System Decomposition Decomposition Technique Technique

1

2

3

4

5 DOD NCO SoS

Development Levels

Functional Decomposition Technique Functional Functional Decomposition Decomposition Technique Technique Functional Decomposition Technique Functional Functional Decomposition Decomposition Technique Technique System Decomposition Technique System System Decomposition Decomposition Technique Technique

Force SoS Goals

(Mission Objectives)

Force SoS Goals

(Mission Objectives) (Mission Objectives)

Subsystem Behavior

(Functional Capabilities) (Functional Capabilities)

Force SoS

Operational Capabilities

Force SoS

Operational Capabilities

Node/System

Operational Capabilities

Node/System

Operational Capabilities

System Behavior

(Functional Capabilities) (Functional Capabilities) System Decomposition Technique System System Decomposition Decomposition Technique Technique

1

2

3

4

5 Reference Models

• Services (SOA based)

• IA and/or Security

• Transport

• Data

Net-Centric Design Principles

Reuse Repositories

(13)

Advanced Network & Space Systems | Information and Knowledge Systems

Close Air Support (CAS) Example Use Case Diagram –

Enterprise Operational Capability

Example, Notional Scenario

(14)

Advanced Network & Space Systems | Information and Knowledge Systems

Provide

Combat

Identification

Establish,

Operate, Maintain

Information

Exchange

Decompose SoS-Level Goals into SoS Operational

Capabilities (OpCap) – CAS Example

A-1

A-2

A-3

A-4

A-5

A-6

A-7

A-8

A-9

A-N

Assess Munitions

Effects on

Operational Targets

Decompose Goals

into constituent Activities

A-2

A-3

A-5

A-1

A-4

A-6

A-8

A-N

A-7

A-9

Collect Goals’ activities

into clusters of functionality

Functionality clusters

for SoS Operational

Capabilities

Constituent

activities

Provide Close Air

Support Integration for

Ground Forces

Assess Re-Attack

Requirement

Establish

Joint Force

Targeting Guidance

SoS-Level

Goals (4 examples)

SoS-Level

OpCaps

(4 examples)

Provide Lethal

Precision

Engagement

Conduct Close

Air Support

2

(15)

Advanced Network & Space Systems | Information and Knowledge Systems

Decompose SoS-Level OpCaps into Node/ System

OpCaps – CAS Example Capabilities and Nodes

Node-Level

OpCap A

Node-Level

OpCap B

Node-Level

OpCap C

Node-Level

OpCap N

A-1

A-2

A-3

A-4

A-5

A-6

A-7

A-8

A-9

A-N

Mission

Planning &

Assessment

Weapon Systems

Planning &

Assessment

Information

System

Delivery

System

Example CAS SoS-Level Operational Capabilities

Force-Level

OpCap A

Force-Level

OpCap B

Force-Level

OpCap C

Force-Level

OpCap N

Decompose OpCaps

into constituent Activities

A-2

A-3

A-5

A-1

A-4

A-6

A-8

A-N

A-7

A-9

Collect OpCap activities

into clusters of functionality

Allocate node/system OpCaps

to candidate nodes/systems

Functionality

clusters

suitable for

nodes/systems

Constituent

activities

Provide Combat

Identification

Provide Lethal

Precision

Engagement

Conduct Close

Air Support

Example CAS

Operational Nodes

3 Establish, Operate,

Maintain Information

Exchange

(16)

Advanced Network & Space Systems | Information and Knowledge Systems

Relationship of Force SoS Structure (the “who”) to the Force

Operational Capabilities (the “need”) to Measures of Effectiveness

Force SoS

Stakeholders

Force

Operational

Authority

Force

System/Organization

Authority

Force SoS

Capabilities

Goals

Force SoS

Operational

Capabilities

Node/System

Operational

Capabilities

Measures of Node/Systems

Effectiveness

Measures of SoS

Operational Effectiveness

Measures of SoS Mission

Effectiveness

Stakeholders

Need

Capabilities

Measured by

Effectiveness

MOEs Drive the Architectural Design at all SoS Architecture Levels

Assessed values

Contribute to SoS

Goals level

Assessed values

Contribute to SoS

Operational level

(17)

Advanced Network & Space Systems | Information and Knowledge Systems

Program Shared Situational Awareness is Achieved

through Interlocking System Architecture Teams (SAT)

Detailed

Design

Team

(a,1,2)

Detailed

Design

Team

(a,1,3)

Detailed Design Team (a,1,1)

Sub-system

(a,2)

SAT

Sub-system

(a,3)

SAT

Sub-system (a,1) IPT SAT

SoS SAT

System (a) SAT

Systems (a, b, and c) SAT Leaders are Member of SoS SAT

Sub-system (a,1) Leader is member System (a) SAT

Leader

Technical Participants:



Domain Specialists (Analysts, HW, SW,

Algorithm, Specialty, T&E)



Scientists & Technologists



Operations Analysts



SE Product Management

System

(c) SAT

Leader

System

(b) SAT

Leader

Other Participants:



Project Management



Marketing



Customer Representative



Process Specialists

Detailed Design Team (a,1,1) Lead

is member of Sub-System (a,1) SAT

Leader

Participants:



HW, SW Design Engineers



Specialty Engineers



IV&V Engineers



Algorithm Developers

( )

_{( )}

( )

(18)

Advanced Network & Space Systems | Information and Knowledge Systems

Summary

SoSE is a

systematic and disciplined system engineering process

for defining SoS and System capabilities and net-ready compliant

architectures; allocating such capabilities to a set of elements:

systems and subsystems; and coordinating strategy of design,

production, sustainment throughout the life cycle of a system.

Develops the

system architecture model to serve as a single

common “Truth” model

with the ability to incorporate the design

view points of all engineering disciplines and provide architecture

“situation awareness” for technical and program leadership

Establishes a “

Top-Down”

analytical framework for determination of

the mission effectiveness for a system of systems

Incorporates

open architecture development strategies

and

techniques and incorporates commercial and/or legacy systems

The system architecture model is

the single most important

development product of the System Architecture Team

(19)

Advanced Network & Space Systems | Information and Knowledge Systems

References

–

Net-Centric Checklist, OASD for Networks and Information Integration, Ver. 2.1.3.

12 May 2004.

–

Net-centric Service Framework, NIF Ver. 2. NCOIC NIF Working Group. 20 August

2008.

–

Recommended Practice for Architectural Description of Software-Intensive Systems.

ANSI/IEEE-std-1471-2000. date.

–

Reference Architecture for Service Oriented Architecture, Ver. 1.0. OASIS. 23 April

2008.

–

Network Centric Operations Conceptual Framework, Ver. 1.0. Prepared for John

Garstka, Office of Force Transformation, Evidence Based Research, Inc., November

2003.

–

Overarching Architecture for FMLS 2010 Technical System. Sweden FMV. LT1K

(20)