Software Quality
Software Quality
Software Quality
Software Quality
• David Garvin [Gar84] suggests that “quality is a complex and multifaceted concept” that can be
described from five different points of view
• The transcendental view argues (like Persig) that quality is something that you immediately
recognize, but cannot explicitly define.
• The user view sees quality in terms of an end user’s specific goals. If a product meets those goals,
it exhibits quality
• The manufacturer’s view defines quality in terms of the original specification of the product. If
the product conforms to the spec, it exhibits quality
• The product view suggests that quality can be tied to inherent characteristics (e.g., functions and
features) of a product
• the value-based view measures quality based on how much a customer is willing to pay for a
product.
• In software development, quality of design encompasses the degree to which the
design meets the functions and features specified in the requirements model.
• Quality of conformance focuses on the degree to which the implementation
follows the design and the resulting system meets its requirements and
performance goals.
• But are quality of design and quality of conformance the only issues
that software engineers must consider? Robert Glass [Gla98] argues
that a more “intuitive” relationship is in order: