Evaluation Criteria: Difference between revisions

From Ameise-en
Jump to navigationJump to search
No edit summary
No edit summary
Line 3: Line 3:
* Project time
* Project time
* Budget
* Budget
* AFPs realised in the  Code as a percentage >> [[zum Diagramm]]
* AFPs realised in the  Code as a percentage >> [[chart]]
* Errors per KLOC in the Code
* Errors per KLOC in the Code
* AFPs realised in the manual as a percentage
* AFPs realised in the manual as a percentage
Line 12: Line 12:




>> [[Back to: Classification of evaluation criteria]]
>> Back to: [[Classification of evaluation criteria]]


   
   
==Completness of documents==
==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]]
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. >> [[chart]]


   
   
Line 23: Line 23:
==Residual errors of documents==
==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:
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 errors of documents>> [[chart]]
* Residual error in the specification
* Residual error in the specification
* Residual error in the system design
* Residual error in the system design
Line 30: Line 30:
* Residual error in the manual
* Residual error in the manual


>> [[Back to: Classification of evaluation criteria]]
>> Back to: [[Classification of evaluation criteria]]


   
   
Line 42: Line 42:
* Efficiency of the module design reviews
* Efficiency of the module design reviews
* Efficiency of code reviews
* Efficiency of code reviews
* Efficiency of manual reviews >> [[zum Diagramm]
* Efficiency of manual reviews >> [[chart]
* Efficiency of module tests
* Efficiency of module tests
* Efficiency of system testing
* Efficiency of system testing
Line 54: Line 54:


* Effectiveness of specification reviews
* Effectiveness of specification reviews
* Effectiveness of system-design reviews >> [[zum Diagramm]]
* Effectiveness of system-design reviews >> [[chart]]
* Effectiveness of modul-design reviews
* Effectiveness of modul-design reviews
* Effectiveness pf code reviews
* Effectiveness pf code reviews
Line 60: Line 60:




>> [[Back to: Classification of evaluation criteria]]
>> Back to: [[Classification of evaluation criteria]]


   
   
Line 69: Line 69:


* Losses in tests
* Losses in tests
* Losses in reviews >> [[zum Diagramm]]
* Losses in reviews >> [[chart]]


   
   
Line 76: Line 76:


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


   
   
Line 86: Line 86:


* Author / authors of  specification
* Author / authors of  specification
Author / authors of  system design >> [[zum Diagramm]]
Author / authors of  system design >> [[chart]]
Author / authors of module design
Author / authors of module design
Author / authors of the code
Author / authors of the code

Revision as of 12:30, 21 April 2013

Objectives

The following objectives can be accessed:

  • Project time
  • Budget
  • AFPs realised in the Code as a percentage >> chart
  • 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. >> chart


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>> chart
  • 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 >> [[chart]
  • 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 >> chart
  • 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 >> chart


Expense Allocation

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


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 >> chart Author / authors of module design Author / authors of the code Author / authors of the manual