FURPS

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) The topic of this article may not meet Wikipedia's notability guideline for neologisms. Please help to demonstrate the notability of the topic by citing reliable secondary sources that are independent of the topic and provide significant coverage of it beyond a mere trivial mention. If notability cannot be shown, the article is likely to be merged, redirected, or deleted. Find sources: "FURPS" – news · newspapers · books · scholar · JSTOR (November 2015) (Learn how and when to remove this message ) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "FURPS" – news · newspapers · books · scholar · JSTOR (November 2015) (Learn how and when to remove this message) (Learn how and when to remove this message)

FURPS is an acronym representing a model for classifying software quality attributes (

• Functionality - Capability (Size & Generality of Feature Set), Reusability (Compatibility, Interoperability, Portability), Security (Safety & Exploitability)
• Usability (UX) - Human Factors, Aesthetics, Consistency, Documentation, Responsiveness
• Reliability - Availability (Failure Frequency (Robustness/Durability/Resilience), Failure Extent & Time-Length (Recoverability/Survivability)), Predictability (Stability), Accuracy (Frequency/Severity of Error)
• Performance - Speed, Efficiency, Resource Consumption (power, ram, cache, etc.), Throughput, Capacity, Scalability
• Supportability (Serviceability, Maintainability, Sustainability, Repair Speed) - Testability, Flexibility (Modifiability, Configurability, Adaptability, Extensibility, Modularity), Installability, Localizability

The model, developed at Hewlett-Packard was first publicly elaborated by Grady and Caswell. FURPS+ is now widely used in the software industry. The + was later added to the model after various campaigns at HP to extend the acronym to emphasize various attributes.

See also

• Types of requirements
• Expanded list of types of requirements

Further reading

• Watson, Mike (2006). Managing Smaller Projects: A Practical Approach. Multi-Media Publications Inc. pp. 117 ff.
  ISBN 978-1-895186-85-7
  .
• Kenett, Ron; Baker, Emanuel (1999). Software Process Quality: Management and Control. CRC Press. pp. 130 ff.
  ISBN 978-0-8247-1733-9
  .
• Nakajo, Takeshi; Sasabuchi, Katsuhiko; Akiyama, Tadashi (April 1989). "A Structured Approach to Software Defect Analysis" (PDF). Hewlett-Packard Journal. 40 (2). Palo Alto: Hewlett-Packard Co.: 50–56. Archived from the original (PDF) on 2023-03-13. Retrieved 2016-03-24.
• Fischer, William A. Jr.; Jost, James W. (April 1989). "Comparing structured and unstructured methodologies in firmware development" (PDF). Hewlett-Packard Journal. 40 (2). Palo Alto: Hewlett-Packard Co.: 80–85. Archived from the original (PDF) on 2023-03-13. Retrieved 2016-03-24.
• Grady, Robert; Caswell, Deborah (1987). Software Metrics: Establishing a Company-wide Program. Prentice Hall. pp. 159.
  ISBN 0-13-821844-7
  .
• Carter, Donald; Stilwell Baker, Barbara (1992). Concurrent Engineering, The Product Development Environment for the 1990s. Addision-Wesley. pp. 175.
  ISBN 0-201-56349-5
  .

• IBM on Furps+

This software-engineering-related article is a stub. You can help Wikipedia by expanding it.

• v
• t
• e