October 30, 2009 at 10:45 pmAssessment of term papers in IT disciplines
Students acquire a certain part of practical skills during the course work (projects). In the process of performing a specific task "from beginning to end", the "cones" necessary in real life are collected. On the correct implementation and execution of term papers written piles of manuals, which, unfortunately, are rarely read on time. And while defending the term papers, the teacher also needs to comprehensively evaluate the work performed by the student, so that "everyone gets according to his own business."
During the semester of teaching the discipline "DBMS MS SQL Server" I developed certain criteria for evaluating student projects, which I want to share with respected habrazhitami. Despite the fact that these criteria are tied to a specific discipline and take into account its features, I believe that they will be of interest to teachers (creating a similar grading system), students (to understand how your work will be evaluated), as well as to developers and managers who evaluate software projects.
For assessment, an A4 format sheet (checklist) is used, divided into two parts: admission and protection of the course project:
The first part is not particularly interesting, but necessary - it reflects formal criteria for admitting the course project to protection.
The second part is divided into two columns: “positive aspects” and “shortcomings”. Each assessment is associated with a corresponding set of criteria. The resulting score is determined by the totality of the marks. Naturally, a few not very serious (random) flaws will not affect the student's assessment.
As a result, both sides of the educational process benefit: it is easier for the teacher to evaluate the student’s work, and the student knows what they will ask him and what he has “worked on”.
This checklist has been successfully tested, shown to be useful and put into service :)
Interested habragers can download the checklist form .
It is clear that it is difficult to capture all the nuances at once - maybe something has been missed and something has been given too much importance, so I am waiting for your comments for further work in this direction.
During the semester of teaching the discipline "DBMS MS SQL Server" I developed certain criteria for evaluating student projects, which I want to share with respected habrazhitami. Despite the fact that these criteria are tied to a specific discipline and take into account its features, I believe that they will be of interest to teachers (creating a similar grading system), students (to understand how your work will be evaluated), as well as to developers and managers who evaluate software projects.
For assessment, an A4 format sheet (checklist) is used, divided into two parts: admission and protection of the course project:
The first part is not particularly interesting, but necessary - it reflects formal criteria for admitting the course project to protection.
The second part is divided into two columns: “positive aspects” and “shortcomings”. Each assessment is associated with a corresponding set of criteria. The resulting score is determined by the totality of the marks. Naturally, a few not very serious (random) flaws will not affect the student's assessment.
As a result, both sides of the educational process benefit: it is easier for the teacher to evaluate the student’s work, and the student knows what they will ask him and what he has “worked on”.
This checklist has been successfully tested, shown to be useful and put into service :)
Interested habragers can download the checklist form .
It is clear that it is difficult to capture all the nuances at once - maybe something has been missed and something has been given too much importance, so I am waiting for your comments for further work in this direction.