Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Discover DoDAF problems early in the lifecycle with model execution


Published on

How to develop DoDAF architectures that are executable, providing verification of understanding of architecture requirements and validating architecture interfaces.
Modelling is based upon the UPDM 2.1 profile as implemented in IBMs Rhapsody Tool.

Published in: Government & Nonprofit
  • Hey guys! Who wants to chat with me? More photos with me here 👉
    Are you sure you want to  Yes  No
    Your message goes here

Discover DoDAF problems early in the lifecycle with model execution

  1. 1. © 2016 IBM Corporation Discover DoDAF problems early in the life cycle with model execution Graham Bleakley PhD. Solution Architect, Unleash the Labs Aerospace,Defence and Automotive
  2. 2. © 2016 IBM Corporation 1 Contents  Introduction to Continuous Engineering  Applying Continuous Engineering to Architecture development and SoS modeling  Executable Modeling in DoDAF (Rhapsody)  Activity Diagrams  Statecharts  The CE infrastructure and how it supports large Architectures and SoS modeling  Managing requirements (DNG, Design Manager)  Understanding the impact of change (RELM)  Impact Analysis  Views  Task planning and change management (RTC)
  3. 3. © 2016 IBM Corporation 2 Continuous engineering is about game-changing capabilities Continuous engineering is an enterprise capability that speeds delivery of increasingly sophisticated and connected products by helping businesses to evolve their engineering practices to adapt to the accelerating pace of business change.
  4. 4. © 2016 IBM Corporation 3 Unified Profile for DoDAF and MODAF  Not a new framework but an Implementation of a UML/SysML based profile that brings together DoDAF, MODAF and NAF to help interoperability  UPDM is a standardized means of  Capturing the operational aspects and specification of Systems of Systems, and Systems as it is based upon SysML  Understanding how the development of these resources map to capabilities and acquisition programs  IBM is a founding and leading member of the UPDM group at the OMG
  5. 5. © 2016 IBM Corporation 4 Quality managementAnalysis, design and prototypingRequirements management Workflow, Planning, Task & Change Management Improving the quality of architectures using Continuous Engineering Engineering context Market Analytics System Verification and Validation System Test System Requirements System Design Deployment/ Release to Mfg. Customer Requirements Operations and Maintenance Implementation Agile Software Engineering Electrical/ Electronics Design Mechanical Design Iterative
  6. 6. © 2016 IBM Corporation 5 Systems of Systems (SoS) architecture and Continuous Engineering  Developing systems of systems implies an integrated approach to requirements, architecture, test and change management  OSLC  SoS architectures should be tested and validated as it improves architecture quality  Test interface requirements  Understand functional behavioural requirements  Evaluate non functional requirements  DODAF 2 implemented in the IBM Continuous engineering platform  DNG/DOORS requirements management  Rhapsody Design Manager for executability  Rational Team Concert for Process Planning and Change Management  Rational Quality Manager for test  RELM for trace and impact analysis
  7. 7. © 2016 IBM Corporation 6 Developing Executable architectures using DoDAF 2  DoDAF 2.0 profile in Rhapsody  Based upon OMG UPDM 2.1 Specification  Based upon SysML  Provides capabilities for creating executable models  Activity diagram execution  Statemachine execution  Evaluation of non-functional requirements using Parametric analysis  Ease of developing consistent interfaces  Modified SE toolkit allows it to work with DoDAF and MODAF UPDM Profiles
  8. 8. © 2016 IBM Corporation 7 Activity diagram execution  Based on Token Flow Semantics (petri nets)  For a token to be generated from an action there must be a token on each input edge.  If you are in the Check Water Tank action what will happen in the next simulation step if water OK is true ?
  9. 9. © 2016 IBM Corporation 8 Question  If you are in the Check Water Tank action what will happen in the next simulation step if water OK is true ?  Alert User-> Check Water  Boil Water  Stay in Check Water Tank
  10. 10. © 2016 IBM Corporation 9 Activity diagram execution  Based on Token Flow Semantics (petri nets) ✔ It will seize at the Check Water Tank  For a token to be generated from an action there must be a token on each input edge
  11. 11. © 2016 IBM Corporation 10 Operational Activities/Functions  Operational Activities/Functions are Activities in their own right  They can be reused  An OV-5b or SV-4 uses references to OperationalActivities or Functions  Create calls to these elements on the OV-5 or SV-4  Use the Create Activities From Actions  Automatically creates the underlying OperationalActivity or Function
  12. 12. © 2016 IBM Corporation 11 Model Structure is Important !!  IT IS MORE IMPORTANT FOR EXECUTABLE MODELING  Activities and activity diagrams need an owner that can be made executable  In Operational Views it is a Logical Architecture or Performer  In System Views it is a PhysicalArchitecture or System  This is the root of the scope of the execution  The diagram can have swimlanes or not
  13. 13. © 2016 IBM Corporation 12 Executing the Activity diagram (1)  The activity diagram is executed by right clicking and selecting simulation  Automatically does a number of checks and generates the underlying code  Correct the errors !!  Spaces in the name of the call behavior or action  Missing Else Statements on decision nodes  Incorrect use of merge nodes  Non-mutually exclusive decision nodes
  14. 14. © 2016 IBM Corporation 13 Executing the Activity diagram (2)  Use the animation toolbar to run the simulation  Do not use “Go” or “Go idle”  DO USE “Go Step”  You will see tokens flowing  You will start to understand the simulation  You can use activity diagrams to represent the behavior for each architectural element
  15. 15. © 2016 IBM Corporation 14 Statechart Execution  If you can build executable models in Rhapsody you can build them in DODAF 2.0  STRUCTURE THE MODELS CORRECTLY  Build a block hierarchical version of your architecture  Build a structural version of your architecture  Defining consistent interfaces  Use the activity diagram to define sequences  Use the SE-Toolkit create ports and interfaces to create a consistent set of Ports and interfaces  Modified SE-Toolkit hep file  Located on the Rational Solutions Process Assets web page   Create statemachines for each “Part” taking a role in the simulation  Possible to test them separately using the rapid simulation  Helps identify semantic incorrectness
  16. 16. © 2016 IBM Corporation 15 Structuring the models  Create an block hierarchical version of the architecture (a BDD)  Creating the composition relationship creates Parts  The Parts are of the correct type  Create a structural version of this diagram( an IBD)  Make sure it has an owning instance
  17. 17. © 2016 IBM Corporation 16 Define Consistent Interfaces  Use a White Box Activity Diagram to derive scenarios  Add the SE toolkit profile and apply the HarmonySE stereotype  Set a package to store interfaces using the ”InterfacePkg” dependency  Apply the SE Toolkit “create ports and interfaces” to the seqeunce Modification of the SE-Toolkit HEP file  Link structural elements together with the appropriate connectors  OV-2 = Needline  SV-1 = ResourceInterface
  18. 18. © 2016 IBM Corporation 17 Creating the component and simulating (1)  Create a component in the SysML part of the model  Beneath the DoDAF 2 Architecture structure  Make sure it is correctly scoped  Include all the parts and elements typing the parts  Make sure animation is enabled  Use Generate Make Run to generate
  19. 19. © 2016 IBM Corporation 18 Creating the component and simulating (2)  Correct ALL  Spelling mistakes (most likely cause of issues)  Syntax  Assignment  If then else  Case statements  Non mutally exclusive decision nodes  Run the simulation  Initialize with Go-Step then use Go Idle,  More controllable than activity diagrams  Validate behavior by generating sequence diagrams
  20. 20. © 2016 IBM Corporation 19 Parametric Execution  Rhapsody 8.1.3 added the ability to build Parametric diagrams into UPDM  Provides the ability to carry out evaluation of non-functional requirements  Basic usage is with Matlab and Maxima  More advanced forms with other third part products  Model Center, phoenix integration
  21. 21. © 2016 IBM Corporation 20 Quality managementAnalysis, design and prototypingRequirements management Workflow, Planning, Task & Change Management Improving the quality of architectures using Continuous Engineering Engineering context Market Analytics System Verification and Validation System Test System Requirements System Design Deployment/ Release to Mfg. Customer Requirements Operations and Maintenance Implementation Agile Software Engineering Electrical/ Electronics Design Mechanical Design Iterative
  22. 22. © 2016 IBM Corporation 21 Continuous Engineering and SoS Architecture development:-the bigger picture Need to understand  What is driving the architecture development  Managing change  Understand internal model relationships UPDM is on Design Manager  Link to requirements in DNG/DOORS  Link to Workitems in RTC  Manage Process in RTC using DODAF process template  Impact analysis in RELM
  23. 23. © 2016 IBM Corporation 22 Working with tools  Set up a Lifecycle project  links DNG, DM, RTC together  Create and add a RELM project to the lifecycle project  Created some high level vision requirements in DNG  Create a collection
  24. 24. © 2016 IBM Corporation 23 Rhapsody and DNG  Opened the collection in Rhapsody Design Manager  Create OSLC Satisfactions and refines from RDM to DNG requirements  Linked to capabilities
  25. 25. © 2016 IBM Corporation 24 Understanding the impact of change  UPDM has a very good information model  It controls the consistency of the traceability  Makes it easy to create impact analysis views across the layers,  See:- veloperworks/communit y/blogs/invisiblethread/e ntry/learn_to_love_your _information_model?lan g=en  Small changes in a model can impact several parts of the architecture
  26. 26. © 2016 IBM Corporation 25 Use Filters and Profiles  Traverse controls the level of upstream and downstream connections  Filters allow you to select a set of elements to appear on a diagram  Filters can be applied to Profiles
  27. 27. © 2016 IBM Corporation 26 Views in RELM  Artifact containers make it easy to create complex views on the information in the architecture  Dynamically Populate based upon UC selection  Can be applied to UPDM  Needs some customisation as native UPDM elements not exposed in RELM currently
  28. 28. © 2016 IBM Corporation 27 Governed by RTC  RTC provides the task planning and Change Management  DODAF process template  Process guidance from RMC  Linked to work items  Intend to update to include details of “how”  Workitems linked to changesets in DM
  29. 29. © 2016 IBM Corporation 28 Benefits of the IBM CE platform when applied to DoDAF 2  Provides a means to develop consistent and high quality DoDAF 2 architectures based upon simulation in Rhapsody Design Manager  Improves the quality of those architectures by  Simulating to understand behavior, define interfaces, validate interfaces, develop test patterns for implements  Using executable parametrics to evaluate potential implementation solutions  Process governance and architecture development is improved by developing architectures in a controlled way, using  DNG or DOORS to manage requirements that can be linked directly to the architecture elements  Managing the test patterns for SoS verification using Rational Quality Manager  Managing the process of developing DoDAF 2 architectures through the use of Rational Team Concert  Managing collaborative develop through the use of Design Manager  Understanding the impact of change through the use of Design Manager and/or RELM
  30. 30. © 2016 IBM Corporation 29 © Copyright IBM Corporation 2016 All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. Also see:- based-approach-to-the-development-of-updm-architectures
  31. 31. © 2016 IBM Corporation 30 Danse  European project to evaluate the benefits of Executable Enterprise Architectures  Used UPDM 2.0 as its framework for defining the architecture  Integrating a variety of models from different tools  Based upon FMI integration
  32. 32. © 2016 IBM Corporation 31 Benefits of Activity diagram simulation  Start to understand the overall flow of behavior across the architecture  At Black Box level it helps with the overall  Mission planning  Use case analysis  At White Box level it helps with  Defining interfaces  Understanding message flows and data between Performers and/or Systems  Approach is compatible with SysML  Improves the quality of the architecture  Helps with understanding the operational and systems behaviour at an abstract level
  33. 33. © 2016 IBM Corporation 32 Benefits of State Chart Execution  Verifies Interface definitions between Performers/Systems  Helps prove the interoperability of the performers/systems from a functional perspective • Performers/Systems can be captured as legacy parts of the architecture so the behavior is AS-IS  Provides an abstraction specification of the behavior of a Performer or System  Important at the Performer level as it helps drive the operational behavior and Standard operating procedures for new operational scenarios or capabilities  Important at the Systems level as it defines the specification and expected behavior of the system or platform that needs to be developed  Provides sets of sequence diagrams as patterns that the implementation can be tested against  Compliant with SysML so it is possible to trace back SysML models to the DoDAF Systems level definition of the System being developed
  34. 34. © 2016 IBM Corporation 33 Statechart Execution Creating an executable model  Create a component  Make sure it is scoped correctly Make sure the behavior is syntactically correct  Generate Make Run (GMR) first checks check model correctness from a syntactic perspective  Use action language, this will help with  Spelling mistakes  Incorrect Syntax Drive the simulation from the simulation menu  Bring up animated Sequence diagrams  Bring up animated Statecharts