Ilities
Encyclopedia
Within systems engineering
, quality attributes are non-functional requirements
used to evaluate the performance of a system. These are sometimes named "ilities" after the suffix
many of the words share. Notable quality attributes include:
Many of these quality attributes can also be applied to data quality
.
Systems engineering
Systems engineering is an interdisciplinary field of engineering that focuses on how complex engineering projects should be designed and managed over the life cycle of the project. Issues such as logistics, the coordination of different teams, and automatic control of machinery become more...
, quality attributes are non-functional requirements
Non-functional requirements
In systems engineering and requirements engineering, a non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. This should be contrasted with functional requirements that define specific behavior or...
used to evaluate the performance of a system. These are sometimes named "ilities" after the suffix
Suffix
In linguistics, a suffix is an affix which is placed after the stem of a word. Common examples are case endings, which indicate the grammatical case of nouns or adjectives, and verb endings, which form the conjugation of verbs...
many of the words share. Notable quality attributes include:
Many of these quality attributes can also be applied to data quality
Data quality
Data are of high quality "if they are fit for their intended uses in operations, decision making and planning" . Alternatively, the data are deemed of high quality if they correctly represent the real-world construct to which they refer...
.
Common Subsets
- A subset of them (reliability, availability, serviceability, usability, and installability) are together referred to as RASUI.
- Another subset used for software requirements (functionality, usability, reliability, performance, supportability) are together referred to as FURPSFURPSFURPS is an acronym representing a model for classifying software quality attributes :* Functionality - Feature set, Capabilities, Generality, Security...
. - AgilityAgility* Agility is a physical trait of an animal or person, and a component of physical fitness. It is the ability to change the body's position and direction with speed and precision.Agility may also refer to:In Sport:...
in working software is an aggregation of seven architecturally sensitive attributes (debuggability, extensibility, portability, scalability, securability, testability, understandability). - For databases RASR is an important concept (reliability, availability, scalability, and recoverability).
- Also, ACIDACIDIn computer science, ACID is a set of properties that guarantee database transactions are processed reliably. In the context of databases, a single logical operation on the data is called a transaction...
for atomicity, consistency, isolation (sometimes integrity), durability. - When dealing with safety-critical systems, the acronym RAMS (reliability, availability, maintainability and safety) is frequently used.
See also
- Information qualityInformation qualityInformation quality is a term to describe the quality of the content of information systems. It is often pragmatically defined as: "The fitness for use of the information provided."- Conceptual problems :...
- ISO/IEC 9126 Software engineering—product quality
- Cognitive dimensions of notations
- Software qualitySoftware qualityIn the context of software engineering, software quality refers to two related but distinct notions that exist wherever quality is defined in a business context:...
Further reading
- Erl, ThomasThomas ErlThomas Erl is a Canadian author, and public speaker known as a major contributor in the fields of service-oriented architecture, service-orientation and cloud computing.- Biography :...
(2008), "SOA: Principles of Service Design", Prentice Hall, NJ. - Gitzel, Korthausa, Schadera (2007). "Using established Web Engineering knowledge in model-driven approaches". Science of Computer Programming 66(2), 30 April 2007, 105–124.