The document discusses IBM Rational Solution for Systems and Software Engineering. It aims to help organizations reduce time, cost and risk of developing profitable products and systems by providing an integrated set of tools, practices and services for specifying, designing, implementing and validating complex products and the software powering them. Key capabilities highlighted include requirements engineering, systems modeling and analysis, quality management, embedded software development, change and configuration management, and collaboration throughout development.
Example: You can see it in the automotive industry, where a typical ford automobile includes 10 million lines of code, more than an F-35 Joint Strike fighter or a Boeing 787 Dreamliner. Now we have entered a next wave of innovation – one we term the wave of Smarter Products and Services. We are looking at an unprecedented conjoining of systems, processes and infrastructure —an accelerated interdependence of the physical, digital, and human. And, what we observe to be a primary driver of this wave of innovation is something everyone in this room knows a lot about: Software. Through software, today’s products and services are increasingly instrumented, interconnected, and intelligent. In fact, software encompasses @ 80% of the innovation that differentiates today’s systems, products and services. The mechanism that powers all this innovation is software and systems delivery.
To stay competitive, companies must transform their business models. Three core competencies they will need are: Software delivery Systems engineering “ System of systems” 1) Software delivery is driving most of today’s innovation. Companies must invest in their software development and delivery capabilities to produce products that are differentiated. Many products look virtually the same on the outside, but the software function inside is what creates competitive advantage. IBM Rational provides an integrated platform for software delivery leveraging a full set of best-of-breed tools, methodologies and best practices. 2) Systems engineering must be done well and efficiently to get high quality products to market with the necessary speed. Gone are the days when it was all about the mechanical design. Today the software and electronics are providing the real innovation and value. The ability to integrate across engineering disciplines (mechanical, software, electronic, electric) is a key competitive advantage. IBM provides a full set of integrated best-of-breed systems engineering capabilities for engineering the “whole product,” including requirements engineering (Rational DOORS), change management and team collaboration (Rational Team Concert and other CCM tools), model-driven systems development (Rational Rhapsody), and quality management (Rational Quality Manager). 3) “Systems of systems” interconnect manufactured products with backend software applications to deliver significant new value to customers. S mart products are converging with conventional information technology to form revolutionary ecosystems that are permanently changing how we work, live and play. Manufacturing and software companies will remain competitive based on how well their products can be integrated into larger “systems of systems,” such OnStar, Google Maps, iTunes, or the smart electric grid. With these opportunities come significant challenges, as “systems of systems” cross multiple organizational, industry, and stakeholder boundaries. This trend presents significant opportunity for Rational and all of IBM to help customers overcome the business and technical issues associated with these large, complex, constantly changing systems.
DAY_01_SYSTEMS_KEYNOTE__v02
DAY_01_SYSTEMS_KEYNOTE__v02
The IBM Rational Systems Engineering (SE) Practices The SE Practices provide a proven starter set for selected aspects of the Systems lifecycle. They can be incrementally adopted. The documentation provides two different workflows, representing two examples on how to combine and use these SE practices – based on system development use-cases or system development operations. Fourteen initial SE Practices are listed below: Release Planning Project Process Tailoring Iterative Development Reviews Shared Vision Elaborate Draft Systems Requirements Specification Build and Validate Use Cases Architectural Analysis - Key System Functions Trade Study – Weighted Objectives Method Architectural Design - Use-Case based Joint Realization Preparation for Downstream Engineering Formal Change Management Test Management The IBM Rational Embedded Software Engineering (ESW) Practices The ESW Practices provide a proven starter set for selected aspects of the Embedded Software lifecycle to complement the SE Practices. They can also be incrementally adopted. Six initial ESW Practices are listed below: High-Fidelity Modeling Real-Time Architectural Design Real-Time Collaboration (“Mechanistic”) Design Real-Time Detailed Design Model-Based Testing Safety and Reliability Analysis The IBM Rational Enterprise Practices The Enterprise Practices provide a proven starter set for selected aspects of overall project management through measurement of performance. They can also be incrementally adopted. Two initial Enterprise Practices are listed below: Managing Performance through Measurements Setting up a Performance Measurement System
DAY_01_SYSTEMS_KEYNOTE__v02
File Name Here.ppt File Name Here.ppt File Name Here.ppt