The idea here is the assigned work is to be evaluated coarsely
to one of the levels of achievment listed below. In the case of
designing a SW system, the goal of the assigned work is for the
student to go through the design and development process and it
is less important how well the system functions, but, rather that
it does function in some sense. This is meant
to encourage creativity and exploration of new ideas without punishment
when there are problems.
Leveled Grading Scheme: |
100% =
- all portions of project designed and implemented, and
run (regardless of accuracy)
- turned in all deliverables
|
low A =
- all portions of project designed and implemented,
- 3/4ths or more (to be judged by grader) of the system components RUN (regardless
of accuracy)
- spent adequate time on project
- turned in all deliverables including documentation of what is not working
|
low B =
- all portions of project designed and at least 3/4th is implemented,
- only half or more of the system components run (regardless
of accuracy)
- attended all work sessions but one
- turned in deliverables, including documentation of what is not working
|
mid C =
- all portions of project designed, and at least 1/2 is implemented
- only 1/3rd to half of the system components run (regardless
of accuracy)
- spent adequate time on project
- turned in all deliverables including documentation of what is not working
|
low C =
- all portions of project designed, and at least 1/2 is implemented
- nothing working
- spent adequate time on project
- turned in all deliverables including documentation of what is not working
|
D =
- anything less than 1/3rd implemented and not working
|
F=
|