Scribd
Upload
210 views1 page

Software Quality Models

The FURPS model, developed by Hewlett-Packard and Robert Grady, categorizes software requirements into functional and non-functional aspects, with the latter including usability, reliability, performance, and supportability. The ISO/IEC 9126 model was established to standardize software quality attributes, organizing them into a hierarchical structure with six main characteristics: functionality, reliability, usability, efficiency, maintainability, and portability, further divided into 21 sub-characteristics. Both models aim to define and improve software quality, though FURPS focuses solely on user requirements while ISO/IEC 9126 provides a comprehensive framework for quality assessment across various software types.

Uploaded by

smarthero73976347
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
210 views1 page

Software Quality Models

The FURPS model, developed by Hewlett-Packard and Robert Grady, categorizes software requirements into functional and non-functional aspects, with the latter including usability, reliability, performance, and supportability. The ISO/IEC 9126 model was established to standardize software quality attributes, organizing them into a hierarchical structure with six main characteristics: functionality, reliability, usability, efficiency, maintainability, and portability, further divided into 21 sub-characteristics. Both models aim to define and improve software quality, though FURPS focuses solely on user requirements while ISO/IEC 9126 provides a comprehensive framework for quality assessment across various software types.

Uploaded by

smarthero73976347
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

3.

FURPS Model

FURPS model was proposed by and Hewlett-Packard Co and Robert Grady. The attributes were classified
into two main categories according to the user’s requirements, the functional and non-functional
requirements. Functional requirements (F): Defined by input and expected output. Non-functional
requirements (URPS):

Usability, reliability, performance, supportability. Also, this model was extended by IBM Rational
Software – into FURPS+. Thus, this model considered only the user’s requirements and disregards the
developer consideration. But, this model fails to take into account the software some of the product
characteristics, like maintainability and portability.

5. ISO IEC 9126 Model

As, many software quality models were proposed, the confusion happened and new standard model
was required. Thus, ISO/IEC JTC1 began to develop the required consensus and encourage
standardization world-wide. The ISO 9126 is part of the ISO 9000 standard, and it is the most important
standard for quality assurance. The first considerations originated in 1978, and in the year 1985 the
development of ISO/IEC 9126 was started.

In this model, for software development companies, the totality of software product quality attributes
was classified in a hierarchical tree structure of characteristics and sub characteristics. And the highest
level of this structure consists of the quality characteristics and the lowest level consists of the software
quality criteria. This model specified six characteristics including Functionality, the Reliability, Usability,
Efficiency, Maintainability and the Portability; all of which are further divided into 21 sub characteristics.
All these sub characteristics are manifested externally when the software is used as part of a computer
system, and thus are the result of internal software attributes. All the defined characteristics are
applicable to every kind of software, including computer programs and data contained in firmware and
provide consistent terminology for software product quality. And they also provide a framework for
making trade-offs between software product capabilities.

You might also like