CSE logo University of Washington Department of Computer Science & Engineering
 CSE 142 Winter 2003 -- Project Assessment
  UW Home     CSE Home   Message Board    Contact Info 

CSE 142
 Home page
 Syllabus
Classwork
 Calendar
 Homework
 Projects
 Exams
 Quizzes
Software & Computing
 Programming Lab Info
 Computing at Home
 Java Libraries
 Troubleshooting
Staying in Touch
 Discussion Board
 Virtual TA
 Announcement Archive
 Mailing Lists
Staff
 Instructors
 TAs
 Consultants
 Consultant Schedule
Check Your Scores
 MyUW
   

CSE 142 Project Assessment

Each project will be graded with respect to four categories. Each category will receive a score from 0 to 4, based on the following guidelines:

Category (Down)/ Score (Across) 0 1 2 3 4
Design, specification, implementation (style of code), testing Lack of evidence for design, specification, implementation, and testing of code At least one part of the process did not get completed. For example, there may be no evidence of testing. All tasks are done but several of them of them are not done well. All parts of the process are documented, but some part may lack clear descriptions. For example, the specification for client code may not be clear Project design, specification, code quality, and testing are well-documented and complete. For example, testing covers most, if not all, cases.
Code correctness and adherence to specification Project code does not function at all [does not compile] or addresses few parts of the specification Project code addresses less than half the specifications and works for a limited number of cases Project code addresses and functions correctly for about half the specifications Project code addresses and functions correctly for more than half the specifications, but does not meet all requirements Project code meets all requirements in the specification and functions correctly
Written report technical content Use of vocabulary is inappropriate, Incomplete descriptions for many sections of report Few technical terms used correctly, some indication that the student understands the process and design of the application Some technical terms used correctly, report is complete but it is clear the student lacks understanding about the process or code Almost all technical terms used correctly, report demonstrates that student is unclear about a stage in the process or the code developed Report demonstrates that the student understands the full process, Use of correct technical terms
Written report writing style Use of incomplete sentences, rough transitions, confusing descriptions, incorrect grammar Much of the report has rough transitions, some incorrect grammar Half of the report is clear and concise with a few rough sections Much of the report is clear and concise, with one or two rough sections Report includes smooth transitions and clear and concise descriptions


CSE logo Department of Computer Science & Engineering
University of Washington
Box 352350
Seattle, WA  98195-2350
[comments to cse142-webmaster]