| Functional suitability | degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions |
| Functional completeness | degree to which the set of functions covers all the specified tasks and user objectives |
| Functional correctness | degree to which a product or system provides the correct results with the needed degree of precision |
| Functional appropriateness | degree to which the functions facilitate the accomplishment of specified tasks and objectives |
| Reliability | degree to which a system, product or component performs specified functions under specified conditions for a specified period |
| Maturity | degree to which a system, product or component meets needs for reliability under normal operation |
| Availability | degree to which a system, product or component is operational and accessible when required for use |
| Fault tolerance | degree to which a system, product or component operates as intended despite the presence of hardware or software faults |
| Recoverability | degree to which, in the event of an interruption or a failure, a product or system can recover the data directly affected and re-establish the desired state of the system |
| Performance efficiency | performance relative to the amount of resources used under stated conditions |
| Time behavior | degree to which the response and processing times and throughput rates of a product or system, when performing its functions, meet requirements |
| Resource utilization | degree to which the amounts and types of resources used by a product or system, when performing its functions, meet requirements |
| Capacity | degree to which the maximum limits of a product or system parameter meet requirements |
| Usability | degree to which a product or system can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use |
| Appropriateness recognizability | degree to which users can recognize whether a product or system is appropriate for their needs |
| Learnability | degree to which a product or system can be used by specified users to achieve specified goals of learning to use the product or system with effectiveness, efficiency, freedom from risk and satisfaction in a specified context of use |
| Operability | degree to which a product or system has attributes that make it easy to operate and control |
| User error protection | degree to which a system protects users against making errors |
| User interface aesthetics | degree to which a user interface enables pleasing and satisfying interaction for the user |
| Accessibility | degree to which a product or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use |
| Maintainability | degree of effectiveness and efficiency with which a product or system can be modified by the intended maintainers |
| Modularity | degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components |
| Reusability | degree to which an asset can be used in more than one system, or in building other assets |
| Analyzability | degree of effectiveness and efficiency with which it is possible to assess the impact on a product or system of an intended change to one or more of its parts, or to diagnose a product for deficiencies or causes of failures, or to identify parts to be modified |
| Modifiability | degree to which a product or system can be effectively and efficiently modified without introducing defects or degrading existing product quality |
| Testability | degree of effectiveness and efficiency with which test criteria can be established for a system, product or component and tests can be performed to determine whether those criteria have been met |
| Security | degree to which a product or system protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorization |
| Confidentiality | degree to which a product or system ensures that data are accessible only to those authorized to have access |
| Integrity | degree to which a system, product or component prevents unauthorized access to, or modification of, computer programs or data |
| Non-repudiation | degree to which actions or events can be proven to have taken place, so that the events or actions cannot be repudiated later |
| Accountability | degree to which the actions of an entity can be traced uniquely to the entity |
| Authenticity | degree to which the identity of a subject or resource can be proved to be the one claimed |
| Compatibility | degree to which a product, system or component can exchange information with other products, systems or components, and/or perform its required functions, while sharing the same hardware or software environment |
| Co-existence | degree to which a product can perform its required functions efficiently while sharing a common environment and resources with other products, without detrimental impact on any other product |
| Interoperability | degree to which two or more systems, products or components can exchange information and use the information that has been exchanged |
| Portability | degree of effectiveness and efficiency with which a system, product or component can be transferred from one hardware, software or other operational or usage environment to another |
| Adaptability | degree to which a product or system can effectively and efficiently be adapted for different or evolving hardware, software or other operational or usage environments |
| Installability | degree of effectiveness and efficiency with which a product or system can be successfully installed and/or uninstalled in a specified environment |
| Replaceability | degree to which a product can replace another specified software product for the same purpose in the same environment |
| Cost | Denotes the amount of money that a company spends on the creation or production of goods or services. |
| Implementation Cost | Estimation of implementation costs based on similar past experiences. |
| Complexity | Complexity characterises the behaviour of a system or model whose components interact in multiple ways and follow local rules, meaning there is no reasonable higher instruction to define the various possible interactions. |
| Flexibility | it normally refers to the ability for the solution to adapt to possible or future changes in its requirements. |
| Development Effort | the process of predicting the most realistic amount of effort required to develop or maintain software based on incomplete, uncertain and noisy input. |
| Implementability | degree to determine how easily a software product can be implemented. |
| Extensibility | Extensibility is a software engineering and systems design principle where the implementation takes future growth into consideration. The term extensibility can also be seen as a systemic measure of the ability to extend a system and the level of effort required to implement the extension. |
| Configurability | Highly configurable software provides adaptable and flexible solutions to complex, real world problems for the ever changing information technology environment |
| Ease of deployment | minimal effort to install and run an application. |
| Ease of development | ease of coding and developing |
| Scalability | Scalability is the capability of a system, network, or process to handle a growing amount of work, or its potential to be enlarged to accommodate that growth. |
| Integrability | Integrability evaluation refers to testing if separately developed components work correctly together. |
| Evolvability | a system's ability to survive changes in its environment, requirements and implementation technologies |
| Variability | the ability of software systems or artifacts to be adjusted for different contexts |
| Traceability | the degree to which a relationship can be established between two or more products of the development process, especially products having a predecessor-successor or master-subordinate relationship to one another; |
| (Un)pluggability | the degree to reusability of a component |
| Understandability | Understandability is defined as the attributes of software that bear on the users' efforts for recognizing the logical concept and its applicability. |
| Latency | Latency is a time interval between the stimulation and response, or, from a more general point of view, a time delay between the cause and the effect of some physical change in the system being observed. |
| applicability | the quality of being relevant or appropriate. |
| Consistency | consistent behaviour or treatment, the way in which a substance holds together |
| manageability | How efficiently and easily a software system can be monitored and maintained to keep the system performing, secure, and running smoothly. |
| Durability | software durability means the solution ability of serviceability of software and to meet user's needs for a relatively long time. For a software security to be durable, it must allow an organization to adjust the software to business needs that are constantly evolving, often in impulsive ways. |
| feasibility | Feasibility is defined as the practical extent to which a project can be performed successfully. |
| Exchangeability | capable of being exchanged for another or for something else that is equivalent. |
| Discoverability | discoverability refers to the ability of a consumer to find a product at the time when they have a need for it. |
| Composability | Composability is a system design principle that deals with the inter-relationships of components. A highly composable system provides components that can be selected and assembled in various combinations to satisfy specific user requirements. |
| Heterogeneity | Heterogeneity in software engineering is usually referring to the composition of a software system. A heterogeneous system is one that is made up of software that could be written in different languages, running on different operating systems, perhaps use different standards for communication. |
| Evolution | Software evolution is the term used in software engineering (specifically software maintenance) to refer to the process of developing software initially, then repeatedly updating it for various reasons. |
| Throughput | Throughput is a measure of how many units of information a system can process in a given amount of time. It is applied broadly to systems ranging from various aspects of computer and network systems to organizations. |
| Response time | Response Time measures the performance of an individual transaction or query. Response time is the amount of time from the moment that a user sends a request until the time that the application indicates that the request has completed. |