1. HRL © 2009 IBM Corporation Model-Driven Product-Lines for Embedded Software and for Supply-Chain Companies Tali Yatzkar-Haham (tali@il.ibm.com) Julia Rubin, Mila Keren, Shiri Kremer-Davidson, Dolev Dotan, Itay Maman, Ofir Bruknertali@il.ibm.com Model Driven Engineering Technologies IBM Haifa Research Lab April, 2009

2. HRL © 2009 IBM Corporation 2 Software & System Product Line Engineering 10 Nokia 2008 models Ford Models 2009 http://autos.yahoo.com/ford/ Companies are developing product lines - families of manufactured products Embedded Software is becoming increasingly large and complex Need to be c ustomized to variety of physical devices, protocols, environments, languages 59 Printers Digital Printers Product Line However, today's software development tools mostly focus on individual products

3. HRL © 2009 IBM Corporation 3 What companies are doing today?  Today's tools mostly focus on individual products  Companies solutions: Clone-and-own –For each new product, make a copy of a similar product and modify –Leads to expensive duplication, divergence and merging –Very difficult to manage and maintain One-size-fits-all –For each new product, add internal code variability for product diversity –Leads to large and complex code –Very difficult to manage and maintain Development & maintenance of a product line using current tools become extremely complex

4. HRL © 2009 IBM Corporation 4 Software Product Line Engineering Software product lines refers to engineering techniques for creating a portfolio of similar software systems from a shared set of software assets  A product line represents a family of manufactured products  A product line model explicitly captures the commonality and variability of a product line artifacts and their relations Software Product Line Engineering makes it possible to  create software for different products  use variability to customize the software to each different product

5. HRL © 2009 IBM Corporation 5 PLE - Benefits  Using software product line techniques, companies such as Nokia, GM, Phillips can improve time-to-market, engineering costs, portfolio size and defect rates by factors of 3 to 50  Reduction of maintenance effort –Propagation of error corrections to all products  Better coping with evolution –Adding a new feature to the platform allows adding it to any derived product  Better predictability – for the time and effort required to introduce a new product  Increase automation using model-driven development Predictive versus opportunistic software reuse

6. HRL © 2009 IBM Corporation 6 6 CE Case - Digital Printer Platform (Product Line) 59 Printers

7. HRL © 2009 IBM Corporation 7 Model Driven Development Environment for Software Product Lines  Supports component based modeling  Supports software product line development variability –Alternative & optional components, connections and interfaces  Based on a standard modeling framework (UML) and on the Rational toolset –UML Profile  Takes advantage of existing IBM Rational tooling capabilities: –Editors –Validation framework –Transformation framework –More…  With tooling to automate transformations from PL model to product models and build scripts

8. HRL © 2009 IBM Corporation 8 Architecture of the Main Printer Component in RSA Variability Support

9. HRL © 2009 IBM Corporation 9 Alternative variation point Variability Support: 15 alternative connections

10. HRL © 2009 IBM Corporation 10 From Product Line Model to Products Product Line Model Components + Variability Digital Printer Platform Run Validation Configuration Product SCX-4321 Model Product MJC-8700 Model Any other printer… Transformation Product SCX-4321 Build Scripts Transformation Product MJC-8700 Build Scripts Update, Add New Features

11. HRL © 2009 IBM Corporation 11 PL for Supply Chains Companies – SoC Case  It is uneconomic for either the semiconductor manufacturer or their customers to develop all the necessary software  Ecosystem of suppliers is developing for feature-specific services  A supply chain is a network that starts with raw material, transforms them into intermediate goods, and then into final product delivered to customers.  Each participant consumes products from one or more upstream suppliers, adds value, and supplies the results to downstream consumer

12. HRL © 2009 IBM Corporation 12 Supply Chain Scenario In-house components Suppliers’ components Supplier S1 Supplier S2 Supplier S3 Delivered to customer C2 Delivered to customer C1

13. HRL © 2009 IBM Corporation 13  Partial configuration of component’s variability options –Can be delivered to different customers in a different form –A customer can further configure the component –A customer shouldn’t be aware of the options that are available to others –Support configuration through a feature model tool Supply Chain Use-Cases Support product line of product lines This was achieved using staged configuration, with multiple transformations

14. HRL © 2009 IBM Corporation 14  Selecting and gluing together components that are parts of the same product, but are provided by different suppliers, and thus have different implementation styles –Different component technology, different interfaces, different style to pass parameters Supply Chain Use-Cases Architectural Model Supplier variability Generated customer model

15. HRL © 2009 IBM Corporation 15 Technical - Glue Specification Screen Sots

16. HRL © 2009 IBM Corporation 16 Summary  Facilitate management and reuse of software components  Incorporate product line variability and support for mass customization  Support for component integration in supply-chain scenario  Increase automation using model-driven development 59 Printers Ford Models 2009 http://autos.yahoo.com/ford/ 10 Nokia 2008 models Digital Printers Product Line

17. HRL © 2009 IBM Corporation 17 Thank You! Questions?