ics2O_summative_Evaluation

include component="page" page="course_tabs_header"

include component="page" page="menu_ics2O_crumbs"

=Summative Evaluation=

Planning

 * ~  ||~ Level 4 ||~ Level 3 ||~ Level 2 ||~ Level 1 ||
 * Concept || Students have a clear picture of what they are trying to achieve. Student can describe what they are trying to do and generally how his/her work will work. || Students have a fairly clear picture of what they are trying to achieve. Each student can describe what they are trying to do overall but has trouble describing how his/her work will work || Student has brainstormed their concept, but no clear focus has emerged. || Student have spent little effort on brainstorming and refining a concept. Student is unclear on the goals and how they will reach the goal. ||
 * Planning || Planning is complete and it is clear what steps are necessary to create the game. || Script is mostly complete. It is relatively clear what steps are necessary to create the game. || Planning has a few major flaws. It is not always clear how student(s) intend to implement game design. || There is no evidence of planning. Game designers will invent what they do as they go along. ||

Production

 * ~ Level 4 ||~ Level 3 ||~ Level 2 ||~ Level 1 ||
 * Code structure and commenting || Code is easy to follow, syntax is exemplary, no spelling mistakes, comments present and plentiful || Code is easy to follow, generally syntax is good, generally no spelling mistakes, comments present and as expected || Code is challenging to follow in parts, syntax is spotty, spelling mistakes, comments present || Code is difficult to follow, syntax is flawed, large numbers of spelling mistakes few comments present ||
 * Code logic || Game appears to be optimized - code is concise, and logic is well thought through. || Game appears to be generally optimized - code is somewhat verbose, and logic is generally well thought through. || Game code appears to be unnecessarily long - code is somewhat verbose, and logic is not particularly well thought through. || Game is unnecessarily long - code is verbose, and logic is not well thought through ||
 * Functionality || No obvious flaws in game. Gameplay is smooth and enjoyable. || Minor flaws in game. Generally gameplay is smooth and enjoyable. || Gameplay is somewhat inconsistent. Flaws in the game are outweighed by enjoyment factor. || Gameplay is poor. Game either completely non-functional or only works occasionally. ||