Evaluation Criteria

Objectives

The following objectives can be accessed:

• Project time
• Budget
• AFPs realised in the Code as a percentage >> zum Diagramm
• Errors per KLOC in the Code
• AFPs realised in the manual as a percentage
• Errors per page in the manual

Objectives are the most important evaluation criteria. At the end of the project the trainee wants to know if he/she has managed the project within the budget, in time and if he/she has realised the required AFPs for the code and for the manual. The evaluation component provides a textual description for every objective.

>> Back to: Classification of evaluation criteria

Completness of documents

This criterium gives an overview of the completness of the documents(Specification, Systemdesign, Moduldesign, Code, Manual) and is presented to the trainee with a diagramm. >> zum Diagramm

Residual errors of documents

Another important evaluation criteria gives an overview how many residual errors are left in the documents. You can distinguish the following evaluations:

• Residual errors of documents>> zum Diagramm
• Residual error in the specification
• Residual error in the system design
• Residual error in the module design
• Residual error in the code
• Residual error in the manual

>> Back to: Classification of evaluation criteria

Efficiency of Reviews and Tests

This criterion is compared with the cost of reviews or tests, the errors found and the cost of correcting these errors. With the help of these diagrams it can be determined whether a review or test was performed efficiently or not.

• Efficiency of the specification reviews
• Efficiency of the system design reviews
• Efficiency of the module design reviews
• Efficiency of code reviews
• Efficiency of manual reviews >> [[zum Diagramm]
• Efficiency of module tests
• Efficiency of system testing
• Efficiency of integration tests

Effectiveness of Reviews

This evaluation criterion compares the residual errors of documents with the located errors through reviews.Thereby it can be determined if the trainee has used the right developers.

• Effectiveness of specification reviews
• Effectiveness of system-design reviews >> zum Diagramm
• Effectiveness of modul-design reviews
• Effectiveness pf code reviews
• Effectiveness of manual reviews

>> Back to: Classification of evaluation criteria

Losses through Reviews and Tests

This evaluation criteria shows the number of AFPs, which get lossed through reviews and tests. This loss can be caused by a bad choice of developers.Therefore the trainess should always check the qualification of a developer.

• Losses in tests
• Losses in reviews >> zum Diagramm

Expense Allocation

This evaluation criteria shows the expense allocation of each single phase (Specification, Design, Code, Test,Manual creation). >> zum Diagramm

Authors of documents

This evaluation should check if the trainee has used the right developers for the different phases. The following evaluations are available:

• Author / authors of specification

Author / authors of system design >> zum Diagramm Author / authors of module design Author / authors of the code Author / authors of the manual