2. OHT 1.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The uniqueness of software quality assurance The environments for which SQA methods are developed

3. OHT 1.2 Galin, SQA from theory to implementation © Pearson Education Limited 2004 High complexity Invisibility of the product Limited opportunities to detect defects (“bugs”)

4. OHT 1.3 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Being contracted Subjection to customer-supplier relationship Requirement for teamwork Need for cooperation and coordination with other development teams Need for interfaces with other software systems Need to continue carrying out a project while the team changes Need to continue maintaining the software system for years

5. OHT 1.4 Galin, SQA from theory to implementation © Pearson Education Limited 2004

6. OHT 1.5 Galin, SQA from theory to implementation © Pearson Education Limited 2004

7. OHT 1.6 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is software? Software errors, faults and failures Classification of the causes of software errors Software quality – definition Software quality assurance – definition and objectives Software quality assurance and software engineering

8. OHT 1.7 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software is: Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.

9. OHT 1.8 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software development process software fault software failure software error

10. OHT 1.9 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The nine causes of software errors are: 1.Faulty requirements definition 2.Client-developer communication failures 3.Deliberate deviations from software requirements 4.Logical design errors 5.Coding errors 6.Non-compliance with documentation and coding instructions 7.Shortcomings of the testing process 8.User interface and procedure errors 9.Documentation errors

11. OHT 1.10 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality is: (1)The degree to which a system, component, or process meets specified requirements. (2)The degree to which a system, component, or process meets customer or user needs or expectations.

12. OHT 1.11 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality is : Conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software.

13. OHT 1.12 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality assurance is: 1.A planned and systematic pattern of all actions necessary to provide adequate confidence that an item or product conforms to established technical requirements. 2.A set of activities designed to evaluate the process by which the products are developed or manufactured. Contrast with: quality control.

14. OHT 1.13 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality assurance is: A systematic, planned set of actions necessary to provide adequate confidence that the software development process or the maintenance process of a software system product conforms to established functional technical requirements as well as with the managerial requirements of keeping the schedule and operating within the budgetary confines.

15. OHT 1.14 Galin, SQA from theory to implementation © Pearson Education Limited 2004 (1)Assuring an acceptable level of confidence that the software will conform to functional technical requirements. (2)Assuring an acceptable level of confidence that the software will conform to managerial scheduling and budgetary requirements. (3)Initiation and management of activities for the improvement and greater efficiency of software development and SQA activities.

16. OHT 1.15 Galin, SQA from theory to implementation © Pearson Education Limited 2004 (1)Assuring an acceptable level of confidence that the software maintenance activities will conform to the functional technical requirements. (2)Assuring an acceptable level of confidence that the software maintenance activities will conform to managerial scheduling and budgetary requirements. (3)Initiate and manage activities to improve and increase the efficiency of software maintenance and SQA activities.

17. OHT 1.16 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The need for comprehensive software quality requirements Classification of requirements into software quality factors Product operation factors Product revision factors Product transition factors Alternative models of software quality factors Who is interested in defining quality requirements? Software compliance with quality factors

18. OHT 1.17 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software quality factors Product operation factors Product revision factors Product transition factors

19. OHT 1.18 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Correctness Reliability Efficiency Integrity Usability

20. OHT 1.19 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Maintainability Flexibility Testability

21. OHT 1.20 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Portability Reusability Interoperability

22. OHT 1.21 Galin, SQA from theory to implementation © Pearson Education Limited 2004

23. OHT 1.22 Galin, SQA from theory to implementation © Pearson Education Limited 2004