Your SlideShare is downloading. ×
0
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
OMG UML Profile for the
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

OMG UML Profile for the

973

Published on

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
973
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
44
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×