Differences

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

--- contract_template [2018/08/29 14:01] – lesperan
+++ contract_template [2019/09/03 15:59] (current) – khatoll
@@ Line 1: / Line 1: @@
 ~~NOTOC~~
-====== Contract Template  ======
+=======EECS 4070 Contract Template=======
-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 following layout:
+The contract is typically about two pages in length. It is prepared by the student in collaboration with the faculty supervisor. It has the following layout:
-**Course:** EECS4080 or 4480
+**Course:** EECS4070
-**Academic Year:** Fall 2018
+**Term:** Fall 2019 / Winter 2020
-**Project title:** < title >
+**Topic title:** < title >
 **Supervisor name (email):** < name > (< email >)
@@ Line 18: / Line 18: @@
 **Student's email:** < email >
-====== Project Description ======
+=====Topic Description and Course Learning Outcomes=====
-What the project is to achieve, a half to one page. Please describe the educational component of the project.
+A half-page describing the topic to be studied in the course. This should include a breakdown of several sub-topics and should specify about 5 course learning outcomes.
-====== Background Requirements ======
+=====Background Requirements=====
 Prerequisite courses: list the courses and the minimum-mark requirement for each
-Corequisite courses: list the courses to be taken concurrently
 Other experience: technical know-how needed, familiarity with languages and systems, mathematical background, etc.
-====== Resources ======
+=====Readings=====
-These should be spelled out because they may be more helpful to the student in choosing a project than the project description.
-Software: list of programming languages, tools, operating systems, etc.
-Hardware: list of computer and other needed devices.
-====== Readings ======
-A short list of research papers/books that could/must be studied or referenced for the project, that can help give some idea of what the project is about and the background required.
-====== 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.
-====== Milestones List ======
-Milestones to be reached during the project. Useful for the project contract and progress evaluation. Some formal evaluation should be provided to the student before the drop date. The following is an example:
+A list of research papers/books that will be studied or referenced during the course. Other types of resources may also be included (e.g., videos, online material).
-  - by <date>: Background reading completed.
+=====Evaluation=====
-  - by <date>: Preliminary project description document due. Background summary (2 pages). Specification of the work to be performed in terms of technical milestones (4 pages). Rationale for the approach and expected intellectual contribution (2 pages).
-  - by <date>: Progress report due. Summary of achievements so far, difficulties encountered, possible change in the technical milestones. Prototype implementation.
-  - by <date>: Preliminary draft of the final documents. Implementation work done except for bells and whistles.
-  - by <date>: Project due. All deliverables completed.
-====== Evaluation ======
+An outline of how the student will demonstrate the knowledge they have gained in the course. This will generally include a literature review. It can also include solving exercises, oral presentations, tests, oral exam, making improvements to a wikipedia article related to the topic, etc. There should be a breakdown of how items will be weighted in calculating the student's final grade.
-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.
+The evaluation should give the student an opportunity to demonstrate that the course learning outcomes have been achieved.
-At least 20% of the evaluation should be available before the drop date.
+The amount of work to complete the deliverables should be comparable to other 4000-level EECS courses.
-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 EECS4080 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 period or in the first week of class following the term that student is enrolled in EECS4080. Students and supervisors should check the course web page for the current term to find the date scheduled for the seminars.
+=====Schedule=====
-  * Mid-project status report – ?%
+A schedule for when the evaluation items mentioned above will be completed. Some formal evaluation (worth at least 20% of the final grade) should be provided to the student before the drop deadline. All deliverables should be completed by the end of the term.
-  * Final documentation & reports – ?%
-  * Programming and technical work – ?%
-  * Poster / presentation – 30% (required component)
-  * Meeting milestones – ?%
+This section should also specify the frequency with which the student will meet with the supervisor.
-====== Signatures ======
+=====Signatures=====
 Student
@@ Line 78: / Line 52: @@
 Supervisor
-Course Director
+Course Coordinator