Presentation is loading. Please wait.

Presentation is loading. Please wait.

May 16, 2007 UPDM – UML profile for DoDAF and MODAF Briefing to the DoDAF WG.

Similar presentations


Presentation on theme: "May 16, 2007 UPDM – UML profile for DoDAF and MODAF Briefing to the DoDAF WG."— Presentation transcript:

1 May 16, 2007 UPDM – UML profile for DoDAF and MODAF Briefing to the DoDAF WG

2 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 2 Introduction to the UPDM specification submission  Background  Approach  Highlights  Deep dive if requested

3 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 3 Background – The Object Management Group (OMG)  OMG is an international industry consortium that produces industry standards using a rigorous technology adoption process –UML, SysML, MDA™, etc.  UPDM Requirements derived from DoDAF and MODAF requirements  UPDM development included broad industry participation from tool vendors and end users, as well as DoD/MOD inputs to requirements  UPDM supports current DoDAF/MODAF requirements and can evolve to meet future needs –Can produce standard DoDAF products –Leverages cross industry standards based approaches (e.g., MDA™,UML, SysML) to enhance tool and architecture data interoperability –MDA™ foundation enables UPDM to evolve with DoDAF v2 and beyond as needs evolve (i.e. SOA) –UPDM is methodology agnostic (structured, OO,..)

4 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 4 June 2006 Sept 2005 Feb 2005 DoDAF v 1.0 (2004) OMG Kickoff RFP issued MODAF v 1.0 March 2007 Three Initial Submissions DoDAF v 1.5 Draft Inputs Unified Submission June 2007 OMG Adopts UPDM Nov 2006 Team 1 & Alpha Merge UST and Telelogic Merge Two Revised Submissions Background: UPDM Timeline – Teams and Submissions Dec 2006

5 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 5 Background – Briefings and Feedback 2007Event JunOMG C4I and Board JunMODAF – TBD - Brussels JunNATO – TBD - Brussels MayDISA - TBD MayImpact Presentation - commercial MayBriefing to DoDAF WG MayBriefing to NCOIC Technical MayJFCOM Presentation AprDoD Architects Conference AprINCOSE Review / Study – Patterns AprBriefing to SAF/XC on UPDM MarOMG C4I Presentation / Review JanBriefing to INCOSE International Workshop JanBriefing to DODAF WG Vol II review session on UPDM 2006Event DecMr. Brian Wilczynski Key Note speaker at OMG’s UPDM info Day DecMr. Tillotson key note speaker at OMG’s Architecture info day (C4I, UPDM, and Software Assurance) NovAFITC presentation OctBriefing to SAF/XC on UPDM OctBriefing to DODAF WG on UPDM SepNCOIC Presentation SepJoint NII and OSJTF briefing to Acquisition M&S WG JulArmy ARCIC workshop on DODAF support for OO/UML FebCoordination meeting with MOD and DoD Sept 05 Briefing on UPDM to OSJTF workshop May 05 Briefing to DODAF WG May 05 Workshop at Mitre with OSD NII, OSJTF, and Army PEO GCS

6 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 6 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) 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 ABC T1 T2 T3 NODES TIME ABC T1 T2 T3 NODES TIME Background: Summary of DoDAF

7 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 7 Acquisition View 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 mapOutputs: DoDAF Views Strategic View Operational View System View Technical View Legacy Systems Standards Prog Plans Cap Audit Inform Inputs: Doctrine & SAGs Background – Summary of MODAF

8 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 8 Approach – Submission Documents UPDMCompliance Level 0 Compliance Level 1 Joint Submissionc4i/ Class Library (xmi) c4i/ Domain Meta-model (xmi) c4i/ c4i/ Profile (xmi) c4i/ c4i/ UPDM Class Library, Domain Meta-model, Profile (HTML) c4i/ Erratac4i/

9 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 9 Approach - Addressing Request for Standard Submission Requirements  Mandatory (Submission Annex A) –[6.5.1] Meta Model (abstract syntax and constraints) (Sections 4 - 6) –[6.5.2] Profile (Sections 4 - 6) –[6.5.3] Notation (concrete syntax)(Sections 4 - 6) –[6.5.4] DoDAF 1.0 and MODAF 1.0 artifacts(Sections 4 – 6 for semantics) –[6.5.5] Additional Views and Viewpoints(Sections 4 & 6 for custom Views and Section 7 on Extensibility) –[6.5.6] Element Taxonomy Reference(Sections 4 & 6 –[6.5.7] Data Interchange(Supplementary Files)  Optional –[6.6.1] Domain Meta Model(Annex C) –Data Interchange Mappings and Transformations(Supported by XMI) –Extensibility to Other Architecture Frameworks(Section 7, SOA Extensions) –Representation of Architectural Patterns(SOA, UML)

10 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 10 Approach  Unified submission –Combines the perspectives of the initial submission teams –Exploitation of both UML and SysML –Compliant specification that addresses the needs of DoDAF and MODAF –Supports both architect and System Engineers perspectives  Domain Metamodel  XMI exports  Working proof of concept –Demonstrated at OMG conference  DoD relevant example included  HTML export of all models

11 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 11 Approach – Principles for Designing UPDM TopicDirectionComment FrameworksDoDAF, MODAF, FEAPlus more AcceptanceOpen StandardMust be widely supported Open Standard DirectionNCO, SOA, System EngineeringTools can import/export legacy ScheduleOn ScheduleUser feedback is best ProfessionsArchitect, Engineer, Developer, moreProfessions interlock and sharing ModelingUML & SysMLModel interoperability and reuse AccuracyProof of ConceptRigorous software engineering method, MDA™ SpecificationModel TransformsGenerate specifications from models GovernanceAgile, team basedConsensus based approach SemanticsDomain Model drives ProfileDoDAF domain model ability to reason InterchangeXMIImport/export to repositories and tools ProfileMDA™Transforms between standards ArchitectureModel OrientedModels with Multiple Views, ad hoc model queries IndustriesWidely applicableDefense, Commercial, Academic

12 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 12 Approach: Role of UPDM Domain MetaModel  DoDAF and MODAF concepts were used as inputs for the UPDM Domain MetaModel  The Domain MetaModel established the context for the UML profile DoDAF MODAF Domain MetaModel UML Profile exampleexample

13 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 13 Approach – Model-Based  As the complexity of a problem increases, the use of modeling becomes necessary to describe both the problem space as well as the solution.  Providing additional DoDAF/MODAF semantics to the modeling experience allows users to create models that exhibit those semantics.  These semantics provide consistency and allow generation of the typical DoDAF/MODAF products as views of the model contents.  The model becomes the repository from which various views can be extracted.

14 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 14 Approach: Profile Conformance  The profile has two conformance levels –Level 0 – all UML may be used –Level 1 – defines SysML-specific extensions to Level-0  We expect models created conformant with Level 0 and Level 1 to be interoperable since –Standard UPDM profile being used –XMI 2.1 specified as the basis for interchange –UML specified as the base language for Level 0 –Limited to the UML4SysML subset –Level 1 extensions based on standard SysML profile of UML UML4SYSML Level 0 UML SYSML Level 1

15 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 15 Transform Models Import & Export Other Profiles Apply External Links URI + model data View Spreadsheet Project Mngt Graphics View Gen. UPDM Profile and Library UML UPDM Domain Meta Model UPDM Profile Meta Model SysML UML4SYSML Level 1 Level 0 SOA Profile IDEF XMI Icons, Attributes BPMN IDEFBPMN Models Approach: The OV-1 for UPDM

16 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 16 Approach: Proof of Concept  Technology Proof of Concept:  Approach was to build and test iteratively –Most of the time this worked –Sometimes we were surprised –Some corner cases of UML were not addressed in the Rational modeling tools –In all cases, we were able to identify the shortcomings and working with engineering, develop workarounds and schedule product fixes  Domain Proof of Concept: –Engaged with team members steeped in DoDAF experience –Applied UPDM profile and modeled real-life example –Finding an unclassified example was difficult!

17 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 17 Approach - Features FeatureComment Capability and EffectsUnification of Strategic, Operational and Service elements Operational to Systems MappingsSystemsNode and OperationalActivityRealization maps to System Functions Service Oriented ArchitectureModel operational nodes, systems and actors as Services External SystemsLinks to taxonomies, requirements, repositories, view generators TraceabilityContext free activities and decomposition of Activities and System Functions CommunityLink Engineers and Architects ReuseOpen Standard Model, import / export, transforms, queries, reporting ValidationOpen Standard Model, queries for validation FEA AlignmentTop down modeling from Enterprise, StrategicMission, Goals and Vision Roles CompetencyRoles, competency, resources and operational nodes Activity ContextsAllocation of activities and system functions to operational nodes and system ReportingDoDAF and MODAF views and ad hoc model queries, export PatternsReusable Asset Specification for pattern repository ExtensibilityViewpoints/stakeholders External references

18 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 18 Errata Summary  OCL stereotype specialization validation  Remove “UPDM” from stereotype names  Fix Architecture View OCL  Several typos  One diagram missing “ownership” line  Other OCL bugs  Added note on patterns and other architectures Minor changes to the specification resulting from validation and testing.

19 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 19 Highlights of the solution – Node and Operational Capability Profile specification metamodel

20 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 20 Highlights of the solution – Comprehensive Traceability Usage example with UML “stereotype” notation

21 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 21 Service Component >

22 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 22 DoDAF Artifact Approach: Deriving the View from the Model  The specification provides support for information needed to deliver all DoDAF products but does not constrain users to use UML or SysML. If the architecture can produce the needed elements, then it is “UPDM compliant” for the view.  The specification provides mechanisms to support export of information to other tools, such as a project management tools.  The specification also supports clear mechanisms for extensions of new views as needed on projects. For example, security, logistics, or service delivery might require additional diagrams.  Annex B of the specification provides a non-normative overview of strategies for delivering products based on the profile elements. The next slide shows portions of the tables included for all artifacts.

23 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 23 The Artifact Guidance in the Specification: OV 5 Example UPDM ElementSignificance to the View ActivityRealization Maps an OperationalActivity to the collection of Systems, people, and Resources used to implement that activity. Effect An Effect is an action that causes a change in the state of some other element, such as an enemy or physical control over space. Some approaches to activity planning stress achieving certain conditions, such as air supremacy or control of strategic points. OperationalTasks and collaborating OperationalNodes will bring about the effect. InformationElement A formalized representation of information used in an operational process. This is the type of information used on the exchange. On activity diagrams, the InformationElement can appear on the input or output pins or as an activity parameter. InformationExchange While the InformationExchange is usually associated with the OV-3, on the OV-5 a user can show information exchanges between Nodes, where the nodes appear as Activity Partitions on the Activity Diagram. Materiel The physical resources used to accomplish a particular mission. In the OV-5, materiel can include physical resources critical to mission success. Each Artifact Has a List of Elements ViewRelationship Details OV-2 The activities annotating an operational Node in an OV-2 map to the OperationalActivities described in an OV -5. Similarly, OV-5 should document the operational Nodes that participate in each OperationalActivity. OV-3 An InformationExchange in OV-3 should map to one or more information flows (an external Input, an external output, or an output from one OperationalActivity mapped to an input to another) in OV- 5, if OV-5 decomposes to a level that permits such a mapping. Above that level of decomposition, a single information flow in an OV -5 may map to more than one InformationExchange (or none, if the information flow does not cross Node boundaries). Note that a physical flow is NOT represented as an information flow. A review of physical exchanges in a model requires a custom view. OV-6 A rule may define conditions that constrain the execution an OperationalActivity in a specific way, or constrain the organization or human role authorized to execute an OperationalActivity. Effects in the OV-6b map to OperationalActivities in OV-5. SV-5 Operational Activities in SV-5 match OperationalActivities in OV-5. Each Artifact Relates to Other Views This is detailed for all artifacts and includes examples from prototypes.

24 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 24 Highlights of the solution – Operational Activity and System Function Link By placing the SystemFunction inside the OperationalActivityRealization collaboration the model has all the information to generate the SV-5.

25 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 25 SV-5, exported from model to external tool (Excel) Highlights of the solution - V-5: An Illustration of Exported Information Dynamic diagrams with system element stereotyped placed in an OperationalActivityRealization provide the information needed for the SV-5 See the UPDM Specification for a more detailed review of examples and artifacts. UPDM provides definitions of needed elements for automation, but it does not specify the implementation of the needed model queries or transformations.

26 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 26 Highlights of the solution - OV-7 Logical Information Model OV-7 Defines Information Model for all Operational Information Flow elements identified within the integrated model and viewed via OV-3 and OV-5

27 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 27 Compliance Level 1…Using SysML Highlights of the solution - SysML Internal Block Diagram Requirements, Problems and Rationale can be attached to any Model Element to Trace Requirements and Capture Issues and Decisions

28 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 28 OV-1 Captures the Operational Context graphically and as Role and Use Case models representing Mission Context, Scenarios and enabling Capabilities Highlights of the solution - OV-1 Representation

29 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 29 OV-5 Activity Diagram captures the behavior defined by OV-1 Use Cases via Operational Activities subsequently allocated to Operational Nodes Highlights of the solution - OV-5 Representation

30 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 30 OV-2 Operational Nodes and Needlines as aggregations of allocated Operational Activities and Information Flows respectively Highlights of the solution - OV-2 Representation

31 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 31 OV-3 Information Exchange Matrix auto generated based on Operational Activity Information Flows Highlights of the solution - OV-3 Matrix Generation

32 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 32 OV-4 Organizations and Roles allocated to each Organization are modeled by UML Composite Structureand SysML and Block Definition Diagrams OV-4 Organizations and Roles allocated to each Organization are modeled by UML Composite Structure and SysML and Block Definition Diagrams Highlights of the solution - OV-4 Representation

33 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 33 OV-6a Captures the Operational Rules allocated to Operational model elements including Nodes, Activities, Flows, Information Elements and States Highlights of the solution - OV-6a Representation

34 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 34 OV-6b State Trace Diagram captures the Operational States and Transitions within Operational Nodes Highlights of the solution - OV-6b Representation

35 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 35 OV-6c Event Trace diagram captures the event flow (messages) between instances of Operational Nodes…synchronized with Operational Activities allocated to Nodes Highlights of the solution - OV-6c Representation

36 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 36 Highlights of the solution - OV-7 Logical Information Model OV-7 Defines Information Model for all Operational Information Flow elements identified within the integrated model and viewed via OV-3 and OV-5

37 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 37 SV-1 Provides the view of the Systems, their connections and data flows, and allocations to Mission Scenarios and Operational Activities Highlights of the solution - SV-1 Representation

38 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 38 Background: Broad Industry, User and Vendor Support  Adaptive  ARTiSAN Software Tools, Ltd.  ASMG  BAE Systems  BCMS Consulting  CSCI  EmbeddedPlus Engineering  EuroStep Group AB  General Dynamics  IBM  Lockheed Martin Corporation  MEGA International  NoMagic  Northrop Grumman  Pathfinder Solutions  Raytheon Company  SAIC  Sparx Systems Pty Ltd  Telelogic AB  THALES Group Unified Submission Supporting Members

39 UPDM – UML Profile for DoDAF and MODAF May 16, 2007 – DoDAF Workgroup and UPDM Team Briefing 39 Conclusion - The Stage is set  Conformant specification that addresses the needs DoDAF and MODAF –Standards based approach will enhance tool and architecture data interoperability –MDA™ foundation enables UPDM evolution to support DoDAF v2 and beyond as needs evolve (e.g., SOA)  Integrates Architecture and Engineering –Exploitation of both UML and SysML  Unified submission –Supported by broad industry consortium of tool vendors and end users  Working proof of concept –Demonstrated at OMG workshop in March Ready for adoption by OMG at meeting in June

40 May 16, 2007 Questions?


Download ppt "May 16, 2007 UPDM – UML profile for DoDAF and MODAF Briefing to the DoDAF WG."

Similar presentations


Ads by Google