Toward Quantitative Process Management With Exploratory Data Analysis
|
|
- Elinor O’Connor’
- 8 years ago
- Views:
Transcription
1 Toward Quantitative Process Management With Exploratory Data Analysis Mark C. Paulk Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Abstract The Capability Maturity Model for Software is a model for building organizational capability that has been widely adopted in the software community and beyond. The Software CMM is a five-level model that prescribes process improvement priorities for software organizations. Level 4 in the CMM focuses on using quantitative techniques, particularly statistical techniques, for controlling the software process. In statistical process control terms, this means eliminating assignable (or special) causes of variation. Organizations beginning to use quantitative management typically begin by "informally stabilizing" their process. This paper describes typical questions and issues associated with the exploratory data analysis involved in initiating quantitative process management. Introduction The Capability Maturity Model (CMM) for Software [Paulk95], developed by the Software Engineering Institute (SEI) at Carnegie Mellon University, is a model for building organizational capability that has been widely adopted in the software community and beyond. The Software CMM is a five-level model that describes good engineering and management practices and prescribes improvement priorities for software organizations. The five maturity levels are summarized in Figure 1. The higher maturity levels in the CMM are based on applying quantitative techniques, particularly statistical techniques [Florac99], to controlling and improving the software process. In statistical process control (SPC) terms, level 4 focuses on removing assignable causes of variation, and level 5 focuses on systematically addressing common causes of variation. This gives the organization the ability to understand the past, control the present, and predict the future quantitatively. Regardless of the specific tools used (and control charts are implied by SPC), the foundation of levels 4 and 5 is statistical thinking [Hare95], which is based on three fundamental axioms: all work is a series of interconnected processes all processes are variable Capability Maturity Model and CMM are registered with the U.S. Patent and Trademark Office. SM Personal Software Process and PSP are service marks of Carnegie Mellon University. The Software Engineering Institute is a federally funded research and development center sponsored by the U.S. Department of Defense. 1
2 understanding variation is the basis for management by fact and systematic improvement The statistical thinking characteristic of a high maturity organization depends on two fundamental principles. First, process data is collected at the process step level for realtime process control. This is perhaps the most important single attribute of a level 4 organization that engineers are using data to drive technical decision making in realtime, thereby maximizing efficiency. Second, and a direct consequence of statistical thinking, is that decision making at the process level incorporates an understanding of variation. A wide range of analytic techniques can be used for systematically understanding variation, ranging from simple graphs, such as histograms and bar charts, and statistical formulas, such as standard deviation, to statistical process control tools, such as XmR charts, u-charts and beyond. The simplicity of a histogram does not lessen its power a simple picture that imparts insight is more powerful than a sophisticated formula whose implications are not understood. Level Focus Key Process Areas Continual process improvement 5 Optimizing 4 Managed 3 Defined 2 Repeatable 1 Initial Product and process quality Engineering processes and organizational support Project management processes Competent people and heroics Figure 1. An overview of the Software CMM. Defect Prevention Technology Change Management Process Change Management Quantitative Process Management Software Quality Management Organization Process Focus Organization Process Definition Training Program Integrated Software Management Software Product Engineering Intergroup Coordination Peer Reviews Requirements Management Software Project Planning Software Project Tracking & Oversight Software Subcontract Management Software Quality Assurance Software Configuration Management Although the Software CMM has been extensively used to guide software process improvement, the majority of software organizations are at the lower maturity levels; as of March 1999, of the 807 organizations active in the SEI's assessment database, only 35 were at levels 4 and 5. While the number of high maturity organizations is growing rapidly, it takes time to institutionalize a measurement program and the quantitative management practices that take good advantage of its capabilities. The typical software organization takes over two years to move from level 1 to level 2 and from level 2 to level 2
3 3 [Herbsleb97]. One to two years is a reasonable expectation for building, deploying, and refining quantitatively managed processes. One of the challenges in moving to level 4 is the discovery organizations typically make when looking at their process data: the defined processes used by the projects are not as consistently implemented or measured as believed. When a process is being placed under statistical process control in a rigorous sense, it is "stabilized" by removing assignable causes of variation. "Informal stabilization" occurs simply by examining the data (graphically) before even placing it on a control chart, as patterns in the data suggestive of mixing and stratification are seen. If there is a great deal of variability in the data, a common complaint when arguing that SPC cannot be applied to the software process [Ould96], the control limits on a control chart will be wide. High variability has consequences: if the limits are wide, predictability is poor, and highly variable performance is to be expected for future performance. If highly variable performance is unacceptable, then the process will have to be changed. Ignoring reality will not change it. Since some studies suggest a 20:1 difference in the performance of programmers, variability is a fact of life in a design-intensive, humancentric process. The impact of a disciplined process can be significant in minimizing variation while improving both quality and productivity, as demonstrated by the Personal Software Process SM [Humphrey95, Hayes97]. Some software organizations are using control charts appropriately and to provide business value [Paulk99a, Paulk99b], thus there are a few examples of SPC for software providing business value. Informally stabilizing the process can be characterized as an exercise in exploratory data analysis, which is a precursor to the true quantitative management of level 4. The processes that are first stabilized tend to be design, code, and test, since there is usually an adequate amount of inspection and test data to apply statistical techniques in a fairly straightforward manner. A fairly typical subset of code inspection data in Table 1 illustrates what an organization might start with. The organization that provided this data was piloting the use of control charts on a maintenance project. Table 1. Representative Code Inspection Data From an Organization Beginning Quantitative Management. Number of Inspectors Inspection Preparation Time Code Inspection Time (number of inspectors X inspection hours) Number of Defects Lines of Code
4 If you were asked to analyze the data in Table 1, what questions might you ask? They will probably fall in four broad categories: operational definitions, process consistency, aggregation, and organizational implications. Operational Definitions Good operational definitions must satisfy two important criteria [Florac99]: communication. If someone uses the definition as a basis for measuring or describing a measurement result, will others know precisely what has been measured, how it was measured, and what has been included and excluded? repeatability. Could others, armed with the definition, repeat the measurements and get essentially the same results? In looking at the data in Table 1, the first question is likely to be, "How is a line of code defined?" The fact that the LOC values are not integers rings a bell, yet, when first hearing that this is a maintenance project, the question should have arisen, "How do they deal with modified, deleted, and unchanged lines?" In this case, a formula was used to create an aggregate size measure that is a weighted function of new, modified, deleted, and unchanged lines. It is more important to know that the formula exists and is being consistently used than to know what the specific formula is. The second question might be, "What are the time units?" One panelist at the 1999 European SEPG Conference reported a case where the unit was not clearly communicated, and they discovered that their time data included both hours and minutes (assuming every value of 5 or less was hours was their pragmatic solution). The third question is obviously, "How is a defect defined?" While the first two metrics can be collected in a fairly objective fashion, getting a good operational definition of "defect" can be challenging. Are multiple severity levels included, from life-critical to major to trivial? Are trivial defects even recorded? How does the inspection team determine what category a defect belongs in? Again, the crucial question is whether the data can be collected consistently and repeatably. A fourth question should be, "Is the data collected at the same point in the process each time?" For example, are code inspections performed before or after a clean compile is obtained? If this is not specified, there may be a mix of compiled/not compiled inspection data, which will increase variability significantly. Process Consistency Even if the data is collected consistently and repeatably, the process itself maybe vary from one execution to the next. For example, some teams may engage in "pre-reviews" before inspections (to ensure that the inspected code is of acceptable quality not an 4
5 unreasonable practice if the number of defects reported in the inspections has ever been used in a performance appraisal). This, too, can lead to a mix of pre-reviewed/not prereviewed data that will increase variability. Another panelist at the 1999 European SEPG Conference identified a case where examination of data revealed two operationally distinct inspection processes. The distinguishing attribute of the inspection was the size of the work product. If the code module being inspected was larger than about 50 lines of code, the inspection rates were significantly different even though the same inspection process was supposedly being performed. The important insight is not whether the existence of two operationally different inspections is appropriate, but that the decision be a conscious one. In the case of the data in Table 1, two questions immediately arise: "Is it a good idea to have inspections covering this wide a range of code sizes?" and the corollary question, "Are the inspection rates for these different sizes of module reasonable?" Different organizations may establish somewhat different guidelines, but150 LOC per hour is a reasonable target [Fagan86]. A casual examination of the data provided in Table 1 suggests that some inspection rates are running at greater than 2,000 LOC per hour, which suggests a significant process consistency issue. Aggregation When analyzing process data, there are many potential sources of variation in the process. It is easy to overlook sources of variation when data are aggregated. Common causes of overly aggregated data include [Florac99]: poor operational definitions inadequate contextual information lack of traceability from data back to its original context working with data whose elements are combinations (mixtures) of values from different sources The predominant source of aggregated data is simply that different work products are produced by different members of the project team. Collecting data on an individual basis would address this, but could have severe consequences in terms of motivational use of the data, e.g., during performance appraisals, which can lead to dysfunctional behavior [Austin96], and in terms of the amount of the data available for statistical analyses. There are no easy answers to this question. It is, however, possible on occasion to disaggregate data. For example, defect data could be separated into different categories, and control charts on each category may provide significantly better insight into separate common cause systems [Florac99]. Organizational Implications In the particular example we have gone through above, the data was used within a single 5
6 project. When dealing with organizational data, these problems are exacerbated. In moving between projects, application domains, and customers, operational definitions may be "adjusted" to suit the unique needs of the new environment, thus it is crucial to understand the context of the data when doing cross-project comparisons. It can be particularly challenging when government regulations or customers demand that data be reported in different ways than the organization would normally collect it. Conclusion This paper provides a simple road map through some of the issues that an analyst must deal with in implementing quantitative process management. As we frequently say about the CMM, this is not rocket science, but it is easy to miss an important point, and it can be quite frustrating at times to work through these issues. These are, however, typical problems that most organizations have work through on the journey of continual process improvement; "informal stabilization" seems to be a necessary precursor to the useful application of rigorous SPC techniques. References Austin96 Fagan86 Florac99 Hare95 Hayes97 Herbsleb97 Robert D. Austin, Measuring and Managing Performance in Organizations, Dorset House Publishing, ISBN: , New York, NY, M.E. Fagan, "Advances in Software Inspections," IEEE Transactions on Software Engineering, Vol. 12, No. 7, July 1986, pp , reprinted in Software Engineering Project Management, R.H. Thayer (ed), IEEE Computer Society Press, IEEE Catalog No. EH0263-4, 1988, pp William A. Florac and Anita D. Carleton, Measuring the Software Process: Statistical Process Control for Software Process Improvement, ISBN , Addison-Wesley, Reading, MA, Lynne B. Hare, Roger W. Hoerl, John D. Hromi, and Ronald D. Snee, "The Role of Statistical Thinking in Management," ASQC Quality Progress, Vol. 28, No. 2, February 1995, pp Will Hayes and James W. Over, "The Personal Software Process (PSP): An Empirical Study of the Impact of PSP on Individual Engineers," Software Engineering Institute, Carnegie Mellon University, CMU/SEI-97- TR-001, December James Herbsleb, David Zubrow, Dennis Goldenson, Will Hayes, and Mark Paulk, "Software Quality and the Capability Maturity Model, Communications of the ACM, Vol. 40, No. 6, June 1997, pp
7 Humphrey95 Watts S. Humphrey, A Discipline for Software Engineering, ISBN , Addison-Wesley Publishing Company, Reading, MA, Ould96 Paulk95 Paulk99a Paulk99b Martyn A. Ould, "CMM and ISO 9001," Software Process: Improvement and Practice, Vol. 2, Issue 4, December 1996, pp Carnegie Mellon University, Software Engineering Institute (Principal Contributors and Editors: Mark C. Paulk, Charles V. Weber, Bill Curtis, and Mary Beth Chrissis), The Capability Maturity Model: Guidelines for Improving the Software Process, ISBN , Addison- Wesley Publishing Company, Reading, MA, Mark C. Paulk, Practices of High Maturity Organizations, The 11 th Software Engineering Process Group (SEPG) Conference, Atlanta, Georgia, 8-11 March Mark C. Paulk, "Using the Software CMM With Good Judgment, ASQ Software Quality Professional, Vol. 1, No. 3, June 1999, pp
Understanding High Maturity Organizations
Understanding High Maturity Organizations Donna K. Dunaway, Charles V. Weber, Mark C. Paulk, Will Hayes, and Mary Beth Chrissis Carnegie Mellon University Pittsburgh, PA 15213-3890 Capability Maturity
More informationEffective CMM-Based Process Improvement
Effective CMM-Based Process Improvement Mark C. Paulk, Software Engineering Institute, USA Abstract The Capability Maturity Model SM for Software developed by the Software Engineering Institute has had
More informationThe Capability Maturity Model for Software, Version 1.1
The Capability Maturity Model for Software, Version 1.1 Mark C. Paulk xxx 1998 Carnegie Mellon University Pittsburgh, PA 15213-3890 Sponsored by the U.S. Department of Defense. 1997 by Carnegie Mellon
More informationUtilization of Statistical Process Control in Defined Level Software Companies to Manage Processes Using Control Charts with Three Sigma
Proceedings of the World Congress on Engineering and Computer Science 00 Vol I WCECS 00, October 0-, 00, San Francisco, USA Utilization of Statistical Process Control in Defined Level Software Companies
More informationMoving from ISO9000 to the Higher Levels of the Capability Maturity Model (CMM)
Moving from ISO9000 to the Higher Levels of the Capability Maturity Model (CMM) Pankaj Jalote 1 Infosys Technologies Ltd. Bangalore 561 229 Fax: +91-512-590725/590413 Jalote@iitk.ernet.in, jalote@iitk.ac.in
More informationSEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS)
SEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS) 1.0 SEI Product 1.1 SEI Level 2 Product 1.1.1 SEI Level 2 Process 1.1.1.1 Requirements Management Process 1.1.1.2 Software Project Planning Process
More informationCMM Level 4 Quantitative Analysis and Defect Prevention With Project Examples Al Florence MITRE
CMM Level 4 Quantitative Analysis and Defect Prevention With Project Examples Al Florence MITRE The views expressed are those of the author and do not reflect the official policy or position of MITRE KEY
More informationJason Bennett Thatcher Clemson University, 101 Sirrine Hall, Clemson, SC 29634 U.S.A. {jthatch@clemson.edu}
RESEARCH ARTICLE IS EMPLOYEE ATTITUDES AND PERCEPTIONS AT VARYING LEVELS OF SOFTWARE PROCESS MATURITY Janet K. Ply Pendére, Inc., 1805 S. 9 th Street, Waco, TX 76706 U.S.A. {janet.ply@pendere.com} Jo Ellen
More informationInternational Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research)
International Association of Scientific Innovation and Research (IASIR) (An Association Unifying the Sciences, Engineering, and Applied Research) International Journal of Engineering, Business and Enterprise
More informationComments on Software Quality by Watts S. Humphrey Fellow, Software Engineering Institute Carnegie Mellon University Pittsburgh, PA
Comments on Software Quality by Watts S. Humphrey Fellow, Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Summary This paper reviews the software industry s current approach to
More informationUse of Metrics in High Maturity Organizations
Use of Metrics in High Maturity Organizations Pankaj Jalote Department of Computer Science and Engineering Indian Institute of Technology Kanpur Kanpur, India 208016 Jalote@iitk.ac.in Summary A high maturity
More informationA Capability Maturity Model for Scientific Data Management
A Capability Maturity Model for Scientific Data Management 1 A Capability Maturity Model for Scientific Data Management Kevin Crowston & Jian Qin School of Information Studies, Syracuse University July
More informationKnowledge Infrastructure for Project Management 1
Knowledge Infrastructure for Project Management 1 Pankaj Jalote Department of Computer Science and Engineering Indian Institute of Technology Kanpur Kanpur, India 208016 Jalote@iitk.ac.in Abstract In any
More informationCapability Maturity Model Software Development Using Cleanroom Software Engineering Principles - Results of an Industry Project
Capability Maturity Model Software Development Using Cleanroom Software Engineering Principles - Results of an Industry Project Robert S. Oshana Member Group Technical Staff Raytheon Systems Company oshana@ti.com
More informationThe Software Engineering Institute developed Capability Maturity Model for software (CMM)
1 1. Introduction The Software Engineering Institute developed Capability Maturity Model for software (CMM) and International Standards Organization developed ISO 9000 series, both have a common concern
More informationSoftware Process Improvement CMM
Software Process Improvement CMM Marcello Visconti Departamento de Informática Universidad Técnica Federico Santa María Valparaíso, Chile Software Engineering Institute Founded by the Department of Defense
More informationCapability Maturity Model Integration (CMMI ) Overview
Pittsburgh, PA 15213-3890 Capability Maturity Model Integration ( ) Overview SM CMM Integration, SCAMPI, SCAMPI Lead Appraiser, and SEI are service marks of Carnegie Mellon University., Capability Maturity
More informationSoftware Engineering: Analysis and Design - CSE3308
CSE3308/DMS/2004/25 Monash University - School of Computer Science and Software Engineering Software Engineering: Analysis and Design - CSE3308 Software Quality CSE3308 - Software Engineering: Analysis
More informationReaching CMM Levels 2 and 3 with the Rational Unified Process
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP174 Table of Contents INTRODUCTION... 1 LEVEL-2, REPEATABLE... 3 Requirements Management... 3 Software Project
More informationUsing the Software CMM in Small Organizations
Using the Software CMM in Small Organizations Mark C. Paulk Abstract The Capability Maturity Model SM for Software developed by the Software Engineering Institute has had a major influence on software
More informationMaking Process Improvement Work
Making Process Improvement Work A Concise Action Guide for Software Managers and Practitioners Neil Potter Mary Sakry The Process Group help@processgroup.com www.processgroup.com Version 2.3 1 Session
More informationThe Capability Maturity Model for Software
The Capability Maturity Model for Software Abstract Mark C. Paulk Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213-3890 Bill Curtis Software Engineering Institute Carnegie
More informationThe Role of Software Processes and Communication in Offshore Software Development
The Role of Software Processes and Communication in Offshore Software Development Anandasivam Gopal, Tridas Mukhopadhyay, and Mayuram S. Krishnan Offshore software development is a new trend in the information
More informationQuantitative Project Management Framework via Integrating
Quantitative Project Management Framework via Integrating Six Sigma and PSP/TSP Sejun Kim, BISTel Okjoo Choi, Jongmoon Baik, Abstract: Process technologies such as Personal Software Process SM (PSP) and
More informationRisk Knowledge Capture in the Riskit Method
Risk Knowledge Capture in the Riskit Method Jyrki Kontio and Victor R. Basili jyrki.kontio@ntc.nokia.com / basili@cs.umd.edu University of Maryland Department of Computer Science A.V.Williams Building
More informationRole of Software Quality Assurance in Capability Maturity Model Integration
Role of Software Quality Assurance in Capability Maturity Model Integration Rekha Chouhan 1 Dr.Rajeev Mathur 2 1 Research Scholar, Jodhpur National University, JODHPUR 2 Director, CS, Lachoo Memorial College
More informationIMPLEMENTATION OF A SOFTWARE PROJECT OFFICE AT HONEYWELL AIR TRANSPORT SYSTEMS. by Michael A. Ross
IMPLEMENTATION OF A SOFTWARE PROJECT OFFICE AT HONEYWELL AIR TRANSPORT SYSTEMS by Michael A. Ross Abstract. This paper justifies, defines and describes an organization-level software project management
More informationExtreme Programming from a CMM Perspective
focus reports from the field Extreme Programming from a CMM Perspective Mark C. Paulk, Software Engineering Institute Extreme Programming is an agile methodology that some people advocate for the high-speed,
More informationMEASURING INTEGRATED PRODUCT TEAMS
MEASURING INTEGRATED PRODUCT TEAMS Dick Stutzke SAIC 6725 Odyssey Drive Huntsville, AL 35806 23 October 2002 Presented at the Los Angeles SPIN Meeting Los Angeles, California 1 Organization s Background
More informationDeveloping CMMI in IT Projects with Considering other Development Models
Developing CMMI in IT Projects with Considering other Development Models Anahita Ahmadi* MSc in Socio Economic Systems Engineering Organizational Process Development Engineer, International Systems Engineering
More information5 Regional Approaches
5 Regional Approaches 5.1 The Capability Maturity Model (SW and Integrated) Tailored in Small Indigenous Software Industries Authors Rosario Blowers and Ita Richardson Abstract The Irish Software Industry
More informationA Report on The Capability Maturity Model
A Report on The Capability Maturity Model Hakan Bayraksan hxb07u 29 November 2009 G53QAT Table of Contents Introduction...2 The evolution of CMMI...3 CMM... 3 CMMI... 3 The definition of CMMI... 4 Level
More informationUsing the Software CMM in Small Projects and Small Organizations
Using the Software CMM in Small Projects and Small Organizations Mark C. Paulk February 1999 Pittsburgh, PA 15213-3890 SM IDEAL, Personal Software Process, PSP, Team Software Process, and TSP are service
More informationProcess Improvement. Objectives
Process Improvement cmsc435-1 Objectives To explain the principles of software process improvement To explain how software process factors influence software quality and productivity To introduce the SEI
More informationSoftware Process Improvement Framework Based on CMMI Continuous Model Using QFD
www.ijcsi.org 281 Software Process Improvement Framework Based on CMMI Continuous Model Using QFD Yonghui CAO 1, 2 1, School of Economics & Management, Henan Institute of Science and Technology, Xin Xiang,
More informationProcess Improvement. From the Software Engineering Institute:
Process Improvement From the Software Engineering Institute: The Software Capability Maturity Model (SW-CMM, CMMI) (Especially CMMI V1.1 Tutorial) The Personal Software Process (PSP) (Also see The Team
More informationAN OVERVIEW OF INDUSTRIAL SOFTWARE DOCUMENTATION PRACTICES
AN OVERVIEW OF INDUSTRIAL SOFTWARE DOCUMENTATION PRACTICES Marcello Visconti 1 Departamento de Informática Universidad Técnica Federico Santa María Valparaíso, CHILE visconti@inf.utfsm.cl Curtis R. Cook
More informationAfter the Appraisal: A Systematic Survey of Process Improvement, its Benefits, and Factors that Influence Success
Technical Report CMU/SEI-95-TR-009 ESC-TR-95-009 After the Appraisal: A Systematic Survey of Process Improvement, its Benefits, and Factors that Influence Success Dennis R. Goldenson James D. Herbsleb
More informationAbout the time Fred Brooks was warning us there was. Capability Maturity Mo. Software Quality and the
Software Quality and the Capability Maturity Mo About the time Fred Brooks was warning us there was not likely to be a single, silver bullet solution to the essential difficulties of developing software
More informationMahmoud Khraiwesh Faculty of Science and Information Technology Zarqa University Zarqa - Jordan mahmoud@zpu.edu.jo
World of Computer Science and Information Technology Journal (WCSIT) ISSN: 2221-0741 Vol. 1, No. 2, 26-33, 2011 Validation Measures in CMMI Mahmoud Khraiwesh Faculty of Science and Information Technology
More informationCMMI Version 1.2. SCAMPI SM A Appraisal Method Changes
Pittsburgh, PA 15213-3890 CMMI Version 1.2 SCAMPI SM A Appraisal Method Changes SM CMM Integration, IDEAL, and SCAMPI are service marks of Carnegie Mellon University. Capability Maturity Model, Capability
More informationProject Management. Week 9 Quality Assurance. Quality Assurance. Lecture Overview
Project Management Week 9 Quality Assurance Lecture Overview What is Quality Assurance? Do we need a quality management system for software? Impact of ISO9000 ISO9001 & ISO9000.3 TickIT ISO9000 V s CMM
More informationProcess Improvement. Process improvement. Process improvement stages. Understanding, Modelling and Improving the Software Process
Process Improvement Understanding, Modelling and Improving the Software Process Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 31 Slide 1 Process improvement Understanding existing processes
More informationThe Personal Software Process SM (PSP SM )
The Personal Software Process SM (PSP SM ) Watts S. Humphrey November 2000 TECHNICAL REPORT CMU/SEI-2000-TR-022 ESC-TR-2000-022 Pittsburgh, PA 15213-3890 The Personal Software Process SM (PSP SM ) CMU/SEI-2000-TR-022
More informationWhat do you think? Definitions of Quality
What do you think? What is your definition of Quality? Would you recognise good quality bad quality Does quality simple apply to a products or does it apply to services as well? Does any company epitomise
More informationCAPABILITY MATURITY MODEL INTEGRATION
CAPABILITY MATURITY MODEL INTEGRATION Radu CONSTANTINESCU PhD Candidate, University Assistant Academy of Economic Studies, Bucharest, Romania E-mail: radu.constantinescu@ie.ase.ro Web page: http:// www.raduconstantinescu.ase.ro
More informationRAMALA: A KNOWLEDGE BASE FOR SOFTWARE PROCESS IMPROVEMENT
RAMALA: A KNOWLEDGE BASE FOR SOFTWARE PROCESS IMPROVEMENT Y. Rimawi Computer Science Department, Carlos III University of Madrid, Avda. de la Universidad 30, 28911 Leganes, Madrid, Spain A. Amescua Computer
More informationUsing Students as Experiment Subjects An Analysis on Graduate and Freshmen Student Data
Using Students as Experiment Subjects An Analysis on and Student Data Per Runeson Lund University, Dept. of Communication Systems, Box 118, SE-221 00 Lund, Sweden per.runeson@telecom.lth.se ABSTRACT The
More informationV. Phani Krishna et al, / (IJCSIT) International Journal of Computer Science and Information Technologies, Vol. 2 (6), 2011, 2915-2919
Software Quality Assurance in CMM and XP- A Comparative Study CH.V. Phani Krishna and Dr. K.Rajasekhara Rao CSE Department, KL University, Guntur dt., India. Abstract Software Quality Assurance is a planned
More informationA Comparison of ISO 9001 and the Capability Maturity Model for Software
Technical Report CMU/SEI-94-TR-12 ESC-TR-94-12 A Comparison of ISO 9001 and the Capability Maturity Model for Software Mark C. Paulk July 1994 Technical Report CMU/SEI-94-TR-12 ESC-TR-94-12 July 1994 A
More informationSW Process Improvement and CMMI. Dr. Kanchit Malaivongs Authorized SCAMPI Lead Appraisor Authorized CMMI Instructor
SW Process Improvement and CMMI Dr. Kanchit Malaivongs Authorized SCAMPI Lead Appraisor Authorized CMMI Instructor Topics of Presentation Why improvement? What is CMMI? Process Areas and Practices in CMMI
More informationThe Personal Software Process 1 by Watts S. Humphrey watts@sei.cmu.edu Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213
The Personal Software Process 1 by Watts S. Humphrey watts@sei.cmu.edu Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 Copyright (c) 1994 Institute of Electrical and Electronics
More informationThe Challenge of Productivity Measurement
Proceedings: Pacific Northwest Software Quality Conference, 2006 The Challenge of Productivity Measurement David N. Card Q-Labs, Inc dca@q-labs.com Biography- David N. Card is a fellow of Q-Labs, a subsidiary
More informationCSC 408F/CSC2105F Lecture Notes
CSC 408F/CSC2105F Lecture Notes These lecture notes are provided for the personal use of students taking CSC 408H/CSC 2105H in the Fall term 2004/2005 at the University of Toronto. Copying for purposes
More informationConfiguration Management and ISO 9001 Robert Bamford, William J. Deibler II Software Systems Quality Consulting
ISO 9000 Update Configuration Management and ISO 9001 Robert Bamford, William J. Deibler II Software Systems Quality Consulting The software engineering practices associated with software configuration
More informationThe Role of the Quality Group in Software Development
The Role of the Quality Group in Software Development Douglas Hoffman Software Quality Methods, LLC. 124646 Heather Heights Place Saratoga, CA 95070 (408) 741-4830 Abstract This paper describes the role
More informationHow To Understand And Understand The Cmm
W H I T E P A P E R SEI's Capability Maturity Model Integrated (CMMI) Relative to ICM's CMII (Rev B) SUMMARY CMMI is built on a set of integrated processes and includes CM as a supporting process. The
More informationHow To Create A Process Measurement System
Set Up and Operation of a Design Process Measurement System Included below is guidance for the selection and implementation of design and development process measurements. Specific measures can be found
More informationImplementing Systematic Requirements Management in a Large Software Development Programme
Implementing Systematic Requirements Management in a Large Software Development Programme Caroline Claus, Michael Freund, Michael Kaiser, Ralf Kneuper 1 Transport-, Informatik- und Logistik-Consulting
More informationQuality Management for Small Enterprises
Quality Management for Small Enterprises Jürgen Börstler, Olof Johansson, Astrid Laryd, Terttu Orci, Hans Segerberg, Ola Ågren UMINF-02.20 ISSN-0348-0542 UMEÅ UNIVERSITY Department of Computing Science
More informationAgile, TSP SM, CMMI pick one, pick two, pick all three!
1 Agile, TSP SM, CMMI pick one, pick two, pick all three! Daniel M. Roy Cape Town SPIN 20 February, 2008 PSP, TSP, Personal Software Process and Team Software Process are service marks of CMU CMM is and
More informationSecure Software Development Life Cycle Processes: A Technology Scouting Report
Secure Software Development Life Cycle Processes: A Technology Scouting Report Noopur Davis December 2005 Software Engineering Process Management Unlimited distribution subject to the copyright. Technical
More informationCS 1632 SOFTWARE QUALITY ASSURANCE. 2 Marks. Sample Questions and Answers
CS 1632 SOFTWARE QUALITY ASSURANCE 2 Marks Sample Questions and Answers 1. Define quality. Quality is the degree of goodness of a product or service or perceived by the customer. Quality concept is the
More informationPersonal Software Process (PSP)
Personal Software Process (PSP) Application of CMM principles to individuals Developed by Watts Humphrey of the Software Engineering Institute (SEI) in the early 1990s Extensive supporting materials: books,
More informationSoftware Process Improvement Works! Advanced Information Services Inc. Pat Ferguson Gloria Leman Prasad Perini Susan Renner Girish Seshagiri
Software Process Improvement Works! Advanced Information Services Inc. Pat Ferguson Gloria Leman Prasad Perini Susan Renner Girish Seshagiri November 1999 TECHNICAL REPORT CMU/SEI-99-TR-027 ESC-TR-99-026
More informationTowards a new approach of continuous process improvement based on CMMI and PMBOK
www.ijcsi.org 160 Towards a new approach of continuous process improvement based on CMMI and PMBOK Yassine Rdiouat 1, Naima Nakabi 2, Khadija Kahtani 3 and Alami Semma 4 1 Department of Mathematics and
More informationHow Rational Configuration and Change Management Products Support the Software Engineering Institute's Software Capability Maturity Model
How Rational Configuration and Change Management Products Support the Software Engineering Institute's Software Capability Maturity Model by Bill Cottrell and John Viehweg Software Engineering Specialists
More informationImplementing a Personal Software Process (PSP SM ) Course: A Case Study
Journal of Software Engineering and Applications, 212, 5, 639-644 http://dx.doi.org/1.4236/jsea.212.5874 Published Online August 212 (http://www.scirp.org/journal/jsea) 639 Implementing a Personal Software
More informationA History of the Capability Maturity Model for Software
G E N E R A L K N O W L E D G E The Engineering Institute developed a five-level Capability Maturity Model for that described how software organizations transform their capability for building software
More informationSimulation of Different SPI Models
Simulation of Different SPI Models Bharti Sharma Neeraj Sharma Neeshu Sharma Student, M-tech Lecturer Student, M-tech Department of CSE Department of CSE Department of CSE Punjabi University Patiala Punjabi
More informationSoftware engineering: a quality management perspective John McManus University of Lincoln, Lincoln, UK, and
The current issue and full text archive of this journal is available at wwwemeraldinsightcom/0954-478xhtm Software engineering: a quality perspective John McManus University of Lincoln, Lincoln, UK, and
More informationSteve Masters (SEI) SEPG North America March 2011. 2011 Carnegie Mellon University
Using Organizational Business Objectives to Guide a Process Improvement Program Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 (SEI) SEPG North America March 2011 Agenda
More informationHOW ISO 9001 COMPARES WITH THE CMM. he Capability Maturity Model
FEATURE Organizations concerned with ISO 9001 certification often question its overlap with the Software Engineering Institute s Capability Maturity Model. The author looks at 20 clauses in ISO 9001 and
More informationScrum and CMMI Level 5: The Magic Potion for Code Warriors
Scrum and CMMI Level 5: The Magic Potion for Code Warriors Jeff Sutherland, Ph.D. Patientkeeper Inc. jeff.sutherland@computer.org Carsten Ruseng Jakobsen Systematic Software Engineering crj@systematic.dk
More informationUsing the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects
Transdyne Corporation CMMI Implementations in Small & Medium Organizations Using the Agile Methodology to Mitigate the Risks of Highly Adaptive Projects Dana Roberson Quality Software Engineer NNSA Service
More informationSoftware Quality Assurance: VI Standards
Software Quality Assurance: VI Standards Room E 3.165 Tel. 60-3321 Email: hg@upb.de Outline I Introduction II Software Life Cycle III Quality Control IV Infrastructure V Management VI Standards VII Conclusion
More informationDistributed and Outsourced Software Engineering. The CMMI Model. Peter Kolb. Software Engineering
Distributed and Outsourced Software Engineering The CMMI Model Peter Kolb Software Engineering SEI Trademarks and Service Marks SM CMM Integration SCAMPI are service marks of Carnegie Mellon University
More informationSoftware Quality. Process Quality " Martin Glinz. Chapter 5. Department of Informatics!
Department of Informatics! Martin Glinz Software Quality Chapter 5 Process Quality " 2014 Martin Glinz. All rights reserved. Making digital or hard copies of all or part of this work for educational, non-commercial
More informationImproper Use of Control Charts: Traps to Avoid
Improper Use of Control Charts: Traps to Avoid SEPG 2006 Virginia Slavin Agenda Why Statistical Process Control? Data Assumptions Signal Rules Common Issues with Control Charts Summary March 2006 2 Why
More informationSoftware Quality Data Part 1: Basic and Derived Metrics
Abstract We measure, quantify and report on software quality. But can we control it? Can we actually assure quality (as opposed to just measuring it)? This is the first of three papers in which we will
More informationThe Software Quality Group's Relationship to Development
The Software Quality Group's Relationship to Development Douglas Hoffman Software Quality Methods San Jose, CA 95130 Abstract This paper presents the roles of the Software Quality Organization in software
More informationCMMI 100 Success Secrets
CMMI 100 Success Secrets Capability Maturity Model Integration 100 Success Secrets - 100 Most Asked Questions: The Missing CMMI-DEV, CMMI-ACQ Project Management and Process Guide Lance Batten CMMI 100
More informationDynamic CMM for Small Organizations
Dynamic CMM for Small Organizations A.Laryd, T.Orci Umeå University, Department of Computer Science 1 S-901 87 Umeå, Sweden astrid.laryd@swipnet.se, terttu@dsv.su.se Abstract Software CMM has gained wide
More informationCapability Maturity Model Integration (CMMI ) Version 1.2 Overview
Capability Maturity Model Integration (CMMI ) Version 1.2 Overview SM CMM Integration, IDEAL, Personal Software Process, PSP, SCAMPI, SCAMPI Lead Appraiser, Team Software Process, and TSP are service marks
More informationCase Study of CMMI implementation at Bank of Montreal (BMO) Financial Group
Case Study of CMMI implementation at Bank of Montreal (BMO) Financial Group Background Started in 1817, Bank of Montreal - BMO Financial Group (NYSE, TSX: BMO) is a highly diversified financial services
More informationChapter 8: Project Quality Management
CIS 486 Managing Information Systems Projects Fall 2003 (Chapter 8), PhD jwoo5@calstatela.edu California State University, LA Computer and Information System Department Chapter 8: Project Quality Management
More informationContinuous Risk Management Guidebook
Carnegie Mellon Software Engineering Institute Continuous Guidebook Audrey J. Dorofee Julie A. Walker Christopher J. Alberts Ronald P. Higuera Richard L. Murphy Ray C. Williams The ideas and findings in
More informationUSING SECURITY METRICS TO ASSESS RISK MANAGEMENT CAPABILITIES
Christina Kormos National Agency Phone: (410)854-6094 Fax: (410)854-4661 ckormos@radium.ncsc.mil Lisa A. Gallagher (POC) Arca Systems, Inc. Phone: (410)309-1780 Fax: (410)309-1781 gallagher@arca.com USING
More informationSoftware Project Management and Support - Practical Support for CMMI -SW Project Documentation: Using IEEE Software Engineering Standards
Software Project Management and Support - Practical Support for CMMI -SW Project Documentation: Using IEEE Software Engineering Standards John Walz The Sutton Group IEEE Computer Society Standards Activities
More informationPROCESS IMPROVEMENT CAPABILITY MATURITY MODEL
PROCESS IMPROVEMENT CAPABILITY MATURITY MODEL Immature versus Mature Software Organisations In an immature software organisation, software processes are generally improvised by practitioners and their
More informationWhy Does Software Work Take So Long? Watts S. Humphrey
In writing this column, I plan to discuss various topics of interest to software professionals and managers. In general, I will write about issues related to engineering productivity, quality, and overall
More informationORACLE NAIO Excellence combined with Quality A CMMI Case study
CASE STUDY ORACLE NAIO Excellence combined with Quality A CMMI Case study softwaredi xide com www.qaiasia.com THE CLIENT Process and Quality are important for measuring improvement. Improvement means different
More informationSTUDY OF SPI FRAMEWORK FOR CMMI CONTINUOUS MODEL BASED ON QFD
STUDY OF SPI FRAMEWORK FOR CMMI CONTINUOUS MODEL BASED ON QFD 1,2 YONGHUI CAO 1 School of Economics & Management, Henan Institute of Science and Technology 2 School of Management, Zhejiang University,
More informationDesign of Software Process Improvement Model
Design of Software Process Improvement Model Ankit Aggarwal Department of Computer Engineering M.TECH H.C.T.M Kaithal India (Haryana) Alankrita Aggarwal Assistant Professor Department of Computer Engineering
More informationA CASE STUDY ON SOFTWARE PROJECT MANAGEMENT IN INDUSTRY EXPERIENCES AND CONCLUSIONS
A CASE STUDY ON SOFTWARE PROJECT MANAGEMENT IN INDUSTRY EXPERIENCES AND CONCLUSIONS P. Mandl-Striegnitz 1, H. Lichter 2 1 Software Engineering Group, University of Stuttgart 2 Department of Computer Science,
More informationEvaluating the Quality of Software Engineering Performance Data
Evaluating the Quality of Software Engineering Performance Data James Over Software Engineering Institute Carnegie Mellon University July 2014 Copyright 2014 Carnegie Mellon University This material is
More informationFundamentals of Measurements
Objective Software Project Measurements Slide 1 Fundamentals of Measurements Educational Objective: To review the fundamentals of software measurement, to illustrate that measurement plays a central role
More informationISO 9000-3 OR CMM: WHICH IS MORE EXTENSIVE FOR THE QUALITY SYSTEMS IN A SOFTWARE INDUSTRY?
International Journal of Advanced Research in Engineering and Applied Sciences ISSN: 2278-6252 ISO 9000-3 OR CMM: WHICH IS MORE EXTENSIVE FOR THE QUALITY SYSTEMS Monika Yadav* Kaushik Kumar** IN A SOFTWARE
More informationSoftware Process Models and Project Performance
Information Systems Frontiers 1:3, 267±277 (1999) # 2000 Kluwer Academic Publishers, Boston. Manufactured in The Netherlands. Software Process Models and Project Performance M.S. Krishnan University of
More information