tailieunhanh - Lecture Software engineering II: Chapter 24 - Dr. Muzafar Khan

Chapter 24 - Software process improvement. In this chapter, the following content will be discussed: Class-oriented metrics, component-level design metrics, operation-oriented metrics, design metrics for webapps, metrics for source code, metrics for object-oriented testing, metrics for maintenance. | Software Process Improvement SEII-Lecture 24 Dr. Muzafar Khan Assistant Professor Department of Computer Science CIIT, Islamabad. 1 Recap Class-oriented metrics Weighted methods per class, depth of the inheritance tree, number of children, coupling, response for class, lack of cohesion Component-level design metrics Cohesion, coupling, and complexity Operation-oriented metrics Average operation size, operation complexity average number of parameters per operation Design metrics for WebApps Metrics for source code Metrics for object-oriented testing Metrics for maintenance 2 Software Process Improvement Triple constraint Effective software process can be defined in effective manner Assessment of existing process based on the defined effective process Meaningful strategy to transform the process It is not free Reduced costs after the process improvement 3 SPI Framework 4 Figure source: Software Engineering: A Practitioner’s Approach, R. S. Pressman, 7th ed., p. 788 SPI Support Groups Quality certifiers Process quality leads to product quality Formalists Process workflow, modeling languages Tool advocates Tool-oriented Practitioners Project-level planning and metrics Reformers Organizational change, human issues Ideologists Suitability for particular domain or organization structure 5 Maturity Model [1/2] Overall indication of process maturity Capability maturity model Level-5, Optimized Quantitative feedback to identify process weaknesses Pro-active approach to strengthen it Software processes are evaluated and updated to prevent known types of defects from recurring Level-4, Managed Detailed process and product metrics Meaningful variations in process performance can be distinguished from noise Trends can be predicted in process and product quality 6 Maturity Model [2/2] Level-3, Defined Processes are documented, standardized, and integrated into a standard software process All projects follow an approved, customized version of process Level-2, Repeatable Basic . | Software Process Improvement SEII-Lecture 24 Dr. Muzafar Khan Assistant Professor Department of Computer Science CIIT, Islamabad. 1 Recap Class-oriented metrics Weighted methods per class, depth of the inheritance tree, number of children, coupling, response for class, lack of cohesion Component-level design metrics Cohesion, coupling, and complexity Operation-oriented metrics Average operation size, operation complexity average number of parameters per operation Design metrics for WebApps Metrics for source code Metrics for object-oriented testing Metrics for maintenance 2 Software Process Improvement Triple constraint Effective software process can be defined in effective manner Assessment of existing process based on the defined effective process Meaningful strategy to transform the process It is not free Reduced costs after the process improvement 3 SPI Framework 4 Figure source: Software Engineering: A Practitioner’s Approach, R. S. Pressman, 7th ed., p. 788 SPI Support Groups .