Engineering 7803/4

Engineering 7803 Electrical Engineering Design Project I
Engineering 7804 Computer Engineering Design Project I

Instructors: Dr. R. Venkatesan Mr. R. Collett
Office Hours: Tu 13:30-15:30 or by appointment, EN-4015 by appointment
Phone: 864-7962 737-1909
Lecture/lab slot: Tu 1400-1645 EN2048 (other rooms will be arranged for lectures)
T.A. Khalid El-Darymli

Projects | Organization & Deliverables | Lectures

Engineering design integrates mathematics, natural sciences, engineering sciences, and complementary studies in order to develop elements, systems, and processes to meet specific needs. It is a creative, iterative, and open-ended process, subject to constraints which may be governed by standards or legislation to varying degrees depending on the discipline. These constraints may also relate to economic, health, safety, environmental, societal, or other interdisciplinary factors.[CEAB Accreditation Criteria and Procedures 2008,]

Engineering 7803/4 is the first part of a pair of courses, continued in 8853/4, during which students will complete their senior design project. These courses together provide a significant design experience based on the knowledge and skills acquired in earlier in the program, and give students an involvement in team work and project management.


Project proposals are invited from faculty, students and industrial clients and may be submitted to R. Venkatesan or Rob Collett using the proposal template document. Projects must involve a significant design experience suitably scoped for a team of three to five students working at a level of one regular course (approximately 10 hours per week) over two academic semesters. Some work may also be completed over the intervening work term. Clients need not be technical experts but must be prepared to interact with student teams as needed to ensure that the project requirements are understood and to give feedback on design outcomes. Clients will be asked to participate in the project review presentations at the end of the Spring semester (late July) and the final project presentations at the end of the Winter semester (late March). Students may propose their own project, but must include with the proposal an additional one page description of the motivation and technical background sufficient for the course coordinators to assess the appropriateness of the scope and technical challenge.

The list of available projects is posted here. Project teams are managed through Desire2Learn.

Organization & Deliverables


May 2EN-40022 pmRobert Collett & R. VenkatesanIntroduction and Report Tips
May 17EN-10002 pmChip ClarkProject Management
May 24EN-40023 pmAmy HsiaoEntrepreneurship
May 31EN-40022 pmBill MorrisseyCommunication
June 14EN-40022 pmEd BrownPatents, Copyright and IP

Handouts for the lectures are available through Desire2Learn.


Date Deliverable Marks
Friday, May 18 Project Selection -
Monday, May 30 Project Description 10%
Week of June 27 Midterm Progress Meeting 5%
Monday, July 18 Preliminary Design and Implementation Report 55%
Week of July 25-29 Project Review 25%
Logbook 5%

Project Selection

Assignment of individual students to particular projects is the purview of the course instructors. The following process will be followed:

  1. From the list of available projects, students are to select the project(s) and role(s) that interest them and inform the course instructors of their choice by e-mail before 2359 hrs Wednesday, May 18.
    • Students may propose their own projects. These must be submitted as described above and approved prior to May 18.
    • Groups of students may propose to work together on a particular project(s). We don't promise to honour all such requests and may modify the group by addition or removal of students.
  2. The assignment of students to projects will be confirmed on May 20.
  3. Following confirmation, proposals for revised teams will be considered only with good cause and will normally only be approved if the revision is acceptable to all parties involved.

Project Description

The Project Description shall be a preliminary report complied by each project team. As a guideline, it is recommended that the document include the following sections:

Report content is not limited to the above as students may choose their own report format. It is expected, however, that the document shall include an executive summary, references, drawings/diagrams, a table of contents, and a conclusion.

Midterm Progress Meeting

The Midterm Progress Meeting shall involve a 20 minute discussion of project progress with course coordinators near the halfway point of the term.

Preliminary Design and Implementation Report

The Preliminary Design and Implementation Report shall be a comprehensive report compiled by each project team. As a guideline, it is recommended that the document include the following sections:

As indicated above for the Project Description, content is not limited to the above as students may choose their own report format. Again, it is expected that the document shall include an executive summary, references, drawings/diagrams, a table of contents, and a conclusion.

Project Review

The Project Review shall involve a formal presentation of all project progress to date before a panel consisting of:

All team members shall be expected to participate in the presentation. Presented material should provide a clear overview of the content discussed in the Preliminary Design and Implementation Report. It is expected that the presentation should last approximately 15 minutes with an additional 15 minutes alloted for discussion.


An engineering logbook represents a formal record of an individual's work and may serve as a helpful reference for any technical undertaking. As part of the senior design project, each student shall maintain a logbook to be used in both Term 7 and Term 8. Logbooks will be evaluated on an on-going basis and may be reviewed at any time by an instructor/TA/supervisor or client. Logbooks may include any information relevant to the project, for example

Logbooks should be written in ink and every page and every entry should be dated.

Related Links

Intellectual Property
Revision Control

back to R. Venkatesan's homepage

Last modified $Date: 2011-05-17 10:18:10 (Tue, 17 May 2011) $ ($Revision: 2 $) by $Author: venky $