ifm
System Manual
ecomat
mobile
PDM360NG (CR1080, CR1081, CR9042) Target V01
2011-07-28
Visualisations in the device
Recommendations for user interfaces
112
ISO 9126 _ Software engineering - Product quality
7446
The standard describes the following criteria:
Functionality: To what extent does the software have the required functions?
Suitability: suitability of functions for specified tasks, e.g. task-oriented composition of functions from sub-functions.
Correctness: providing the correct or agreed results or effects, e.g. necessary accuracy of calculated values.
Interoperability: ability to interact with specified systems.
Security: ability to prevent unauthorised access (inadvertent or intentional) to programs and data.
Compliance: software features that cause the software to comply with application-specific standards or agreements or legal
provisions and similar regulations.
Reliability: Can the software maintain a defined performance level under defined conditions for a
defined period?
Maturity: low failure frequency by error states.
Error tolerance: ability to maintain a specified performance level in case of software errors or non-compliance with its
specified interface.
Robustness: ability to ensure a stable system in case of inputs which have not been intended. The software withstands
"lusers".
Restorability: ability to restore the performance level in case of a failure and to retrieve the directly involved data. The time
and the needed level of input have to be taken into account.
Conformity: degree to which the software complies with standards or agreements on reliability.
Usability: What level of input does the use of the software require from users and how is it assessed
by them?
Understandability: level of input required from the user to understand the concept and its application.
Learnability: level of input required from the user to learn the application (e.g. handling, input, output).
Usability: level of input required from the user to handle the application.
Attractiveness:
attractiveness
of the application for the user.
Conformity: degree to which the software complies with standards or agreements on usability.
Efficiency: How is the relationship between performance level of the software and equipment used?
Time behaviour: response and processing times as well as data processing speed when executing the function.
Consumption behaviour: Number and actuation time of the required operating elements to carry out the functions.
Resource consumption, such as CPU time, hard disc access, etc.
Conformity: degree to which the software complies with standards or agreements on efficiency.
Changeability: What level of input is required make the defined changes in the software? Changes can
include corrections, improvements or adaptations to changes of the environment, requirements or
functional specifications.
Analysability: level of input required to diagnose defects or causes of failure or to determine parts that need to be changed.
Modifiability: level of input required to carry out improvements, eliminate faults or adapt to a changed environment.
Stability: probability of the occurrence of unexpected effects of changes.
Testability: level of input required to test the changed software.