Differences

This shows you the differences between two versions of the page.

--- contract [2010/04/21 18:28] – created bil
+++ contract [2012/03/15 19:12] (current) – dymond
@@ Line 1: / Line 1: @@
 ====== Contract Template ======
-A contract is typically a few pages in length. It has the following layout:
+The project contract is typically about three pages in length. It is prepared by the student with required input from their faculty project supervisor.
+It has the layout shown below.  You may use the {{:contract-template.tex|LaTeX template}}.
 **Course**:    CSE4080
-**Academic Year**:   e.g. Fall 2009
+**Academic Term**:   Summer 2012
-**
-Project title**:   < title >
-**Supervisor name (email)**:   < name > (< email >)
+**Project title**:   < title >
-**Student name**:  < name >
+**Supervisor's name**:   < name >
+**Supervisor's email address**:  <address>
+**Student's name**:  < name >
 **Student number**:  123456789
@@ Line 22: / Line 25: @@
 What the project is to achieve, a half to one page. Please describe the educational component of the project.
-=== Requirements ===
+=== Background Requirements ===
 Prerequisite courses: list the courses and the minimum-mark requirement for each
-Corequisite courses: list the courses to be taken concurrently
+Corequisite courses: list the courses to be taken concurrently (if any)
 Other experience:  technical know-how needed, familiarity with languages and systems, mathematical background, etc.
@@ Line 32: / Line 35: @@
 === Resources ===
-This is worth spelling out because it may be more helpful to the student in choosing a project than the project description.
 Software:  list of programming languages, tools, operating systems, etc.
@@ Line 46: / Line 47: @@
 === Deliverables ===
-List of artifacts to be completed by the final due date; includes programs, documentation, reports, user guides, etc.   One of them is your  final project poster presentation on a date around the end of term, usually during the exam period or at the start of the next term.
+List of //artifacts// to be completed by the final due date; includes programs, documentation, reports, user guides, etc.   One of them is your  final project //poster presentation// on a date around the end of term, usually during the exam period or at the start of the next term.
 === Milestones List ===
-Milestones to be reached during the project. Useful for the project contract and progress evaluation. The following is an example:
+//Milestones// to be reached during the project. Useful for the project contract and progress evaluation. The following is an example:
   - by <date>: Background reading completed.
@@ Line 61: / Line 62: @@
 === Evaluation ===
-Some indication as to how the project will be evaluated. For example, the project can be marked on the basis of the progress towards stated goals, and the clarity and completeness of programs, documentation and reports. It is strongly recommended and encouraged that evaluation has a number of components and not just a grade at the end. Grades can be associated with different deliverables or their parts. Components could include: documentation, programming style, quality of the interface design, project proposal presentation, project status presentation, and overall evaluation.
+Indication as to how the project will be evaluated. For example, the project can be marked on the basis of the progress towards stated goals, and the clarity and completeness of programs, documentation and reports. It is strongly recommended and encouraged that evaluation has a number of components and not just a grade at the end. Grades can be associated with different deliverables or their parts. Components could include: documentation, programming style, quality of the interface design, project proposal presentation, project status presentations, and overall evaluation.
 At least 20% of the evaluation should be available before the drop date.
 The following is an example. Note that all projects must have a requirement for a poster preparation and presentation. The grading of this requirement is worth 30% of the final grade and is assigned by the CSE4080 seminar committee. By signing this contract both student and supervisor agree to participate in the seminar day which will be typically scheduled during the exam week or in the first week of class following the term that student is enrolled in CSE4080. Students and supervisors should check the course web page for the current term to find the date scheduled for the seminars.
   * Mid-project status report -- ?%
@@ Line 73: / Line 74: @@
   * Programming and technical work -- ?%
-  * Poster presentation -- 30%
+  * Poster presentation -- 30% (required component)
   * Meeting milestones -- ?%