Product quality |
Functional supportability: capacity of the software product to provide functions to meet explicit and implicit needs for which it has been conceived. |
Functional completeness: capacity of the software product to provide an appropriate set of functions for specified tasks and objectives of the user. |
Functional correctness: capacity of the software product to provide, with the necessary degree of precision, correct or as agreed results or effects. |
Functional adequacy: capacity of the software product to facilitate the performance of user tasks and objectives. |
Performance efficiency: capacity of the software product to maintain a proper level of performance when used in specified conditions. |
Behavior in relation to time: capacity of the software product to provide fitting response and processing times, when the software performs its functions under established conditions. |
Use of resources: capacity of the software product to use fitting types and quantities of resources, when performing its functions under established conditions. |
Capacity: Maximum limits of system parameters (items that can be stored, number of competing users, bandwidth, transaction speed, size of database etc.) that meet requirements. |
Compatibility: capacity of the software product to enable an exchange of information with other applications and/or share the same hardware or software environment. |
Coexistence: capacity of the software product to coexist with other independent software products in a common environment and sharing common resources. |
Interoperability: capacity of the software product to interact with one or more specified systems through an exchange of information and the use of the information that is exchanged. |
Product quality |
Usability: capacity of the software product to be understood, learned, operated and attractive to the user, effectively and efficiently, when used under specified conditions. |
Intelligibility: capacity of the software product to enable the user to understand whether the software is fitting and how it can be used for specific-use tasks and conditions. Depends on software documentation. |
Aprehendability: capacity of the software product to enable the user to learn how to use it. Depends on software documentation. |
Operability: capacity of the software product to enable the user to operate and control it easily. |
User error protection: capacity of the software product to protect the user from errors. |
Interface aesthetics with the user: capacity of the software product to be attractive to the user by offering an interface with pleasant interaction. |
Accessibility: capacity of the software product to be used by a broad spectrum of people, including those with special needs and age-associated limitations. |
Reliability: capacity of the software product to execute its functions continuously. |
Maturity: capacity of the software product to avoid failures resulting from defects in the software, maintaining normal operations. |
Availability: capacity of the software product to be operational and accessible when its use is required. |
Failure tolerance: capacity of the software product to operate at a specified level of performance in cases of defects in software or hardware. |
Recoverability: capacity of the software product to reestablish its specified level of performance and recover the data directly affected in the case of a failure. |
Safety: capacity of the software product to protect information and data – unauthorized people or systems cannot read them or modify them and access to authorized people and systems is denied. |
Confidentiality: capacity of the software product to guarantee the data will be accessible only to people authorized to have access to them. |
Integrity: capacity of the software product to avoid unauthorized access for access to or modification of programs or data. |
Non-questioning: capacity of the software product to guarantee that the occurrence of actions or events can be proved, thus avoiding future questioning. |
Responsibility: capacity of the software product to audit the traceability of access to operations. |
Authentication: capacity of the system to validate the identity of a user. |
Maintainability: capacity of the software product to be modified. Modifications can include corrections, improvements or adaptation of the software due to changes in the environment and in functional requirements or specifications. |
Modularity: capacity of the system to have discrete components so a modification in one component has minimal impact on other components. |
Reusability: capacity of software components to be used in other software or in the construction of other components/systems. |
Analyzability: capacity of the software product to allow the diagnosis of deficiencies or causes of failures, or the identification of parts to be modified. |
Modifiability: capacity of the software product to allow implementation of a specified modification. |
Testability: capacity of the software product to allow the validation of the software when it has been modified. |
Product quality |
Portability: capacity of the software product to be transferred from one environment to another. |
Adaptability: capacity of the software product to be adapted to different specified environments, without the need for other actions or means besides those provided for this purpose by the software in question. |
Capacity to be installed: capacity of the software product to be installed in a specified environment. |
Capacity to replace: capacity of the software product to be used to replace another specified software product, with the same purpose and in the same environment. |
Quality of use |
Effectiveness: capacity of the software product to allow users to achieve specified goals with accuracy and completeness in a specified use context. |
Efficiency: capacity of the software product to enable users to employ an appropriate quantity of resources in relation to effectiveness obtained, in a specified use context. |
Satisfaction: capacity of the software product to satisfy users in a specified use context. |
Utility: degree to which the user perceives the software helps in executing his activities. |
Credibility: degree of confidence the user has in the correct behavior of the system. |
Pleasantness: degree of user contentment in using the software. |
Comfort: degree of physical comfort in using the software. |
Absence of risk: capacity of the software product to present acceptable levels of risk of damage to people, business, property or the environment. |
Mitigation of economic risk: degree in which the software reduces potential risk of a financial, operations, property or reputation nature in its context of use. |
Mitigation of risks to safety and health: degree in which the software reduces potential risk in its context of use. |
Mitigation of environmental risks: degree in which the software reduces potential risk to the environment in its context of use. |
Coverage of context: capacity of the software product to be used in its context of use and beyond those initially specified. |
Completeness of context: degree in which the software is used in all contexts of use (for example: using a low resolution monitor, with a low access to network rate, by an inexperienced user or without access to the network). |
Flexibility: degree in which the software is used beyond its projected context of use (if software is not designed for flexibility, it may not be safe in unplanned contexts). |
Quality of services: The degree to which the software product provides infrastructure for user support, in capacitation and support for the solution of problems regarding the system. |