SYLLABUS
Contact Information:

Lecture Time	T: 12:30 - 1:50 PM
Lecture Place	GL L024
Laboratory	Anderson Hall 104 (see your department's lab manager)
Lecturer	Joseph Picone, Professor
Lecturer Office	EA 712
Lecturer Office Hours	TR: 11:00 - 12:30 AM (also available as needed at other times)
Lecturer Phone	215-214-4841
Lecturer Email	picone@temple.edu
Class Alias	engr_sd_2012s@listserv.temple.edu
URL	http://www.isip.piconepress.edu/publications/courses/temple/engr_4196
Facebook	Temple Engineering - Senior Design
Textbook	None
Prerequisites	ENGR 4169: Engineering Seminar   You must also be a member of a team   and project that has been approved   by the course coodinators.

Grading Policies:

Item	Weight
Weekly Deliverables	50%
Design Document	10%
Web Site	10%
Preliminary Design Review	10%
Design Review	10%
Advisor/Coordinator Evaluation	10%
Extra Credit: Hardware Prototype	10%
Lab Penalty: Failure To Clean The Lab	-10%

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 that your project can be successfully constructed to meet your design constraints is an important requirement to complete this course. Receiving a passing grade is not a guarantee that you will be allowed to proceed to Senior Design Project II. You must first demonstrate feasibility to your advisor and the course instructor. In the event that you do not meet this requirement, 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.

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 eventually hardware measurements (for the final system), demonstrating that your project 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.

Technical writing is a very important part of the overall course goals in senior design. Because you are supplied with a detailed Microsoft Word template for the design document, grading of the design document will be strict. Documents will first be graded based on their technical content. Next, for each infraction of the formatting guidelines, you will have one letter grade deducted from the overall grade for your document. A failing grade on the design document will be counted more heavily - a team cannot receive a grade higher than a C in this course if they fail the design document component of the course.

Each design document will be checked for plagiarism. Even one instance of plagiarism will result in a grade of 0 for the design document. Review your technical writing course (ENGR 2196 or the equivalent) for a comprehensive discussion of plagiarism and how to avoid it.

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.

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.

Another significant component of your grade is derived from your advisor's and course coordinator's evaluation of your role on the team. Remember the prime directive: "Keep your advisor happy." The rationale your advisor and course coordinator use to arrive at your grade is at his or her discretion. Be sure to communicate with your advisor and course coordinator to fully understand his or her expectations.

If you have concerns about a team member's performance, you need to document this and involve the course coordinator from the beginning. For example, if a member repeatedly misses weekly meetings, document that in the meeting logs. If a member is not completing assignments in a timely fashion, document it. It is your obligation to bring personnel issues to the attention of your management.

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.

Your course grade will be computed using the categories and weights described above. Final grades can be adjusted by 5% (one-half 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). This will be explained in greater detail at the end of the semester.

Since demonstrating proof of concept is important, we are offering you a chance to earn extra credit by creating a hardware prototype in the first semester. This will help guarantee you a successful build phase in the second semester. This is an optional step. Teams electing to do this must demonstrate a working prototype by the last regularly scheduled class. The maximum credit that can be earned will be 25%; partial credit will be awarded based on the degree of completion.

Schedule:

Senior Design Project I will meet as a class every Tuesday for one hour. The lecture topics are shown below. Every Thursday, with no exceptions, teams are expected to meet as a team. Every team member must be available at this time. Course coordinators will also be available.

Class	Date	Topic(s)
1	01/17	Organization and Document Templates
2	01/24	The Design Cycle, the Problem Statement, and Design Constraints
3	01/31	Problem Decomposition (3a) and Work Breakdown Structure (3b, 3c, 3d)
4	02/07	Technical Presentations and PowerPoint Tips
5	02/14	Approach
6	02/21	Standards and Testing
7	03/01	Preliminary Design Reviews
8	03/13	Cost and Schedule
9	03/20	Executive Summary
10	03/27	Product Specifications
11	04/03	Teamwork
12	04/12	Design Reviews
13	04/17	Design Review Post-Mortem
14	04/24	What's Next?

Please note that the dates above 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.

Deliverables:

All deliverables will be posted to the project web site by 8 AM on the day indicated below. The course instruction team will download these documents from the web site at this time and grade them.

HW	Due Date	Item(s)
1	01/17	Web Site
2	01/24	Project Report Cover Page     Project Title     Project Abstract     Baseline Project Schedule
3	01/31	Problem Statement     Meeting Logs Checkpoint
4	02/07	Design Constraints     Design Constraints Narrative
5	02/14	Project Schedule Checkpoint     Meeting Logs Checkpoint
6	02/21	System Block Diagram
N/A	02/28	Preliminary Design Review
7	03/13	Approach
8	03/20	Project Schedule Checkpoint     Meeting Logs Checkpoint
9	03/27	Test Specifications
10	04/03	Executive Summary
N/A	04/12	Design Reviews
11	04/17	Product Specification
N/A	04/24	Design Document     Web Site