Software Quality Engineering CS 449 LECTURE 1 Course

Software Quality Engineering CS- 449 LECTURE # 1

Course introduction See the course outline

Quality q. Luxury q. Class q. Taste q. Excellence q. Eminence q. Value q. Worth

Quality: Popular view q. Robert Persig [Per 74] commented on the thing we call quality: “Quality. . . you know what it is, yet you don't know what it is. But that's self-contradictory. But some things are better than others, that is, they have more quality. But when you try to say what the quality is, apart from the things that have it, it all goes poof! There's nothing to talk about. But if you can't say what Quality is, how do you know what it is, or how do you know that it even exists? If no one knows what it is, then for all practical purposes it doesn't exist at all. But for all practical purposes it really does exist. What else are the grades based on? Why else would people pay fortunes for some things and throw others in the trash pile? Obviously some things are better than others. . . but what's the betterness? . . . So round and round you go, spinning mental wheels and nowhere finding anyplace to get traction. What the hell is Quality? What is it? ” q“I know it when I see it”

Quality: Professional view q. Conformance to requirements (Crosby, 1979) q. Fitness for use (Gryna, 1970) q. Quality of design q. Quality of conformance

Quality Definitions q. The American Heritage dictionary defines quality as “a characteristic or attribute of something”. q. IEEE Glossary: Degree to which a system, component, or process meets 1. specified requirements, and 2. customer or user needs or expectations q. ISO 8402: The totality of features and characteristics of a product or service that bear on its ability to satisfy specified or implied needs. q. Another definition, coined by Gerald Weinberg in Quality Software Management: Systems Thinking, is "Quality is value to some person. “ This definition stresses that quality is inherently subjective – different people will experience the quality of the same software very differently.

Different views of quality q. Transcendental View q. User View q. Manufacturing View q. Product View q. Value based View

Different views of quality q. The transcendental view argues (like Persig) that quality is something that you immediately recognize, but cannot explicitly define. q. The user view sees quality in terms of an end-user’s specific goals. If a product meets those goals, it exhibits quality. q. 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. q. The product view suggests that quality can be tied to inherent characteristics (e. g. , functions and features) of a product. q. Finally, the value-based view measures quality based on how much a customer is willing to pay for a product. In reality, quality encompasses all of these views and more. q. How much a customer is willing to pay for a certain level of quality. q. Quality is meaningless if a product does not make economic sense. q. The value-based view makes a trade-off between cost and quality.

Quality Types q. Quality of design q. Quality of conformance

Quality of Design q. How well software is designed q. Measures how valid the design are in creating a worth while product q. Quality of design is the quality which the producer or supplier is intending to offer to the customer. When the producer is making the quality of design of the product, he should take in to consideration the customer's requirements in order to satisfy them with fitness for use of the product.

Quality of conformance q. How well the software conforms to that design q. Quality of conformance is the level of the quality of product actually produced and delivered through the production or service process of the organization as per the specifications or design. q. When the quality of a product entirely conforms to the specification (design), the quality of conformance is deemed excellent. q. It focuses on implementation based on the design.

Software Quality can be defined as, q“Conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software” [Roger Pressman. Software Engineering: A Practitioner's Approach Mc. Graw Hill 6 edition 2004] q. This definition emphasizes three important points q. Software requirements are the foundation from which quality is measured. Lack of conformance to requirements is lack of quality q. Specified standards define a set of development criteria that guide the way in which software is engineered. If the criteria are not followed, lack of quality will almost surely result. q. If a software conforms to its explicit requirements but fails to meet implicit requirements, software quality is suspect.

Software Quality q. Software quality can be defined as: An effective software process applied in a manner that creates a useful product that provides measurable value for those who produce it and those who use it. [Bes 04]

Effective software process q. An effective software process establishes the infrastructure that supports any effort at building a high quality software product. q. The management aspects of process create the checks and balances that help avoid project chaos—a key contributor to poor quality. q Software engineering practices allow the developer to analyze the problem and design a solid solution—both critical to building high quality software. q. Finally, umbrella activities such as change management and technical reviews have as much to do with quality as any other part of software engineering practice.

Useful Product q. A useful product delivers the content, functions, and features that the end-user desires q. But as important, it delivers these assets in a reliable, error free way. q. A useful product always satisfies those requirements that have been explicitly stated by stakeholders. q. In addition, it satisfies a set of implicit requirements (e. g. , ease of use) that are expected of all high quality software.

Adding value q. By adding value for both the producer and user of a software product, high quality software provides benefits for the software organization and the end-user community. q. The software organization gains added value because high quality software requires less maintenance effort, fewer bug fixes, and reduced customer support. q. The user community gains added value because the application provides a useful capability in a way that expedites some business process. q. The end result is: qgreater software product revenue, qbetter profitability when an application supports a business process, and/or qimproved availability of information that is crucial for the business.

References q. Software engineering: A practitioner’s approach by Roger S. Pressman 8 th edition q. Metrics and models in software quality engineering by Stephen H. Kan 2 nd edition