1. ® IBM Software Group © 2011 IBM Corporation Innovation for a smarter planet Model-Based Agility for Embedded Systems Development Dr. Bruce Powel Douglass, Ph.D. Chief Evangelist, IBM Rational Bruce.Douglass@us.ibm.com Twitter: @BruceDouglass Yahoo: http://tech.groups.yahoo.com/group/RT-UMLhttp://tech.groups.yahoo.com/group/RT-UML IBM: www-01.ibm.com/software/rational/leadership/thought/brucedouglass.html

2. IBM Software Group | Rational software Innovation for a smarter planet Agenda  State of Agile in the Systems Space  High-Fidelity Modeling  Model-Based Testing  Dependable by Design …. With Agile  Does it Work? Case Studies  New Technologies and Approaches in the 21 st Century

3. IBM Software Group | Rational software Innovation for a smarter planet The State of Agile in the Systems Space Typical agile project IBM Agility@Scale™

4. IBM Software Group | Rational software Innovation for a smarter planet 100% Project Delivery Time The Agile Time to Value Curve Build Progress Time to value Waterfall Governance Stovepipe architectures Proprietary tools/methods Time to value Iterative processes Middleware components Mature commercial tools Time to value Agile Processes Arch & Test Driven, Reuse Collaborative platforms

5. IBM Software Group | Rational software Innovation for a smarter planet Addressing misconceptions about agile 1.Agile teams write documentation 2.Agile teams model 3.Agile requires greater discipline than traditional approaches 4.Agile teams do more planning than traditional teams, but it’s dynamic not ballistic 5.Agile is more predictable than traditional 6.Agile scales very well 7.Agile is not a fad, it is being adopted by the majority of organizations 8.Agile can do fixed price, but there’s more effective options available to you 9.Agile processes can be certified to whatever CMMI level you desire 10.Agile methods can be used in the system space for both systems engineering and embedded sw 11.Agile can be used to develop high security/reliability/safety systems

6. IBM Software Group | Rational software Innovation for a smarter planet 6 Embedded Agile: The Harmony™ Process

7. IBM Software Group | Rational software Innovation for a smarter planet 7 Harmony™ for Embedded RealTime Agile Practices  Use dynamic 2-level planning  Incrementally construct/unit test several times per day (nanocycle)  Incremental development (microcycle)  High-Fidelity Modeling  Continuous integration  Dependability analysis/assessment in parallel with development  Avoid defects with defensive development  Apply design patterns Intelligently  Actively manage project risks  Use model-code associativity to automatically maintain model-code in sync Practices are workflows that produce and consume work products to achieve the goals based on principles and concepts

8. IBM Software Group | Rational software Innovation for a smarter planet Use Dynamic Planning  A schedule is always developed with incomplete information  There are things you don’t know  Some of the things you know are wrong or will change  Harmony recommends a two-tier planning approach  Overall schedule plans the set of iterations and their expected content  Each iteration has a more detailed plan whose scope is a single iteration  This is done at the start of each iteration  At the end of each iteration, the current project status is used to update the overall plan Microcycle 2 Iteration plans Project plan plan update Microcycle1 Microcycle 3 Microcycle 4

9. IBM Software Group | Rational software Innovation for a smarter planet 9 Embedded Agile SW Development Nanocycle Continuous Integration Typically 10-30 minutes Unit testing Test Driven Development Incremental High-Fidelity Modeling

10. IBM Software Group | Rational software Innovation for a smarter planet Best Practices for Modern Systems Engineering  High-fidelity model-based engineering (Hi-MBE)  Incremental functional analysis with use cases  Executable requirements modeling with SysML/UML  Test-driven development of system specifications  Integrated safety and reliability analysis  Model-based handoff to downstream engineering  Automated document generation from model artifacts 10 Systems Engineering

11. IBM Software Group | Rational software Innovation for a smarter planet Agile High-Fidelity Modeling

12. IBM Software Group | Rational software Innovation for a smarter planet 12 UMMI – UML Maturity Model Index LevelBenefitFocusTechnologiesResult 5 Optimizing 100%Agile and Engineering Best Practices Model-based testing, nanocycle execution, test driven development, continuous integration Productivity and Quality 4 Executing 70%Model-based verification Model execution, code generation, model-based debugging 3 Behavioral Modeling 30%State and algorithmic modeling State, sequence and activity diagrams 2 Structural Modeling 15%Class and block modeling of structure Class and block diagrams 1 Visualization 5%Visualizing code structures Reverse engineering 0 Code Based Development 0%Manual, time intensive heroic development

13. IBM Software Group | Rational software Innovation for a smarter planet 13 Models and Viewpoints in Model-Based Systems Engineering Functional Model Executable use cases Functional and QoS requirements Dependability Model Safety, reliability, and security analysis FTA, FMEA, FEMCA, Asset Diagram, SAD Control Model Control algorithms, mathematical models Model-based handoff Subsystem Model(s) Mechanical Specification Electronic Specification Software Specification Model and text Architectural Model Subsystems, interfaces, Subsystem use cases/ Requirements Trade-off analysis

14. IBM Software Group | Rational software Innovation for a smarter planet Model-Based Handoff to Downstream Engineering

15. IBM Software Group | Rational software Innovation for a smarter planet Model-Based Testing

16. IBM Software Group | Rational software Innovation for a smarter planet Where Testing fits into the Development Process Harmony/ESW Microcycle (Spiral) Repeats every 4-6 weeks Harmony/ESW Microcycle (Spiral) Repeats every 4-6 weeks Harmony for Embedded RealTime™

17. IBM Software Group | Rational software Innovation for a smarter planet Testing Automation Overview  Requirements-Based test tools allow design-level testing using standard UML sequence diagrams. PassFail %Completion Stimulate......Monitor Scenario- based Test Generation Test Configuration Monitors / Test Drivers Test Cases System Under Test

18. IBM Software Group | Rational software Innovation for a smarter planet TDD – Requirements Based Testing  Uses “Requirements” sequence diagrams to drive the execution and validation of the system

19. IBM Software Group | Rational software Innovation for a smarter planet Continuous Testing in Harmony™ for Embedded RealTime Final acceptance testing at end of project and at key delivery points Design and requirements testing every incremental prototype every 4-6 weeks Continuous informal and formal testing via elaboration and execution every few minutes Software and system integration performed daily or weekly

20. IBM Software Group | Rational software Innovation for a smarter planet Dependable by Design … with Agile

21. IBM Software Group | Rational software Innovation for a smarter planet Dependable by Design … with Agile  Dependability has three aspects  Safety  Reliability  Security  All three cross-cutting concerns must be addressed  Safety and reliability are well established disciplines within the systems space, but …  There is no presence today of requirements and design concepts or tools within the confines of industrial control systems for cybersecurity let alone SoS that incorporate many control systems. These have critical impacts on safety and reliability  Activities must address these concerns at  Requirements  Systems engineering  Software development  It is crucial that we provide tools and methods for reasoning about these concerns at the requirements and design level Ref: Protecting Industrial Control Systems from Electronic Threats by Joe Weiss

22. IBM Software Group | Rational software Innovation for a smarter planet Model-Based Dependability Analysis with FTA

23. IBM Software Group | Rational software Innovation for a smarter planet Linking Dependability Analysis to Reqs and Model Elements

24. IBM Software Group | Rational software Innovation for a smarter planet Security Analysis Diagram  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

25. IBM Software Group | Rational software Innovation for a smarter planet Asset Diagram  An Asset Diagram looks at the semantic relations between roles, authentication, vulnerabilities, and countermeasures. It is a way of representing the security-relevant design elements.  Here it is shown with traceability links to requirements  Assets can be  Physical  Informational  Currency  Resource  Security

26. IBM Software Group | Rational software Innovation for a smarter planet Auto-generation of Dependency-Relevant Summary Data Fault Source Matrix, Fault Detection Matrix, Fault-Requirement Matrix, Hazard Analysis… Traceability improves your ability to make your safety/security case Dependability metadata guides downstream engineering work

27. IBM Software Group | Rational software Innovation for a smarter planet 27 Harmony/SE: Design Synthesis

28. IBM Software Group | Rational software Innovation for a smarter planet Does it Work? Case Studies

29. IBM Software Group | Rational software Innovation for a smarter planet Eaton and UPS The Challenge The Solution - Instructed team in the use of Rhapsody and DOORS - Multiple workshops solidified the system requirements and identify many missing requirements - Using the Rhapsody safety analysis profile, the engineers performed a detailed safety analysis and with trace links to the system architecture and requirements - System engineering model handed off to software and electronics and mechanical eeers for development Developed the hybrid drive train systems engineering model with a combination of high-fidelity modeling and agile methods.  Create series hydraulic hybrid vehicle that can achieve 60-70% fuel emission reduction for challenging UPS drive cycle for the vehicle Results/Accomplishments - Significantly reduced requirements defects before software, electronics, and mechanical engineers got to work - Accelerated progress on the most complex hybrid design by Eaton and perhaps in the world - System successfully achieved its aggressive fuel economy goals (70% improvement) and achieved 40% reduction in CO 2 emissions - Successfully used modeling for both systems engineering and for software development - Used automatic code generation for vehicle software reducing defects and improving time-to-market

30. IBM Software Group | Rational software Innovation for a smarter planet Ikerlan-IK4 The Challenge The Solution  - Adopted Rational Rhapsody and agile model-driven development to model their system architecture  - Use of UML to visual the architecture, couple with SysML allowed them to formulate an overall architecture approach Developed wind turbine models for system and software development using product line engineering tooling to save time to market for product lines  Design and build wind turbines that automatically optimize their performance based on environmental factors Results/Accomplishments  90% reduction in development time for each customized wind turbine model  25% reduction in cost of development for wind turbine control systems  Reduced development time by a factor of 10 for each variation in its product line

31. IBM Software Group | Rational software Innovation for a smarter planet Where do we go from Here?

32. IBM Software Group | Rational software Innovation for a smarter planet Technological Advances for SW Development  Autonomic Computing (AC) systems  Refers to self-governing massively parallel computing inspired by biological computing  Adds agent-oriented goal-directed elements  An agent is an autonomous element that embeds policies that achieves goals specified by rules or minimization of energy functions  Collective Intelligence (COIN)  Related to, but distinct from AC  Attempts to create desired system properties (including QoS) as a set of emergent properties from independent autonomous agents in the same way ant colonies display emergent intelligent behavior  Main obstacle is the selection of local energy functions that produce the desired emergent behavior  Run-time interface adherence  Specification of interfaces with run-time middleware ensuring  Preconditions  Postconditions  Class invariants  See Babel home page as an example of such an IDL https://computation.llnl.gov/casc/components/#page=home https://computation.llnl.gov/casc/components/#page=home

33. IBM Software Group | Rational software Innovation for a smarter planet 33 References