Abstract

The purpose of this paper is to identify the importance quality in software engineering when the projects or products are developed. The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations is the quality. The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs is software quality. Some even say that ‘quality’ cannot be defined and some say that it can be defined but only in a particular context. Some even state confidently that ‘quality is lack of bugs’. In this paper we discuss about the quality and the quality models.

Highlights

  • The purpose of this paper is to provide an overview on quality by different high profile experts and different quality models

  • One of the two perspectives chosen to survey the area of quality structures within this research paper is by means of quality management gurus

  • In the previous section we presented some quality management gurus as well as their ideas and views on quality primarily because this is a used and appreciated approach for dealing with quality issues in software developing organizations

Read more

Summary

Introduction

The purpose of this paper is to provide an overview on quality by different high profile experts and different quality models. One of the two perspectives chosen to survey the area of quality structures within this research paper is by means of quality management gurus. This perspective provides a qualitative and flexible [2] alternative on how to view quality structures

Quality According to Crosby
Quality According to Deming
Quality According to Feigenbaum
Quality According To Ishikawa
Quality According to Juran
Quality According to Shewhart
Quality Models
ISO 9000
ISO 9126
Conclusions and Recommendations
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call