Software Engineering: A Practitioner’s Approach, 6/eSoftware Engineering: A Practitioner’s Approach, 6/eCCChapter 26Chapter 26Quality ManagementQuality Managementcopyright © 1996, 2001, 2005R.S. Pressman & Associates, Inc.For University Use OnlyMay be reproduced ONLY for student use at the university levelhdijtiithS ft E i i A P titi ' A hThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20051when used in conjunction with Software Engineering: A Practitioner's Approach.Any other reproduction or use is expressly prohibited.QualityQuality The The American Heritage DictionaryAmerican Heritage Dictionary defines defines qualityquality as as “a characteristic or attribute of something”“a characteristic or attribute of something”a characteristic or attribute of something. a characteristic or attribute of something. For software, two kinds of quality may be encountered: For software, two kinds of quality may be encountered: Quality of designQuality of design encompasses requirements, specifications, encompasses requirements, specifications, and the design of the system. and the design of the system. Quality of conformanceQuality of conformance is an issue focused primarily on is an issue focused primarily on implementation.implementation.ti f ti li t d t + d lit + d liti f ti li t d t + d lit + d liThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20052 user satisfaction = compliant product + good quality + delivery user satisfaction = compliant product + good quality + delivery within budget and schedulewithin budget and scheduleSoftware QualitySoftware QualityConformance to explicitly stated functional and Conformance to explicitly stated functional and performance requirements, explicitly documented performance requirements, explicitly documented development standards, and implicit characteristics development standards, and implicit characteristics that are expected of all professionally developed that are expected of all professionally developed software. software. These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20053Cost of QualityCost of Quality Prevention costsPrevention costs includeinclude quality planningquality planning formal technical reviewsformal technical reviewstest equipmenttest equipmenttest equipmenttest equipment TrainingTraining Internal failure costsInternal failure costs includeinclude reworkrework repairrepair failure mode analysisfailure mode analysis External failure costsExternal failure costs arearecomplaint resolutioncomplaint resolutionThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20054complaint resolutioncomplaint resolution product return and replacementproduct return and replacement help line supporthelp line support warranty workwarranty workSoftware Quality AssuranceSoftware Quality AssuranceFormalProcessFormalTechnicalReviewsTest Planning&ReviewMtAnalysis&ReportingDefinition &StandardsThese courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20055& ReviewMeasurementRole of the SQA GroupRole of the SQA Group--II Prepares an SQA plan for a project. Prepares an SQA plan for a project. The plan identifiesThe plan identifiesThe plan identifiesThe plan identifies evaluations to be performedevaluations to be performed audits and reviews to be performedaudits and reviews to be performed standards that are applicable to the projectstandards that are applicable to the project procedures for error reporting and trackingprocedures for error reporting and tracking documents to be produced by the SQA groupdocuments to be produced by the SQA group amount of feedback provided to the software project teamamount of feedback provided to the software project team Participates in the development of the project’s software process Participates in the development of the project’s software process description.description.These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 20056 The SQA group reviews the process description for compliance with The SQA group reviews the process description for compliance with organizational policy, internal software standards, externally imposed standards organizational policy, internal software standards, externally imposed standards (e.g., ISO(e.g., ISO--9001), and other parts of the software project plan.9001), and other parts of the software project plan.Role of the SQA GroupRole of the SQA Group--IIII Reviews software engineering activities to verify compliance with the Reviews software engineering activities to verify compliance with the defined software process.defined software process. identifies, documents, and tracks deviations from the process and verifies that identifies, documents, and tracks deviations from the process and verifies that ,, p,, pcorrections have been made.corrections have been made. Audits designated software work products to verify compliance with Audits designated software work products to verify compliance with those defined as part of the software process.those defined as part of the software process. reviews selected work products; identifies, documents, and tracks deviations; reviews selected work products; identifies, documents, and tracks deviations; verifies that corrections have been madeverifies that corrections have been made periodically reports the results of its work to the project manager.periodically
View Full Document