1. Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II

2. Software Engineering Process - II 7.2  What are your expectations from this unit? Before You Begin…

3. Software Engineering Process - II 7.3 Unit Objectives  Define quality management activities.  Explain process and product quality.  Define the quality assurance process.  Explain the types of quality standards and their importance.  Describe several types of documentation standards.  Identify the components of a quality plan.  Define the various methods of quality control.  Explain the fundamental types of software reviews.

4. Software Engineering Process - II 7.4 Quality Management  Formalized quality management consists of three activities:  Quality assurance: Establishment of a framework of organizational procedures and standards.  Quality planning: Selection of standards and procedures from this framework for a specific project.  Quality control: Establishment of processes to ensure that quality procedures and standards have been followed.

5. Software Engineering Process - II 7.5 Quality Management Process

6. Software Engineering Process - II 7.6 Quality Management Team  Quality management team:  Ensures an independent check on software development activities.  Should be independent from the development team so that they can take an objective view of the software.  Should take organization wide responsibility for quality management.

7. Software Engineering Process - II 7.7 Process and Product Quality  In manufacturing, development process quality directly affects the quality of delivered products.  In software, intangible aspects to software quality cannot be embodied in processes.  Role of design and creativity in the software process makes it difficult to predict how process changes will affect the product quality.

8. Software Engineering Process - II 7.8 Process and Product Quality (cont.)  Experience shows that process quality still has significant influence on the quality of software.

9. Software Engineering Process - II 7.9 Process and Product Quality (cont.)  Process quality management involves:  Defining process standards, such as how and when reviews should be conducted.  Monitoring the development process to ensure that the standards are being followed.  Reporting the software process to project management and to the client.

10. Software Engineering Process - II 7.10 Class Activity - 1  Discuss and list the problems associated with process-based quality assurance.

11. Software Engineering Process - II 7.11 Quality Assurance and Standards  Quality assurance defines the standards that should be applied to the software development process and work products.  Two types of quality standards may be established:  Product standards  Process standards

12. Software Engineering Process - II 7.12 Quality Assurance and Standards (cont.)  Software standards are important because:  They are based on knowledge of the most appropriate practice for the organization.  They provide a framework for implementing the quality assurance process.  They assist in continuity where work carried out by one person is taken up by someone else as the learning effort is less.

13. Software Engineering Process - II 7.13 Quality Assurance and Standards (cont.)  National and international standards, such as IEEE, can be used by quality assurance teams to create their organizational standards.  The team should organize a standards handbook that defines the standards to be used by organization.

14. Software Engineering Process - II 7.14 Just a Minute  Provide examples of standards that should go into the organization handbook.

15. Software Engineering Process - II 7.15 Quality Assurance and Standards  To ensure that the standards are followed without much resistance, quality managers can take following steps:  Involve software engineers in the selection of product standards.  Review and modify standards to reflect changing technologies.  Provide software tools to support standards wherever necessary.  Assign project managers the authority to modify a process or a standard to suit an individual project.

16. Software Engineering Process - II 7.16 ISO 9000 and 9001  ISO 9000 is an international set of standards that can be used for developing a quality management system in any organization from manufacturing to service industries.  ISO 9001, a derivative of ISO 9000, sets out general principles that are applicable to software:  It lays out the organizational standards and procedures that a company should define.  The standards should be documented in an organization’s quality manual.

17. Software Engineering Process - II 7.17 ISO 9000 and 9001 (cont.)

18. Software Engineering Process - II 7.18 Class Activity - 2  Discuss the advantages and disadvantages of ISO 9000.

19. Software Engineering Process - II 7.19 Documentation Standards  Documents are the only tangible way of representing the software and the software process.  Documentation standards can be of three types:  Documentation process standards: Define the process that should be followed for document production.  Document standards: Define the structure of documents.  Document interchange standards: Define the procedures to ensure that all electronic copies should be compatible.

20. Software Engineering Process - II 7.20 Documentation Standards (cont.)

21. Software Engineering Process - II 7.21 Documentation Standards (cont.)  Some examples of document standards are:  Document identification  Document structure  Document presentation  Document update

22. Software Engineering Process - II 7.22 Quality Planning  Quality planning is the process of developing a quality plan for a project.  A quality plan should include:  Product introduction: Product description, intended market, and quality expectations.  Product plans: Release dates and responsibilities, distribution, and warranty plan.  Process descriptions: Development and service processes to be used for the project.  Quality goals: Identification of critical quality attributes.  Risks and risk management: Key risks and action to address these risks.

23. Software Engineering Process - II 7.23 Quality Planning (cont.)  Quality plan should include the most important quality attributes for the software that is being developed: SafetyUnderstandabilityPortability SecurityTestabilityUsability ReliabilityAdaptabilityReusability ResilienceModularityEfficiency RobustnessComplexityLearnability

24. Software Engineering Process - II 7.24 Quality Control  Quality control involves monitoring the software development process to ensure that quality standards are being followed.  The two approaches of quality control are:  Quality reviews : Documentation and processes are reviewed by a group of people.  For example, performing a quality review of software requirement specifications.  Automated software assessment: Software and documents are processed by some program and results are compared with quality standards.  For example, checking the security of a bank system through a login program.

25. Software Engineering Process - II 7.25 Quality Reviews  The objectives of quality reviews are to:  Ensure that the software product conforms to its specifications and meets the needs of the customers.  Ensure that defined quality standards have been followed.  Record the review conclusions and pass them to the product developer who is responsible for correcting them.  Verify the corrected items.

26. Software Engineering Process - II 7.26 Quality Reviews (cont.)  The following table describes several review types. Review TypePrincipal Purpose Design or program inspectionsTo detect detailed errors in the requirements, design, or code. A checklist of possible errors should drive the review. Progress reviewsTo provide information for management about the overall progress of the project. This is both a process and a product review and is concerned with costs, plans, and schedules. Quality reviewsTo carry out a technical analysis of product components or documentation to find mismatches between the specification and the document design, code, or documentation and to ensure that defined quality standards have been followed.

27. Software Engineering Process - II 7.27 Summary  What was your key learning from the unit?