Policies CPSC 436D Video game Programming january 2018
GradingEvaluation criteria (tentative)
The course is a project course with no exams or finals.
5% Hello Video Games - Introductory Individual Assignment
3% Game Pitch - Individual or mini-team
92% Team Project. Project done in teams of 6 (other team sizes accepted in special circumstances).
Project grade breakdown:
Bi-weekly project progress assessments: 52% (8%,4x11%), including cross-play feedback
Final project assessment: 25%
Weekly reports (participation): 5%
Leadership and teamwork assessment (peer feedback): 10%
Extra bonus marks will be provided for award winning projects (based on jury/public feedback).
Assignment and Milestone Grading: There will be face-to-face grading for the assignments, and milestones where the student/team will sign up for a slot to demo the work to the grader. You will be asked to explain the algorithms used in your program to the grader. If you cannot explain an algorithm, at the discretion of the grader, you will not receive credit for the entire assignment/milestone or part of it.
Attendance: Attendance and active participation in all lectures and other in-person activites is expected. You are responsible for knowing all material presented and any advice provided there. Most lecture material will be made available online. However, there is no guarantee that everything covered in lectures and elsewhere will be in the posted material.
It is important that assigned work be completed on time, because subsequent milestones depend on your comprehension of earlier work. To allow for unforeseeable circumstances, you will be allowed three days of grace during the term, which can be used on assignment 0 or any project milestones with no explanation required. Use these as you wish to help manage your time, but use them wisely. It is strongly recommended that you do not use all your grace days early in the term. You can use all three on one task, or spread the days across multiple tasks.
Once your grace days are all used, late milestones will receive a grade of zero. Exceptions to this late policy will be made only with advance approval from the instructor; or medical, emotional, or other problems documented in writing as below.
Severe Illness or Other ProblemsSee the UBC Policy on Academic Concession.
Documentation of Severe Illness or Other Problems: It is the responsibility of the student to provide adequate documentation of the situation and to inform the instructor in a timely manner so that the necessary appropriate action can be taken. Often assignments will be granted no-penalty extensions, but all cases are subject to the instructor's discretion. Usually it is expected that the student will provide a written explanation of the situation to the instructor within three days of returning to the University after any absence or period of illness or other problem. In no case will documents be considered more than seven days after a student has returned to the University. A written explanation must be submitted along with supporting documentation (i.e. a doctor's note in cases of illness); talking to or emailing the instructor is not an acceptable substitute for submitting the required supporting documentation.
Late/Missing Milestones: One of the following courses of action will be taken after receipt of appropriate documentation of the situation.
Religious Holidays: Students who are scheduled to attend classes or write examinations on the holy days of their religion must notify the instructor in writing three weeks in advance of the religious holiday they wish to observe. The instructor will provide opportunity for students to make up the missed work or examination without penalty.
Plagiarism and Cheating
Read the Computer Science Department's Guidelines and Practices Regarding Collaboration. Consult the University's policies and procedures regarding academic offenses for more information on plagiarism and the penalties sanctioned by the University.
CollaborationCollaboration outside the team without explicit instructor permission is not allowed. As explained in the CS collaboration guidelines, general discussion of programming and algorithms is allowed. However, source code may not be shared: all forms of reuse, such as electronic copying of a current or former student's source files, typing in source from a printout, or typing in source read from another student's screen, when done outside your team, will constitute an act of plagiarism in the context of CPSC 436D.
CitationYou are expected to cite all sources of inspiration (Internet or book or human) in your writeups. Acknowledging your sources of information in writing is the best way to avoid grey areas of possible academic misconduct. You do not need to cite anything covered in lecture or in the assigned readings, or discussions with the instructor or TAs. You should cite all other sources in writing: either at the end of the README documenting your program for the programming part of the assignments, or in a list at the bottom of the written part of the assignment. In the case of written assignments, any people with whom you have had extended discussions should be listed at the bottom of the paper that you turn in. Casual discussions of a few minutes do not need to be documented, but study groups do. The Web is full of fantastic resources for students: detailed tutorials with well-annotated source code; archives of mailing lists and newsgroups that contain programming questions and answers; and explanations of how to avoid, fix, or work around common (or uncommon) errors. You are welcome to use these resources responsibly, as long as you cite the sources. For example: if you looked at code fragments from the Web or from other books, list the Web sites or book titles in the References section of your README. Looking on the Web for ideas and information is permitted and encouraged. Even looking at sample graphics code is permitted, but simply copying that code and handing it in as your own is not. You will be asked to explain algorithms during the face-to-face grading slots, if you are not able to do so you will not receive credit for all or part of the assignment.
Due DiligenceIn the context of CPSC 436D, every student is held responsible to ensure that:
Cheating includes, but is not limited to: falsifying any material subject to academic evaluation; having in an examination any materials other than those permitted by the examiner; and using unauthorized means to complete an examination (e.g. receiving unauthorized assistance from a fellow student); giving somebody else money to complete course assignments instead of doing them yourself.
The first offence within the context of CPSC 436D (across all years, terms, etc.) shall cause the student and their team to receive a mark of 0 for all affected milestones, and the Chair of the Undergraduate Affairs Committee will receive a report detailing the particulars of the case. Further disciplinary action may be undertaken by the department, faculty, or university.
A second offence within the context of CPSC 436D (across all years, terms, etc.) shall cause the student to receive a grade of 0 for the course, the student will not be permitted to enroll in further offerings of CPSC 436D, and the Chair of the Undergraduate Affairs Committee will receive a report detailing the particulars of the case. Further disciplinary action may be undertaken by the department, faculty, or university.
Students not enrolled in CPSC 436D who are involved in a 436D-related plagiarism incident will not be permitted to enroll in future offerings of CPSC 436D, and the Chair of the Undergraduate Affairs Committee will receive a report detailing the particulars of the case. Further disciplinary action may be undertaken by the department, faculty, or university.
Although the instructor reserves the right to exercise leniency as she sees fit, the instructor usually considers cheating to be an insult to all other course participants, and aggressively prosecutes cheaters in order to create a level playing field where individual efforts are rewarded appropriately.