SE401 · Quality · Annotated SlidesQuality Assurance, Quality Control and Metrics
Original
Overview

Quality Assurance, Quality Control and Metrics

Definitions of software quality, quality assurance vs. quality control, the SQA group’s role, what makes projects succeed or fail, and software measurement: measures, metrics, product vs. process metrics, direct vs. indirect measures and size-oriented metrics.

How to read this page

Every original slide is shown unchanged. Yellow marks on a slide point to a numbered note: hover or tap a mark to jump to its note, and hover a note to see its marks. Questions tagged Past exam appeared on a real paper; Prediction questions are likely angles, not confirmed. Pick an answer to each question: a wrong pick tells you why it is wrong, so you can try again.

All 45 slides
  1. 1 Slide 1
  2. 2 • Software Quality • Quality Assurance
  3. 3 Slide 3
  4. 4 • A definition of quality should emphasize three important points:
  5. 5 • The purpose of software testing is to assess and evaluate the quality of work performed at each step of the software development process.
  6. 6 • A good development process, tools, methods, and people go far in providing quality products
  7. 7 Slide 7
  8. 8 • Quality assurance (QA) activities strive to ensure:
  9. 9 • The following need to be considered: Scope, Stakeholders, Risks, Internal and External Environmental Factors, Process
  10. 10 Slide 10
  11. 11 Perform quality control is concerned with monitoring specific project results for compliance with quality standards
  12. 12 • The group should prepare an SQA plan for a project. • The plan identifies
  13. 13 • Participates in the development of the project’s software process description
  14. 14 Slide 14
  15. 15 • Keep requirements tight & focused • One milestone at a time
  16. 16 Too much medicine can kill the patient
  17. 17 Be Disciplined and Professional
  18. 18 • MBWA – Management by Walk About
  19. 19 1. On schedule
  20. 20 • How to identify a project’s success potential
  21. 21 • Executive support • User involvement
  22. 22 • Top management can help to:
  23. 23 • Factors that may influence the success or failure of the software projects could be:
  24. 24 Technologies on Unsuccessful Projects Technologies on Successful Projects
  25. 25 Social Factors on Unsuccessful Projects Social factors on Successful Projects
  26. 26 • Do the same things you did on the last project. Over and over and over.
  27. 27 Slide 27
  28. 28 • “Not everything that can be counted counts, and not everything that counts can be counted.”
  29. 29 • Software measurement is concerned with deriving a quantitative (numeric) value for an attribute of a software product or process
  30. 30 • Measure
  31. 31 • Any type of measurement which relates to a software system, process or related documentation
  32. 32 • Product
  33. 33 • Private process metrics (e.g., defect rates by individual or module) are only known to by the individual or team concerned.
  34. 34 • A quality metric should be a predictor of product quality • Classes of product metric
  35. 35 • A software team can use software project metrics to adapt project workflow and technical activities
  36. 36 • A software property can be measured • The relationship exists between what we can measure and what we
  37. 37 • Many software developers do not collect measures. • Without measurement it is impossible to determine whether a process
  38. 38 • Direct measures of a software engineering process include cost and effort
  39. 39 • A software measurement process may be part of a quality control process
  40. 40 Product Measurement Process
  41. 41 • A metrics program should be based on a set of product and process data
  42. 42 • Don’t collect unnecessary data
  43. 43 What Are Metrics For?
  44. 44 • It is not always obvious what data means
  45. 45 • Size-oriented metrics
Slide 1 / 45

Slide 1

Slide 1: Slide 1
Slide 2 / 45

• Software Quality • Quality Assurance

Slide 2: • Software Quality • Quality Assurance
Slide 3 / 45

Slide 3

Slide 3: Slide 3
Slide 4 / 45

• A definition of quality should emphasize three important points:

Slide 4: • A definition of quality should emphasize three important points:
Slide 5 / 45

• The purpose of software testing is to assess and evaluate the quality of work performed at each step of the software development process.

Slide 5: • The purpose of software testing is to assess and evaluate the quality of work performed at each step of the software development process.
Slide 6 / 45

• A good development process, tools, methods, and people go far in providing quality products

Slide 6: • A good development process, tools, methods, and people go far in providing quality products
Slide 7 / 45

Slide 7

Slide 7: Slide 7

Notes

  1. Quality assurance (QA): PROCESS-oriented, preventive: make sure the right processes are followed so defects aren’t introduced.

Slide 8 / 45

• Quality assurance (QA) activities strive to ensure:

Slide 8: • Quality assurance (QA) activities strive to ensure:
Slide 9 / 45

• The following need to be considered: Scope, Stakeholders, Risks, Internal and External Environmental Factors, Process

Slide 9: • The following need to be considered: Scope, Stakeholders, Risks, Internal and External Environmental Factors, Process
Slide 10 / 45

Slide 10

Slide 10: Slide 10

Notes

  1. Quality control (QC): PRODUCT-oriented, detective: inspect and test the product to find defects.

  2. Memory trick QA = prevent (process). QC = detect (product). Testing is part of QC.

Exam angle

PredictionQ1

Testing a product to find defects is an example of:

Slide 11 / 45

Perform quality control is concerned with monitoring specific project results for compliance with quality standards

Slide 11: Perform quality control is concerned with monitoring specific project results for compliance with quality standards
Slide 12 / 45

• The group should prepare an SQA plan for a project. • The plan identifies

Slide 12: • The group should prepare an SQA plan for a project. • The plan identifies
Slide 13 / 45

• Participates in the development of the project’s software process description

Slide 13: • Participates in the development of the project’s software process description
Slide 14 / 45

Slide 14

Slide 14: Slide 14
Slide 15 / 45

• Keep requirements tight & focused • One milestone at a time

Slide 15: • Keep requirements tight & focused • One milestone at a time
Slide 16 / 45

Too much medicine can kill the patient

Slide 16: Too much medicine can kill the patient
Slide 17 / 45

Be Disciplined and Professional

Slide 17: Be Disciplined and Professional
Slide 18 / 45

• MBWA – Management by Walk About

Slide 18: • MBWA – Management by Walk About
Slide 19 / 45

1. On schedule

Slide 19: 1. On schedule
Slide 20 / 45

• How to identify a project’s success potential

Slide 20: • How to identify a project’s success potential
Slide 21 / 45

• Executive support • User involvement

Slide 21: • Executive support • User involvement
Slide 22 / 45

• Top management can help to:

Slide 22: • Top management can help to:
Slide 23 / 45

• Factors that may influence the success or failure of the software projects could be:

Slide 23: • Factors that may influence the success or failure of the software projects could be:
Slide 24 / 45

Technologies on Unsuccessful Projects Technologies on Successful Projects

Slide 24: Technologies on Unsuccessful Projects Technologies on Successful Projects
Slide 25 / 45

Social Factors on Unsuccessful Projects Social factors on Successful Projects

Slide 25: Social Factors on Unsuccessful Projects Social factors on Successful Projects
Slide 26 / 45

• Do the same things you did on the last project. Over and over and over.

Slide 26: • Do the same things you did on the last project. Over and over and over.
Slide 27 / 45

Slide 27

Slide 27: Slide 27
Slide 28 / 45

• “Not everything that can be counted counts, and not everything that counts can be counted.”

Slide 28: • “Not everything that can be counted counts, and not everything that counts can be counted.”
Slide 29 / 45

• Software measurement is concerned with deriving a quantitative (numeric) value for an attribute of a software product or process

Slide 29: • Software measurement is concerned with deriving a quantitative (numeric) value for an attribute of a software product or process

Notes

  1. Measure: a quantitative value of an attribute. Metric: a measure related to a goal (defects per KLOC).

Slide 30 / 45

• Measure

Slide 30: • Measure
Slide 31 / 45

• Any type of measurement which relates to a software system, process or related documentation

Slide 31: • Any type of measurement which relates to a software system, process or related documentation
Slide 32 / 45

• Product

Slide 32: • Product

Notes

  1. Product metrics (size, complexity, defects), process metrics (effort, defect-removal efficiency), project metrics (cost, schedule).

Slide 33 / 45

• Private process metrics (e.g., defect rates by individual or module) are only known to by the individual or team concerned.

Slide 33: • Private process metrics (e.g., defect rates by individual or module) are only known to by the individual or team concerned.
Slide 34 / 45

• A quality metric should be a predictor of product quality • Classes of product metric

Slide 34: • A quality metric should be a predictor of product quality • Classes of product metric
Slide 35 / 45

• A software team can use software project metrics to adapt project workflow and technical activities

Slide 35: • A software team can use software project metrics to adapt project workflow and technical activities
Slide 36 / 45

• A software property can be measured • The relationship exists between what we can measure and what we

Slide 36: • A software property can be measured • The relationship exists between what we can measure and what we
Slide 37 / 45

• Many software developers do not collect measures. • Without measurement it is impossible to determine whether a process

Slide 37: • Many software developers do not collect measures. • Without measurement it is impossible to determine whether a process
Slide 38 / 45

• Direct measures of a software engineering process include cost and effort

Slide 38: • Direct measures of a software engineering process include cost and effort
Slide 39 / 45

• A software measurement process may be part of a quality control process

Slide 39: • A software measurement process may be part of a quality control process
Slide 40 / 45

Product Measurement Process

Slide 40: Product Measurement Process
Slide 41 / 45

• A metrics program should be based on a set of product and process data

Slide 41: • A metrics program should be based on a set of product and process data
Slide 42 / 45

• Don’t collect unnecessary data

Slide 42: • Don’t collect unnecessary data
Slide 43 / 45

What Are Metrics For?

Slide 43: What Are Metrics For?
Slide 44 / 45

• It is not always obvious what data means

Slide 44: • It is not always obvious what data means
Slide 45 / 45

• Size-oriented metrics

Slide 45: • Size-oriented metrics

Notes

  1. Size-oriented metrics normalise by size: errors per KLOC, cost per KLOC, pages of documentation per KLOC.

Exam angle

PredictionQ1

12 defects in 4,000 lines of code is: