View stunning SlideShares in full-screen with the new iOS app!Introducing SlideShare for AndroidExplore all your favorite topics in the SlideShare appGet the SlideShare app to Save for Later — even offline
View stunning SlideShares in full-screen with the new Android app!View stunning SlideShares in full-screen with the new iOS app!
User-Based. . According to the user-based view of quality, quality is the satisfaction of user wants or needs. If product A satisfies more user wants and needs than product B, then product A has higher quality than product B. ใ 2 problems
1. d esigning a product that simultaneously meets the needs of a diverse group of users. For example, the popular image editing program PhotoShop is used by average consumers, professional photographers, and high-end animation studios.. What might be satisfying to one customer might be completely unacceptable to another.
2. User satisfaction is based on an aggregate of product factors--only one of which is quality. (See figure 6.) Just because a user is satisfied with a product you can't conclude it is exclusively because of high quality. A user might be satisfied with a low quality product if the other factors that influence satisfaction are high enough to compensate for the dissatisfaction attributable to low quality
BEFORE this perspective can serve as a basis for quality management, there has to be some way of measuring the extent to which product quality is contributing to user satisfaction independent of other product features that might also be influencing overall user satisfaction.
ADVANTAGES: When quality is defined as conformance to requirements, there is no ambiguity about what quality is. A quality product is one that conforms to specified requirements and design.
simplifies the production or implementation phase of the product life cycle.
is a good operational definition of quality because manufactures of all types of products can specify quality goals and control progress towards the accomplishment of these goals.
PROBLEMS: It does not accommodate for subjective view of 'goodlness' (McDonalds vs Ritz) .
It d isregard s the needs of the user. Quality as conformance to requirements doesn't discount the importance of meeting the needs of the user, it just assumes that these needs will be represented in the requirements.
Quality - (1) The degree to which a system, component, or process meets specified requirements. (2) The degree to which a system, component, or process meets customer or user needs or expectations. [IEEE Std. 610-12-1990]
Software Quality - the degree to which software possesses a desired combination of attributes . [IEEE Std 1061-1998] (Italics added for emphasis.)
Software Quality - degree to which the software, (1) conforms to specified requirements, (2) meets the needs and expectations of customers, users and stakeholders in general (3) is designed and developed according to sound engineering practices and standards.
t esting is performed too late in the product cycle to be an efficient method of avoiding defects. With most software development methodologies, testable code isn't produced until late in the development cycle. Even when doing short iterations, a lot of work is performed before the first line of code is written. Testing is an inefficient method of detecting defects because the cost of finding and fixing a defect increases dramatically with the length of time the defect exists in the system. Starting the search for defects late in the software development life cycle increases the expense of finding and removing defects that are introduced earlier in the software development life cycle.
Testing addresses only a narrow, although important, dimension of quality. Testing has the potential to improve the reliability of the end product but no amount of testing will improve its maintainability, extensibility, etc. These other dimensions of software quality have to be engineered into the product from the beginning.
Only the quality of code is improved through testing. A software product or solution is more than just code. It also includes requirements, designs, user manuals and other documentation. The supporting documentation of a software system has a significant influence on the overall quality of the system but can't be verified through testing.