Sonoma State University
Department of
Engineering Science
ES 492- Senior Design
Project I - Fall 2009
ES 493 - Senior Design
Project II - Fall 2009
Check for updates - Last updated: 09/28/2009
|
Deliverables |
Meetings |
||||
|
Requirements |
|||||
Description:
Capstone course calls on the professional skills of
the discipline; it draws on the core disciplines of the students`
major field of study, as well as explore necessary topics such as scheduling,
organization, budgeting,, prototyping, develop teamwork, customer liaison
skills, employ creativity in proposing new solutions, and so forth. Hence, by
the end of the capstone process students are expected to have a good
understanding about various design phases, including analysis phase, a design
phase, a validation phase and a production phase.
Second Semester: Continuing the work in the first semester, refining, testing, and demonstrating the final product. Final prototype must be shown to meet initial specifications. Prerequisite: ES 592.
Objectives:
After successfully completing this course, a student should be
able to:
1.
Apply engineering design
principles to formulate problem statement, analyze requirements and produce a
system-level block diagram.
2.
Prototype an electronic
and/or software system to meet given specifications.
3.
Integrate knowledge from
across the core CS or EE curriculum.
4.
Take a systems approach to
problem solving.
5. Work productively in a team environment.
6.
Effectively
communicate technical ideas and concepts.
7.
Understand the
environmental and social impacts of the design.
Project Requirements:
Completing
the capstone project will require spending significant time and resources.
Hence, all students are highly encouraged to find a project topic that is
interesting to them. However, I highly encourage students to be open minded and
consider the case that many projects, although initially don`t seem to be
attractive and appealing, may turn out to be very interesting.
Although,
individual students are allowed to find their own project, all capstone
projects must meet the following criteria:
1-
Customer driven: In general, sources of projects
are preferred to be Industry sponsored (Real-world problem from local industry
or Support provided for materials and other expenses), Faculty Research based
(Projects funded by research grants) or Competition based (examples are ASME
Human Powered Vehicle, SAE Mini Baja, ASME annual
design competition). In either case, all capstone projects must have an external client (customer).
That is, projects cannot be proposed by participating students (exceptions will
be made in special circumstances). Therefore, students working in a company are
strongly recommended to talk to their co-workers and find a sponsor (customer)
at work. All students are expected to produce
industry-standard deliverables throughout the two-semester course. All project
sponsors (clients) must complete the sponsorship sheet and sign it in order for the
project to be officially considered as a capstone project.
2-
Team oriented: All projects
must be done in teams of 2-3 students (exceptions will be made in special circumstances).
You are highly encouraged to find students from other disciplines to assist you
in the project. Sometimes, these students can actually receive credit toward
their major in forms of Independent Study or Research Project. I strongly
encourage you to consider teaming us with students majoring in Arts.
Environmental Sciences, Computer Science, Biology and/or Physics.
3-
User friendly:
All final projects must be operational and
easily useable by external clients. Hence, all projects must be accompanied in
a (software or hardware) package ready for the client to use.
Please note that all final projects, engineering notebooks, and ideas developed
throughout the project are considered to be intellectual properties of
or used commercially without its written
permission.
Project Leader/Management:
In order to facilitate team organization and communication, each
team will have one member who is designated as the project manager. This
position can be permanent or rotate amongst the team members. The project
manager is decided by the team and advisor.
Responsibilities of the project manager include:
-
functioning as liaison between the team and the advisor;
-
insuring that deadlines are met
-
insuring that the team is prepared for the weekly advisor meetings
-
being responsible for assembling weekly team report.
In addition, the team leader is
responsible responsible for logistics and confirmations associated with weekly
team meetings, weekly advisor meetings, deliverables, and Demo Day. This
includes room and presentation equipment reservations. In addition, the project
leader must ensure that all meeting minutes are posted online in a timely
manner.
It should be noted that other
team members will have areas of responsibility defined as the project moves
forward. The role of project manager is clearly defined early in the process
due to the general logistical nature of the role. The project manager offers
general support of the design effort while the other roles will be tailored to
project-specific needs.
Notebook:
Engineering laboratory notebooks
are legal documents that can be used in court to prove ownership of a design.
You are to keep notes in a bound notebook (one for each team member). Before
using the notebook, number all the pages. This book is to be taken with you to
your meetings with your advisor. It will be used to monitor your progress and
demonstrate to your advisor the ownership of your design. No electronic
notebook is acceptable.
Weekly Team Meetings:
Weekly team meetings are for the team members to meet with each other. This can be either before or after the weekly advisor meetings. You are encouraged to meet before the meeting with your advisor in order to be prepared to make the best use of the time.
Weekly/Biweekly Advisor Meetings:
Each project team will have a
weekly team meeting with their project advisor. The purpose of each meeting is
to have each team member report on progress that has been made, barriers that
have been identified and clarification of short- and long-term goals. It is the
project manager`s responsibility to set up these meetings with the project
advisor. All members must participate in these meetings and be prepared to
elaborate on their activities. All weekly Advisor Meeting minutes must be typed
and posted online.
Web Page
It is mandatory for each
team to create a web page dedicated to the Senior Design Project. Contents of
this page must be saved on a CD and submitted along with the final
deliverables. Your project documents can be shared in sites such as
SlideShare
. The web site must include the following components:
1- Summary of the requirements and project.
2- Name of the client.
3- Team members, each member`s background and role in the project. Link to personal web page of each member must be included.
4- Each project must have a discussion group and members are expected to communicate with one another through the discussion group.
5- All projects must have a YouTube link describing how the project operates.
6- All the links and references must be saved on a http://delicious.com/ link. For each link, a short description must be provided.
7-
Summary of all meeting minutes must be posted on the
web site.
Grading:
Team members will be graded
individually by their project advisors. After the Mid-course Design Review, the
Design Review Board will recommend semester grades for each team member based
on the report and oral presentation. The project advisors will take this
feedback into account when assigning the semester grade.
The team members may receive different letter grades. Your performance on your portion of the project, contributions towards progress reports and your participation level in the weekly meetings will impact your final grade. The importance of each member`s preparedness and participation in the weekly meetings is crucial to the success of the projects. Please note that teams/individuals which did not complete the first semester requirements satisfactorily will not be allowed to take the second semester of the Senior Design Project course.
Grading policy: 
| Class Assignments | 20% |
| Individual progress (*) | 30% |
| Preliminary Design Review (PDR) - Team effort | 20% |
| Mid-course Design Review (MDR) - Team effort | 30% |
| Any unexcused absence (Mondays or Fridays)(**) | -2% |
(*) You will receive maximum of 3% for your progress in each individual meeting - individual progress will be determined based on amount of individual work recorded in the Engineering Notebook.
(**) Missing more than 15 minutes of any class/meeting results in an unexcused absence - please don`t be late!
Suggested Text:
-
Practical Engineering Design by Maja Bystrom, Bruce Eisenstein
-
J. E. Salt and R. Rothery, Design for Electrical and Computer Engineers, Wiley, 2002, ISBN 0-471-39146-8
Course Deliverables:
In addition to the weekly team
meetings and advisor meetings, the schedule includes all-course meetings and
deliverables:
-
Project Web Site
-
Problem Statement and Problem Solution
-
Project Schedule (Gantt Chart PS)
-
Requirement Specifications
-
Project Budget and Economic Analysis (include it in PS)
-
System Block Diagram
-
Preliminary Design Review (PDR)
-
Bill of materials (BOM)
-
Environmental and Social Impact Assessment
-
Simulation Results
-
Mid-Term Design Review (MDR)
-
User Document (DR) **
-
Test Plan (include simulation results)
-
Comprehensive Design Review (CDR) **
-
Poster **
-
Public Demo **
-
Final Product **
[** document
must be submitted the second semester. ]
The contents of the Preliminary
Design Review (PDR), Mid-Term Design Review (MDR) and Comprehensive Design Review
(CDR), will be as follow (refer to the provided Sample Report for details):
A-
Title page
B-
Executive Summary
C-
Abstract
D-
Table of Contents
E-
List of Figures
F-
List of Tables
G-
List of Abbreviations
H-
Introduction
I-
Body
a.
Problem statement
b.
Literature review/ existing
patents
c.
Design approach
d.
Economic analysis
e.
Timeline or Gantt
chart
f.
Social and
environmental impact
g.
Future work
J-
Summary
K-
Glossary
L-
Reference (Note a)
M-
Appendices
a.
Detail budgets
b.
Test
plan/procedures/results including simulations
c.
System block diagram
d.
Circuit diagrams
e.
Flowcharts
f.
In-depth description
of technology and components used it the project
g.
Bill of materials
h.
Program codes
i.
Images of the final
product
j.
Screen shots of the
software interface
Details of the deliverables are described in the section below.
[Note (a) Do not use online
references unless it belongs to a recognized organization or standard body]
Problem Statement Assignment
You are asked to prepare a
statement of work for the project you have chosen. It is to be a team effort
(one report per team). You are encouraged to work closely with your advisor on
this assignment, but remember that you, not your advisor, are responsible for
it. The page limit for this assignment is 4-6 pages.
Requirement Specification Assignment
You are asked to prepare a requirement specification for the project you have chosen. It is to be a team effort (one report per team). You are encouraged to work closely with your advisor on this assignment. The page limit for this assignment is 7-10 pages.
Proposed Schedule
(Gantt Chart)
Each project is required to
have a Project Schedule. A good scheduling allows the best result through the
most effective use of all resources. Learning the project process and using the
appropriate tools for scheduling can save considerable time and improve the
final design project. All students are recommended to use MS Project Management
software to complete the schedule.
Once the project schedule
is defined, it is the team`s responsibility to ensure all deadlines are met.
Schedules are evaluated at each Advisor Meeting.
Project Cost
Each project is required to
have a preliminary projected cost. Such economic analysis allows designers to
have a better understanding as to how much time they will be expected to devote
to the project and how much money is required to spend on the project. The cost
analysis allows designers to have a more realities view of their design before
they get too involved in building it. You are encouraged to work closely with
your advisor on this assignment, but remember that you, not your advisor, are
responsible for it. This document must clearly identify the source of funding
for the project. The cost of the following must be itemized in your budget:
1- Engineering development
cost
2- Production cost
3- Labor cost
4- External services cost.
Students are highly
recommended to your MS Project Management Software (a good tutorial is
available HERE).
Social and Environmental Impact Report (SEIR)
All teams are required to
complete and present EIP prior to implementing the design. This document must
discuss possible environmental hazards of the design while operating and when
it is disposed in landfills. The report must specify all specific measurements
and steps which were taken to make the design more environmentally friendly,
such modular design, recyclables of the product, upgradeability, usage of
hazardous materials such as Coltan, mercury, lead,
etc.
In addition, this document must clearly identify possible unintentional and negative social impacts. For example, what are the possible unconventional application of the design which can result in harmful ways.
System Block Diagram Assignment
The team is to prepare a
block diagram of a system that will meet the specifications in the requirement
specifications. A general description of how the system works and a plan for
the system analysis must accompany the block diagram. (Note: Only a plan for
how the system will be analyzed is required.) The analysis plan will point out
things like:
1. The system will be
modeled mathematically and analyzed using transform theory.
2. The system is very
non-linear and cannot be linearized over the region
of operation therefore the system must be analyzed through computer simulation.
3. The key to the system
lies in the performance of a particular block and it is essential that this
block is built and its performance measured as part of the system analysis.
The analysis plan should
also contain estimates of how long it will take to complete the analysis. You
are encouraged to work closely with your advisor. The grading guide for this
assignment is attached. The page limit for this assignment is 4-6 pages.
Preliminary Design Review (PDR)
The twofold purpose of the PDR
is for the team to present their preliminary design and receive feedback from
the Faculty Review Board on that design. At the PDR, each team will deliver a
written report presentation to the Faculty Review Board and team advisor. Each
team member will participate in the preparation of the report as well as the
preparation and delivery of the PowerPoint presentation. The report and
presentation will include problem statement, requirement specifications,
system-level block diagram and project specifications, as well as the team`s proposed MDR prototype specifications. The advisor and Faculty Review Board will modify
the proposed MDR prototype specifications at the PDR. The MDR prototype
specifications should be substantial and complete enough to demonstrate that
the team has successfully tackled one or more of the core technical design
challenges of the overall project. The MDR prototype specifications will be
included in the team presentation to the class at an all-course meeting. The
MDR prototype specifications will be sent to the SDP course coordinators by the
project manager.
The project manager`s
responsibility to schedule their team`s PDR.
Mid-Course Design Review (MDR)
The Mid-course Design Review
(MDR) will take place before the Faculty Review Board and the team advisor near
the end of the first part of the Capstone course. The twofold purpose of the
MDR is for the team to present a prototype (and its associated design) and to
receive feedback from the Faculty Review Board and the team advisor on that
design. The hardware and/or software prototype presented should demonstrate
that the chosen design path is likely to lead to a completed project in April
which meets or exceeds the project specifications. The role of the Faculty
Review Board is to provide independent feedback to the advisors and team
members. The review board will consist of ES faculty members and will
participate in all MDRs.
Each team will turn in a written report and deliver a PowerPoint presentation at the MDR. Each team member will participate in the preparation of the report as well as the preparation and delivery of the PowerPoint presentation. The MDR report and presentation will include problem statement, requirement specifications, system-level block diagram, project specifications, and an explanation and demonstration of how the MDR specifications were met this semester. Board suggests grade to advisor
The project manager is responsible to schedule the specific MDR time for their team.
Test Result Document
(TRD)
The Test Result Document (TRD) includes all test results, design constraints, and operational limitations found during testing of the final product. This document also includes all the simulation results implemented for each system block. A comprehension comparison between the simulation and actual results must be presented and sufficient discussions must be accompanied.
Comprehensive Design Review (CDR):
CDR must be presented to
Faculty Review Board and Project Advisor. CDR includes poster presentation. The
CDR presentation focuses on a working demonstration of how the prototyped
software/hardware meets the project specifications. The board suggests grade to
advisor.
Forms:
The following templates and forms are available for students.
|
Document |
Description |
|
Examination
of Problem Statement |
Rubrics
to grade individual documents |
|
Must
be completed for receiving final grade for each semester |
|
|
|
|
|
Must
be completed by the faculty for each student after the Advisor Meeting |
|
|
Report Rubric |
Various
rubrics for grading |
|
List
of materials required by the teach to be purchased |
|
|
Equipment
required to be checked out by the team ; many equipments require receiving
certification fro the department |
|
|
Project
External Support Form |
|
|
Equipment
Usage Certification |
This
form is required if you are planning to check out any equipment or more any equipment
between rooms or buildings |
|
Poster
Guidelines |
|
|
|
|
|
|
|
Schedule:
(University Calendar)
|
# |
Week of |
Lecture |
Reading
Materials |
Assignment/Activity |
|
1 |
Aug. 26 |
-
Welcome/Syllabus |
|
-
Read the syllabus -
|
|
2 |
Aug. 31 |
|
|
|
|
3 |
Sep. 7 |
NO LECTURE |
|
- Complete HW1 - Make sure you get all your stuff out of 2007 |
|
4 |
Sep. 14 |
|
- - Submit HW2 - Select team`s Project Leader - |
|
|
5 |
Sep. 21 |
Lecture 3- Engineering Specification | - Visit the preserve |
- Assignment 3 - |
|
|
|
-
Project Proposal Review - |
-
Project Management with Microsoft
Project - Tutorial
-
|
-
-
|
|
6 |
Sep. 28 |
- Discuss your progress - Assign individual tasks - Members; Receive a Faculty Advisor Meeting Log Sheet - First Individual Meeting |
- Assignment 3 - |
|
|
|
|
-
Project Proposal Review
-
Project Scheduling and Cost
|
- Here are just some ideas to think about Advanced Research Projects
and some more
ideas
MS Project Management Acceptable Projects:
|
-
HW1: Project management assignment (due)
-
HW2: Project cost assignment
- |
|
7 |
Oct. 5 |
-
Design Documentation -
Review Team`s Project
|
|
- Submit project statement and possible solution ideas (example) - This is the abstract for your project. - Submit the first draft fro Engineering Requirements - Submit the first draft of Marketing Requirements; include all your questions from the client - Submit individual assignment for the next month and team leader until December; group confirmation is required. - |
| 8 | Oct. 12 | No Lecture | No Lecture |
- Field Survey; Test your wireless
- Complete a survey of 5 different wireless
technologies.
- Submit
- Review
Client Information Form
(Note 3)
- Research about the existing electrical
system
-
|
|
- Social and Environmental Impact /RoHS
|
|
|||
|
9 |
Oct. 19 |
-
Individual Members - Second Advisor Meeting |
|
- Report your wireless test results.
- Submit Client Information Form (Note 3) - Submit a Progress Report (Note 1) -
Submit project team member responsibility (Note 2) - Submit system block diagram ; First presentation |
|
10 |
Oct. 26 |
-
Third Advisor Meeting |
|
-
HW2: Submit Project cost assignment
|
|
11 |
Nov. 2 |
-
Meeting with Individual Members |
|
-
Submit simulation tools/results/needs/justifications
; Discussion
-
Submit an Environmental and Social Impact Assessment |
|
12 |
Nov. 9 |
-
|
|
-
Submit bill of materials (BOM)-
Example of BOM / Include costs / All requested items
must be individually justified.
-
Fill out the part request
form.
-
|
|
13 |
Nov. 16 |
-
Fourth Advisor Meeting
-
Meeting with Individual Members |
|
-
Submit first draft of the PDR to all faculty members
-
Fill out Equipment
Request Form for your project Submit your preliminary Test plan ; How are
you going to test the project? What are you going to test? |
|
0 |
Nov. 23 |
NO
CLASS |
NO CLASS |
-
NO CLASS |
|
15 |
Nov. 30 |
-
Meeting with Individual Members |
GLOBECOM Nov. 30 ; Dec. 4 |
-
Final Presentation is due - Must receive approval of faculty members. |
|
16 |
Dec. 7 |
-
|
|
|
|
17 |
|
-
Project update
-
Meeting with Individual Members |
|
|
|
18 |
|
- How to Present |
|
|
|
|
|
-
|
|
|