1. Q & QA1 Quality & Quality Assurance Advanced Software Engineering COM360 University Of Sunderland © 1999

2. Q & QA2 Quality & Quality Assurance definitions cost motivation process & product QA tasks

3. Q & QA3 Definitions quality, software, quality assurance.

4. Q & QA4 Cost of Quality prevention costs appraisal costs failure costs external failure costs

5. Q & QA5 Development of Quality Deming, Juran, Ishikawa etc. TQM –kaizen –atarimae hinshitsu –kansei –miryokuteki hinshitsu

6. Q & QA6 Quality - People Motivation motivators and demotivators quality circles commitment - all levels

7. Q & QA7 Product vs Process good process = good product? process improvement (CMM)

8. Q & QA8 Quality Assurance (I) Juran defined quality assurance, in his Quality Control Handbook, as: the activity of providing to all concerned the evidence needed to establish confidence that the quality function is being performed adequately

9. Q & QA9 Quality Assurance (II) systematic activities providing evidence of fitness for purpose of the total software product

10. Q & QA10 QA activities - part 1 prepare a SQA plan participate in the definition of a project’s software development plan (and process model) review (software engineering) activities to verify compliance with defined software process

11. Q & QA11 QA activities - part 2 review selected (software) work products to verify compliance with specifications ensure deviations from defined activities and products are documented and handled according to defined procedures record any noncompliances regularly report to senior management

12. Q & QA12 Launching a SQA Programme initiate the programme identify the issues write the plan establish standards establish the function train and promote implement the plan evaluate the programme

13. Q & QA13 Humphrey says: The people responsible for the software projects are the only ones who can be responsible for quality. the role of SQA is to monitor the way these groups perform their responsibilities.

14. Q & QA14 Pitfalls: it is a mistake to think that SQA people (alone) can do anything about quality the existence of a SQA function does not ensure that the standard procedures are followed unless management periodically demonstrates its support for SQA, by following their recommendations, SQA will be ineffective unless line management requires that SQA tries to resolves their issues with project management before escalation, SQA and development will not work together effectively.