EE492 Senior Design
Spring 2007
Web Page:http://www.coe.montana.edu/ee/courses/ee/ee492/ee492hpg.htm
EE492 List Server: EE49201@listserv.montana.edu
Project Deliverables
The EE492 course project deliverables, in addition to any project related deliverables are the
following:
Engineering Standards and Constraints Review
Design Journal
Design Fair Poster Presentation Package
Technical documentation package
These are to be delivered to the ECE office as shown on the schedule below.
Grading
There will be four components used to determine each student=s final grade.
50%
Faculty Advisor
This portion of the grade will be determined by your faculty
advisor and may include any factors the advisor wants including
student self-evaluations, peer evaluations, and an assessment of the
student=s work throughout the semester. This could include
performance in design reviews, attendance at project coordination
meetings, discussion participation, contribution toward project
accomplishments, and teamwork. Additional components that the
faculty advisor may evaluate include the project's technical
documentation package and user's manual.
15% Design Fair
A public presentation describing the project and each student's
contribution is scheduled for Thursday, May 3. 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.
20% Demonstration
All projects must be demonstrated to a team of faculty members
during the morning of the design fair unless arranged otherwise.
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 site, the students must
arrange an alternative demonstration PRIOR to the Design Fair.
15% Class Grade
The Aclass grade@ consists of several components:
35% Design Journal and Milestone Tracking.
35% Self/Peer Evaluations
20% Engineering Constraints Report
10% Project Web Page, weekly progress reports, class
attendance, and other class assignments
The final grade for EE492 will be assigned by the Head of Department based on all the
components listed above.
1
EE492 Project Milestones:
Week of:
Each Week
Date:
Thur, 3 PM
W1: Jan 15
W2: Jan 22
Mon, 4:30 PM
Thur, Jan 18
Thur, Jan 25
W4: Feb 5
W5: Feb 12
W6: Feb 19
W7: Feb 26
W9: Mar 19
W10: Mar 26
W15: Apr 30
Exam Week:
May 7
May 3
Thur Feb 8
Thur Feb 22
Thur, Mar 1
Thur, Mar 29
Thur, May 3
Milestone Event or Project Requirement:
One hour class meetings, 307 Roberts, Check your email
Thursday mornings to see if class is cancelled. If no
message, assume class will be held.
Weekly progress reports are due.
First class meeting; get the rules of the road
Project Demonstration Milestones dates to be submitted as
a memo report.
Engineering standards and constraints paper due.
Make an appointment to review your Design Journal
Draft web pages due
Midterm Self/Peer reviews due
Make an appointment to review your Design Journal
Updated web pages due
Senior Design Fair presentation and project
demonstration. One copy the poster demonstration
materials to be delivered to the ECE Office as part of the
final project documentation.
Mon, May 3 4:30 Technical Documentation Package delivered to faculty
advisor.
Final Self/Peer Review due.
Wed, May 9 4:30 Complete project documentation package including all
project materials delivered to the ECE office for inclusion
in the EE492 file. Additional copies may be required by
the project's faculty advisor and/or project sponsor.
Materials to submit include:
Engineering Standards and Constraints Review Paper
EE492 Design Journal(s)
Design Fair Poster
Technical Documentation Package (Report, design
Description, and User’s Manual
Senior Design Checklist fully completed
Weekly Progress Reports (A component of the class grade)
Each student is to submit a weekly progress report in a single page memo format. 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. A project
advisor may request other information. The report is due on Monday at 4:30 PM delivered to the
project faculty advisor with a copy (email or hard copy) to the EE492 instructor. (The project
advisor does not need to assign a grade for your report but may take the opportunity to Acounsel@
you on how you are doing.)
2
Here is a suggested format for the progress reports you are to produce weekly.
Email to:
Project Advisor
Copy to:
fcady@ece.montana.edu
Email Subject: [E492 2007-mm-dd] Weekly Report
Memo to:
From:
Date:
date)
Project Advisor
Project Group Member
12th of Never 2007 (Note: Do not use an automatically updating field for the
Reference: Project Title Progress Report
1.
Review: What was planned for the past week.
2.
Report: What was done the past week including any problems that came up.
3.
Responsibility: What is planned for the coming week.
3
Project Web Page (a component of the class 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 (Spring 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.
Project Design Journal (a component of the class 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 two times during the semester and then at the end as part
of your technical documentation package. 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.
4
Milestone Demonstrations (a component of the class 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 (January 25), each student will submit a memo report
detailing the two milestones to be demonstrated and the dates by which the milestones will be
achieved. Each student is to arrange the manner in which the advisor and the instructor can veriy
milestones.
Self/Peer Reviews (a component of the class 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 do this for
yourself and your project partners. The letter grades you give to yourself and your project
partners will be ABSOLUTELY confidential and used solely by the course instructor. There will
be two “evaluations”, one at midterm and one at the end of the semester.
EE492 Engineering Standards and Constraints Review Paper (a component of the class 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. These can include the following: economic; environmental; sustainability;
manufacturability; ethical; health and safety; social; and political. A copy of your report will be
included in the EE492 project file.
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 (see Sample IEEE Paper link on the EE492 website). 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.
5
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 (15% of final grade)
The Design Fair is scheduled for the last week of classes (dead week), on Thursday, May 3,
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 (20% of final 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 (May 3, 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
6
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
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 4:30 PM on
Monday of 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. Additional copies may be required by the
faculty project advisor and/or sponsor. 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 File
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 file will be maintained by the ECE office 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 presentation package.
4.
The technical documentation package
5.
The project's user manual (if produced).
7
Library Resources
Author
Graf
Graf
Inglis
Bostock
Sidensticker
Berlin
Antoniou
Sterns
Book - Subject
"Modern measuring circuit encyclopedia"
"Modern detector circuit encyclopedia"
"Video Engineering" - Television [TK6630]
"Programmable Logic Handbook" [TK7872]
"The Well Tempered Digital Design"
"The 555 Timer Applications Source Book"
"Digital Filters: Analysis, Design and Applications" [TK7872]
"Signal Processing Algorithms using Fortran and C" (with software disk)
[TK5102]
Williams
"EMC for Product Designers" [TK7867]
Baher
"Selective linear-phase switched-capacitor and digital filters" [TK7872]
Linnartz
"Narrowband Land-Mobile Radio Networks" [TK6570]
Lee
"Computer-aided Analysis and Design of Switch-mode power supplies"
[TK786]
Mills
"Electro-Magnetic Interference Reduction in Electronic Systems" [TK7867]
Carr
"Sensors and circuits: sensors, transducers, and supporting circuits for
electronic projects", [TK7872]
Dye
"Radio frequency transistors: principles and practical applications"[TK7871]
Powers
"Introduction to fiber optic systems", [TA1800]
Chichester
"Power mosfet design [TK7871]
Mazda
ATelecommunications engineer's reference book", [TK5101]
Dorf
"The electrical engineering handbook"
Brooklands
AElectronic Circuits Handbook: Design, Testing and Construction", [TK7867
Lenk
"McGraw-Hill Circuit encyclopedia and trouble shooting guide" [TK7867
Hess
"Land-mobile radio system engineering" [TK6570]
Bishnu
"Fundamentals of fibre optics in telecommunication and sensor systems"
[TK5103]
Silva
"High performance CMOS continuous-time filters", [TK7872],
Motchenbacher "Low-noise electronic system design", [TK7867]
Flanagan
"Handbook of transformer design and applications" [TK2791]
Dern
"Internet guide for new users" [TK5105.875]
Hood
"The art of linear electronics", [TK7874]
Lenk
"Simplified design of linear power supplies"
Levy
"Battery hazards and accident prevention"
Roumenin
"Handbook of sensors and actuators", [TK7872]
Daugherty
"Analog-to-digital conversion: A practical approach"
Butterworth
"simplified design of switching power supplies" (should be good for projects)
[TK7868]
Rumsev
"Digital interface handbook"
CRC Press
"Circuits and Filters Handbook"
Berube
"Computer simulated experiments for electronic devices using electronics
workbench"
Shani
"Electronics for radiation measurements, Vol 1 and 2"
8
Brookes
Fowler
Pain
Horn
"Electronic surveillance devices"
Electronic instrument design: architecting [sic] for the life cycle"
"Practical electronic fault finding and troubleshooting"
"Master IC cookbook"
Web Resources
http://www.coe.montana.edu/ee/courses/ee/ee492/ee492hpg.htm EE492 Home Page
http://www.coe.montana.edu/ee/cady/misclink.htm
Miscellaneous links about various
hardware such as keyboards, A/D,
motor drives etc.
http://www.coe.montana.edu/ee/cady/ee361/hc11lnks.htm Microcontroller links, PC board
software, embedded systems info
http://www.coe.montana.edu/ee/cady/ee361/embedded.htm More embedded systems info
http://www.coe.montana.edu/ee/info/eesrces1.htm
Electronics parts searches,
application notes, data sheets, on-line
parts catalogs
http://www.eecentral.com/
EE Central. All sorts of useful
information including parts lookup.
http://www.hardware-guru.com
Neat hardware design help
http://www.circuitsage.com/
Ditto
http://www.lansing-enclosures.com/
This is the company that makes
lowcost small enclosures that are
ideal for Sr. projects. Very nice
product!!
Please email me any other urls that you find especially useful.
G:\1wpdocs\univ\dept\courses\ee492\EE492_Course_forms_s04.doc
9
EE492 Senior Design Project Check List
Spring 2007
This check list MUST be completely checked off by the indicated people before the Department
will submit the course grade to the Register. Failure to complete all of the items will result in an
AI@ grade until the unfinished tasks or documents are completed. One sheet is required for
each project. . It is the responsibility of each project group to maintain this sheet and hand it
into the ECE office no later than 3:00 PM on Wednesday May 9, 2007.
Project Title
Student Project
Members
Faculty Advisor
Task or
Document
Completed
(Initial)
Responsible
Person
Engineering standards and constraints review documentation
delivered to ECE Office.
Dept. Secretary
Poster Presentation package delivered to ECE Office to be placed in
EE492 file
One copy of technical documentation package delivered to ECE
office.
Dept. Secretary
Any addition copies (if required) of technical documentation
package delivered to the faculty advisor and sponsor.
Faculty
Advisor
Completion of the project
Sponsor
Delivery of the project and any sponsor provided equipment to the
sponsor
Sponsor
Clean up the laboratory and return equipment borrowed from the
department
Stockroom
Reconciliation of any project accounts in the ECE Stockroom
Stockroom
Return of the laboratory key to the campus police (receipt must be
shown)
Dept. Secretary
Dept. Secretary
Note: Initialization areas blanked out will be checked off on another check list by the Dept. Secretary
10