Transcript UPDM - Object Management Group

OMG UML Profile for the
DoD and MoD Architecture
Frameworks (UPDM)
Dwayne Hardy
American Systems
[email protected]
Jan 30, 2007
UML Profile for DoDAF/MODAF
(UPDM) Overview

OMG initiative underway to develop tool
specification for representing & exchange of
DODAF and MODAF products






Requirements (RFP) issued Sept 05
Initial submissions received June 06
Final submissions expected Mar ‘07
Goal is to provide robust architecture modeling
capability, improve communications and tool
interoperability, and reduce re-training
Multiple tool vendors and users participating
Should leverage SysML, UML and BPMN and
experience gained from existing tools
DoD & UK MOD are supporting and hope to adopt!
2
Summary of DoDAF Views
NODES
TIME A
T1
T2
T3
B
System Functionality
Description (SV-4)
Y
X
Systems Functionality
Sequence and Timing
Description (SV-10 a/b/c)
c
System - System
Matrix (SV-3)
XY
Z
X
Y
C
Systems Interface
Description (SV-1)
Physical Schema
SV-11
Activity to System
Function (SV-5)
Systems Evolution
Description (SV-8)
Technical Architecture
Profile (TV-1)
Standards Technology
Forecast (TV-2)
CONNECTION
TO NODE B
NODE A
System 1
System 2
One-Way
Communications
Link
Two-Way
Communications
Links
System 4
System 3
CONNECTION
TO NODE B
Local Area Net
System 5
EXTERNAL
CONNECTION
(OUTSIDE THE
NODES OF INTEREST)
CONNECTION
TO NODE C
Systems Communications
Description (SV-2)
Operational
Systems Data Exchange
Matrix (SV-6)
Systems Performance
Parameters Matrix (SV-7)
Operational Concept
Description (OV-1)
Systems Technology
Forecast (SV-9)
Operational Activity
Model (OV-5)
• .....
• .....
• .....
Organizational
Relationships
Chart (OV-4)
Node Connectivity
Description (OV-2)
•
-
Logical Data
Model (OV-7)
Information
Exchange Matrix
(OV-3)
NODES
TIME A
T1
T2
T3
B
C
Operational Activity
Sequence and Timing
Description (OV-6 a/b/c)
3
MOD Architecture
Framework (MODAF)
Inputs:
Cap Audit
Legacy
Systems
Standards
Prog Plans
Inform
Inform
Inform
Inform
Inform
Strategic View
Enterprise
Architecting
Doctrine
& SAGs
Outputs:
Operational View
System View
Technical View
Acquisition
View
DoDAF
Optimise
Capability
Phasing
Provides
Operational
Concepts
Defines System
Components &
Key Interface
Points
Structures the
Mandated
Standards
Provides the
Route map
Improved Policy
Coherent Effects
System of Systems
Standards and
Principles
NEC Roadmap
Context
4
MODAF
StV-5 Capability to Systems
Deployment Mapping
EPOCH 4
System deployment
by operational capability
category
EPOCH 3
Overlap of systems
between epochs
EPOCH 2
EPOCH 1
Capability 1
Capability 2
Capability 3 Capability 4
PJHQ
JTF
System deployment
by echelon level
LCC
Corp
Div
Bde
BG
Coy
Plt
System connectivity and
systems involved
5
AcV-2 SoS Acquisition
MODAF
Programmes
MG 01/10/04
IOC 01/04/05
FOC 01/08/05
System A
IG 01/05/04
IOC 01/06/04
MG 01/11/04
System B
IG 01/06/04
IOC 01/10/06
MG 01/01/05
System C
MG 01/10/04
IOC 01/05/05
FOC 01/01/06
System D
OUT OF SERVICE 01/06/05
DISPOSAL 01/11/04
System E
2004
2005
D
2006
LoD 'Hexagon'
Project Phase
octrine
E
T
quipment
No outstanding issues
Pre-IG
Manageable issues
IG to MG
raining
Key to View
LoDs
Critical issues
P
S
eople
ustainment
O
MG to IOC
IOC to FOC
In Service
rganisation
Disposal
6
Motivation for UPDM


UML is used extensively to represent architecture
products (e.g., artifacts) across industry
DoDAF v1.0



MODAF extends DoDAF



Volume II provides guidance on using UML
But based on UML 1.x which has been superseded by UML
2
Defined its metamodel (M3) as a profile of UML 2
But adds additional viewpoints (perspectives)
NATO and other architecture frameworks further
extend DoDAF and MODAF
7
Goals for UPDM




Significantly enhance the quality, productivity,
and effectiveness associated with architecture
and system of systems modeling
Enable architecture model reuse and
maintainability
Improve tool interoperability and
communications between stakeholders
Reduce training impacts due to different tool
implementations and semantics
Develop UML Profile for DoDAF/MODAF that provides
industry standard UML/SysML representation of 8
DoDAF/MODAF architecture views
Relationship of Standards to
DoD’s Architecture Program
Explorations *
ASM
ABM
OMG
International
Vendor tools
DODAF 1.5 - 2.0
Academic
Industry best practices
Federal
coordination
AP233-CADM mapping
spec will define data
exchange in XML
OPERATIONAL-NODE
Evolutions
DOD governance
UPDM will define a
Department
processes
UML/SysML implementation
Transformation
of DoDAF products and
MOF
based learned
data exchanges
Lessons
CCB & DODAF Working Group
• DODAF Vol II structured diagrams
• DODAF Vol III chapters on CADM
PHYSICAL-NODE
DATA
INFORMATION
CADM 1.0x
SYSTEM
EVENT-TRIGGER
OPERATIONAL-ACTIVITY
UPDM may define an XMI
implementation for this
CCB & CADM
TWG
interface
SYSTEM-FUNCTION
TECHNOLOGY
PERFORMANCE
CCB & AIP
STANDARD
OPERATIONAL-NODE
PHYSICAL-NODE
DATA
INFORMATION
OPERATIONAL-NODE
PHYSICAL-NODE
SYSTEM
DATA
EVENT-TRIGGER
OPERATIONAL-ACTIVITY
INFORMATION
SYSTEM
SYSTEM-FUNCTION
EVENT-TRIGGER
PERFORMANCE
TECHNOLOGY
STANDARD
DARS Federation
OPERATIONAL-NODE
OPERATIONAL-ACTIVITY
SYSTEM-FUNCTION
PHYSICAL-NODE
DATA
PERFORMANCE
TECHNOLOGY
INFORMATION
SYSTEM
OPERATIONAL-NODE
PHYSICAL-NODE
EVENT-TRIGGER
DATA
OPERATIONAL-ACTIVITY
SYSTEM-FUNCTION
STANDARD
CCB & DARS
Users Group
INFORMATION
SYSTEM
PERFORMANCE
TECHNOLOGY
STANDARD
EVENT-TRIGGER
OPERATIONAL-ACTIVITY
PERFORMANCE
SYSTEM-FUNCTION
TECHNOLOGY
STANDARD
* NII briefing slide
9
OMG UPDM RFP Scope





RFP was issued by OMG Sept. 2005
Uses DoDAF v1.0 as a baseline
Incorporates MODAF’s additional views (Acquisition
and Strategic views)
Incorporates additional requirements from DoDAF 1.5
Supports modeling system-of-systems architectures


Systems that include hardware, software, data, personnel,
procedures, and facilities (DOTMLPF & MOD Lines of
Development )
Service oriented architectures and net-centricity
RFP page: http://www.omg.org/cgi-bin/doc?dtc/2005-09-12
10
UPDM RFP Requirements Mandatory

Develop profile that specifies







Metamodel (abstract syntax and constraints)
UML2 Profile
Notation (concrete syntax)
DoDAF and MODAF artifacts
Additional views and viewpoints
Element taxonomy reference
Data interchange
11
Metamodel

Defines:



Key terms and definitions used in the proposed profile
Concepts that are required for the description of
architectures and consistent with those defined in IEEE
1471 and specific architecture frameworks (e.g., DoDAF,
MODAF)
Constraints on elements that ensure connectivity and
integrity of the model
12
SV Metamodel
13
Profile & Notation

Defines:




The selected UML modeling elements using a standard
notation
Their stereotypes
Additional constraints using the profiling mechanism
provided by UML
The relationship of notation to model elements defined by
the metamodel shall be represented in tabular form
14
SV-1 Example
15
Views & Viewpoints

DODAF/MODAF artifacts using UML/SysML

New model elements using MOF QVT, when
no direct diagrammatic representation is
provided for individual DODAF and MODAF
artifacts in UML/SysML
16
Creating the SV-5: An Illustration
of Exported Information
The SystemThreads and SystemEventTraces placed in the OperationalActivityRealization
collaboration provides the information needed for the SV-5
17
UPDM Team Members







Adaptive
Artisan Software
BAE Systems
CSCI
General Dynamics
IBM
Lockheed Martin








Mega International
No Magic
NorthropGrumman
Raytheon
SAIC
Sparx Systems
Thales
Telelogic
18
UPDM Timeline
LOI
Feb 06
Need
Feb. 05
Evaluate
Submission
Vote
Adoption of a
Specification
June 07
RFP
Sept. 05
Initial
Submissions
Dec. 06
June 06
Issue
RFP
March07 June 07
Revised
Submission(s)
Implementation
Evaluate
Submissions
Tools
~ 2008
19
UML Profile for DODAF/MODAF (UPDM)
Roadmap
DODAF v 1.0
(2004)
DODAF v 1.5
Inputs
MODAF
v 1.0
OMG
Kickoff
RFP
issued
1st draft
Submissions
revised
Submission
OMG
Adopts
UPDM
Feb 2005
Sept 2005
June. 2006
March 2007
20
For More Information

DoDAF



MODAF


http://syseng.omg.org/UPDM.htm
UPDM Request for Proposals (RFP)



http://www.modaf.com
Background on UPDM


http://www.defenselink.mil/nii/doc
https://dars1.army.mil/IER/index.jsp
http://www.omg.org/techprocess/meetings/schedule/UPDM_RFP.html
http://www.omg.org/cgi-bin/doc?dtc/2005-09-12
UPDM OMG meeting agendas

http://syseng.omg.org/SE_DSIG_Meetings/
21
Questions?
22
Backup
Metamodel & TaxonomyRelationship


The metamodel defines
Enterprise Architecture
concepts
The taxonomy supports the
metamodel, specializing the
model elements into more
specific items


Acts as a dictionary of
terminology
Allows the metamodel
to be more generic
metamodel
equipment
platform
hosts
system
Taxonomy
weapon system
business system
A system
which has the
capability to…
A system which
manages the…
warship
HR system
accounts system
A system which
manages the…
A system which
manages the…
fighter
aircraft
bomber
etc…
24
Distributed Taxonomies

OWL is designed for the web:
 Allowing references between OWL files at different locations
(e.g. synonyms)
 Allowing one OWL file to specialise definitions in other files
NATO
Taxonomy
Sdfjhsdfjhsdf
sdfjdsfknweiewnmn
dfldsflmc
sdfkmsdm
sdfsdfweo
0fhebhnfefwef
sdfmdfdsfgsdf
sdfsdfgksdfgnf
sdfsdofjnsdf
sdfhsdeidjjd
dsofhsdfoheee
sdadsdwewqffee
Sdfksdjfweewmewewf
AF
Equipment
Taxonomy
DoD Core
Taxonomy
Sdfjhsdfjhsdf
sdfjdsfknweiewnmn
dfldsflmc
sdfkmsdm
sdfsdfweo
0fhebhnfefwef
sdfmdfdsfgsdf
sdfsdfgksdfgnf
sdfsdofjnsdf
sdfhsdeidjjd
dsofhsdfoheee
sdadsdwewqffee
Sdfksdjfweewmewewf
Sdfjhsdfjhsdf
sdfjdsfknweiewnmn
dfldsflmc
sdfkmsdm
sdfsdfweo
0fhebhnfefwef
sdfmdfdsfgsdf
sdfsdfgksdfgnf
sdfsdofjnsdf
sdfhsdeidjjd
dsofhsdfoheee
sdadsdwewqffee
Sdfksdjfweewmewewf
DODAF
Taxonomy
Sdfjhsdfjhsdf
sdfjdsfknweiewnmn
dfldsflmc
sdfkmsdm
sdfsdfweo
0fhebhnfefwef
sdfmdfdsfgsdf
sdfsdfgksdfgnf
sdfsdofjnsdf
sdfhsdeidjjd
dsofhsdfoheee
sdadsdwewqffee
Sdfksdjfweewmewewf
Supplier
Taxonomy
sdfjdsfknweiewnmn
dfldsflmc
sdfkmsdm
sdfsdfweo
0fhebhnfefwef
sdfmdfdsfgsdf
sdfsdfgksdfgnf
sdfsdofjnsdf
sdfhsdeidjjd
dsofhsdfoheee
sdadsdwewqffee
Sdfksdjfweewmewewf
25
Data Exchange


UML profile and meta-model enable XMI for architecture tool
interoperability.
Elements in the XMI exchange file may refer to relevant
taxonomy definitions
Tool A
Tool B
data exchange
structure
XMI
XMI
meaning
Taxonomy
Sdfjhsdfjhsdf
sdfjdsfk nweiewnmn
dfldsflmc
sdfkmsdm
sdf sdf weo
0fhebhn fefwef
sdfmdfd sfgsdf
sdfsdfgksdfgnf
sdfsdofjnsdf
sdfhsd eidjjd
dsofhsdfoh eee
sdadsd wewqf fee
Sdfksdj fweewmew ewf
META
MODEL
26
XMI for Data Exchange


XML is an industry standard
• XMI is XML for model interchange
UPDM requires XML that conforms to a model
• Make use of “vanilla” XMI with heavy use of stereotypes
• Specified by extending the UML meta model
Meta Object Facility (MOF)
UML Meta Model
UPDM Meta Model
stereotype
specifications
XMI for UML
Stereotypes
27