5 Part 5: V-Modell Reference Work Products

5.3 Products

5.3.5 Evaluation

5.3.5.8 Evaluation Report Usability

Process module: Usability and Ergonomics

Responsible: Inspector (when using process module Usability and Ergonomics)

Purpose

The evaluation report includes the »Inspector 's recordings on the course of the test, the comparison between actual and planned results, the analysis of the identfied planned/actual deviations, and the appropriate suggested solutions. It should be ensured that the evaluation result is replicable.

Number and frequency of tests - and thus of the corresponding evaluation reports - depend on the specifications in the »QA Manual and the applicable implementation, integration and evaluation concepts.

Is generated by

Hardware Architecture, Hardware Implementation, Integration and Evaluation Concept (see product dependency 4.6)

Hardware Architecture, Hardware Implementation, Integration and Evaluation Concept (see product dependency 4.7)

System Implementation, Integration and Evaluation Concept, System Architecture (see product dependency 4.4)

Hardware Architecture, Hardware Implementation, Integration and Evaluation Concept (see product dependency 4.8)

Overall System Specification (see product dependency 4.26)

Overall System Specification (see product dependency 4.25)

Software Implementation, Integration and Evaluation Concept, Software Architecture (see product dependency 4.18)

Software Implementation, Integration and Evaluation Concept, Software Architecture (see product dependency 4.17)

Software Implementation, Integration and Evaluation Concept, Software Architecture (see product dependency 4.19)

System Implementation, Integration and Evaluation Concept, System Architecture (see product dependency 4.20)

System Implementation, Integration and Evaluation Concept, System Architecture (see product dependency 4.4)

System Implementation, Integration and Evaluation Concept, System Architecture (see product dependency 4.23)

System Implementation, Integration and Evaluation Concept, System Architecture (see product dependency 4.15)

Enabling System Implementation, Integration, and Evaluation Concept, Enabling System Architecture (see product dependency 4.21)

Enabling System Implementation, Integration, and Evaluation Concept, Enabling System Architecture (see product dependency 4.5)

Enabling System Implementation, Integration, and Evaluation Concept, Enabling System Architecture (see product dependency 4.24)

System Implementation, Integration and Evaluation Concept, Enabling System Architecture (see product dependency 4.16)

5.3.5.8.1 Evaluation Object

This subject specifies an unambiguously defined identifiable version of the evaluation object to which the evaluation specification or the evaluation report will be referred.

5.3.5.8.2 Evaluation Results

The results of the »Requirements Evaluation includes particularly the overall evaluation of user requirements, which evaluates inhowfar it is possible to fulfill specified restrictions, posed either by the budget or the schedule or the available resources, or if these restrictions will be exceeded. In addition all user requirements recorded will be reviewed, and their classification will be evaluated: The user requirements postponed and the rationale for their postponement will be reviewed (e.g. can the necessity not be demonstrated). The modified user requirements and the rationale for the modification will be reviewed (e.g. by the more economical use of off-the-shelf products). The necessity of additional user requirements will be reviewed (e.g. have important non-functional user requirements not been recorded). The evaluation results also include the results of the consideration of economic efficiency of user requirements, e.g., cost-benefit analyses, the identification of cost-driving user requirements and the affordability of user requirements.

5.3.5.8.3 Analysis of Results and Proposals for Corrective Actions

The analysis of results analyzes contents and cause of the observed deviations between actual results and planned results. If it is possible to identify the cause, any suggested correction which is recognizable should be documented as well. If the evaluation results show a certain tendency regarding the occurrence of similar deficiencies, this should be documented, and appropriate measures should be suggested. These data will be integrated into the »Quality Status Report.

In accordance with the specifications of the Project Manual, an evaluation result or suggested correction could lead to a problem report or change request.