9/20/11 Webinar: Saving resources with simulation


Published on

Slides from 9/20 IBM/Alidade Webinar

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

9/20/11 Webinar: Saving resources with simulation

  1. 1. IBM Rational Rhapsody:Saving Resources with Simulations and Prototyping<br />Reduce the Time, Cost and Risk of Developing Profitable Products and Systems<br />
  2. 2. 2<br />360 degreesurround vision<br />Predictive collisionavoidance<br />Adaptive cruise control<br />Driver assistance safety alarms<br />Intelligentnavigation<br />Hybrid and electricvehicle control<br />Smart Products Require Innovative SystemsIncremental value is created by global interconnection across products, systems, applications and networks<br />System of Systems<br />Emergency services, vehicle diagnostics, and GPS / location services<br />Smart gridhybrid / electricvehicle recharging<br />Fleet and trafficmanagement systems<br />Integration of vehicle subsystems into a functioning automobile<br />Collaboration and visibility across diverse teams and disciplines<br />Systems Engineering<br />Software-intensive Subsystems<br />
  3. 3. 3<br />Building a Competency in Systems is ChallengingOvercoming a history of cost overruns, schedule slips and quality issues<br />Poor requirements engineering = failed projects<br />Paper-based and manual processes hinder efficiency<br />Complex architecture is difficult to textually explain<br />Functionality is poorly distributed across components <br />Hardware/software integration is often late<br />Many organizations lack formalized practices<br />Silos of people,process, and projects<br />Organizational Barriers<br />Geographic Barriers<br />Infrastructure Barriers<br /><ul><li>Incompatible tools
  4. 4. Unreliable access
  5. 5. Lengthy on-boarding
  6. 6. Inflexible integration
  7. 7. Weak collaboration
  8. 8. Poor project governance and LOB oversight
  9. 9. Security of IP
  10. 10. Poor communication
  11. 11. Language, culture, time
  12. 12. Process gaps resulting in rework</li></li></ul><li>4<br />Modern Approaches for Describing Systems Are EvolvingTo Better Manage Complexity and Reduce Time-to-market<br />Past<br />Future<br />Specifications<br />Interface requirements<br />System design<br />Analysis & trade-off<br />Test plans<br />Moving from manual methods to a model-driven approach<br />
  13. 13. 5<br /><ul><li>Model Based System Engineering Project (MBSE)
  14. 14. Close collaboration with customers
  15. 15. Facilitated workshops based around prioritized Use Case Analysis
  16. 16. Issues resolved within days/weeks
  17. 17. Traditional ( Textual Requirements )
  18. 18. Regular customer design reviews
  19. 19. Design studies main source of issue resolution
  20. 20. Issues resolved within Weeks/Months
  21. 21. Several Design issues remained at “Design Chill”</li></ul>The solution in practice – real world results<br />
  22. 22. 6<br />$7,600/defect*<br />$960/defect*<br />$240/defect*<br />$80/defect *<br />Requirements Phase<br />Development phase<br />Released Product <br />QA/Testing phase<br />Traditional testing methodologies are insufficient80% of development costs are spent identifying and fixing defects<br />Repair Cost<br />Induced<br />Errors<br />DefectsIntroduced<br />DefectsFound<br />HW/SW integration<br />Test<br />Development<br />Operation<br />Integration<br />*Source: 2008 GBS Industry standard study<br />Defect cost derived in assuming it takes 8 hrs to find, fix and repair a defect when found in code and unit test. Defect FFR cost for other phases calculated by using the multiplier on a blended rate of $80/hr<br />
  23. 23. 7<br />Why use Model-Based Simulation and Test?<br />Model-based specifications are<br />Executable<br />early validation and verification of the designs against requirements<br />Visual<br />improved maintainability and communication<br />Model-driven Testing<br />Enables early and repeated testing<br />Bugs are found early; hence easier to fix with less cost<br />Easy to cross-link requirements, model, code and test data and to synchronize this continuously<br />Required for safety standards, like ISO DIS 26262, DO-178B/C, etc.<br />High degree of automation possible<br />Enables parallel development and test of embedded software<br />
  24. 24. 8<br />Rational Solutions for Systems and Software Engineering Visually refine requirements into a robust system using Rational Rhapsody<br />Model Based Systems Engineering (MBSE): <br />A standards-based practice for the development of complex systems<br />across the mechanical, electronic and software disciplines <br />
  25. 25. 9<br />Key Enabling Technologies of the Rational Rhapsody Solution<br />Model<br />Execution<br />Software- Centric Workflow<br />Requirements Visualization<br />Standards-Based <br />MDD<br />Model-Based Testing<br />Team Collaboration<br />
  26. 26. 10<br />Model Execution<br />Simulate & Animate<br />Validate requirements and design early with continual simulation and testing <br />Analyze system functionality for correctness and to determine next steps<br />Visually demonstrate and communicate intended behavior to customer and stakeholders<br />Execute on the target and animate on the host to verify the application is correct<br />
  27. 27. 11<br />Graphical Execution of State Machines and Activity Diagrams<br />Model Execution<br />Visual highlights of system or software state machines and activity diagrams as model executes.<br />Easily answers questions such as, “What state is the system in? What path was taken to reach that state?”<br />Active State<br />Active State<br />Active State<br />
  28. 28. 12<br />Graphical Execution of Sequence Diagrams<br />Model Execution<br />Visualize message communication using animated sequence diagrams.<br />Sequence Diagram drawn automatically during simulation based on inputs and model behavior.<br /><ul><li>Easily compare specification scenarios to scenarios created from model execution in order to identify inconsistencies.</li></li></ul><li>13<br />View Run-Time Objects and Data<br />View objects created and their data while simulating the system or software.<br />Object<br />Data<br />Run-time <br />Objects<br />Run-time <br />Objects<br />
  29. 29. 14<br />Enhance Simulation with Graphical Panels <br />Model Execution<br />Panels can be created and bound to inputs and outputs of the model for enhanced simulation.<br />LED bound<br />to model output<br />Button bound<br />to model input<br />Button bound<br />to model input<br />
  30. 30. 15<br />Build in Quality from Concept to Launch<br />Model Based Testing<br />System<br />acceptance<br />Requirementscapture & analysis<br />Systems<br />analysis & design<br />(Sub-)System <br />integration & test<br />Module<br />integration & test<br />Model Based Testing<br />Model Based Testing<br /> SW design<br />Ensure Correctness <br />Specification & Design<br />Ensure Correctness <br />Implementation<br />SW implementation<br />& unit test<br />Visual test definition for improved collaboration<br />Automated test execution, monitoring and test architecture creation<br />Early validation of requirements during systems engineering<br />Automate unit and regression testing helping improve software quality<br />Traceability to requirements, model, code and test data <br />
  31. 31. 16<br />Model Driven Testing<br />Rational Rhapsody TestConductorIncrease Productivity through Continual Testing<br />Record simulations often to validate functionality and verify correctness<br />Link to requirements, model, code and test data for traceability <br />Automatically create and execute tests from the design model or target platform <br />Manage test cases using Rational Quality Manager<br />
  32. 32. 17<br />Model Driven Testing<br />Requirements-driven testing<br />Quick definition and execution of model and requirement-aware tests <br />Unit testing and regression testing<br />Reuse design scenarios as test cases<br />Requirement change impact and analysis<br />Know which part of the model or which tests are affected by changing requirements<br />Pass/fail results can be synchronized with RM tool<br />
  33. 33. 18<br />Open Services for Lifecycle Collaboration<br />Rational solution for Systems and Software EngineeringOn-target product and process management via integration on an open platform<br />QUALITY MANAGEMENT<br />Achieve “quality by design” with an integrated, automated testing process<br />Rational Quality Manager<br />REQUIREMENTS MANAGEMENT<br />Manage all system requirements with full traceability across the lifecycle<br />Rational DOORS<br />ARCHITECTURE & DESIGN<br />Use modeling to validate requirements, architecture and design throughout the development process<br />Rational Rhapsody<br />COLLABORATION, PLANNING & CHANGE MANAGEMENT<br />Collaborate across diverse engineering disciplines and development teams<br />Rational Team Concert<br />
  34. 34. 19<br />iPLONSmarter solar power solutions<br />What’s smart?<br /><ul><li>Remote management and control of photovoltaic systems
  35. 35. Collection and analysis of power consumption data</li></ul>Smarter business outcomes<br /><ul><li>Savings of approximately €10,000 per product due to 25% defect reduction
  36. 36. Reduced development time for a new product line by 60% (five months down to two months)</li></ul>How Rational enables smarter products<br /><ul><li>Model driven development to accelerate reuse of subsystems and software
  37. 37. Model driven testing to improve quality and reduce product development cost</li></ul>“Rational Rhapsody enables our system engineers and software developers to improve productivity, quality and communication by abstracting complex designs graphically, automating the development process and finding defects early.”<br />
  38. 38. 20<br />EWE Group – BTC Embedded Systems AGSmarter energy metering for sustainable energy supply<br />What’s smart?<br /><ul><li>Real time visualization of energy usage
  39. 39. Empowering consumers with information to help reduce their energy consumption
  40. 40. Enables consumers to save costs and reduce peak energy loads</li></ul>Smarter business outcomes<br /><ul><li>On time delivery of high quality, robust system
  41. 41. Consumers reduced energy costs by 10% typically
  42. 42. EWE recognized with environmental and innovation leadership awards</li></ul>How Rational enables smarter products<br /><ul><li>Model-based development manages the complexity of developing an interconnected system
  43. 43. Model Driven Testing helps improve quality and reduce product development costs</li></ul>“Rational Rhapsody with TestConductor solution provided all the needed features, functions and workflows to manage complexity and automate testing for on time and high quality delivery of our trio Smart Box Meter system “<br />
  44. 44. 21<br />Ensure Success with Rational<br />Process and methodology<br />Implementation services<br />Training and mentoring<br />Technical services<br /><ul><li>Process framework workshops
  45. 45. Rational Harmony family of Best Practices and Processes
  46. 46. Process training
  47. 47. Adoption quick starts
  48. 48. Deployment support
  49. 49. Project architecture workshops
  50. 50. Project management
  51. 51. Planning support
  52. 52. Escalation/risk mitigation
  53. 53. Product familiarity
  54. 54. Product expertise and specialization
  55. 55. Technology transfer
  56. 56. Adoption mentoring
  57. 57. e-Learning
  58. 58. Measured Capability Improvement Framework (MCIF)
  59. 59. Product optimization and customization
  60. 60. Tool configuration</li></li></ul><li>22<br />Summary<br />Complexity can rapidly increase as you develop products and systems<br />Finding defects too late in the product lifecycle can be very costly and time-consuming<br />IBM Rational’s solution for Systems and Software Engineering:<br />Enables simulation of models and discovery of defects much earlier in the product lifecycle when they are cheapest to fix<br />Builds in quality from concept to product launch<br />Ensure designs and products meet market demands and industry requirements<br />
  61. 61. 23<br />TOP 5 REASONS TO ATTEND<br />Learn the latest solutions and best practices for Systems Engineering, embedded software development, and testing <br />Hands-on technical workshops show how to apply IBM Rational system solutions to help improve design outcomes<br />Innovate 2011 focuses on systems engineering and embedded software development on the Modeling, Architecture and Construction track and newSystems Engineering track<br />Real world results and best practices from customers in A&D, Electronics, Automotive, Energy & Utilities and other industries<br />High-energy Exhibit Hall and IBM Solution Center featuring Innovation Labs and Business Partner Solutions<br />Profit from Software. Everyware.Starting at Innovate 2011. Mark your calendar and register today!<br />Network and gain insight from peers, product developers, product managers, and thought leaders<br />Register now and save $100 with promo code MAC11<br />
  62. 62. 24<br />Learn more at:<br /><ul><li>IBM Rational software
  63. 63. IBM Rational Software Delivery Platform
  64. 64. Process and portfolio management
  65. 65. Change and release management
  66. 66. Quality management
  67. 67. Architecture management
  68. 68. Rational trial downloads
  69. 69. Leading Innovation Web site
  70. 70. developerWorks Rational
  71. 71. IBM Rational TV
  72. 72. IBM Business Partners
  73. 73. IBM Rational Case Studies</li></ul>© Copyright IBM Corporation 2010. 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, Telelogic, the Telelogic 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.<br />24<br />
  74. 74. 25<br />Appendix<br />
  75. 75. 26<br />Domain-Focused Model-Driven Development<br />Standards-Based<br />MDD<br />Raise level of abstraction to help manage complexity<br />More than just pictures – consistency maintained across views<br />Unified Modeling Language – UML 2.x<br />Industry-standard notation for specifying, visualizing, and documenting systems and software designs<br />Systems Modeling Language - SysML <br />Extends/specializes UML to address needs of the Systems Engineer<br />Open standard published by the OMG and INCOSE<br />Sequence Diagrams show collaboration <br />Activity Diagram shows functions and functional flows<br />Use Case Diagram shows high level operation<br />
  76. 76. 27<br />Standards-based modeling <br />Standards-Based<br />MDD<br />Visualize:<br />Requirements<br />Structure<br />Behavior<br />Interaction<br />Constraints<br />Improves communication <br />Maintains consistent information across views<br />Enhances collaboration<br />Industry Standard, Formal Language<br />Unambiguous<br />UML for software/architecture<br />SysML for systems engineer<br />Tailorable <br />Customize for particular domain<br />Safety Analysis, MISRA profiles<br />DoDAF, MODAF, UPDM, MARTE<br />
  77. 77. 28<br />Requirements Visualization<br />Build the right product because the requirements are visible at all times<br />Prove that all requirements (user, safety, regulatory, etc.) were fully satisfied<br />Understand the requirements<br />Analyze stakeholder needs<br />Evaluate coverage and impact analysis<br />Validate the requirements<br />Analyze for correctness and to determine next steps<br />Manage Requirements across Lifecycle and Disciplines <br />
  78. 78. 29<br />Translate Requirements into a System Design<br />Requirements Visualization<br /><ul><li>Build the product right with structural and behavioral analysis and design
  79. 79. Visualize the system
  80. 80. Reduce confusion over requirements
  81. 81. Specify system functionality
  82. 82. Simulate to confirm functionality
  83. 83. Analyze impact of changes
  84. 84. Whether in requirements or design
  85. 85. Trace requirements in either direction
  86. 86. Provide full accountability and understanding
  87. 87. Specify and develop software
  88. 88. Monitor and control the system</li></li></ul><li>30<br />Control the System with Optimized Software<br />Software- Centric Workflow<br />Design efficient embedded source code<br />Specify and create from the system requirements <br />Import, visualize and refine existing C, C++, C#, Java and Ada applications<br />Generate behavior for C, C++, Java, and Ada for embedded targets <br />Unite the architecture and code<br />Simultaneously work with the system design, software and target platform<br />View how a change in any one area is reflected in the others<br />Source Code<br />Architectural View<br />
  89. 89. 31<br />Leverage existing software investments <br />Software- Centric Workflow<br />“Code Centric” workflow integrates legacy code into modeling<br />Visualize structure and behavior of code for better understanding and identify dependencies<br />Visualize interfaces of external code to reference within model<br />Code Visualization - allows continuous model reflection of externally evolved code<br />Code and model are synchronized - Change one view and other changes automatically<br />Class Diagram<br />Flowchart<br />
  90. 90. 32<br />Software- Centric Workflow<br />Full application generation<br />Generate complete C, C++, Java, and Ada applications<br />Comprehensive code generation, much more than code frames<br />Produce construction artifacts such as makefiles<br />Customization of generated code by user or organization <br />Clean, readable, production quality code <br />Rapidly deploy your design onto any target platform<br />Rhapsody provides real-time services such as threading, mutexes, message queues, timers, and more<br />Can scale down to smaller footprint applications<br />Legacy<br />Code<br />Rhapsody Application<br />Linux<br />Vxworks, Integrity, others<br />16 bit/no RTOS<br />RTOS<br />
  91. 91. 33<br />Team Collaboration<br />Collaborate and Communicate throughout Development<br /><ul><li>Collaborate across teams and geographies
  92. 92. Reduce time and risk associated with parallel development
  93. 93. Enable integrated design, sharing and review across diverse engineering teams
  94. 94. Enhance productivity
  95. 95. Share views
  96. 96. Collaboratively debug
  97. 97. Link work items
  98. 98. Develop in parallel with graphical base aware differencing and merging
  99. 99. Automatically generate reports and documentation directly from the design</li>