Evaluation Criteria

Objectives

The following objectives can be evaluated and accessed:

• Project Time
• Budget
• AFPs realised in the Code as a Percentage >> chart
• Errors per KLOC
• 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 a simulation run, trainees want to know if they have managed the project within the budget, in time and if they have 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 the Evaluation Criteria

Completeness of Documents

This criterion gives an overview of the completeness of the documents(Specification, System design, Modul design, Code, Manual) and is presented to trainees in the form of a diagram. >> chart

Remaining Errors in Documents

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

• Remaining errors of Documents >> chart
• Remaining errors in the Specification
• Remaining errors in the System Design
• Remaining errors in the Module Design
• Remaining errors in the Code
• Remaining errors in the Manual

>> Back to: Classification of the Evaluation Criteria

Efficiency of Reviews or Tests

This criterion is compared with the costs of reviews or tests, the errors found and the costs 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 >> [[chart]
• Efficiency of Module Tests
• Efficiency of System Testing
• Efficiency of Integration Tests

Effectiveness of Reviews

This evaluation criterion compares the remaining errors of documents with the located errors of reviews. Thereby it can be determined if trainees have deployed the right developers.

• Effectiveness of Specification Reviews
• Effectiveness of System Design Reviews >> chart
• Effectiveness of Modul Design Reviews
• Effectiveness of Code Reviews
• Effectiveness of Manual Reviews

>> Back to: Classification of the Evaluation Criteria

Losses by Reviews or Tests

This evaluation criterion shows the number of AFPs, which were missing from reviews and tests. This loss can be caused by a bad choice of developers.Therefore, the trainees should always check the qualification of a developer.

• Losses in Tests
• Losses in Reviews >> chart

Expenses

This evaluation criterion shows the expenses of each single phase(Specification, Design, Code, Test, Manual). >> chart

Authors of Documents

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

• Author / authors of Specification
• Author / authors of System Design >> chart
• Author / authors of Module Design
• Author / authors of the Code
• Author / authors of the Manual