|
Performance
Indicator
|
1
Poor
|
2
Insufficient
|
3
Satisfactory
|
4
Good
|
5
Excellent
|
|
Programming paradigms
|
Does not understand concepts from programming paradigms (object oriented and functional).
|
Does not quite understand concepts from programming paradigms (object oriented and functional).
|
Understands and uses concepts from programming paradigms (object oriented and functional) some of the time.
|
Understands and uses concepts from programming paradigms (object oriented and functional) most of the time.
|
Understands and uses concepts from programming paradigms (object oriented and functional) when appropriate.
|
|
Functions and methods
|
Functions/methods are usually longer than 2 dozen lines of code.
|
Functions/methods are often longer than 2 dozen lines of code.
|
Functions/methods are sometimes longer than 2 dozen lines of code.
|
Functions/methods are generally shorter than 2 dozen lines of code.
|
Functions/methods are almost never more than 2 dozen lines of code.
|
|
Testing
|
Has no concept of testing. Stubs and drivers are not considered in the development stage. Does not use a testing framework.
|
Understands the concept of testing. Drivers and stubs are used but not well defined. May use a testing framework but only minimally.
|
Aware of the importance of testing. The use of stubs and drivers is considered before implementation. Uses a testing framework consistently.
|
Makes testing plans, and testing is integrated with development. Stubs and drivers are written before further implementation. Writes test cases for a testing framework before writing code.
|
Makes testing plans, and testing is integrated with development. Stubs and drivers are written before further implementation. Writes test cases for a testing framework before writing code. Produces rigorous test reports.
|
|
This page has been viewed 1233 times.