Integrated modeling: Adopting Architecture Frameworks for Model-based Systems Engineering

Transcription

1 Integrated modeling: Adopting Architecture Frameworks for Model-based Systems Engineering Copyright 2014 by No Magic Inc. Published and used by The SSSE and INCOSE with permission. The author or assignee retains the copyright to the materials. Aurelijus Morkevicius

2 Speaker Dr. Aurelijus Morkevičius, Solution No Magic Europe Works with companies such as BMW, Deutsche Bahn, General Electric, Kongsberg Defense and Aerospace, SKA, INDRA, Amadeus etc. Chairman and one of the leading architects for the current OMG UPDM standard development group 2

3 Some History about No Magic 3 3

4 Contents I. Why Architectural Framework is Key to MBSE Success II. Things that get solved if using Architectural Framework III. Architectural Frameworks in Practise IV. Summary 4 4

5 MBSE is about driving systems engineering by modeling & models MBSE is SE! 5

6 Getting Value from Models and Modeling Manage Complexity Preserve knowledge Reuse Automate Picture MODEL 6 6

7 Manage Complexity SKA 2014 The data SKA collected central computer by the SKA will in have a single the day The processing would SKA will take power use nearly enough of about two optical million one hundred fibre years to to wrap million playback twice PCs around on an ipod the Earth!

8 SysML is critical enabler for MBSE 8

9 What is SysML? OMG Systems Modeling Language (SysML) is a graphical modeling language for specification, analysis and design, verification and validation of systems. Modeling language that includes 9 diagrams Dedicated for modeling complex systems that may include hardware, software, information, personnel, procedures, and facilities. 9

10 SysML is neither a modeling methodology nor a framework 10

11 The modeling language is just the language, and must be combined with a methodology to be useful 11

12 Need for a Framework This opens discussions of: how to structure the model what views to build which artifacts to deliver and in what sequence Every company deals with the same issue differently. Some use: defense architecture frameworks: DoDAF, NAF, MODAF MBSE methods: OOSEM, Harmony, SYSMOD, FAS; however, saying there is no need for an architectural framework just doesn t work. 12

13 You always end-up using an architecture framework whether you want one or not, or whether you intend to or not 13

14 If there is no Framework Requirements diagram Use Case Diagram Activity diagram Sequence Diagram System Requirements & Business Analysis Evaluation & Optimization (V&V) System Analysis & Design Package diagram Block Definition diagram Activity diagram Sequence diagram State diagram Detailed Design: Software & Hardware Package diagram Block Definition diagram Internal Block diagram Parametric diagram Sequence diagram State diagram Requirements diagram Use Case diagram Parametric diagram Activity Diagram Sequence Diagram Block Definition diagram Internal Block diagram Package diagram System Integration System Implementation 14

15 15 15

16 System Engineering Standards Sanford Friedenthal, Alan Moore, Rick Steiner, A Practical Guide to SysML The Systems Modeling Language 16 16

17 Ontology ISO/IEC/IEEE42010, DoDAF 17

18 EA Framework Conventions, principles and best practices for the description of architectures established within a specific domain of application and/or community of stakeholders Usually EA Framework consists of: Set of Views and Viewpoints Set of Presentation Artifacts Ontology (Metamodel) or recommendations for modeling languages 18

19 Viewpoints Capability Operational Scenario Capability Configuration 19

20 EA Frameworks: Future Ian Bailey 20

21 Where to read more? 21

22 UPDM is critical enabler to integrate AFs with SysML 22

23 What is UPDM? UPDM is Unified Profile for DoDAF, MODAF, and NAF UPDM is NOT a new Architectural Framework UPDM is not a methodology or a process UPDM is an enterprise modeling language UPDM was developed by members of the OMG with help from industry and government domain experts SoaML BPMN UPDM UML SysML 23

24 SysML AF integration point Capability Operational Scenario SysML 24

25 Contents I. Why Architectural Framework is Key to MBSE Success II. Things that get solved if using Architectural Framework III. Architectural Frameworks in Practise IV. Summary 25

26 What Sometimes Happens in Modeling Practice ~450 Actions ~950 Control Flows Some facts about the project: Model-driven development 50 engineers working 4 years diagrams 30 modules 26 26

27 MBSE Pitfalls: unmanaged abstractions Ambiguous understanding Duplicating information Dependence on technical platform A. Unmanaged abstractions Raise level of abstraction 27

28 MBSE Pitfalls: disintegrated model Difficult to maintain Duplicated/redundant information C. Disintegrated model Make model a single source of data 28

29 MBSE Pitfalls: too complex diagrams Ambiguous understanding Hides incompleteness issues Model = Diagram & View = Diagram B. Too complex diagrams Use different views to represent model data (view >= diagram) 29

30 MBSE Pitfalls: different roles are not involved D. Different roles are not involved Gap between cross-functional teams Single aspect oriented model Bring different roles together Systems Engineers Software Engineers Product/Project Managers Requirements Engineers 30

31 The Recipe for Success think BIG start SMALL and EVOLVE 31 31

32 EA Framework for Unsuccessful Project Created their own 60% Don't know 27% Zachman 13% TOGAF 7% D/MODAF 0% Scott W. Ambler 33

33 Contents I. Why Architectural Framework is Key to MBSE Success II. Things that get solved if using Architectural Framework III. Architectural Frameworks in Practise IV.Summary 34 34

34 Successfully adopted MBSE with EA Frameworks Most experience is generic and does not depend on a particular modeling domain 35 35

35 MBSE Solution for Submarine Warfare Federated Tactical System (SWFTS) Copyright 2013: PennWell Corporation A Common Combat System Deployed Across Multiple Fleets USN: Los Angeles (SSN 688), Ohio (SSGN 726), Seawolf (SSN 21), Virginia (SSN 774), Ohio Replacement (SSBN) RAN: Collins (SSG 73) Federates Multiple Subsystems from Multiple Program Offices and Vendors SWFTS Manages Subsystem Interfaces and System I&T

36 Manage the complexity faced by systems Context Challenges engineers Manage High Variability Between SWFTS Manage Platforms The Complexity Faced by Systems engineers Maximize Reuse Between Baselines Manage Improve High the quality Variability and Between efficiency SWFTS of the baseline Platforms configuration process Maximize Reuse Between Baselines Improve the Quality and Efficiency of the Baseline Configuration Process Solutions Adopt MBSE to Enable a More Efficient Systems Engineering Process Provide Intuitive MBSE tools for Engineers to Develop Complex Systems with Maximum Reuse Adopt UPDM and SysML modeling languages Train Systems Engineers in MBSE Technologies and Tools Results Hierarchy of Models Supporting TEAM SUBMARINE Engineering Reduced Duplication and Inconsistency of Element Definitions Developed Libraries and Catalogs to Improve the Quality and Efficiency of The Baseline Configuration Process 13% Savings to SE from MBSE 25% in Capability Definition Another 10% over DOORS in Baseline Management Savings Seen in 4th Year 2 Years to Implement Model 1 Year Transition Overlap with Current Process ROI Copyright 2012 Net Resources International, a trading division of SPG Media Limited

37 Workflow in Defence Contracting Authority Contractor/ Sub-Contractor 38

38 Contents I. Why Architectural Framework is Key to MBSE Success II. Things that get solved if using Architectural Framework III. Architectural Frameworks in Practise IV.Summary 39 39

39 Top 4 Benefits Architectural Frameworks provide 1. Raise level of abstraction 2. Make model a single source of data 3. Use different views to represent model data (view >= diagram) 4. Bring different roles together 40

40 The Recipe # 1 for Success A good beginning makes a good end! 41 41

41 The End Thank You for Attention! Questions??? Let s Keep in Touch! Aurelijus Morkevicius Solution No Magic Europe Mobile: aurelijus.morkevicius@nomagic.com LinkedIn: