Software Quality Management Lecture Notes PDF

Software Quality Management Prof. R. Mall Dept. of CSE, IIT, Kharagpur 1  Plan of the Talk  Introduction to Quality Engineering.  Quality control and Quality Assurance  ISO 9000  SEI CMM  Summary 2  Int...

Software Quality Management Prof. R. Mall Dept. of CSE, IIT, Kharagpur 1  Plan of the Talk  Introduction to Quality Engineering.  Quality control and Quality Assurance  ISO 9000  SEI CMM  Summary 2  Introduction  Traditional definition of quality: Fitness of purpose: A quality product does exactly what the users want it to do. 3  Fitness of Purpose  Fitness of purpose for software products: Satisfaction of the requirements specified in SRS document. 4  Fitness of Purpose  A satisfactory definition of quality for many products: A car, a table fan, a food mixer, microwave oven, etc.  But, not satisfactory for software products. Why? 5  Quality for Software Products  Consider a software product: Functionally correct:  Performs all functions as specified in the SRS document. But, has an almost unusable user interface.  Cannot be considered as a quality product. 6  Quality for Software Products  Consider another example: A product which does everything that users want. But has an almost incomprehensible and unmaintainable code. Will you call it a quality product? 7  Modern View of Quality  Several quality factors are associated with a software product : Correctness Reliability Efficiency (includes efficiency of resource utilization) Portability Usability Reusability Maintainability 8  Correctness  A software product is correct: If different requirements as specified in the SRS document have been correctly implemented. Results are accurate. 9  Portability  A software product is said to be portable: If it can be easily made to work In different operating systems. In different machines, With other software products, etc. 10  Reusability  A software product has good reusability: If different modules of the product can easily be reused to develop new products. 11  Usability  A software product has good usability: If different categories of users (i.e. both expert and novice users) can easily invoke the functions of the product. 12  Maintainability  A software product is maintainable: If errors can be easily corrected as and when they show up, New functions can be easily added to the product, Functionalities of the product can be easily modified. 13  Software Quality Management System  Quality management system (or quality system): Principal methodology used by organizations to ensure that the products have desired quality. 14  Quality System  A quality system consists of the following: Managerial Structure Individual Responsibilities.  Responsibility of the organization as a whole. 15  Quality System  Every quality conscious organization has an independent quality department: Performs several quality system activities. Needs support of top management. Without support at a high level in a company:  Many employees may not take the quality system seriously. 16  Quality System Activities  Auditing of projects  Development of: standards, procedures, and guidelines.  Production of reports for the top management: Summarizing the effectiveness of the quality system in the organization.  Review of the quality system itself. 17  Quality System  A good quality system must be well documented. Without a properly documented quality system,  Application of quality procedures become ad hoc,  Results in large variations in the quality of the products delivered. 18  Quality System  An undocumented quality system: Sends clear messages to the staff about the attitude of the organization towards quality assurance.  International standards such as ISO 9000 provide: Guidance on how to organize a quality system. 19  Evolution of Quality Systems  Quality systems have evolved: Over the last six decades.  Prior to World War II: Accepted way to produce quality products:  Inspect the finished products  Eliminate defective products. 20  Evolution of Quality Systems  Since World war II, Quality systems of organizations have undergone:  Four stages of evolution.  Many advances came from Japanese: Helped resurrect Japanese economy. 21 Evolution of Quality Systems 22  Evolution of Quality Systems  Initial product inspection method: Gave way to quality control (QC).  Quality control: Not only detect the defective products and eliminate them But also determine the causes behind the defects. 23  Quality Control (QC)  Quality control aims at correcting the causes of errors: Not just rejecting defective products.  Statistical quality control (SQC): Quality of the output of the process is inferred using statistical methods. In stead of inspection or testing of all products. 24  Quality Control (QC)  The next breakthrough: Development of quality assurance principles. 25  Quality Assurance  Basic premise of modern quality assurance: If an organization's processes are good and are followed rigorously:  The products are bound to be of good quality. 26  Quality Assurance  All modern quality paradigms include: Guidance for recognizing, defining, analyzing, and improving the production process. 27  Total Quality Management (TQM)  TQM advocates: Continuous process improvements through process measurements. 28  Business Process Reengineering  BPR:A term related to TQM.  Process reengineering goes a step further than quality assurance: Aims at continuous process improvement. 29  Business Process Reengineering  TQM focuses on reengineering of the software process.  Whereas BPR aims at reengineering the way business is carried out in any organization:  Not just software development. 30  Total Quality Management (TQM)  TQM goes beyond documenting processes Optimizes them through redesign.  Over the years the quality paradigm has shifted: From product assurance to process assurance. 31 Process Improvement  Implies introducing process changes to improve:  Product quality  Reduce costs  Accelerate schedules.  Most process improvement work so far has focused on defect reduction. 32  Process Attributes Process Description characteristic Understandability To what extent is the process explicitly defined and how easy is it to understand the process definition? Visibility Do the process activities culminate in clear results so that the progress of the process is externally visible? Supportability To what extent can CASE tools be used to support the process activities? Acceptability Is the defined process acceptable to and usable by the engineers responsible for producing the software product? Reliability Is the process designed in such a way thatprocess errorsare avoided or trapped before they result in product errors? Robustness Can the processcontinue in spite ofunexpected problems? Maintainability Can the process evolve to reflect changing organisational requirements or identified process improvements? Rapidity How fast can the process of delivering a system from a given specification becompleted? 33  The Process Improvement Cycle Measure Change Analyse 34  Process Improvement Stages  Process measurement  Attributes of the process are measured.  Form a baseline for assessing improvements.  Process analysis  The process is assessed and bottlenecks and weaknesses are identified.  Process change  Changes to the process that have been identified during the analysis are introduced. 35  Process and Product Quality  A good process is usually required to produce a good product.  For manufactured goods, process is the principal quality determinant.  For design-based activity, other factors are also involved:  For example, the capabilities of the designers. 36  ISO 9000  ISO (international Standards Organization): a consortium of 63 countries established to formulate and foster standardization.  ISO published its 9000 series of standards in 1987. 37  What is ISO 9000 Certification?  ISO 9000 certification: Serves as a reference for contract between independent parties.  The ISO 9000 standard: Specifies guidelines for maintaining a quality system. 38  What is ISO 9000 Certification?  ISO 9000 specifies: Guidelines for repeatable and high quality product development. Also addresses organizational aspects  Responsibilities, reporting, procedures, processes, and resources for implementing quality management. 39  ISO 9000  A set of guidelines for the production process. Not directly concerned about the product it self. A series of three standards:  ISO 9001, ISO 9002, and ISO 9003. 40  ISO 9000  Based on the premise: If a proper process is followed for production: Good quality products are bound to follow. 41  ISO 9001  Applies to: Organizations engaged in design, development, production, and servicing of goods. Applicable to most software development organizations. 42  ISO 9002  ISO 9002 applies to: Organizations who do not design products:  but are only involved in production.  Examples of this category of industries: Steel or car manufacturing industries  Buy the product and plant designs from external sources:  only manufacture products. Not applicable to software development organizations. 43  ISO 9003  ISO 9003 applies to: Organizations involved only in installation and testing of the products. 44  ISO 9000 for Software Industry  ISO 9000 is a generic standard: Applicable to many industries,  Starting from a steel manufacturing industry to a service rendering company.  Many clauses of ISO 9000 documents: Use generic terminologies Very difficult to interpret them in the context of software organizations. 45  Software vs. Other Industries  Very difficult to interpret many clauses for software industry: Software development is radically different from development of other products. 46  Software vs. Other Industries  Software is intangible: Therefore difficult to control.  It is difficult to control anything that we cannot see and feel. In contrast, in a car manufacturing unit:  We can see a product being developed through stages such as fitting engine, fitting doors, etc.  One can accurately tell about the status of the product at any time. Software project management is an altogether different ball game. 47  Software vs. Other Industries  During software development: The only raw material consumed is data.  For any other product development: Lot of raw materials consumed  e.g. Steel industry consumes large volumes of iron ore, coal, limestone, etc.  ISO 9000 standards have many clauses corresponding to raw material control.  Not relevant to software organizations. 48  Software vs. Other Industries  Radical differences exist between software and other product development: Difficult to interpret various clauses of the original ISO standard in the context of software industry. 49  ISO 9000 Part-3  ISO released a separate document called ISO 9000 part-3 in 1991: To help interpret the ISO standard for software industry.  At present: Official guidance is inadequate. 50  ISO 9000: 2000  ISO 9001:2000: Combines the three standards 9001, 9002, and 9003 into one.  Design and development procedures are required: Only if a company does in fact engage in the creation of new products.  The 2000 version sought to make a radical change in thinking: By actually highlighting the concept of process management. 51  ISO 9000: 2000  Another goal is to improve effectiveness via process performance metrics: Numerical measurement of the effectiveness of tasks and activities. Continual process improvement and tracking customer satisfaction were made explicit. 52  Why Get ISO 9000 Certification?  Several benefits: Confidence of customers in an organization increases.  If organization qualified for ISO 9001 certification.  This is especially true in the international market. 53  Why Get ISO 9000 Certification?  Many international software development contracts insist: Development organization to have ISO 9000 certification. 54  Why Get ISO 9000 Certification?  Requires: A well-documented software production process to be in place. Contributes to repeatable and higher quality software.  Makes development process: Focussed, efficient, and cost- effective 55  Why Get ISO 9000 Certification?  Points out the weakness of an organizations: Recommends remedial action.  Sets the basic framework: For development of an optimal process and TQM. 56  How to Get ISO 9000 Certification?  An organization intending to obtain ISO 9000 certification: Applies to a ISO 9000 registrar for registration.  ISO 9000 registration process consists of several stages. 57  How to Get ISO 9000 Certification?  Application stage: Applies to a registrar for registration.  Pre-assessment: The registrar makes a rough assessment of the organization. 58  How to Get ISO 9000 Certification?  Document review and adequacy audit: Process and quality-related documents. The registrar reviews the documents. Makes suggestions for improvements. 59  How to Get ISO 9000 Certification?  Compliance audit: The registrar checks:  Whether the suggestions made by it during review have been complied. 60  How to Get ISO 9000 Certification?  Registration: The registrar awards ISO 9000 certificate after successful completions of all previous phases.  Continued surveillance:  The registrar continues monitoring the organization periodically. 61  ISO 9000 Certification  An ISO certified organization : Can use the certificate for corporate advertizements. Cannot use the certificate to advertize its products.  ISO 9000 certifies organization's process  Not any product of the organization. An organization using ISO certificate for product advertizements:  Risks withdrawal of the certificate. 62  Summary of ISO 9001 Requirements  Management responsibility(4.1): Management must have an effective quality policy. The responsibility and authority of all those whose work affects quality:  Must be defined and documented. 63  Management Responsibility(4.1)  Responsibility of the quality system. Independent of the development process. Can work in an unbiased manner.  The effectiveness of the quality system: Must be periodically by audited. 64  Quality System (4.2) and Contract Reviews (4.3):  A quality system must be maintained and documented.  Contract reviews (4.3): Before entering into a contract, an organization must review the contract  Ensure that it is understood,  Organization has the capability for carrying out its obligations. 65  Design Control (4.4)  The design process must be properly controlled: This includes controlling coding also.  A good configuration control system must be in place. 66  Design Control (4.4)  Design inputs must be verified as adequate.  Design must be verified.  Design output must be of required quality.  Design changes must be controlled. 67  Document Control (4.5)  Proper procedures for: Document approval, issue and removal.  Document changes must be controlled. Use of some configuration management tools is necessary. 68  Purchasing (4.6)  Purchased material, including bought-in software: Must be checked for conforming to requirements. 69  Purchaser Supplied Products (4.7)  Material supplied by a purchaser: For example, Client-provided software must be properly managed and checked. 70  Product Identification (4.8)  The product must be identifiable at all stages of the process. In software development context this means configuration management. 71  Process Control (4.9)  The development must be properly managed.  Quality requirements must be identified in a quality plan. 72  Inspection and Testing (4.10)  In software terms this requires effective testing i.e., Unit testing, integration testing and system testing.  Test records must be maintained. 73  Inspection, Measuring and Test Equipment(4.11)  If integration, measuring, and test equipments are used, Must be properly maintained and calibrated. 74  Control of Nonconforming Product (4.13)  In software terms, Keeping untested or faulty software out of released product, Or out of other places whether it might cause damage. 75  Corrective Action (4.14)  This is both about correcting errors when found: Investigating why they occurred Improving the process to prevent further occurrences.  If an error reoccurs despite the quality system: The system needs improvement. 76  Handling (4.15) and Quality Audits (4.17):  Handling (4.15) Deals with: Storage, packing, and delivery of the software product.  Quality Audits (4.17) : Quality system audit must be carried out to ensure its effectiveness. 77  Training (4.18)  Training needs must be identified and met.  Most items of ISO standard: Are largely common sense. 78 Salient Features of ISO 9001 Requirements:  All documents concerned with the development of a software product: Should be properly managed, authorized, and controlled.  Proper plans should be prepared: Progress against these plans should be monitored. 79  Salient Features of ISO 9001 Requirements  Important documents independently checked and reviewed:  For effectiveness and correctness.  The product should be tested : Against specification.  Several organizational aspects: e.g., management reporting of the quality team. 80  Shortcomings of ISO 9001 Certification  ISO 9000 requires a production process to be adhered to: But does not guarantee the process to be of high quality. Does not give any guideline for defining an appropriate process. 81  Shortcomings of ISO 9001 Certification cont…  ISO 9000 certification process: Not fool-proof No international accredition agency exists. Likely variations in the norms of awarding certificates:  Among different accredition agencies and among the registrars. 82  Shortcomings of ISO 9001 Certification (3)  Organizations qualifying for ISO 9001 certification: Tend to downplay domain expertise. Tend to believe that since a good process is in place,  Any engineer is as effective as any other engineer in doing any particular activity relating to software development. 83  Shortcomings of ISO 9001 Certification (4)  In manufacturing industry: Clear link between process quality and product quality. Once a process is calibrated:  Can be run again and again producing quality goods.  Software development is a creative process: Individual skills and experience is significant. 84  Shortcomings of ISO 9001 Certification (5)  Many areas of software development are very specialized: Special expertize and experience (domain expertize) required.  ISO 9001: Does not automatically lead to continuous process improvement, Does not automatically lead to TQM. 85  Shortcomings of ISO 9001 Certification (6)  ISO 9001 addresses mostly management aspects.  Techniques specific to software development have been ignored: Configuration management Reviews Release builds Problem Notification system Intranets 86  SEI Capability Maturity Model (CMM)  Developed by Software Engineering Institute (SEI) of the Carnegie Mellon University, USA: To assist the U.S. Department of Defense (DoD) in software acquisition. The rationale was to include:  Likely contractor performance as a factor in contract awards. 87  SEI Capability Maturity Model  Major DoD contractors began CMM-based process improvement initiatives: As they vied for DoD contracts.  SEI CMM helped organizations: Helped Improve quality of software they developed Realized adoption of SEI CMM model had significant business benefits.  Other organizations adopted CMM. 88  SEI Capability Maturity Model  In simple words: CMM is a model for apprising the software process maturity of a contractor into different levels. Can be used to predict the most likely outcome to be expected:  from the next project that the organization undertakes. 89  SEI Capability Maturity Model  Can be used in two ways: Capability evaluation Software process assessment. 90  Capability Evaluation  Provides a way to assess the software process capability of an organization: Helps in selecting a contractor Indicates the likely contractor performance. 91  Software Process Assessment  Used by an organization to assess its current process: Suggests ways to improve the process capability. This type of assessment is for purely internal use. 92  SEI Capability Maturity Model  The SEI CMM classifies software development industries into:  Five maturity levels.  Stages are ordered so that improvements at one stage provide foundations for the next.  Based on the pioneering work of Philip Crosby. 93  SEI Capability Maturity Model Optimizing (5) Managed (4) Defined (3) Repeatable (2) Initial (1) 94  Level 1: (Initial)  Organization operates Without any formalized process or project plans  An organization at this level is characterized by Ad hoc and often chaotic activities. 95  Level 1: (Initial)  Software production processes are not defined, Different engineers follow their own process Development efforts become chaotic. The success of projects depend on individual efforts and heroics. 96  Level 2: (Repeatable)  Basic project management practices Tracking cost, schedule, and functionality are followed.  Size and cost estimation techniques: Function point analysis, COCOMO, etc. used.  Production process is ad hoc: Not formally defined Also not documented. 97  Level 2: (Repeatable)  Process used for different projects might vary between projects: Earlier success on projects with similar applications can be repeated. Opportunity to repeat process exist when a company produces a family of products. 98  Level 3: (Defined)  Management and development activities: Defined and documented. Common organization-wide understanding of activities, roles, and responsibilities. 99  Level 3: (Defined)  The process though defined: Process and product qualities are not measured.  ISO 9001 aims at achieving this level. 100  Level 4: (Managed)  Quantitative quality goals for products are set.  Software process and product quality are measured: The measured values are used to control the product quality. Results of measurement used to evaluate project performance:  Rather than improve process. 101  Level 4: (Managed)  Organization sets quantitative quality goals.  World-wide about 100 organizations assessed at this level. 102  Level 5: (Optimizing)  Statistics collected from process and product measurements are analyzed: Continuous process improvement based on the measurements.  Known types of defects are prevented from recurring by tuning the process  Lessons learned from specific projects incorporated into the process 103  Level 5: (Optimizing)  Identify best software engineering practices and innovations: Tools, methods, or process are identified. Transferred throughout the organization.  World-wide about 500 organizations have been assessed at this level. 104  Key Process Areas  Each level is associated with a key process area (KPA) identifies: Where an organization at the previous level must focus to reach this level. 105  Level 2 KPAs  Software project planning: Size, cost, schedule. Project monitoring  Configuration management  Subcontract management 106  Level 3 KPAs  Process definition and documentation.  Reviews  Training program 107  Level 4 KPAs  Quantitative measurements.  Process management. 108  Level 5 KPAs  Defect prevention.  Technology change management.  Process change management. 109  Comparison Between ISO 9001 and SEI CMM  ISO 9001 awarded by an international standards body: Can be quoted in official documents and communications.  SEI CMM assessment is purely for internal use. 110  Comparison Between ISO 9001 and SEI CMM  SEI CMM was developed specifically for software industry: Addresses many issues specific to software industry.  SEI goes beyond quality assurance Aims for TQM. ISO 9001 correspond to SEI level 3. 111  Comparison Between ISO 9001 and SEI CMM  SEI CMM provides a list of key areas: On which to focus to take an organization from one level to the other  Provides a way for gradual quality improvements over several stages. e.g trying to implement a defined process before a repeatable process:  Counterproductive as managers are overwhelmed by schedule and budget pressure. 112  CMMI (CMM Integration)  CMMI is the successor of the CMM.  The CMM was developed from 1987 until 1997.  In 2002, CMMI Version 1.1 was released. Version 1.2 followed in August 2006.  The goal of the CMMI to integrate many different models into one framework. It was created by members of industry, government and the SEI. 113  Remarks on Quality Model Usage  Highly systematic and measured approach to software development process suits certain circumstances Negotiated software, safety-critical software, etc.  What about small organizations?  Typically handle applications such as internet, e- comm.  Without an established product range,  Without revenue base, experience on past projects, etc.  CMM may be incompatible 114  Small Organizations  Small organizations tend to believe: We are all competent people hired to do a job, we can’t afford training. We all communicate with one another.  Osmosis works because we are so close. We are all heroes:  We do what needs to be done.  Therefore rules do not apply to us. 115  Small Organizations  Often have problems: Undocumented requirements Inexperienced managers Documenting the product Resource allocation Training Peer reviews 116  Small Organizations  A two week CMM-based appraisal is probably excessive:  Small organizations need to operate more efficiently at lower levels of maturity Must first fluorish if eventually they are to mature 117  Personal Software Process (PSP)  Based on the work of Humphrey.  PSP is a scaled down version of industrial software process: Suitable for individual use.  Even CMM assumes that engineers use effective personal practices. 118  Personal Software Process (PSP)  A process is the set of steps for doing a job.  The quality and productivity of an engineer Largely determined by his process  PSP framework: Helps software engineers to measure and improve the way they work. 119  Personal Software Process (PSP)  Helps developing personal skills and methods. Estimating and planning method. Shows how to track performance against plans. Provides a defined process;  Can be fine tuned by individuals.  Recognizes that a process for individual use is different from that necessary for a team project. 120  Time Management  Track the way you spend time: Boring activities seem longer then actual. Interesting activities seem short.  Record time for: Designing Writing code Compiling Testing 121  Personal Software Process (PSP) Planning Design Code Logs Compile Test Project plan Postmortem summary 122  PSP-Planning  Problem definition  Estimate max, min, and total LOC  Determine minutes/LOC  Calculate max,min, and total development times  Enter the plan data in project plan summary form  Record the planned time in Log 123  PSP-Design  Design the program.  Record the design in specified format.  Record the Design time in time recording log. 124  PSP-Code  Implement the design.  Use a standard format for code text.  Record the coding time in time recording log. 125  PSP-Compile  Compile the program.  Fix all the defects.  Record compile time in time recording log. 126  PSP-Test/Postmortem  Test: Test the program. Fix all the defects found. Record testing time in time recording log.  Postmortem: Complete project plan summary form with actual time and size data. Record postmortem time in time record. 127  Personal Software Process (PSP) PSP 3  Personal process evolution PSP 2  Personal quality management  Design and code reviews PSP 1 Personal planning  Time and schedule PSP 0  Personal measurement  Basic size measures 128  Six Sigma  Six sigma is a quantitative approach to eliminate defects: Applicable to all types of industry - from manufacturing, product development, to service.  The statistical representation of Six Sigma quantitatively describes : How a process is performing. 129  Six Sigma  To achieve six sigma: A process must not produce more than 3.4 defects per million opportunities. 5 Sigma -> 230 defects per million. 4 Sigma -> 6210 defects per million.  Six sigma methodologies: DMAIC (Define, Measure, Analyze, Improve, Control). DMADV: (Define, Measure, Analyze, Design, Verify). 130 Six Sigma Methodologies  The methodologies are implemented by Green belt and Black belt workers: Supervised by Master black belt worker.  Pareto Chart: Simple bar chart to represent defect data Identify the problems that occurs with greatest frequency  or incur the highest cost 131  Summary  Evolution of quality system: Product inspection Quality control Quality assurance Total quality management (TQM)  Quality paradigm change: From product to process 132  Summary  ISO 9000: Basic premise: If a good process is followed Good products are bound to follow. Provides guidelines for establishing a quality system. 133  Summary  ISO 9000: Series of three standards 9001, 9002, and 9003 9001 is applicable to software industry. 134  Summary  SEI CMM Developed specially for software industry. Classifies software organizations into five categories.  According to the maturity of their development process.  CMMI: Integrates existing quality techniques. 135  Current Trends  Many organizations have already tuned their process for: Budget, Schedule, and Quality product.  Competition is challenging them to: Reduce time for delivery Adopt Six-Sigma methodology 136