Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

List of system quality attributes

From Wikipedia, the free encyclopedia
Non-functional requirements for system evaluation
This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages)
This articleis inlist format but may read better asprose. You can help byconverting this article, if appropriate.Editing help is available.(September 2015)
icon
This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "List of system quality attributes" – news ·newspapers ·books ·scholar ·JSTOR
(January 2017) (Learn how and when to remove this message)
(Learn how and when to remove this message)

Withinsystems engineering,quality attributes are realizednon-functional requirements used to evaluate the performance of a system. These are sometimes named architecture characteristics, or "ilities" after thesuffix many of the words share. They are usuallyarchitecturally significant requirements that require architects' attention.[1]

Insoftware architecture, these attributed are known as "architectural characteristic" ornon-functional requirements. Note that it'ssoftware architects' responsibility to match these attributes withbusiness requirements and user requirements. Note that synchronous communication between software architectural components, entangles them and they must share the same architectural characteristics.[2]

Quality attributes

[edit]

Notable quality attributes include:

Many of these quality attributes can also be applied todata quality.

Common subsets

[edit]
  • Together, reliability, availability, serviceability, usability and installability, are referred to as RASUI.
  • Functionality, usability, reliability, performance and supportability are together referred to asFURPS in relation to software requirements.
  • Agility in working software is an aggregation of seven architecturally sensitive attributes: debuggability, extensibility, portability, scalability, securability, testability and understandability.
  • For databases reliability, availability, scalability and recoverability (RASR), is an important concept.
  • Atomicity, consistency, isolation (sometimes integrity), durability (ACID) is a transaction metric.
  • When dealing with safety-critical systems, the acronym reliability, availability, maintainability and safety (RAMS) is frequently used.[citation needed]
  • Dependability is an aggregate of availability, reliability, safety, integrity and maintainability.
    • Integrity depends on security and survivability.
    • Security is a composite of confidentiality, integrity and availability. Security and dependability are often treated together.

See also

[edit]

References

[edit]
  1. ^Chen, Lianping (2013)."Characterizing Architecturally Significant Requirements"(PDF).IEEE Software.30 (2):38–45.doi:10.1109/MS.2012.174.hdl:10344/3061.S2CID 17399565.
  2. ^Richards, Mark; Ford, Neal (2020).Fundamentals of Software Architecture: An Engineering Approach. O'Reilly Media, Incorporated.ISBN 978-1492043454.

Further reading

[edit]
Qualities
Internal
External
Standards and lists
Processes
Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_system_quality_attributes&oldid=1328434673"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2026 Movatter.jp