Quality management

Disponible uniquement sur Etudier
  • Pages : 14 (3298 mots )
  • Téléchargement(s) : 0
  • Publié le : 4 juillet 2010
Lire le document complet
Aperçu du document
Quality Management

©Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 27

Slide 1

Objectives








To introduce the quality management process and key quality management activities To explain the role of standards in quality management To explain the concept of a software metric, predictor metrics and control metrics To explain how measurement may be usedin assessing software quality and the limitations of software measurement

©Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 27

Slide 2

Topics covered
● ● ● ●

Process and product quality Quality assurance and standards Quality planning Quality control

©Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 27

Slide 3

Software quality management●





Concerned with ensuring that the required level of quality is achieved in a software product. Involves defining appropriate quality standards and procedures and ensuring that these are followed. Should aim to develop a ‘quality culture’ where quality is seen as everyone’s responsibility.
Software Engineering, 7th edition. Chapter 27 Slide 4

©Ian Sommerville 2004

What isquality?




Quality, simplistically, means that a product should meet its specification. This is problematical for software systems
• There is a tension between customer quality requirements (efficiency, reliability, etc.) and developer quality requirements (maintainability, reusability, etc.); Some quality requirements are difficult to specify in an unambiguous way; Software specificationsare usually incomplete and often inconsistent.

• •

©Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 27

Slide 5

The quality compromise




We cannot wait for specifications to improve before paying attention to quality management. We must put quality management procedures into place to improve quality in spite of imperfect specification.

©Ian Sommerville2004

Software Engineering, 7th edition. Chapter 27

Slide 6

Scope of quality management




Quality management is particularly important for large, complex systems. The quality documentation is a record of progress and supports continuity of development as the development team changes. For smaller systems, quality management needs less documentation and should focus on establishing aquality culture.

©Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 27

Slide 7

Quality management activities


Quality assurance
• Establish organisational procedures and standards for quality. Select applicable procedures and standards for a particular project and modify these as required. Ensure that procedures and standards are followed by the softwaredevelopment team.



Quality planning




Quality control




Quality management should be separate from project management to ensure independence.

©Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 27

Slide 8

Quality management and software development

©Ian Sommerville 2004

Software Engineering, 7th edition. Chapter 27

Slide 9

Process and productquality






The quality of a developed product is influenced by the quality of the production process. This is important in software development as some product quality attributes are hard to assess. However, there is a very complex and poorly understood relationship between software processes and product quality.
Software Engineering, 7th edition. Chapter 27 Slide 10

©IanSommerville 2004

Process-based quality




There is a straightforward link between process and product in manufactured goods. More complex for software because:
• • The application of individual skills and experience is particularly imporant in software development; External factors such as the novelty of an application or the need for an accelerated development schedule may impair product...
tracking img