Department of Electrical and Computer Engineering
Montana State University
Fall Semester 2005
SEMINAR: Section 1 (CRN 20538), Thursday 8:00-8:50AM, RobH 208
| Office: |
529 Cobleigh Hall (southwest corner of 5th floor) |
| Phone: |
Office: 994-7759 |
| Email: | |
| Class Page: | |
| Office hours: |
MWF 10:30AM-noon. |
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.
EACH WEEK: Project weekly reports (email) are due each Monday by 5:00PM, starting September 12, 2005.
| Week |
Date |
Topics |
| 1 |
September 1, 2005 |
Lecture: Project Management |
| 2 |
September 8, 2005 |
Lecture: Engineering Design Considerations □ Get project lab (521 Cobleigh) door lock code and locker assignment (if necessary) from Sharon in ECE office. □Project Demonstration Milestones dates to be submitted as a memo report. |
| 3 |
September 15, 2005 |
Lecture: Written Documentation and Paper Writing □EE492 Design Journal submitted (1) |
| 4 |
September 22, 2005 |
Lecture: Prototyping Methods |
| 5 |
September 29, 2005 |
Lecture: Printed Circuit Boards |
| 6 |
October 6, 2005 |
No class this day. □Draft Project Web Pages due |
| 7 |
October 13, 2005 |
Lecture: Packaging □EE492 Design Journal submitted (2) |
| 8 |
October 20, 2005 |
Lecture: Intellectual Property |
| 9 |
October 27, 2005 |
Lecture: Professional Poster Presentations □Midterm Self/Peer reviews due |
| 10 |
November 3, 2005 |
Lecture: Professional Oral Presentations □Updated Project Web Pages due |
| 11 |
November 10, 2005 |
No class this day. □EE492 Design Journal submitted (3) |
| 12 |
November 17, 2005 |
Lecture: Starting a Business |
| 13 |
November 24, 2005 |
Thanksgiving Holiday (No Class) |
| 14 |
December 1, 2005 |
Lecture: Course Wrap Up |
| 15 |
December 8, 2005 |
No Class this day. □EE492 Design Journal submitted (4) Note: one copy of the poster display materials is to be delivered to the ECE Office as part of the final project documentation package. |
| 16 |
MONDAY, December 12, 2005 |
Finals Week □Final Self/Peer Review due by 5:00PM. □Technical Documentation Package due to faculty advisor by 5:00PM. |
| WEDNESDAY, December 14, 2005 | □Complete project documentation package delivered to the ECE office by 3:00PM for inclusion in the EE492 file. The project's faculty advisor and/or project sponsor may require additional copies.
Materials to submit include:
|
| Faculty Advisor: | 50% |
The faculty advisor for each team will determine a grade individually for each student based on an assessment of the work throughout the semester: weekly progress reports, performance in design reviews, attendance at project coordination meetings, discussion participation, contribution toward project accomplishments, teamwork, and professionalism. Additional components that the faculty advisor will evaluate include the project's Technical Documentation Package and User's Manual, self-evaluation scores, and peer evaluation scores. |
| Design Fair: | 15% |
A public presentation describing the project and each student's contribution is scheduled for the afternoon of Thursday, December 8, 2005 (the last week of the classes). People attending the Design Fair (faculty, public, etc.) will be asked to turn in an evaluation form which will be used to generate your group's grade. I will give you more information when we get to the end of the semester. |
| Project Demonstration and Review: | 20% |
All projects must be demonstrated to a team of ECE faculty members during the morning of the Design Fair (Thursday, December 8). The ECE department will establish a team of faculty members for this purpose. If the project is off-site or involves equipment that cannot be demonstrated at the Design Fair, the students must arrange an alternative demonstration PRIOR to the Design Fair. |
| Class Participation: | 15% |
The class participation consists of several components:
|
|
100%
|
The final grade for EE492 will be assigned by the Head of Department based on all the components listed above.
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
[EE492 2005-mm-dd] in the subject line (where mm-dd is the month and day of the weekly memo). The report is to cover at a minimum (a) what was planned for the past week, (b) what was done the past week, including any problems that have come up, and (c) what is planned for next week. The project advisor may request other information. The report is due each Monday at 5 PM (The project advisor does not need to assign a grade for your report but may take the opportunity to counsel you on how you are doing).Suggested weekly report format
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 2005). 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.
Instructions on where to store the web page files will be provided during the semester.
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 four times during the semester. The Journals will be evaluated on the following criteria:
Each student is expected to demonstrate some working hardware or software at two key project milestones during the semester. At the end of the second class meeting (September 8, 2005), each student will submit a memo report detailing the two milestones to be demonstrated and the dates by which the demonstrations will occur
. It is up to the student to arrange a mutually convenient time for the instructor to observe each milestone demonstration.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
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 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 paper must be in a form that would be appropriate for a technical publication such as an IEEE article. The example format is available here:
http://www.coe.montana.edu/ee/pdffiles/PG4-sample.pdf
You should conform to the format specified in the sample, EXCEPT the preferred Body text size will be 12 point. 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.
The Design Fair is scheduled for the last week of classes (dead week), on Thursday, December 8, 2005. 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 Project File.
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 8, 2005). 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.
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 Project File.
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.
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:
Project File Checklist (required!)