Download EE 494 - csserver

EE 494
Syllabus
Spring 2004/05
Dr. Blandford
EE 494 is a non-credit class. The objective of this class is to present a sequence of
problems that are suitable as senior design projects in EE 495/497. To successfully
complete this class students must choose a problem for the senior project sequence along
with the appropriate project sponsors. Each student must then do an oral presentation to
the class describing the project.
Every student is expected to meet the following requirements:
1. Attend all scheduled class sessions.
2. Select a project suitable for the senior project sequence.
3. Prepare a written "mini-proposal".
4. Complete and oral presentation to the class for the chosen project.
5. Attend two or more EE 497 presentations.
Registration in EE 495 is restricted to those with successful mini-proposals.
The first ten weeks of the class will be used for the presentation and selection of projects.
The eleventh and twelfth weeks will be used for gathering data, conducting a literature
search, and preparing the initial written statement of the problem (mini-proposal). The
last three weeks of the semester will be used for student presentations.
A mini-proposal outline is attached.
This syllabus, proposed projects, and other information pertaining to the class will be
posted at the web site at
http://csserver.evansville.edu/~blandfor
EE 494
Proposal Outline
I. Abstract
(This is a short summary of the proposed project telling clearly what is be done. You
should also include the names of the faculty and the industrial sponsor.)
II. Statement of need (Summary of RFP)
a. What is the problem?
b. What is it's origin?
c. Why is its solution important?
III. Work Done to Data by Others (if any)
(This is a brief summary of the major work efforts including their degree of success
and/or failure and treason for failure. Use this section to highlight the basis for
expecting this work to be successful.)
IV. Statement of Proposed Work
a. Objectives
b. Technical description of work to be done
c. Approach to solving the problem
d. Examples and illustrations of why you think your approach will work
e. Equipment and facilities needed.
f. Explanation of how the important acceptance criteria of the RFP will be satisfied
V. Schedule and Milestone Events
(Select well defined events throughout the program that can be used to measure
progress towards objectives.)
VI. Cost and Manpower Requirements
a. Equipment costs and types
b. T4ravel Costs
c. Number of man-hours required
d. Distinguish between one-time development costs and the recurring costs (if any).
Rules and Guidelines for Choosing a Senior Project
1. All senior projects must result in some final piece of hardware or software which can be
demonstrated by the student doing the project. The purpose of the demonstration is to verify
the design completed by the student. Paper designs or projects which contain little design are
specifically excluded.
2. Secret projects (such as for the government) or proprietary projects (such as a co-op might do
for a company) where pictures and demonstrations before a group are not allowed are not
eligible for senior projects.
3. Co-ops who expect to do a project which is part of their normal co-op duties as their senior
project must get permission from a sponsoring faculty member before the project is started.
The sponsoring faculty member must monitor the project as it progresses to verify that the
student is doing a significant portion of the design for the project. In no case will a student
be permitted to complete any project prior to a formal design review and presentation.
4. Project demonstrations must be done for the EE/CS 497 class on the UE campus. In the case
where a student is completing a large project tied to an industrial sponsor's equipment or
plant the student may seek special permission to do a demonstration in one of the following
ways:
1. Some portion of the project may be duplicated on a small scale so that it can be
demonstrated to the EE/CS 497 class in the normal manner.
2. A video (or extensive) slides may be produced on site. These can be shown in the EE/CS
497 presentation as the demonstration.
5. In the case where the student presents a scaled down project or pictures, the sponsoring faculty
member assumes responsibility for verifying that the student actually completed a significant
portion of the design and did so without extensive help from the employer. In most cases,
this verification would be done by an on site visit by the sponsoring faculty member followed
up by an informal oral exam. The EE/CS 497 written report should contain a statement
signed by the sponsoring faculty member to this affect.
6. All senior projects will have both a faculty sponsor and an industrial sponsor. In cases where
the project is internally sponsored a second faculty member may serve as the industrial
sponsor. In no case will the faculty sponsor also serve as the industrial sponsor.
7. The industrial sponsor will assume the responsibility of writing the specifications for the
project and determining whether or not those specifications have been met. The faculty
sponsor will act as a technical consultant to the project. The faculty sponsor will ultimately
determine the grade for the project but this should be done in consultation with the industrial
sponsor.