ISO/IEC 9126

The standard ISO / IEC 9126 is one of a number models to ensure software quality. It relates with its criteria solely on the quality of the software "product" ( product quality), or only indirectly (via the results ) on the quality of software development processes ( process quality ).

This ISO standard has risen in the ISO / IEC 25000 and is replaced by the new standard.

Quality characteristics

The following quality features are listed (Part features are listed in the annex of the standard as suggestions only ):

  • Functionality: The extent to which software possesses the required functions? - The existence of functions with specified properties. These features meet the defined requirements. Appropriateness: Suitability of functions for specified tasks, such as task-oriented composition of functions from sub-functions.
  • Accuracy: delivering the right or agreed results or effects, for example, the required accuracy of calculated values.
  • Interoperability: the ability to interact with specified systems.
  • Security: ability, unauthorized access, both accidentally and intentionally, to prevent programs and data.
  • Regularity: Characteristics of software that cause the software application-specific standards or agreements met or legal regulations and similar regulations.
  • Compliance: The ability of the software product standards, conventions or legal provisions and similar provisions in relation to the functionality to comply
  • Maturity: Low failure frequency by error conditions.
  • Fault tolerance: ability to provide a specified level of performance in software errors or non - compliance with its specified interface to preserve.
  • Recoverability: Ability to restore the level of performance in a failure and recover the data directly affected. Considerations include the time required and the effort required.
  • Conformity: degree to which software meets the standards or agreements for reliability.
  • Intelligibility: effort for the user to understand the concept and application.
  • Learnability: effort for the user to learn the application (for example, operation, input, output ).
  • Ease of use: effort for the user to operate the application.
  • Attractiveness: attractive force of the application to the user.
  • Conformity: degree to which software meets the standards or agreements for usability.
  • Timing: response and processing times and throughput in the execution of the function.
  • Consumption behavior: number and duration of resources needed to fulfill the functions. Consumption of resources, such as CPU time, disk access, etc.
  • Conformity: degree to which the software meets standards or agreements to efficiency.
  • Analysability: effort to diagnose deficiencies or causes of failures, or to determine change needy parts.
  • Modifiability: expense for executing improvements, troubleshooting or adaptation to environmental changes.
  • Stability: probability of the occurrence of unanticipated effects of changes.
  • Testability: expenditure which is required to test the modified software.
  • Conformity: degree to which software meets the standards or agreements to changeability.
  • Adaptability: ability of the software to adapt to different environments.
  • Of installation: effort that is necessary in a specified environment for installing the software.
  • Coexistence: ability of the software to work alongside another with the same or similar functions.
  • Interchangeability: possibility of this software to be used in place of a specified other in the vicinity of that software, and the effort necessary.
  • Conformity: degree to which software meets the standards or agreements on the portability.
Maintainability Software testability FURPS
419266
de