Architecting with Models and UML/SysML Dr. Kenneth Kung Architecture Technology Area Director Raytheon Company June 2005 © 2005 Raytheon Company All Rights

Architecting with Models and UML/SysML

Dr. Kenneth KungArchitecture Technology Area DirectorRaytheon CompanyJune 2005

© 2005 Raytheon Company All Rights Reserved

Page 2© 2005 Raytheon Company All Rights Reserved

Raytheon Company

SAS IIS NCS IDS MS RTSC

RAC


Four Strategic Business Areas (SBA’s)

Missile DefenseMissile DefenseHomeland Homeland SecuritySecurity

Precision EngagementPrecision Engagement

IntelligenceIntelligenceSurveillance Surveillance

Reconnaissance Reconnaissance (ISR)(ISR)

The SBA’s Focus on Cross-Business Opportunities


Technology Strategy to Support Business and SBAs

Business Units

Strategic Business Area

MS RACIDS NCSIIS SAS

Technology Areas

RF

EO/Lasers

Processing

Arch/Syst Int

Missile Defense

Precision Strike

Homeland Security

ISR

CorrelateRationalizeStrategize

RF

EO/Lasers

Processing

Arch/Syst Int

Mat’l & Structure Mat’l/Struct

• Architecture Vision

• Reference Architectures

• Implementation Guidelines

• Repositories for Reuse

• Architecture Review Board (ARB)

• Training and Certification

• Framework and Standards

• REAP (Raytheon Enterprise Arch Process)


Architecture Vision – System of Elements™

Traditional System of Elements ™


Reference Architecture

Raytheon Enterprise Architecture Process (REAP)

Customer Needs

Customer Needs

Specific Program

Requirements

Apply Ref ArchTechnology,

Lessons Learned, Best

Practices

Applicable Strategy statement

““System of System of ElementsElements””

Reference Architecture offers a single point of departureReference Architecture offers a single point of departurein implementing mission solutionsin implementing mission solutions

Reference Architecture offers a single point of departureReference Architecture offers a single point of departurein implementing mission solutionsin implementing mission solutions

Governed by ARB

Mission Mission SolutionSolution

Businesses


System Architecture Implementation Approach

System Prototype

SystemBuild

Integration & Test

CapabilitiesDatabase

Operational View

Logical View

Physical View

Operational, Process & Workflow Modeling

Logical Architecture

Modeling

PhysicalModeling


Operational View


Logical ViewMission

Staff/ CrewExternal

Nodes

• Mission Services• Networking• Information Assurance• Resource Management• Workflow Management• Plans Management• Task/Decision Support• Data Synchronization

Common Human-Machine Interface (HMI)

• Client Applications•• Applets

Integration Framework

ComputingInfrastructure

Radios/ Data Links

Platform/Node Systems

Web Applications

Groupware Infrastructure:• Visualization Serv ices Collaboration Identity

Legacy and Node-Specific Databases

Pla

nn

ing

ISR

Mg

mt

Mis

sio

n M

gm

t

Se

ns

or

Ma

na

ge

me

nt

Co

mm

Mg

mt

Inte

l M

gm

t

Re

so

urc

e

Ma

na

ge

me

nt

Gro

wth

Mission Services

Metadata Catalog(MDC)

Co

mm

unic

ati

ons/

Ne

two

rkin

g S

ervi

ces

De

miu

lita

rize

dZo

ne (

DM

Z)/S

ecu

rity

Se

rvic

es

Alerts•

Controls/Status Displa ys•Shared Operational Picture•

Application Services:

. . .

Legacy/ Specialized

Clients/Viewers

Browser/ Web

Portal

Workflow/Orchestration Information Assurance Discov ery/Inference Web Services Softcopy Reference Folders Applications Support Serv ices Messaging/Networking

• Human Performance Design• Common Look and Feel• Style Guide

Client/Presentation Layer

Process/Business Logic Layer

Repository/Resources Layer

Data Services: Metadata Framework Ontology/Discov ery Proxies Agents/Access Serv ices

System & Support Services: Operating System System Management/Support Serv ices Physical Environment Services

LayeredArchitecture

Patterns


Physical View

Hardware Block Diagram

Node 1

:Obj n

:Obj 1

:Obj 2

Node 2

:Obj 4

:Obj 3

:Obj 5

:Obj 6

Node 3

Node

Component

ContainedObjects Interface

<<communication>>

Connection

Connection Type

Connection Type

Deployment DiagramDesign Documentation

• Product Data• Standards Profile• Software Documentation• Timing/Performance Data


Architecture Analysis

Operator RolesActivity Threads

Use CasesDomain Collaboration

Diagram

Operational/Mission Analysis

Process/Workflow Analysis

Scenarios/Events

MissionOutcomes

Actor Inputs/Events

System

Outputs

Messages/Data

Action

Timing

Digital Product Model

Logical/Functional Analysis

Physical Analysis

Physical Architecture

Product DataSize/Timing

Estimates

Design PatternsFoundation ClassesBehavioral Patterns Logical ArchitectureExecutable ArchitectureDesign Verification


Integrated Model

“SysML DoDAF Operational Architecture”

OVs

CIM - Computation Independent Model

Elaborated “SysML DoDAF System Architecture”

SVs

PIM - Platform Independent Model

Hardware and OS Independent

Common Services + HW & OS(OACE)

Platform Model

Delivered Components

PSM - Platform Specific Model

X

Platform Profile

Mission Profile

Unit Test, VV&A

Drive Architecture-Based M&S

AnalyzeRequirements

X

XTesting Space

NetCentric

Stand-alone

Liv

eM

&S

Drive Testing


UML Profiles: Major MDA Autocode Generation Mechanism

• UML profiles support the development of domain or technology specific semantics extensions to UML.

• Association of code to these standard profiles is a major mechanism for auto-code generation.

• Profiles can be built on other profiles, and multiple profiles can be used together.

–Define a majority of the Platform Model–Key Language Mappings profiles include CORBA, DSS (publish&

subscribe) and XML-SOAP. –Key facilities profiles include:

■ Scheduling, Performance, and Time (RT support)■ Testing■ QoS and Fault Tolerance

–Key domain profiles include SysML and DoDAF. ■ SysML is the System Engineering UML-2 Profile in process of being

adopted. ■ SysML has defined interfaces to HLA, MATHLAB, AP233, SystemC, and

other SysEng constructs ■ DoDAF will become a SysML Profile.


UML Profile for Systems Engineering (SysML) - Observations

• SEDSIG RFP for UML Profile for System Engineering Very Solid

• Raytheon supports and agrees with this development

• SysML Partners haveGood Technical productStrive for consensus, both users and vendorsNeed to push forward, despite schedule slips


UML Profile for Systems Engineering (SysML) - Expectations

• A model driven language for holistic system representation– SysML is broader than UML can do

– Can capture all salient aspects of complex system design

• A language that is intuitive for system engineers– Supporting proven systems engineering concepts

– The language must not be a barrier to traditional system engineering methods

• A language that facilitates, but does not mandate OO concepts

• A language that is consistent with, or transitionable to, UML used in software development

• A language that is embraced by a critical mass of tool vendors


UML Profile for DoDAF and MoDAF (UPDM) - Observations

• Customers demanding DoDAF artifacts

• Lack of Standard expression of DoDAF views in UML

• Non-standard tools and techniques for modeling DoDAF

• RFP – very solid team

– Got DoDAF 2 key people involved

• Submission Development– Raytheon values this activity

– Will participate in the development of this profile


UML Profile for DoDAF and MoDAF (UPDM) - Expectations

• A set of representations that is intuitive to our customer, and to non-UML engineers

• A model-based approach for developing DoDAF/MoDAF views– Consistency between views, based on underlying model

• An implementable profile, based on UML 2/SysML– More consistent tools – compliance beyond basics (intermediate or

complete)

• Usable data exchange between tools– XMI - XML meta data interface

■ Expect tools to compliant with XMI to support interoperability

– Diagram exchange interface


Final Thoughts

• Integration of processes has blurred the distinction between software and system

• Integrated tool from operational views down to executable code can ease the communication among engineers from various disciplines

• OMG is building the right products– Encourage faster consensus building

• Challenge: Very few of us get to design a brand new system. – How do we bring the legacy applications into the framework?

– How do we decompose their functionality to be re-used in an SOA architecture?

Documents

Architecting with Models and UML/SysML Dr. Kenneth Kung Architecture Technology Area Director Raytheon Company June 2005 © 2005 Raytheon Company All Rights