1. Zádor Dániel Kelemen, Katalin Balla Budapest University of Technology and Economics, SQI - Hungarian Software Quality Consulting Institute Jos Trienekens, Rob Kusters Technical University of Eindhoven ICCC 2008, Sinaia

2.  Process Modeling  Software Process Evolution  Process Modeling Approaches  Process Modeling Architectures  Process Modeling and Process-based Quality Approaches  Structure of Process-based Quality Approaches  Comparison of QAP elements vs. process elements

3.  Software lifecycle models  (eg. waterfall model -idealised processes)  Methodologies  (eg. JSP, JSD - recipes, paperwork)  Formal development  (proving correctness, not scalable)  Automation  (Software Development Environments – eg. requirements specification cannot be automated)  Management and Improvement  (ISO, CMMI - increased bureaucracy)  Process Modeling and Process Programming  (Osterweil, Little JIL)

4. Companies are using multiple quality approaches simultaneously (eg. ISO 9001, CMMI, ITIL etc.) Hundreds of documentation pages are present at organizational level, even more at org & project level No one wants to read and process it

5. Minimalist approach describes the most important elements understandable for humans Maximalist approach describes and validates the whole model could be processed also by computers

6. Question: Could process modeling help in representing process-based quality approaches? Probably yes (?) Comparison of quality approaches elements with process elements may help…

7. Process Elements: Purpose Inputs Entry criteria Activities Roles Measures Verification steps Outputs Exit criteria Activity 1 Input Activity 2 Output Output2

9. Elements: Chapter Subchapter Sub-subchapter Requirement (in /simple/ sentences)

10. Elements: Process area Specific Goal Specific Practice Typical Work Product Sub Practice Generic Goal Generic Practice Generic Practice Elaboration

11. Elements: Chapter Subchapter Process Process Description Activity Task Option Condition Documentation requirement Responsibility

12.  Chapter  Subchapter  Sub-subchapter  Requirement (in /simple/ sentences)  Guideline  Process  Process Description  Activity  Task  Option  Condition  Documentation requirement  Responsibility  Chapter / process activity  Subchapter /sub-activity  Sub-sub-activity  Activity description Process area Specific Goal Specific Practice Typical Work Product Sub Practice Generic Goal Generic Practice Generic Practice Elaboration Process Mission Statement Goal Activity Benefit Critical Success Factor Key Performance Indicator Further Specific Informative Components Method Practice Value Feature Process

13. Process Elements: Purpose Inputs Entry criteria Activities Roles Measures Verification steps Outputs Exit criteria QAP Elements: Chapter Subchapter Sub-subchapter Requirement (in /simple/ sentences) Guideline Process Process Description Activity Task Option Condition Documentation requirement Responsibility Chapter / process activity Subchapter /sub-activity Sub-sub-activity Activity description Process area Specific Goal Specific Practice Typical Work Product Sub Practice Generic Goal Generic Practice Generic Practice Elaboration Process Mission Statement Goal Activity Benefit Critical Success Factor Key Performance Indicator Further Specific Informative Components Method Practice Value Feature Process

14.  Chapter  Subchapter  Sub-subchapter  Requirement (in /simple/ sentences)  Guideline  Process  Process Description  Activity  Task  Option  Condition  Documentation requirement  Responsibility  Chapter / process activity  Subchapter /sub-activity  Sub-sub-activity  Activity description Process area Specific Goal Specific Practice Typical Work Product Sub Practice Generic Goal Generic Practice Generic Practice Elaboration Process Mission Statement Goal Activity Benefit Critical Success Factor Key Performance Indicator Further Specific Informative Components Method Practice Value Feature Process

15.  QAPs are focusing on:  Suppliers  Customers  Configuration management  Change management  SW Life cycle  Coding  Verification  Validation  Project Management  Project tracking  Requirements life  PPQA …… Differences in: – approach – elements – terminology Common: Giving a solution for the problems faced

16. 1) 6 QAPs were analysed 2) Similar elements are present in the QAPs and processes 3) Could serve a basis for a common QAP meta-model.  In order to create a meta-model for process-descriptive quality approaches requires further steps:  analysing the structure and content further well-known quality approaches and methods;  selecting the possible main elements to be used for the meta- model;  analysing process modelling languages, models and methods.  examining information loss during transformations.

17.  This project has been supported by BME (IT) 2 (BME Innovation and Knowledge Centre of Information Technology) within the frame of Peter Pázmány Programme, National Office for Research and Technology, Hungary. Acknowledgement

18. Thank you for attention! Questions?Contact: kelemen.daniel@cmmi.hu www.sqi.hu www.cmmi.hu