Ilities
Within systems engineering, -ilities are aspects or non-functional requirements. They are so-named because most of them end in "-ility."
The "-ilities" often include:
- accessibility
accountability - adaptability
- administrability
- affordability
- agility
auditability availability - credibility
compliant with standards composability - configurability
- customizability
- degradability
- demonstrability
- dependability
- deployability
- distributability
- durability
- evolvability
extensibility - flexibility
- installability
- interchangeability
- interoperability
- learnability
maintainability - manageability
mobility
modularity - nomadicity
- operability
portability predictability - recoverability
- relevance
- reliability
repeatability - reproducibility
reusability scalability - seamlessness
- serviceability (a.k.a. supportability)
- securability
simplicity stability survivability sustainability - tailorability
- testability
- timeliness
- understandability
- usability
Many of the "-ilities" can be applied to data quality.
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 FURPS. - For databases RASR is an important concept (Reliability, Availability, Scalability, and Recoverability).
- When dealing with safety-critical systems, the acronym RAMS (Reliability, Availability, Maintainability and Safety) is frequently used.
See also
External links
This entry is from Wikipedia, the leading user-contributed encyclopedia. It may not have been reviewed by professional editors (see full disclaimer)





