EE492: Electrical Engineering Design II

Instructor:  Prof. Robert C. Maher

Class Objective

To complete successfully a capstone design experience involving teamwork, application of engineering principles, understanding and working within a clear set of design constraints, and realistic project verification and documentation.

Class Outline (subject to change)

EACH WEEK:  Project weekly reports (email) are due each Monday by 5:00PM, starting September 10, 2007.

Course Grading

The final grade for EE492 will be assigned by the Head of Department based on all the components listed above.

Weekly Progress Reports (faculty advisor grade)

Each student must submit a weekly progress report in the form of a brief email memo to the faculty advisor with a copy to the EE492 course instructor (rob.maher@montana.edu). The email message must include

Suggested weekly report format

Project Web Page (instructor grade)

Each project must have a descriptive web page.  The page (or pages) must list the project name, student names, sponsor, faculty advisor, and the semester (Fall 2007).  The page must also have a one paragraph description of the project design goals, a summary of the engineering constraints, and any other relevant information.  Students are encouraged to include photographs, diagrams, and other information that would help other students and members of the public to understand the nature of the design process.

Here are some instructions on where to store the web page files . These will be updated during the semester as necessary.

ECE Design Journal or Lab Notebook (instructor grade)

A design journal is the "diary" of intellectual contributions to your project.  The purpose of the Journal is to follow the required practices of industrial or academic research and development laboratories, where complete and accurate records of laboratory work are vital. The lab journal is a legally recognized paper that is essential in documenting project progress, discoveries, billable work time, and patent disclosures. Some companies require lab notebooks to be officially notarized and filed so that any legal questions later on can refer directly to the original, unaltered notebook entries.  Even if you end up working for a company that does not require a notebook or journal, it is worth getting in the habit as a way to document your own work and to organize your development activities.

The pages of the Journal must be bound (not loose leaf or spiral) and should be numbered consecutively. The notebook entries must be in ink, and no pages should be left blank between entries. Begin the entries for each work day on a new page, giving the date and time, your name, the topic, and in the case of a meeting, the names of all of the people present.  The entries themselves can be full of written comments, calculations, sketches, data tables, speculative ideas, brainstorms, design alternatives, contact information (email, phone, URLs, etc.), references to electronic files, schematic diagrams, and so forth.

In case some of the data or calculations written in the Journal turn out to be in error, do not tear out the page or completely obliterate the entries: a single line through the error is preferred. This way there is no question regarding the legitimacy and completeness of the notebook material. Furthermore, you will not be penalized in this course for having lined-out errors and corrections in your notebook.

Each student's Journal will be collected three times during the semester.  The Journals will be evaluated on the following criteria:

• Overall Form:  Entries in ink; writing legible; dates, times, and topics indicated clearly.
• Thoroughness:  Cogent sequence of activities and meetings; presence of design ideas, data collection, data analysis, and schedule planning; examples of design results and conclusions.
• Creativity and Insight:  Journal entries show a connection between initial ideas, preliminary activities and the resulting design and implementation decisions.

Milestone Tracking (instructor grade)

Each student is expected to be able to demonstrate some working hardware or software at two key project milestones during the semester.  The milestones and dates are intended to allow the student, the student's teammates, and the advisor to assess the rate of progress, make mid-course corrections, and avoid surprises during the design project.

At the end of the second class meeting (September 6, 2007), each student will submit a memo report detailing the two milestones to be demonstrated and the dates by which the milestones will be achieved.  It is up to the student to arrange the manner in which the advisor and the instructor can verify milestones.

Self/Peer Reviews (instructor grade)

Personnel reviews are a part of project management responsibilities. You will be having regular reviews with your boss and will need to provide reviews of those you supervise. This is often a difficult--but necessary--thing to do. To give you some practice we are asking you to complete an evaluation form for yourself and your project partners. The letter grades you give to yourself and your project partners will be confidential and used solely by the course instructor.  There will be two evaluations performed: one at midterm and one at the end of the semester.

Self/peer review directions and evaluation sheet

EE492 Engineering Standards and Constraints Review Paper (instructor grade)

The purpose of this assignment is to encourage thinking about these important design topics that we might otherwise overlook while concentrating on the "technical" details.  The Review Paper should include all of the project objectives and expectations that were presented in the project proposal from EE391.

In the 4th week of the semester each project group will submit a formal report that describes the realistic engineering standards and constraints that have been considered in the design as it has progressed to that point. These considerations include the following impacts: economic; environmental; sustainability; manufacturability; ethical; health and safety; social, and political.

The paper must be in a form that would be appropriate for a technical publication such as an IEEE article.  Thus, a Microsoft Word template will be provided:  papers must be prepared using the IEEE stylesheet (.doc).  Latex stylesheets are available from:
 http://www.ieee.org/portal/pages/pubs/transactions/stylesheets.html

Don't bother with fancy binders; just staple in the upper left corner. You do not have to supply a picture with your biography, but there should be a one paragraph bio for each project member.  The length should be no greater than five single-space pages excluding figures and appendices. 

Grades for the paper will be based on the following four main points:

Format: Following the required format.

Content: Effective explanations, complete description of the design considerations.

Organization: Structure is easy to follow; report has headings and transitions.

Design and Illustration: Understandable and legible tables and figures; overall professional appearance.

Grammar, Style and Mechanics: Correct spelling, grammar, punctuation, and sentence structure. Readable and clear style.  Professional tone, not informal writing. Complete and correct list of references.

NOTE that two copies of the report are required: one for grading on the due date and one for inclusion in the team's EE492 Project File at the end of the semester.

EE492 Design Fair Presentation Guidelines (visitor evaluation grade)

The Design Fair is scheduled for the last week of classes (dead week), on Thursday, December 6, 2007. The format is a public poster presentation and demonstration of your project. Each student will prepare materials describing his or her part of the project and the project team will display a comprehensive combined poster and demonstrate the project (if possible) during the public session held in the SUB. This is a group presentation with each student participating and describing his or her own contribution to the project.

The entire system hardware and software should be included in the display. The poster materials should include an overview of the project, discussion of engineering constraints, information regarding each student's contribution to the final design, project performance, results, conclusions and recommendations for future work. Additional assessment information will be provided a few weeks before the Fair.

NOTE that a presentation package consisting of the posters and other presentation materials is to be delivered to the ECE Office as part of the EE492 documentation.

EE492 Project Demonstration Guidelines (faculty review team grade)

Each project team must arrange to demonstrate their fully functioning project to a faculty review team in the SUB Ballroom during the morning of the Design Fair (December 6, 2007). Each project team member is required to participate, and a schedule will be set up to allow all team members to be there during the demonstration. In addition to the design fair poster displays, you should be prepared with project goals, schematics, flow diagrams, and similar materials to demonstrate that project performance goals have been met. Grades will be assessed primarily on the degree to which the project performance goals have been achieved.  Project teams without demonstrable evidence that the design goals have been met should expect a very low score from the review team.

The review team will also assess the team's preparation (documentation ready, readable and sufficient), the ability of each team member to answer project-related questions, and whether or not the appropriate test equipment is available to verify the project's performance. More detailed information to help you prepare for this presentation will be given to you during the semester.

In the event that a project is not suitable for demonstration at the Design Fair venue (e.g., cumbersome hardware that cannot be brought to the Fair, or an off-site design project of some kind), alternate arrangements must be made PRIOR to the Design Fair date on a case-by-case basis only.

EE492 Technical Documentation Package Guidelines (faculty advisor grade)

Each project team is to produce a Technical Documentation Package for the project. One copy is delivered to the project's faculty advisor and/or sponsor (if required) by 5 PM on Monday of final exam week. The goal of the technical documentation package is to supply sufficient information so that an engineer (or follow-on project students) can completely understand and reconstruct your project hardware and software. The package may include, but is not limited to, the following items:

Project notebook; schematic diagrams; PC board layout; PC board files; mechanical drawings; construction information; circuit descriptions; written test plans; written test results; software design documentation; software listings; software test plans and results; component data sheets; trouble shooting techniques; error messages; copies of progress reports; references

NOTE that a copy of the Technical Documentation Package is to be delivered to the ECE Office as part of the EE492 documentation.

EE492 Project User's Manual Guidelines

If a user's manual is appropriate for the project (not all projects will have a user's manual) the project team is to produce one as part of the final documentation. It is to be delivered to the ECE office with the technical documentation package. The faculty project advisor and/or sponsor may require additional copies. The user's manual normally contains complete information for the user to install, run the system, and troubleshoot problems. Maintenance information, if appropriate, should be included, as well as error messages and what to do about them.

ECE Department EE492 Project Documentation

To assist the Department in meeting its accreditation goals and to provide useful information for future project students, we have established a documentation file for all EE492 projects. The ECE office will maintain the file and students will submit material for it. Each project's file will have the following material:

1. Engineering Standards and Constraints Review Paper
2. EE492 Design Journals
3. The Design Fair Poster
4. The Technical Documentation Package
5. The Project's User Manual (if produced)

Project File Checklist (required!)