Table of Contents

1. PROFESProduct Focused ImprovementofEmbedded Software ProcessesBlanko’98Seija Komi-SirviöVTT Electronics

2. Table of Contents • Introduction • Objectives of the PROFES methodology • Overview of the PROFES methodology • Overview of some PROFES elements • Experiences with the PROFES methodology • Conclusions

3. PROFES project • Product driven process improvement • Esprit project • January 97 - June 99 • 3.2 MECU • EU funding 1.7 MECU • 303 personmonths

4. Project Consortium Combination of highly skilled methodology providers and practitioners with expertise in process improvement: • Dräger Medical Technology, The Netherlands - Application Developer • Ericsson, Finland - Application Developer • Etnoteam S.P.A., Italy - Method Provider • Fraunhofer IESE, Germany - Method Provider • Schlumberger Retail Petroleum Systems, France - Application Developer • University of Oulu, Finland - Method Provider • VTT Electronics, Finland, - Project Leader - Method Provider Industrial follow-up group in Finland

5. Parallel Applications • Three parallel industrial applications which are replicated twice • Medical instruments, retail petroleum systems, and telecommunication systems • Parallel experiments are used in order to • Facilitate a higher degree of formality in the experimental design • Improve the external validity and statistical significance of obtained results • Augment knowledge transfer between the industrial companies involved

6. What customers ask for? QUALITY Reliability, maintainability, usability... COSTS TIME TO MARKET

7. What is Missing? • Knowledge of the cause-effect link between process and product attributes • Ability to predict and monitor results of investments in process improvement and technology • Data on proven effectiveness of process improvement approaches and use of specific technology • Ability to learn from experience

8. Key Objectives • To link customer-oriented product factors to process characteristics • Focus on improvements to those characteristics of the process that are critical for product quality • To combine and enhance the strengths • goal-oriented measurement • process assessment • product and process modelling and • experience factory • To support evaluation of cost-benefits • To support learning and re-use of experience • To address the embedded system domain

9. How they are achieved? • A model of product and process dependencies (PPD) • A suggested improvement cycle • A cost-benefit model

10. PROFES modularity • It is possible to use only the parts which are relevant to an organisation • Organisations can choose the method they want to apply for: • process modelling • process assessment (SPICE conformant) • product assessment

11. Background Standards & Methods • ISO 9126 (Product) • ISO 15504, SPICE (Process) • BOOTSTRAP 3.0 (SPICE conformant) • GQM (Measurement) • QIP (Improvement activities) • Experience Factory (Reuse) • Product assessment and Process modelling (No specific method is recommended) PPD (Product Process Dependency) Models

12. Approach to Product Quality • ISO 9126 is adopted as reference for definition of quality characteristics and sub-characteristics • No specific method for product assessment is recommended • GQM can be used to define specific product goals to be evaluated

13. ISO 9126 Sub-characteristics Characteristics

14. Which Process Assessment? • Several assessment methods are available • CMM • BOOTSTRAP • Trillium • ….. • PROFES recommends a SPICE conformant assessment

15. Goal-Oriented-Measurement Typical difficulties when performing measurement programmes: • Unnecessary and too much data is collected. • Inadequate and / or insufficient data is collected. • Collected data is not used properly. • People are not motivated for providing data. • The usefulness of measures cannot be judged out of context. • Measurements have to be chosen, customised, and used according to goals of interest and the context/environment. Goal-oriented measurement according to the Goal/Question/Metric (GQM) approach.

16. Goal Q4 ... Q2 Model 2 Q3 Model 3 Q1 Model1 Definition Interpretation ... M1 M2 M3 The Elements of GQM GQM has four elements: Goals, Questions, Models and Measures:

17. Product/Process Dependencies (PPDs) ? Which software processesor development practices which software product quality yield Verification Cost Reliability Inspections Case Tools Time to Market Planning GQM Maintainability UML etc.. etc.. OO Development Large Projects Unstable Requirements etc.. … in which context situation?

18. Product - Process - axis GQM Bootstrap PPD PRODUCT PROCESS ISO9126 QIP/EF

19. The PPD-EP • PPD-EP (Product Process Dependency Experience Package): • helps in the selection of process improvement actions driven by product quality targets • can be continuously enhanced by including additional product-process links experimentally validated using GQM • accumulates software engineering best practices

20. Improvement Programme Develop & Tailor PPD Models 3 • Data Analysis • Knowledge Acquisition • Validation Evaluate & Update PPD Models Retrieve & Reuse PPD Models 1 2 Experience Base PPD Development and Usage

21. An example of building and using PPD-EP

22. PPD-EP.1.3.1 Product Quality Reliability Process ENG.3 Software Requirements Analysis Practice Software Inspections Viewpoint Software Engineer Environment PROFES-A Status Preliminary Context CF.1 Size of inspection team 1-2 3-5 6-8 9-10 CF.2 Experience of inspection team low average high CF.3 Problem treatment of pragmatic inspection team detailed CF.4 Complexity of inspected low average high document very_high CF.5 Size of inspected document small average large very_large CF.6 Management commitment low high CF.7 Overall time pressure low average high CF.8 Module affected by new old_hw new_hw hardware CF.9 Module developed externally internally externally Notes & Comments This PPD-EP addresses the interrelation between document complexity and characteristics of the inspection team. For complex documents, the team needs to have average size, high experience level, and a pragmatic problem treatment attitude. Otherwise, requirements inspections of complex documents are not regarded to be effective. An example of a PPD-EP

23. Benefits from PPD models PPD models provide • Well-organised planning and evaluation of product-driven software process improvement • Reduction of overhead cost for improvement programmes • Easy access to software engineering best practices • Acquisition and reusability of organisational knowledge and experience

24. Experience Factory - Why ? Projects and organisations have different aims: • Projects: to develop software products according to predefined requirements, costs and time constraints. • Organisations: to improve their products over time, to avoid making the same mistake twice, to perform re-use wherever advantageous. • Reuse of experiences across projects is needed • Projects cannot be expected to “manage” corporate experience • A separate organisational unit is required: the Experience Factory (EF) PROFES

25. Types of “Experience” • Experience is packaged in the form of models PROFES

26. The Improvement Cycle • The improvement cycle provides guidelines to: • effectively combine process assessment, goal oriented measurements and process modelling • package experience for re-use • define hypothesis and validate them to feed the PPD-EP

27. - Motivation presentations to achieve commitment - Preliminary product quality needs identification - Process assessment and descriptive process modelling - Product assessment and characterisation - Measurement data analysis - Product improvement goal setting - Process re-assessment and - Select or build PPDs interpretation - PPD evaluation - Improvement planning - Process changes implementation - Prescriptive process modelling - Continuous measurement and quality monitoring - Measurement planning The PROFES improvement Cycle - Packaging and storing experiences for reuse PACKAGE CHARACTERISE d n P a r o l j a e n c o t i t P a r s i e o c s s o n - r D c P e a - e p t g e s c n r u s d d e O e s o n r c P y ANALYSE PRODUCT SET GOALS PPD PROCESS PLAN EXECUTE

28. Organisational and Project Level • Improvement at organisational level : • definition of overall product improvement goals • planning of the overall improvement programme • definition and implementation of organisational solutions • selection of pilot projects • monitoring of improvement programme • organisational learning • Improvement at project level: • implementation and evaluation of suggested improvement solutions • achievement of product improvement goals

29. The Cost-Benefit Model • The cost-benefit model is a repository of costs-benefits data based on use of improvement methods • It can be enhanced and tailored to specific environments

30. Exploitable Results • User Manual and PROFES book • Consultancy service package • Presentation and training material • Tools to support the PROFES methodology • A core PPD repository • A core cost-benefit model

31. Conclusion • PROFES integrates and enhances well known methods • assessment, measurement, product & process modeling • PROFES supports industry in • focusing investments in process improvement on customer driven product quality objectives • PPD repository & learning and re-using experience