Search results
Results from the WOW.Com Content Network
Within systems engineering, quality attributes are realized non-functional requirements used to evaluate the performance of a system. These are sometimes named architecture characteristics, or "ilities" after the suffix many of the words share.
For instance, failure to meet security and compliance requirements complicates the system and process assurance audits and increases the risk of audit findings. [10] Exemplary advice on how to address system quality attributes (including architecturally significant requirements) is available in the literature. [11] [12]
FURPS is an acronym representing a model for classifying software quality attributes (functional and non-functional requirements): Functionality - Capability (Size & Generality of Feature Set), Reusability (Compatibility, Interoperability, Portability), Security (Safety & Exploitability)
Broadly, functional requirements define what a system is supposed to do and non-functional requirements define how a system is supposed to be.Functional requirements are usually in the form of "system shall do <requirement>", an individual action or part of the system, perhaps explicitly in the sense of a mathematical function, a black box description input, output, process and control ...
Newer proposals for quality models such as Squale and Quamoco [85] propagate a direct integration of the definition of quality attributes and measurement. By breaking down quality attributes or even defining additional layers, the complex, abstract quality attributes (such as reliability or maintainability) become more manageable and measurable.
ISO/IEC 9126 Software engineering — Product quality was an international standard for the evaluation of software quality.It has been replaced by ISO/IEC 25010:2011. [1]The quality criteria according to ISO 9126
This one, plus the Non Functional Requirements page, the System Quality Attributes page, and the ISO 9126 page. All are dealing with system quality attributes. ISO 9126 is simply a standard set of system quality attributes. The term "non functional requirements" has been repeatedly criticized in systems development literature.
S. Safety-critical system; Scalability; Search-based software engineering; Second-system effect; Secure by design; Software assurance; Software bloat; Software crisis