presentation from april 8, 2008 dinner meeting

8/9/2019 Presentation from April 8, 2008 Dinner Meeting

1/25

2006 Vitech Corporation. All rights reserved.

System Engineering &Architecting with CORE

INCOSE WMA Chapter MeetingStuart Booth

4/8/2008


2/25

2007 Vitech Corporation. All rights reserved.071015 [DoDAF 1.5] 2

Agenda

Introduction to DoDAF 1.5 Introduction to MBSE COREs Implementation of DoDAF 1.5 Demonstration

Questions


3/25

2007 Vitech Corporation. All rights reserved.071003 Intro to CORE and MBSE 3

Evolution of DoDAF


4/25


DoDAF v1.5: Key Messages

Introduces Net-Centric concepts into existingOV/SV/TV baseline

Introduces Service Oriented Architectures (SOA) Introduces the concept of Federated

Architectures Increased support for data-centric architecture

management and the support for CADM

Backward Compatibility Maintains completebackward compatibility with DoDAF v1.0


5/25


Integrated and Federated Architecture

071015 [DoDAF 1.5] 5


6/25 2007 Vitech Corporation. All rights reserved.

What is Service Oriented Architecture (SOA)?

071015 [DoDAF 1.5] 6

SOA is a design for linking business andcomputational resources (principallyorganizations, applications and data) ondemand to achieve the desired results for

service consumers (which can be end users orother services).SOA is a key Net Centric strategy: the ability

to share information when it is needed, where it is needed, and with those who need it.

http://en.wikipedia.org/wiki/Service-oriented_architecture#Other_SOA_Concepts



Common Examples of Services

071015 [DoDAF 1.5] 7

Telephony Services ATM Services

Web Services


8/25 2007 Vitech Corporation. All rights reserved.071003 Intro to CORE and MBSE 8

New Sub-views for Products

SV-4a Systems FunctionalityDescriptionFunctions performed by systems and

the system data flows amongsystem functions.

SV-4b Services FunctionalityDescriptionFunctions performed by services and

the service data flow amongservice functions.

SV-5aOperational Activity to

Systems FunctionTraceability Matrix

Mapping of system functions back tooperational activities

SV-5bOperational Activity to

Systems TraceabilityMatrix

Mapping of systems back tocapabilities or operational activities

SV-5cOperational Activity to

Services FunctionTraceability Matrix

Mapping of services back tooperational activities



CORE Approach to GenerateDoDAF v1.5 Products

Extend the underlying systems engineering designlanguage to support development of the specializedDoDAF architecture-specific products

Apply the MBSE approach to developing DoDAF views:repository, schema, scripts, hierarchies, and views.



Systems Engineering with CORE

Data

Data Data

verified by

Source Requirements Domain

Architecture Domain

Behavior Domain

V&V Domain

verified by

Originating requirements trace to behavior

Originating requirements trace to physical components

Behavior is allocated to physical components

verified by

Data

The CORE System

Engineering Repository

Data

Utilizing a layered approach to progressively clarify and elaborate all four domainsconcurrently ensures consistency and completeness.


11/25 2007 Vitech Corporation. All rights reserved.071015 [DoDAF 1.5] 11

Organization of DoDAF FrameworkProducts

Presented by Mr. Truman Parmele at the DoD Architectures Conference February 24, 2004



System Design Repository

Operational Views

Requirements Views

Physical Views

Functional Views

Integrated Repository and View Generators ProvideConsistency of Views and Products

DoDAF Views

The CORE System

Definition

Repository



Dynamic Validation

System behavior diagram definesarchitecture of simulation model which allows

us to analyze Behavior, Timelines,Resources, Queues, and Flows



basis of

Added Type ServiceAdded Service Type attribute

Added Status attribute

Service Specification

documented by

Added Behavior TypeIntegrated (Services)

implemented by

implemented by

Architecture composed ofcomposed of

implemented by

implemented by

achieves

CORE DoDAF 1.0/1.5 Schema

071015 [DoDAF 1.5] 14

Interface

Link

Functiondecomposed by

Item decomposed byinputs / outputs

/ triggered by

performs

connected to/ thru

built fromComponent

specifiesRequirement

refined by

Selected Classes

governs

Selected

Classes

includes

Standard

ExchangeCharacteristic

joins &joins thru

exhibits

exhibits

basis of

InterfaceElement

RequirementElement

PhysicalElement

FunctionalElement

C o l o r C o d e

specifies

System Architecture Domain

Exit

Resource

implemented by

exits by

Selected Classes

Organization

captures /consumes /produces

includes

Operational Architecture Domain

achieves

NeedLine

transfers

decomposed by

OperationalInformation

decomposed by

exits by

inputs /outputs /triggered by

captures /consumes /

produces

performs

connected to /

thru

guides

Selected Classes

achieves

built from

OperationalNode

includes

Guidance

OperationalTask

includes

Mission

includes


exhibits

exhibits

OperationalActivity



Description: The Tactical Image Management Architecture is composed of both an operational element and an image management system which

supports the architecture.

Image Management System: AddingServices Example Problem

dd



Image Management System: AddingServices Example Problem (cont.)

Image Management System With Services

TacticalCustomers

ImageCollectors

INTERNAL SERVICES AVAILABLESearchDistributionSubscription

ExternalCustomers For

Service

ExternalCustomerValidation

Service

New servicescapability

ImageCollectorInterface

ExternalServicesInterfaceCustomer

Interface


17/25


Demonstration


18/25


basis of

Added Type ServiceAdded Service Type attribute

Added Status attribute

Service Specification

documented by

Added Behavior TypeIntegrated (Services)implemented by

implemented by

Architecture composed ofcomposed of

implemented by

implemented by

achieves

CORE DoDAF 1.0/1.5 Schema

071015 [DoDAF 1.5] 18

Interface

Link

Functiondecomposed by

Item decomposed byinputs / outputs

/ triggered by

performs

connected to/ thru

built fromComponent

specifiesRequirement

refined by

Selected Classes

governs

Selected

Classes

includes

Standard


joins &joins thru

exhibits

exhibits

basis of

InterfaceElement

RequirementElement

PhysicalElement

FunctionalElement

C o l o r C o d e

specifies

System Architecture Domain

Exit

Resource

implemented by

exits by

Selected Classes

Organization

captures /consumes /produces

includes

Operational Architecture Domain

achieves

NeedLine

transfers

decomposed by

OperationalInformation

decomposed by

exits by

inputs /outputs /triggered by

captures /consumes /

produces

performs

connected to /

thru

guides

Selected Classes

achieves

built from

OperationalNode

includes

Guidance

OperationalTask

includes

Mission

includes


exhibits

exhibits

OperationalActivity

NA


19/25


CORE DoDAF v1.5 Provides:

A way to produce architecture view artifacts (OV,SV, and TVs) that meet the wants and desires

of the DoD customer. A way to deliver System Architecture that

includes specifications, design and interfacedocumentation.

A way to produce Integrated Architectures.

A way to produce Executable Architectures. A methodology to do the above


20/25


CORE DoDAF 1.5 View/Product Description

ApplicableView

FrameworkProduct Framework Product Name CORE Solution/Summary

All Views AV-1 Overview and Summary Information Description, purpose, scope, time frame and mission; optional externalgraphic

All Views AV-2 Integrated Dictionary Architecture Description Document (ADD) Report

Operational OV-1 High-Level Operational Concept Graphic Identified in CORE database as an External Graphic. Viewable in COREand incorporated in CORE reports.

Operational OV-2 Operational Node Connectivity DescriptionPhysical Block Diagram (PBD) for Operational Node displaying theOperationalNodes decomposition with Needlines connecting internal andexternal nodes.

Operational OV-3 Operational Information Exchange MatrixOV-3 Report script (Outputs a summary or full information exchangematrix listing Needlines, Operational Information exchanged and theExchangeCharacteristics.)

Operational OV-4 Organizational Relationships Chart Hierarchy Diagram showing command and coordination relationships ofthe Organization

Operational OV-5 Operational Activity Model EFFBD, FFBD or IDEF0 representing behavior models including control,input/output, sequencing and decomposition of OperationalActivities

Operational OV-6Operational Rules ModelOperational State Transition DescriptionOperational Event-Trace Description

Complete, executable operational activity model as EFFBDs. Optionaloutput includes rules, a captured COREsim timeline file or an externalevent trace file.

Operational OV-7 Logical Data Model OperationalInformation characterization table

Systems andServices SV-1 Systems Interface DescriptionServices Interface Description Physical Block Diagram for Component or an external file that augmentsthe Component

Systems andServices SV-2

Systems Communications DescriptionServices Communications Description

Physical Block Diagram for Component or an external file that augmentsthe Component

Systems andServices SV-3a,b,c

Systems-Systems MatrixServices-Systems MatrixServices-Services Matrix

Matrix representing the interfaces between SystemsMatrix identifying the interfaces between Systems and internal andexternal ServicesMatrix identifying the interfaces between Services

Systems andServices SV-4 Systems Functionality Description

EFFBD, FFBD, N2 or IDEF0 representing behavior models includingcontrol, input/output, sequencing and decomposition of Functions


21/25


CORE DoDAF 1.5 View/Product Description

ApplicableView

FrameworkProduct Framework Product Name General Description

Systems and

ServicesSV-5a,b,c

OperationalActivity to Sys. Function Traceability MatrixOperational Capability to Services Traceability MatrixOperational Capability to Services Traceability Matrix

Matrix tracing between the OperationalActivities and Functions with anoption to show the Component performing each Function.Matrix tracing between a capabilitys OperationalActivities and Systems

Matrix tracing between a capabilitys OperationalActivities and Services


Systems Data Exchange MatrixServices Data Exchange Matrix

Summary or full data exchange matrix listing Links, Item exchanged, andExchangeCharacteristics.


Systems Performance Parameters MatrixServices Performance Parameters Matrix

Table containing quantitative performance characteristics (current,threshold, objective for near-term, mid-term, and far-term time frames) forComponents and their associated Interfaces, Links and Functions.


Systems Evolution DescriptionServices Evolution Description An ExternalFile (text or graphic).

Systems andServices SV-9 Systems Technology Forecast

Table containing technology forecast information for Components andtheir associated Interfaces, Links, Functions and Items.

Systems andServices SV-10a, b, c

Systems Rules ModelServices Rules Model

Complete, executable functional model as EFFBDs. Optional outputincludes rules, a captured COREsim timeline file or an external eventtrace file.

Systems andServices SV-11 Physical Schema Item characterization table and/or an ExternalFile.

Technical TV-1/2 Technical Standards ProfileTechnical standards information or each Standard that governs theSystems and their associated Interfaces, Links, Functions, and Items isprovide in table format.


22/25


Spare Slides


23/25


Architecture Terms

Architecture - The term architecture is generally used both to refer to an architecture description and an architecture implementation.An architecture description is a representation of a current or

postulated real-world configuration of resources, rules, andrelationships. Once the representation enters the design,development, and acquisition portion of the system developmentlife-cycle process, the architecture description is then transformed

into a real implementation of capabilities and assets in the field. TheFramework itself does not address this representation-to-implementation transformation process but references policies thatare relevant to that process.

Integrated Architecture - the term integrated architecture refers to one in which architecture data elements are uniquely identified andconsistently used across all products and views within thearchitecture.

071015 [DoDAF 1.5] 23


24/25

O i A hit t D l t


25/25

2007 Vi h C i All i h d0 0 [ ]

Overview Architecture Development:How the Process and Products Relate

5. Develop the Operational Context Diagram

15. Conduct Trade-off Analyses

6. Develop Operational Scenarios

1. Capture and Analyze Related Documents

4. Capture Constraints

3. Identify Existing/Planned Systems

2. Identify Assumptions

7. Derive Functional Behavior

8. Derive System Elements

10. Prepare Interface Diagrams

14. Provide Options

12. Perform Dynamic Analysis

11. Define Resources, Error Detection & Recovery

13. Develop Operational Demonstration Master Plan

16. Generate Operational and System Architecture Graphics, Briefings and Reports

Requirements Analysis

Functional Analysis

Synthesis

System Analysisand Control

AV-1

AV-2

9. Allocate Functions to System ElementsTV-1 TV-2

OV-1OV-2

OV-3

OV-4

OV-5

OV-6

OV-7

SV-1

SV-2SV-3

SV-4

SV-5SV-6

SV-7

SV-8 SV-9

SV-10

SV-11

Time