Table des matières
SharedEvaluation Module: Use cases
Having plugins of an open source project evaluated in a software architecture course
The exercise consists in exploring and qualifying, against several quality criteria, plugins of a well-known open source project, in order to give students structured critical analysis reflexes.
The teacher defines as “Evaluations” plugin identities with a short description, with a link to the publication pages of these plugins.
Each evaluated plugin has the same number of questions:
Question 1: Does the plugin show a structured design?
A1: 0 points: no A2: 1 point: MVC structures can be recognised in the code A3: 2 points: A controller is clearly identifiable and separate from the rest. A4: 3 points: Controllers are identifiable and used systematically
Question 2: Does the plugin comply with service contracts? (the teacher indicates how to find these service contracts)
A1: 0 points: not really, the plugin only has the contracts essential to its operation A2: 1 point: the plugin fulfils 1/4 of the service contracts A3: 2 points: the plugin fulfils 50% of the service contracts A4: 3 points: the plugin fulfils all the service contracts relevant to it
Question 3: Is the plugin stable?
A1: 0 points: It does not install. A2: 1 point: It installs but with errors. A3: 2 points: The main functions contain errors. A4: 3 points: The main functions work, the secondary functions have errors. A5: 4 points: There are only warnings. A6: 5 points: The plugin works without errors.
The interesting final results are the 3 scores: the lowest rated, the highest rated, the average of the evaluations, for each plugin.
Setting up a simple peer evaluation scheme
A course wants to set up an exercise with peer evaluation. The evaluation method is defined by 3 criteria on a 5-point scale. The work is done in groups.
