Quality characteristics (ISO 25010)

The process of obtaining user account information based on trial and error with the intention of using that information in a security attack.

The degree to which the actions of an entity can be traced uniquely to that entity.

The capability of the software product to provide the right or agreed results or effects with the needed degree of precision.

The capability of the software product to be adapted for different specified environments without applying actions or means other than those provided for this …

The capability of the software product to be diagnosed for deficiencies or causes of failures in the software, or for the parts to be modified to be …

Repeated action, process, structure or reusable solution that initially appears to be beneficial and is commonly used but is ineffective and/or …

The capability of the software product to be attractive to the user.

The degree to which the identity of a subject or resource can be proved to be the one claimed.

One of four levels that specify the item's or element's necessary requirements of ISO 26262 and safety measures to avoid an unreasonable residual risk.

The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage.

A set of automated tests which validates the integrity of each new build and verifies its key/core functionality, stability and testability.

A framework that describes the key elements of an effective product development and maintenance process. The Capability Maturity Model Integration covers …

The degree to which the maximum limits of a component or system parameter meet requirements.

Testing to evaluate the capacity of a system.

The capability of the software product to co-exist with other independent software in a common environment sharing common resources.

A type of security attack performed by inserting malicious code at an interface into an application to exploit poor handling of untrusted data.

The degree to which a component or system can exchange information with other components or systems, and/or perform its required functions while sharing the …

The practice of determining how a security attack has succeeded and assessing the damage caused.

The degree to which a component or system ensures that data are accessible only to those authorized to have access.

A capability maturity model structure wherein capability levels provide a recommended order for approaching process improvement within specified process areas. …

A form of static analysis based on a representation of unique paths (sequences of events) in the execution through a component or system. Control flow analysis …

The degree to which a website or web application can function across different browsers and degrade gracefully when browser features are absent or lacking.

A security attack that is intended to overload the system with requests such that legitimate requests cannot be serviced.

(1) The capability of the software product to provide appropriate performance, relative to the amount of resources used, under stated conditions. (2) The …

The ability, capacity, and skill to identify, assess, and manage the emotions of one's self, of others, and of groups.

A security tester using hacker techniques.

An informal usability review in which the reviewers are experts. Experts can be usability experts or subject matter experts, or both.

The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified …

A component or set of components that controls incoming and outgoing network traffic based on predetermined security rules.

The degree to which the set of functions covers all the specified tasks and user objectives.

A software testing technique used to discover security vulnerabilities by inputting massive amounts of random data, called fuzz, to the component or system.

A person or organization who is actively involved in security attacks, usually with malicious intent.

A usability review technique that targets usability problems in the user interface or user interface design. With this technique, the reviewers examine the …

An approach to design that aims to make software products more usable by focusing on the use of the software products and applying human factors, ergonomics, …

Measures that protect and defend information and information systems by ensuring their availability, integrity, authentication, confidentiality, and …

Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data.

A security threat originating from within the organization, often by an authorized system user.

The capability of the software product to be installed in a specified environment.

The degree to which a component or system allows only authorized access and modification to a component, a system or data.

The capability of the software product to interact with one or more specified components or systems.

Testing to determine the interoperability of a software product.

A system which monitors activities on the 7 layers of the OSI model from network to application level, to detect violations of the security policy.

The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or …

Testing to determine the correctness of the pay table implementation, the random number generator results, and the return to player computations.

(1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. (2) The capability of the software …

Degree of process improvement across a predefined set of process areas in which all goals in the set are attained.

A structured collection of elements that describe certain aspects of maturity in an organization, and aid in the definition and understanding of an …

A table containing different test approaches, testing techniques and test types that are required depending on the Automotive Safety Integrity Level (ASIL) and …

The degree to which a system is composed of discrete components such that a change to one component has minimal impact on other components.

Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.

The degree to which actions or events can be proven to have taken place, so that the actions or events cannot be repudiated later.

Operational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff …

A security attack recovering secret passwords stored in a computer system or transmitted over a network.

The maximum operating capacity of a component or system.

A testing technique aiming to exploit security vulnerabilities (known or unknown) to gain unauthorized access.

A security attack intended to redirect a web site's traffic to a fraudulent web site without the user's knowledge or consent.

The ease with which the software product can be transferred from one hardware or software environment to another.

A feature or characteristic that affects an item's quality.

A product risk related to a quality attribute.

A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases: inception, elaboration, construction and …

The capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure.

The ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of …

A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in …

The capability of the software product to be used in place of another specified software product for the same purpose in the same environment.

An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements, e.g., tests that exercise …

The degree to which a work product can be used in more than one system, or in building other work products.

A set of risks grouped by one or more common factors such as a quality attribute, cause, location, or potential effect of risk. A specific set of product risk …

The degree to which a component or system can be adjusted for changing capacity.

A person who executes security attacks that have been created by other hackers rather than creating one's own attacks.

An attempt to gain unauthorized access to a component or system, resources, information, or an attempt to compromise system integrity.

An audit evaluating an organization's security processes and infrastructure.

A high-level document describing the principles, approach and major objectives of the organization regarding security.

A set of steps required to implement the security policy and the steps to be taken in response to a security incident.

A quality risk related to security.

Testing to determine the security of the software product.

A weakness in the system that could allow for a successful security attack.

A program of activities designed to improve the performance and maturity of the organization's software processes and the results of such a program.

A questionnaire-based usability test technique for measuring software quality from the end user's point of view.

A model structure wherein attaining the goals of a set of process areas establishes a maturity level; each level builds a foundation for subsequent levels.

A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified workloads, or with reduced …

A scripting technique that builds and utilizes a library of reusable (parts of) scripts.

The step-by-step process of reducing the security vulnerabilities of a system by applying a security policy and different layers of protection.

A simple, ten-item attitude scale giving a global view of subjective assessments of usability.

An item or event of a component or system that could be verified by one or more test cases, e.g., a function, transaction, feature, quality attribute, or …

The calculated approximation of a result related to various aspects of testing (e.g., effort spent, completion date, costs involved, number of test cases, …

A five-level staged framework for test process improvement, related to the Capability Maturity Model Integration (CMMI), that describes the key elements of an …

A program of activities undertaken to improve the performance and maturity of the organization's test processes.

A group of test activities aimed at testing a component or system focused on a specific test objective, i.e. functional test, usability test, regression test …

A usability testing technique where test participants share their thoughts with the moderator and observers by thinking aloud while they solve usability test …

The degree to which a component or system can perform its required functions within required response times, processing times and throughput rates.

A continuous business-driven framework for test process improvement that describes the key elements of an effective and efficient test process.

The capability of the software to be understood, learned, used and attractive to the user when used under specified conditions.

A process through which information about the usability of a system is gathered in order to improve the system (known as formative evaluation) or to assess the …

A test facility in which unintrusive observation of participant reactions and responses to software takes place.

A requirement on the usability of a component or system.

A representative user who solves typical tasks in a usability test.

A document specifying a sequence of actions for the execution of a usability test. It is used by the moderator to keep track of briefing and pre-session …

A test session in usability testing in which a usability test participant is executing tests, moderated by a moderator and observed by a number of observers.

A usability test execution activity specified by the moderator that needs to be accomplished by a usability test participant within a given period of time.

Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and attractive to the users under specified …

A usability evaluation whereby a representative sample of users are asked to report subjective evaluation into a questionnaire based on their experience in …

A view of quality, wherein quality is the capacity to satisfy needs, wants and desires of the user(s). A product or service that does not fulfill user needs is …

A static analyzer that is used to detect particular security vulnerabilities in the code.

A questionnaire-based usability test technique for measuring web site software quality from the end user's point of view.