UW Home     CSE Home   Announcements    Message Board    Contact Info 

 
 
 

CSE 143 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 - The Program Code Score
Code correctness and adherence to specification, testing
  • 4 - Project code meets all requirements in the specification and functions correctly. Good test cases cover most, if not all, of the program functions.
  • 3 - Project code addresses and functions correctly for most of the specifications, but does not meet all requirements in some significant way.
  • 2 - Project code addresses and functions correctly for about half the specifications. Some evidence of test cases.
  • 1 - Project code addresses less than half the specifications and works for a limited number of cases.
  • 0 - Project code does not function at all or addresses few parts of the specification.
Design, specification, implementation (style and quality of code)
  • 4 - Project design, specification, and code quality are well-documented and complete.
  • 3 - All parts of the process are documented, but some part(s) may lack clear descriptions. For example, the specification for client code may not be clear.
  • 2 - All tasks are done but several of them are not done well.
  • 1 - Most tasks are done but several of them of them are not done well and at least one is not done at all.
  • 0 - Almost complete lack of evidence for good design, specification, and implementation of the project requirements.
Category - The Written Report Score
Written report technical content
  • 4 - Report demonstrates that the student understands and reports about the project fully, Use of correct technical terms.
  • 3 - Almost all technical terms used correctly, report demonstrates that student is unclear about a stage in the process or the code developed.
  • 2 - Some technical terms used correctly, report is complete but it is clear the student lacks understanding about the process or code.
  • 1 - Few technical terms used correctly, some indication that the student understands the process and design of the application.
  • 0 - Use of vocabulary is inappropriate. Incomplete descriptions for many sections of report.
Written report writing style
  • 4 - Report includes smooth transitions and clear and concise descriptions.
  • 3 - Much of the report is clear and concise, with one or two rough sections; significant spelling and grammar errors that make the report hard to read.
  • 2 - Half of the report is clear and concise with a few rough sections.
  • 1 - Much of the report has rough transitions, some incorrect grammar.
  • 0 - Use of incomplete sentences, rough transitions, confusing descriptions, incorrect grammar.