1. ® IBM Software Group © 2014 IBM Corporation Innovation for a smarter planet MBSE for Complex Systems Development Dr. Bruce Powel Douglass, Ph.D. Chief Evangelist Global Technology Ambassador IBM Rational Bruce.Douglass@us.ibm.com Twitter: @IronmanBruce

2. IBM Software Group | Rational software Innovation for a smarter planet Continuous Engineering 2

3. IBM Software Group | Rational software Innovation for a smarter planet Agenda 3 Dependability Analysis Model-Based Architectural Specification Handoff from Systems Engineering Model-Based Requirements Engineering

4. IBM Software Group | Rational software Innovation for a smarter planet What do we need from Models? Visualization Of structure, behavior, functionality, requirements, code, and design Understanding Different aspects of requirements, design, and implementation Communication Among many stakeholders with different concerns and points of view (designers, testers, users, managers) Consistency Of many work products done by different people at different times. Includes customer needs, requirements, designs, and code Provability Demonstrating the correctness of your requirements, design and code Reusability Save time by reusing existing IP in new systems quickly, easily, and correctly Adoptability Be able to easily move from a code-based to a model-based approach

5. IBM Software Group | Rational software Innovation for a smarter planet Modeling 5 Drawing Don’t worry if it’s right or not, just get the basic concept Capture deep meaning (semantics) Use a precise language Don’t worry if you “misuse” a drawing – it’s just a picture! Once you’re done drawing, then go do the “real work” Verify the model with review (secondarily) “Verify” with quick discussion (review) Sketch out an idea Generate any needed documentation from the model repository Store underlying semantics in model repository Verify the model is exactly right through execution and/or formal methods Foundational concept

6. IBM Software Group | Rational software Innovation for a smarter planet So What IS a Model in MBSE then? 6 Modeling is the development of a semantically correct set of engineering data of relevant systems and their properties Models have scope Models have purpose Models have accuracy Models have precision Models are data Models have views (e.g. diagrams) Diagrams have singular purpose Diagrams answer questions Diagrams support specific reasoning Models are verifiable Diagrams show subsets of eng. data

7. IBM Software Group | Rational software Innovation for a smarter planet Syntactic Verification Semantic Verification Syntactic Verification – “well-formed” (compliance in form) Performed by quality assurance personnel Audits – work tasks are performed as per plan and guidelines Syntactic review – work products conform to standard for organization, structure and format Verification of engineering data Semantic Verification “correct” (compliance in meaning) Performed by engineering personnel Three basic techniques Testing – requires executability of work products, impossible to fully verify Formal methods – strongest but hard to do and subject to invariant violation Semantic review (subject matter expert & peer) – most common, weakest means 7

8. IBM Software Group | Rational software Innovation for a smarter planet Good models are verifiable via execution and formal analysis 8

9. IBM Software Group | Rational software Innovation for a smarter planet Harmony Process for Agile MBSE 9

10. IBM Software Group | Rational software Innovation for a smarter planet Harmony Process for Agile MBSE 10

11. IBM Software Group | Rational software Innovation for a smarter planet Harmony aMBSE: System Requirements Def & Analysis 11

12. IBM Software Group | Rational software Innovation for a smarter planet Harmony: Flow-Based Analysis 12

13. IBM Software Group | Rational software Innovation for a smarter planet Harmony: Scenario-Based Analysis 13

14. IBM Software Group | Rational software Innovation for a smarter planet 14 System Functional Analysis Key Activities  Functionally analyze your use cases  Create scenarios those show the flow of system behavior as per requirements  Build normative state machine representing the use case  Execute and analyze model / requirements  Identify missing, incomplete, inaccurate, and inconsistent requirements  Update System Requirements  Update traceability  Update Verification Plan  Manage Work  Manage Change

15. IBM Software Group | Rational software Innovation for a smarter planet Functional Analysis via Executable Requirements? A functional requirement is a specification of an input-output control or data transformation A quality of service requirement is a specification of how well a control or data transformation is achieved Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall be “real good” and “very fast” Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation. Requirement Control surfaces shall be updated every 10 ms +/- 2 ms with an accuracy of.5 cm and a latency of no more than 1 ms Poor requirements Much better requirements Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation. Requirement Cyberattcks shall be detected within 10 ms on onset and result in active security measures including incident reports. 15 Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation. Requirement The system shall perform error correct and detection during initialization and operation.

16. IBM Software Group | Rational software Innovation for a smarter planet Example: Air Control Surface Enactment System (ACES) 16

17. IBM Software Group | Rational software Innovation for a smarter planet Build Model Context: Starting Point (Use Case Diagram) 17

18. IBM Software Group | Rational software Innovation for a smarter planet Allocation of Requirements to use cases 18

19. IBM Software Group | Rational software Innovation for a smarter planet Build Model Context: Starting Point (Context Diagram) 19 Block representing the use case Block representing an actor Interface (operational contract) between actor and use case

20. IBM Software Group | Rational software Innovation for a smarter planet 20 Sequence diagram show actor-system interaction

21. IBM Software Group | Rational software Innovation for a smarter planet 21 Sequence diagram show actor-system interaction

22. IBM Software Group | Rational software Innovation for a smarter planet 22 State machine defines all possible scenarios for a use case (and it executes and is formally analyzable too)

23. IBM Software Group | Rational software Innovation for a smarter planet 23 State machine defines all possible scenarios for a use case (and it executes and is formally analyzable too)

24. IBM Software Group | Rational software Innovation for a smarter planet 24 State machine defines all possible scenarios for a use case (and it executes and is formally analyzable too)

25. IBM Software Group | Rational software Innovation for a smarter planet Running the Specification Model (Sunny Day) 25

26. IBM Software Group | Rational software Innovation for a smarter planet Agenda 26 Dependability Analysis Model-Based Architectural Specification Handoff from Systems Engineering Model-Based Requirements Engineering

27. IBM Software Group | Rational software Innovation for a smarter planet Integrated Safety and Reliability Analysis 27  Fault Tree Analysis (FTA) connects hazards with logical combinations of events, conditions, errors, and faults  Allows you to identify  Effects of combinations of conditions and events on safety  Safety measures  Safety requirements  Impacts of architectural, technological, and design choices on safety Screen shot of the UML FTA Profile

28. IBM Software Group | Rational software Innovation for a smarter planet Screen shot of the UML Security Analysis Profile Model-Based Threat Analysis  Security Analysis Diagram (SAD) is like a Fault Tree Analysis (FTA) but for security, rather than safety  It looks for the logical relation between assets, vulnerabilities, attacks, and security violations  Permits reasoning about security  What kind?  How much?  Risk assessments  Cost of security penetration  Adequacy of countermeasures  Who has access to assets 28 Screen shot of the UML Security Analysis Profile

29. IBM Software Group | Rational software Innovation for a smarter planet Agenda 29 Dependability Analysis Model-Based Architectural Specification Handoff from Systems Engineering Model-Based Requirements Engineering

30. IBM Software Group | Rational software Innovation for a smarter planet Harmony Process for Agile MBSE 30

31. IBM Software Group | Rational software Innovation for a smarter planet Allocate Use Cases to Subsystems 31

32. IBM Software Group | Rational software Innovation for a smarter planet 32 Systems Architectural Design Key Activities  Evaluate architectural selections with trade studies & select architecture  Allocate requirements to identified architectural elements  Detail subsystem requirements  Allocate elements of control laws to subsystems  Detail logical interfaces between subsystems  Update dependability analysis  Update traceability  Update verification plan  Manage work  Manage change

33. IBM Software Group | Rational software Innovation for a smarter planet Systems Architecture (Context) 33

34. IBM Software Group | Rational software Innovation for a smarter planet 34 System architecture as Block Definition Diagram

35. IBM Software Group | Rational software Innovation for a smarter planet System Architecture as Internal Block Diagram 35

36. IBM Software Group | Rational software Innovation for a smarter planet System Architecture as Internal Block Diagram 36

37. IBM Software Group | Rational software Innovation for a smarter planet Agenda 37 Dependability Analysis Model-Based Architectural Specification Handoff from Systems Engineering Model-Based Requirements Engineering

38. IBM Software Group | Rational software Innovation for a smarter planet Auto-generation of summary documentation from models 38 Hazard Analysis Documents are generated automatically from engineering work in models Typical auto-generated documentation includes  Traceability matrix  Hazard Analysis  FMEA / FMECA  Cyberphysical threat analysis table  Interface Control Document  Design Description  Architecture Notebook

39. IBM Software Group | Rational software Innovation for a smarter planet 39 References New 2 nd Edition