Hide Notes 

Slide 1: ® IBM Software Group Best Practices for Component-based Asset Reuse With Synergy and Change © 2008 IBM Corporation
Slide 2: IBM Software Group | Rational software Agenda  Why Software Reuse?  How is Software Reuse achieved with Component-based Development?  Where do Synergy and Change help?  What are the Best Practices Patterns for CBD? (with customer examples)  Conclusion and Q&A and
Slide 3: IBM Software Group | Rational software Software Reuse - background • Reuse yields software Economies of Scale • Goal is to increase the productivity, quality, and time-to-market in software development thanks to the deployment of both standard componentry and production automation • Concept of Reuse is not new – approaches to achieving it keep evolving
Slide 4: IBM Software Group | Rational software Number of mobile phone models 35 30 25 20 15 10 5 0 Standard Development Practices Reusability driven Engineering time Nokia is able to produce 25-35 phone models per year (instead of 4-6) because of Reusability Engineering practices Source: Software Architecture in Practice – Len Bass, Paul Clements, Rick Kazman
Slide 5: IBM Software Group | Rational software 100% 200% 400% Motorola CBSE sphere Motorola observed 400% productivity improvements in a family of one-way pagers Source: Software Architecture in Practice – Len Bass, Paul Clements, Rick Kazman
Slide 6: IBM Software Group | Rational software Reuse benefits in action . . . contd.  The US National Reconnaissance Office required 10% less development resources and reported 90% fewer defects with a family of Satellite Ground Control Systems  HP reported a time-to-market reduction by a factor of 7 and a productivity increase of a factor of 6 in a family of printers  Cummins - Reduced the time it takes to produce software for a Diesel engine from 12 months to about 2 weeks
Slide 7: IBM Software Group | Rational software Understanding Reusability
Slide 8: IBM Software Group | Rational software The evolution of Reuse: Component Based Development?  Component Based Development (CBD) provides a more powerful and easier-touse level of reuse than earlier approaches  Began formally in 1968; became mainstream in the 1980s  Lets you manage complexity in a versatile fashion  Benefits are enormous, if done right:  Lower cost  The components start to become more valuable over time  Agility in practice and responsiveness  Quality - risk mitigation, trust  Reduced time-to-market (reduced testing times, faster implementation, distributed development, etc)  Higher ROI through shorter delivery cycle times  More reliable software  Reduced maintenance costs  Guaranteed QOS
Slide 9: IBM Software Group | Rational software Component-based Development scope  Simplification Removing one or more steps from an unnecessarily complicated process, or reducing unnecessary variety in the process.  Integration Joining two or more previously unconnected or uncoordinated processes into a larger coordinated process  Transformation Creating a radically new process Telelogic Synergy and Change can help you meet any of the above initiatives
Slide 10: IBM Software Group | Rational software How does CBD relate to SOA? Services: Intelligent assemblies of components hierarchies Component Reuse 73% of CIOs see SOA as a business strategy for greater agility 47% use SOA for “strategic business transformation” SOA-based applications will double in 2 years – how do you control Business Risk? Source: IDC's Software Developer Network Survey, 2007
Slide 11: IBM Software Group | Rational software CBD Challenges  Balancing long-term reference architecture needs vs short-term development progress  Managing system evolution - frequency and Impact : Requirements, Lifecycles, Regulations, Technologies, Tools, Languages and Methodologies  Arriving at Component Granularity for system[s] under development  Managing Versions, Upgrades, Configurations, Platforms, and Dependencies  Balancing Testing and Quality Assurance with complex Release and Maintenance cycles  Modeling real-world scenarios through the inherent abstract nature of domain  Designing for replacing proprietary components with Standard ones  Managing Organizational impediments – design-centered, economic and cultural "Reusing other people's code would prove that I don't care about my work. I would no more reuse code than Ernest Hemingway would use other writer’s paragraphs” Software Engineer, Apple Corp
Slide 12: IBM Software Group | Rational software Telelogic Synergy – Pattern-based Configuration Management  Out of the box and customizable CM workflows  Generalize best development practices across the organization assigned or all completed tasks for OW N ER for release RE LEA SE collaborative pr ojects completed tasks for release RE LE AS E for  Task Based CM  Configuration consistency  Project understanding and visibility  Status reports and audits  Roll-back and re-work Collaborative Development all completed tasks for r elease RELE AS E all system testing tasks for release RE LEA SE Integration Testing Syst em Testing Insulat ed Development Lat est Baseline Other Purposes are available Integration Testing Baseline Syst em Testing Baseline  Fully integrated with Telelogic Change  Change Request Based CM
Slide 13: IBM Software Group | Rational software Leading Imaging and Printing Technology Conglomerate - Oce Reengineering Software Reuse and Componentization with Telelogic Synergy Customer Success  Enhanced team communication and collaboration  Master Component Repository  Standard, automated patterns for linking partner ecosystem  More responsive organization Accelerated delivery of products Lower Total Cost of Ownership Reduced risk of rework and project delays Business Challenge  Organizational transformation  Needed to evolve CBD approach and methodology in order to optimize cost and time-to-market capabilities.  Business Partner communication “Using Telelogic Synergy and Change, implementing our vision of the software reuse paradigm was much faster even with very limited resources.”
Slide 14: IBM Software Group | Rational software Synergy: Process definitions 14
Slide 15: IBM Software Group | Rational software E.g. Built-in Processes and creating your own  See the URL for the manually created diagram.  Select purposes for the release.  Select which process rule should be used for the available purposes.  Note: You can have multiple process rules for each purpose. 15
Slide 16: IBM Software Group | Rational software Telelogic Synergy - Effective CBD through SCCM support  Controlling exactly what component is published where  Finding all consumers of a given component  Customization of source components and integrating these changes into source component releases  Identification of published vs. internal components  Establishing Reuse mechanisms  Monitoring feature interaction and testing prior to production build  Managing the process of component sharing
Slide 17: IBM Software Group | Rational software Component-based Patterns support  Primary: Controlled Update Implement Stability Large number Implement Components of consumers Test  Primary: Incremental Update from published Components Test Integration baselines Develop Scripts Classes, Shells, & Code Build/Revise Application Components Regression Scripts Legacy Assets Reverse Engineer  Primary: Incremental UpdateDefine UML Activity Diagrams Design BPMN XMI Process Model Simulate  Variation: Define Bus. Process BPEL Incremental Model Update with Requirements active Speed Collaborative Work Limited number of IT Focused consumers development Requirements ofDefine subcomponents Compliance Synergy: Process Tailoring training Business Focused Detailed Presentation available on the sales corner
Slide 18: IBM Software Group | Rational software Example CBD Best Practices at customer sites  A large application composed of many components is developed iteratively and rapidly with all components on the same release cycle.  A large application integrating components having their own release cycle, and having dependencies with other evolving components.  Products development projects share components, each project may have the need to modify the components they consume.  A very large project divided in sub-projects that can impact any component of the software application and demonstrates management of parallel development streams and their continuous integration.
Slide 19: IBM Software Group | Rational software Change Management and CBD Location 1 modifiable  Enables breakdown of more complex work into smaller units of work and more control over the organizations development work flow.  A Change request is related to an application  The Change request can require modifying several components.  Each component can be maintained by a different team in a different location. => Use of Child CRs to control the change process at the component level in Application CR 226 modifiable in component 1 CR 225 Child Parent CR 227 modifiable in component 2 Child Location 2  Synergy allows to control which CRs belong to a specific Build
Slide 20: IBM Software Group | Rational software Summary: How Synergy lets you meet CBD challenges  Best Practices for Developing Components and Software Reuse  Native support for a layered architectural approach to design and development thereby promoting true business alignment  A good architectural approach coupled with a promotional model for intra- and intercomponent testing,  Metadata to identify characteristics of components as well as dependencies and relationships, including those with associated non-source artifacts
Slide 21: IBM Software Group | Rational software Summary: How Synergy lets you meet CBD challenges  An end-to-end Task-based Change and Configuration Management system (TBCM) providing for higher component interaction thereby establishing a fast, reliable process between component consumers and developers.  Tasks properties allowing you to monitor and design asset relationships with extensible, customizable attributes, thus providing for greater definition, conflict resolution, dependency knowledge, functionality propagation, tailored workflow and change management
Slide 22: IBM Software Group | Rational software Summary: How Synergy lets you meet CBD challenges Development Domain Business Domain Enterprise & Embedded Tau design pattern, an architecture  In a broader sense, an asset maybe a software component, a & Rhapsody System Architect layer, a business process, a test algorithm, etc. Its development framework should therefore Analysis & combineBusiness EA and with Application Lifecycle Management disciplines such as Requirements Design DOORS Fastrak Process Management, Enterprise Architecture, etc to&provide a scalable and systematic approach to DOORS development, resulting in higher quality products and faster time-to-market. Focal Point Portfolio/Product Management Requirements Tau, Rhapsody & Eclipse & .Net Integrations Implementation Telelogic Change & Telelogic Synergy Configuration & Change Mgmt Telelogic Synergy Release Mgmt Telelogic Dashboard Measurement Telelogic Integrations Production DOORS/T3 & Quality Center Integrations Test
Slide 23: IBM Software Group | Rational software Optional Slides
Slide 24: IBM Software Group | Rational software Example CBD Best Practices at customer sites  A large application composed of many components is developed iteratively and rapidly with all components on the same release cycle.  A large application integrating components having their own release cycle, and having dependencies with other evolving components.  Products development projects share components, each project may have the need to modify the components they consume.  A very large project divided in sub-projects that can impact any component of the software application and demonstrates management of parallel development streams and their continuous integration.
Slide 25: IBM Software Group | Rational software Development of Families of Products using a Shared Component Repository  Context  Often a component is owned by a specific team, which controls its evolutions and implements the requirements of the components consumer. This approach lacks flexibility when organizations developing families of products need to be more reactive to customer requests.  A component can be modified by any product development team
Slide 26: Shared Component Repository Collaborative Process IBM Software Group | Rational software  When should this approach be used?  The Organization is developing product families that share a common set of components,  There are independent projects that reuse and possibly require modifications on shared components,  It is not possible for a central team maintaining the shared components to cope with the change and adaptation requests,  There is a strong focus on project execution, shared components must not get in the way of delivering the projects,  The organization is open to new development techniques such as those established in the Open Source community, and accept coordination of shared components changes,
Slide 27: IBM Software Group | Rational software Shared Component Repository Collaborative Process (2)  Principles:  No dedicated team for the shared components,  No (permanent) component ownership,  Component Customers that find bugs, need new features, new components, become contributors to the Consumed Components,  When changes to a component are performed and verified they are published on the repository, so they become available for the other projects.  An Architecture Board composed of the architects from the various customers & contributors defines and updates the roadmap for the shared component:  What is / What should / What will be in the repository  What is required for components / Who will use them
Slide 28: IBM Software Group | Rational software Shared Component Repository Collaborative Process (3) B V1.0 B V1.1 B V1.2 B V1.3 B xx  An Executive Board decides which project can modify a component andConsumer A helps avoid unnecessary parallel modifications:  Explicit separation between component interfaces and implementation B yy Consumer B Committer B  Permission to fix the implementation does not give the right to modify the interface Committer A
Slide 29: IBM Software Group | Rational software Delco Electronics Systems Business Challenge: (Automotive)  Software quality is critical, standards drive development (Six Sigma, etc.)  Compressed product cycles  Component development and reuse Customer Success:  World’s largest vehicle electronics and components company; supplies electronic systems and transportation component systems for mobile applications.  12 development sites with 200 to 300 different programs being developed simultaneously  SYNERGY’s task-based and project-oriented paradigm offers built-in support for component reuse, enabling Delphi to reduce development time and costs “We’re trying to go to shrink-wrapped component reuse. We realize the strategic significance of being able to reuse components and reduce development time.” Todd Alden, Senior Software Strategist, Software Process Group