SYLLABUS

Contact Information:

Time Thursday: 3:30 PM - 4:50 PM (Classroom Lectures)
Tuesday: 2:00 PM - 3:15 PM (Entrepreneurship Lectures)
Thursday: 2:00 PM - 4:50 PM (Laboratory)
Place Lecture: 100 Simrall (Auditorium)
Entrepreneurship Lectures: 100 Simrall (Auditorium)
Meetings: Simrall 206
Labs: Simrall 323 (other rooms by appointment)
Instructor Joseph Picone
Office: 413 Simrall
Office Hours: 8-9 TR (others by appt.)
Email: picone@cavs.msstate.edu
Phone: 662-325-3149 / Fax: 662-325-2298
Teaching Assistants Jordan Goulder (Documentation)
Office: 302 Simrall
Office Hours: 2:00 PM to 5:00 PM TR (others by appt.)
Email: jwg10@msstate.edu
Phone: 662-325-8111

Balaji Venkatesan (Laboratory)
Office: 302 Simrall
Office Hours: 2:00 PM to 5:00 PM TR (others by appt.)
Email: bv20@ece.msstate.edu
Phone: 662-325-8111
Class Alias ece_4532@cavs.msstate.edu
URL http://www.cavs.msstate.ed./publications/courses/ece_4532
Textbook Resources D.C. Hanselman and B.L. Littlefield, Mastering MATLAB: A Comprehensive Tutorial and Reference, 1/e,, Prentice-Hall, 1996, pp. 542, ISBN: 0-13-191594-0.

P. Horowitz and W. Hill, The Art of Electronics, 2nd Edition, Cambridge University Press, 1994, ISBN: 0-521-37095-7.

R. Schinzinger and M.W. Martin, Introduction to Engineering Ethics, McGraw-Hill, 2000, ISBN 0-07-233959-4.

K.A. Smith, Project Management and Teamwork, McGraw-Hill, 2000, ISBN 0-07-12296-2.

G. Voland, Engineering By Design, Addison-Wesley, 1999, ISBN 0-20-14985-10.
Prerequisite CS 3324 and Grade of C or better in ECE 4743, and consent of instructor.

You must also be a member of a team that has a project registered in the Project Proposal database.

Grading Policies:

Grades are calculated using the following weights:

Standard:
  Weekly Deliverables 25%
  Design Document 15%
  Preliminary Design Review 15%
  Design Review 15%
  Hardware Prototype 10%
  Advisor Evaluation 10%
  Web Site 5%
  Peer Review 5%

Letter grades will be assigned according to the following distribution:

A
100 - 90
B
89 - 80
C
79 - 70
D
69 - 60
See you next semester
Below 60
Description:

The goal of our two semester sequence is to provide you with a realistic design experience, and teach you the tools and methodologies that can help you be successful at this endeavor. Demonstration of a fully functional prototype is requirement. Receiving a passing grade is not a guarantee that you will be allowed to proceed to Senior Design II. You must first demonstrate a fully functional prototype to your advisor and the course instructor. In the event that your prototype doesn't work at the end of the semester, you should plan on making up the work over the semester break. Without this approval, you will not be allowed to enroll in the second semester of this course.

In order that each team member be motivated to participate fully in the team, teams are allowed to vote members out of the group (we were inspired by the television series "Survivor") at the end of semester. For the member voted out, this might mean you have to retake this course, so you need to work to avoid this at all costs. Communication amongst team members and the project advisor about expectations and performance is essential. Far too often, students voted out complain that no one in the group appreciated how much work they really did.

To be considered for a passing grade in this portion of the class, your design review must convince the committee this project is ready for the fabrication stage (the following course in the two-course sequence). You also must convince the committee that you have done a sufficient amount of simulation and prototyping of your system, and that all critical design questions have been answered.

We now use a popular project planning tool, Microsoft Project, in this course. This will help you plan your projects on a daily basis. Every Friday evening, you will be responsible for making a deliverable available on your web site. There will be approximately 15 deliverables over the course of the semester, each worth 1% to 2% of your grade. These will be described in detail in class and via email. A schedule is provided below. Team leaders will be responsible for managing the project document. This will be explained in more detail in class. The weekly MS project assignments, and related documentation assignments, now comprise the single largest component of your final grade.

The design document is a comprehensive description of the entire project including: requirements, test specification, design, and test certification. It presents both simulation data and hardware measurements (for the packaged version of the hardware!), demonstrating that your design has met its goals. This document should address most of the points listed on the cover page of the course web site. Templates for this document are available on-line.

A large component of your grade is derived from your advisor's evaluation of role on the team, and your peer review. Remember the prime directive: "Keep your advisor happy." The rationale your advisor uses to arrive at your grade is at his or her discretion. Be sure to communicate with your advisor to fully understand his or her expectations.

The preliminary design review should be a dry-run of the final presentation. It is a 15-minute presentation by one team member that reviews project. At this presentation, any deficiencies that are documented must be rectified in your final design review. At this stage of the course, you will be expected to show solid design constraints, a preliminary design, and a comprehensive simulation and testing plan.

The design review is the big enchilada. You must address all design deficiencies noted in your preliminary review, and review all aspects of the project (with technical details supporting your claims). This will be a 15-minute presentation. At the time of the design review, a project web site must be available containing all information about the project, including the documents described above and the design review presentation.

Concurrent with the design review, we will host a conference-style prototype hardware demonstration. This will be set up in a room adjacent to the presentations, and consist of a conference booth type format where each team is allocated a table at which they will demonstrate their hardware. Each team will be responsible for constructing a poster providing an overview of the project. Faculty, student, and industrial representatives will visit each project and provide a detailed evaluation of the hardware. This portion of the final design review will last about two hours and run concurrently with the design presentations.

The project web site will be graded according to its comprehensiveness. A good site will contain a complete archive of the project, including all documents, presentations, data, measurements, schematics in source file format, software, etc. Web sites are graded on a competitive basis so keep an eye on your competition.

We will attend four entrepreneurship lectures this semester in coordination with GE 3011. Developing an appreciation of global issues in engineering is very important at this stage in your career. The entrepreneurship lectures are one means by which we encourage you to start thinking about important non-technical aspects of your career.

Your course grade will be computed using the categories and weights described above. Final grades can be adjusted by 5% (one letter grade) based on feedback collected from a peer review process. The method of application of this input is rather complicated, and arrived at using a "raise-pool" format (based on the way salary raises work in industry). Each member of the team is allowed to influence each other team member's grade by 5%. To raise one grade by an amount delta, you must reduce another team member's contribution by an equivalent amount. The sum of your adjustments must equal zero. If all team members receive the same rating, their grades remain unchanged. To increase one member's grade by the maximum of 5%, you must lower all other members grades by an equivalent amount. Feedback from each student will be collected and averaged, so the actual contribution per team member is 5/N where N is the number of members in your group. If each team member tries to assign all the credit to themselves, the net result will be that no one receives extra credit. To arrive at these evaluations, team members will submit a written evaluation of their fellow team members. All claims of mutiny, insurgency, poor performance, etc., must be documented in sufficient detail to be given consideration.

Schedule:

Please note that the dates below are fixed since they have been arranged to optimize a number of constraints. You need to adjust your schedules, including job interviews and site visits, accordingly.

Class
Date
Time
   Topic(s)
1
08/21
3:30 - 4:50 PM
   Organization and Introductions
2
08/28
3:30 - 4:50 PM
   The Design Cycle / Design Document Overview
3
09/04
3:30 - 4:50 PM
   MS Project
4
09/11
3:30 - 4:50 PM
   Software Engineering
5
09/16
2:00 - 3:15 PM
   Entrepreneurship Lecture No. 1
6
09/25
2:00 - 4:50 PM
   Project Meetings
7
09/30
2:00 - 3:15 PM
  Entrepreneurship Lecture No. 2
8
10/9
3:30 - 4:50 PM
   Laboratory Skills Lecture
9
10/14 - 10/16
2:00 - 4:50 PM
   Preliminary Design Review
10
10/23
3:30 - 4:50 PM
   Teamwork
11
10/28
2:00 - 3:15 PM
   Entrepreneurship Lecture No. 3
12
11/06
3:30 - 4:50 PM
   Lecture - TBD
13
11/11
2:00 - 3:15 PM
   Entrepreneurship Lecture No. 4
14
11/20
2:00 - 4:50 PM
   Project Meetings
15
12/02 - 12/04
2:00 - 4:50 PM
   Design Reviews


Deliverables:

Presentations and hardware demonstrations are due at times shown above. The weekly deliverables will be due at the times shown in your Microsoft Project documents. All other deliverables, such as the final design document, the web site, peer reviews, etc., are due on 12/04. The course instruction team will download these documents from the web site at this time and grade them.

Assignment
Due Date
 Item(s)
1
08/22
 proposal database entry
2
08/29
 proposal database entry;
preliminary web site;
product specification.
3
09/05
 revised proposal database entry;
revised product specification.
4
09/12
 MS Project document;
problem statement.
5
09/19
 MS Project document (update);
design constraints;
software interface design (physical model).
6
09/26
 MS Project document (update);
software interface design (use cases).
7
10/03
 MS Project document (update);
revised design constraints;
mid-term presentation review.
8
10/10
 MS Project document (update).
9
10/17
 MS Project document (update);
test specifications;
information model.
10
10/24
 MS Project document (update);
software process model.
11
10/31
 MS Project document (update);
revised test specifications.
12
11/07
 MS Project document (update);
executive summary.
13
11/14
 MS Project document (update);
revised Executive Summary.
14
11/21
 MS Project document (update);
design document checkpoint.


Miscellaneous:

Here are a few miscellaneous items that need your attention: