Improving Software Quality: a benchmarking approach

Size: px

Start display at page:

Download "Improving Software Quality: a benchmarking approach"

Leon Osborne
8 years ago
Views:

1 Improving oftware Quaty: a benchmarking approach Asad Imam oftware Quaty Assurance peciast & Researcher, Karachi-Pakistan. hakeel Khoja Research Fellow, Learning ocieties Lab, University of outhampton, UK. Imranulla hariff Executive Director Pakistan Institute of Quaty Control, Karachi Chapter-Pakistan. oftware tandards Quaty Management ystem Manual (QMM/QMM) Benchmarking Research urvey IO 9001:2000 QM oftware Quaty CMM (W) CMMI (staged, W) Continuously improving oftware quaty Constantly changing Industrial tandards Compcated Exercise The software development system based on internal, commercial standards and improve over the years have proved to be a good system [11]. I am unable to understand what do you mean by the nes above??? Please re-phrase your statements!!!!!! How to build up an efficient, workable quaty system from basic principles to writing Quaty Management ystem Manual which is compatible for IO 9001:2000, CMM (W), CMMI (staged-w) that will improve software quaty. Related research tudy software standards Mappings of different software standards Market research survey Research on existing quaty manuals Proposing a structure of QMM Implementing QMM and proving the result. 1

oftware tandards Quaty Management ystem Manual (QMM/QMM) Benchmarking Research urvey IO 9001:2000 QM oftware Quaty CMM (W) CMMI (staged, W) Continuously improving oftware quaty Constantly changing

2 1998-Improving oftware Quaty, there is no absolute formula that can be used to improve software quaty but there are many guidenes and approaches that have been provided by the quaty experts and industry professional [13] 2001-oftware Quaty Management and oftware Process In Denmark, almost all organizations have a positive attitude towards oftware Quaty Management (QM), but QM standards and/or oftware Process Improvement (PI) methodologies are not known by 40% (44) organizations [4] 2001-The Complex Quaty World - Developing Quaty Management ystem, present a Quaty Management ystem (QM-Quaty through Managed) model to improve software quaty This in turn will kely facitate work on improved automation support of the software process [5] 2004-An Integrated Model of IO 9001:2000 and CMMI for IO Registered Organizations, present an integrated model of IO 9001:2000 and CMMI which will be useful tool for IO registered organizations aim to attain higher CMMI Levels.. but it was not practically implemented at any organization [8] 2006-AQ, Are standards the answer? These standards and practices tend to be one size fits all approach that may be optimum for some projects but is often times ill-suited for others. Because this exercise has become compcated by the fact that the standards are continually improving [1] 1996-IEEE discussion Do standards improve quaty? chneidewind says that there are many examples of standards improving software product quaty [9], Fenton says that he found no evidence that software standards improve the quaty of the resulting software products costeffectively [9] G. Gordon chulmeyer says that he has seen standards apped successfully, whereas previous implementation and quaty assurance without standards was inadequate [2] There is always a need to enhanced and refined existing process and adapt it to the need of software producing units or software organizations. Examples: BOEING [11] European trategic Program for Research in Information Technology (EPRIT) [13] Assumed clauses and abbreviations of CMM (W) Key Process Areas Maturity Level Clause Process Areas of CMM (W) Clauses and abbreviations of CMMI (W) KPAs [50] Maturity Level Clause Process Areas of CMM (W) 2. Repeatable 2.1 RM REQUIREMENT MANAGEMENT 2. Repeatable 2.1 RM Requirement Management 2.2.PP PROJECT PLANNING 2.2 PP oftware Project Planning 2.3 PT oftware project tracking and oversight 2.4 M oftware subcontract management 2.3 PMC PROJECT MONITORING AND CONTROL 2.4 AM UPPLIER AGREEMENT MANAGEMENT 2.5 M&A MEAUREMENTAND ANALYI 2.5 QA oftware quaty assurance 2.6 PPQA PROCEAND PRODUCT QUALITY AURANCE 2.6 CM oftware configuration management 2.7 CM CONFIGURATION MANAGEMENT 3 Defined 3.1 OPF Organization process focus 3- DEFINED 3.1 RD REQUIREMENT DEVELOPMENT 2

and/or oftware Process Improvement (PI) methodologies are not known by 40% (44) organizations [4] 2001-The Complex Quaty World - Developing Quaty Management ystem, present a Quaty Management ystem

3 1-1 Correspondence between IO 9001:2000 and IO 9003:1997 (E) IO 9001:2000 IO :1997 (E) Clause Name C.no C.no Clause Name Quaty Pocy Quaty Pocy Planning [title] 5.4 Quaty objectives Quaty management system planning Responsibity, authority and communication [title] Organization [title] Responsibity and authority Responsibity and authority Resources Clause level mapping between IO :1997 with CMM for oftware is explained by CMU/EI [47]. 1 to N mapping between CMMI (staged representation, W) against the practices of CMM (W) is explained by U Air Force oftware Technology upport Centre. [48], also supported by CMU/EI. While mapping CMMI (W) with CMM (W), use the abbreviations assumed for CMM (W) Ratio of questions 34% questions were related to the issues faced during the implementation of software standards which is a problem domain of the thesis, 28% questions related to feedback after implementing any software standards to know if its brings some improvement/discipnes in core areas of development cycle or it is same as previous which is a solution domain of the thesis, 26% questions were asked about the company profile to understand the organization background as how the pocies working which will be utized in defining the organization s scope in the quaty manual, 12% questions related to understand the process approach and the degree of quaty assurance Results Assessment Areas % Questions Total %Yes Total (NC) %Yes (NC) (C) %Yes (C) Organization Quaty Assurance oftware tandards/oftware Models Feedback on existing standards Findings Non certified organizations does not estabsh the organization purpose, vision, mission or quaty objective. 60% does not consider any guidenes for the improvement of processes (see question 20). 40% were interested to get a label of higher level (Q.22 and Q.23) certification/assessment in order to gain some reputation in the market but were not famiar as how to improve productivity All Organizations were interested in accepting thus quaty manual which will help them to get a label of certification/assessment (Q.35) 60% were interested in accepting any such integrated model which will either improve the quaty of software or not (Q.36) Conclusion 80% responded low confident level in improving the processes themselves (Q.27) Non certified organizations were ignoring the documentation process and they did not understand the measurement and analysis by replying low ratings in question 28 (Q.38 to Q.47). Consideration in Quaty Management ystem Manual Consodated mapping tudy of existing quaty management system manual Feedback from survey 3

1 to N mapping between CMMI (staged representation, W) against the practices of CMM (W) is explained by U Air Force oftware Technology upport Centre. [48], also supported by CMU/EI.

4 tructure of QMM [table 4.1] cope of QMM [table 4.2] Documentation tructure QMM [table 4.3] Combination of all research methods could guaranteed improvement in software quaty. Mappings of software standards Research survey / GAP analysis tudy of QMM Implementation of QMM Don t skip the initial level Don t strive for market label only Improve the standard even further as the software development process matured Organization Profile Quaty Assurance oftware tandards/oftware Models Feedback on existing standards 4

Mappings of software standards Research survey / GAP analysis tudy of QMM Implementation of QMM Don t skip the initial level Don

5 Feedback from market survey or gap analysis and study of existing quaty manual will help in representing a better quaty management system manual else only the mapping among standards will not guarantee the improvement in software quaty Questions Mappings of standards will make the processes compatible with IT standards but they also measure and analyzed existing process 5

will not guarantee the improvement in software quaty Questions Mappings of standards will

Improving Software Quality a benchmarking approach

Improving Software Quality a benchmarking approach Asad Imam*, Shakeel A. Khoja** & Imranuulla Shariff*** * Department of Computer Engineering, Software Quality Assurance Specialist & Researcher, Karachi-Pakistan