Sonoma
State University 
Department of
Engineering Science
ES 492- Senior Design
Project I - Fall 2010
ES 493 - Senior Design
Project II - Fall 2010 / Spring 2011
Last updated: September 3, 2015
|
Requirements |
|||||
|
Sign up with IGNITESSU |
|||||
| Previouse Projects: Spring 2009 / Fall 2010 / | Final Report Template | ||||
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 exploring 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.
The Senior Design Project (Capstone) is a two semester course with the following objectives:
First Semester: Understanding principles of engineering design process, completing small group projects, formulating problem statement, analyzing requirements, delivering high-level design block diagram, and bill of materials.
Second Semester: Continuing the work in the first semester, implementing, 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 curriculum.
4.
Take a systems approach to
problem solving.
5. Work productively in a team environment.
6.
Effectively
communicate technical ideas and concepts.
7.
Learn about project
management, timely delivery, and customer relationship.
8.
Understand the
environmental and social impacts of the design.
Through completing the senior design project, students
must demonstrate solid understanding of the following technical topics:
Wireless communications, LabVIEW and MatLAB, microprocessors, sensors and transducer, networking
and data communications, digital and analog communication, C/Java programming,
etc.
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 easily handled, and useable by external
clients. Hence, all projects must be accompanied in a (software or hardware) package ready for the client to use.
4-
Content: The project
must demonstrate substantial study in at least three of the following topics:
digital design and microelectronics, microprocessors, digital/analog
communications, networking.
5-
Community
needs: All projects must meet actual community needs (building a
rocket that hits the flying target is not acceptable unless its clear benefit
to the community is demonstrated). Community may be defined on a local, state,
national, or global level (to this end, projects must agree with Center for Community Engagement
guidelines.)
6-
Funding: All teams are
required to submit a Research Grant
Proposal and request for funding for their project. The proposal is due
October. Please note that, as of now, no substantial funding is available for
senior design projects. Thus, all students are highly encouraged to seek
funding from the client.
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 must rotate amongst the team members. The project manager is
decided by the team and advisor.
Responsibilities of the project manager include:
1. functioning as liaison between the team and the advisor;
2.
insuring that deadlines are
met ;
3.
insuring that the team is
prepared for the weekly advisor meetings ;
4. being responsible for assembling weekly team report.
In
addition, the team leader is responsible for
logistics and confirmations associated with weekly team meetings, weekly
advisor meetings, deliverables, and Demo Day. This includes room and
presentation equipment reservations. Furthermore, the project leader must
ensure that all meeting minutes are posted online in a timely manner.
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.
Please note that all final projects, engineering notebooks, and
ideas developed throughout the project are considered to be intellectual
properties of
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/Blogs
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 Capstone 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-
ll 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.
Each team must complete and submit the TME at the end of each month. The forms must be returned to the instructor. The team leader is responsible for collection of the evaluation forms.
NOTES:
- Individual students who failed to complete their portion of the project could not register for the Second Semester or receive final grade for Senior Design Project.
- Teams that failed to complete their project as expected will receive Incomplete grade and are expected to complete the project in Summer.
- Teams with working prototypes but incomplete documentations will receive Incomplete grade and are expected to complete the project in Summer.
Grading policy ES492:
|
Class Assignments |
30% |
|
Individual progress (*) |
35% |
|
Preliminary Design Review (PDR)- Team effort / End of the semester |
30% |
|
Team Member Evaluation (TME) - monthly |
5% |
|
Any unexcused absence (**) |
-4% |
Grading policy ES493:
|
Individual progress (*) |
35% |
|
Midterm Design Review (PDR)-Team effort |
25% |
| Final Design Review (PDR)-Team effort | 30% |
|
Team Member Evaluation (TME)-monthly |
10% |
|
Any unexcused absence (**) |
-4% |
(*) You will receive maximum of 3-10% for your progress in each individual meeting - individual progress will be determined based on amount of individual work recorded in the Engineering Notebook. Note: If a certain student does not complete his/her assigned task (for any reason) he/she will receive an Incomplete grade.
(**) Missing more than 15 minutes of any class/meeting results in an unexcused absence - please don`t be late!
Suggested Texts:
- Practical Engineering Design by Maja Bystrom, Bruce Eisenstein - Slides
- 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:
1. Project Web Site
2.
Problem Statement and
Problem Solution
3.
Project Schedule
(Gantt Chart PS)
4.
Requirement
Specifications
5.
Project Budget and
Economic Analysis (include it in PS)
6.
System Block Diagram
7. Preliminary Design Review (PDR)
8.
Bill of materials
(BOM)
- Environmental and Social Impact Assessment
10.
Simulation Results
11. Mid-Term Design Review (MDR)
12.
User Document (DR) **
13. Test Plan (include simulation results)
14.
Comprehensive Design Review (CDR) **
15.
Poster **
16.
Public Demo **
17.
Final Product **
[**
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 is to schedule the 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 and maintaining all the required forms.
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.
Please note that all projects must be subject to prior approval of at least one faculty in the department of Engineering Science. In addition, approved projects MUST have a supporting customer, who MUST be present at during the presentations.
Here is the link to other projects:
Previous
Projects
1- Presentations: Please note that the MDR or CDR must be presented ONE WEEK prior to final exam day. Teams will receive incomplete grade if they fail to do so.
2- Documentations: In addition, all documentations related to MDR or CDR must be prepared and distributed to other faculty members 10 DAY prior to the meeting. Teams will not be allowed to have their MDR or CDR presentation without complete documentations.
3- Participation: Each team must ensure that the following individuals are present during the MDR or CDR. Failure to do so results in receiving and Incomplete grade.
Forms:
The following templates and forms are available for students.
| Document | Description |
| Examination
of Problem Statement
|
Rubrics
to grade individual documents
|
| Faculty
Advisor Approvals Form
|
Must be completed for receiving final grade for each semester |
| Faculty Advisor Survey | |
| Faculty
Advisor Meeting Log Sheet
|
Must
be completed by the faculty for each student after the Advisor Meeting
|
| Part
Request Form
|
List
of materials required by the teach to be purchased
|
| Equipment
Request Form
|
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
|
| Project
Proposal Evaluation
|
|
| Bill of material request | form |
Schedule:
(University
Calendar)
|
Wk
|
Date
|
Topic/Unit
|
|
|
1
|
Aug.27
|
Welcome / Introduction
|
|
|
2
|
Sep. 3 |
Lecture-1:
Engineering Process / Clean the lab!/ Organize magazines/
|
Join the Capstone Discussion Group -Read NASA Projects / Write about two possible projects - submit by Thursday 11am. |
|
3
|
Sep.10
|
- Lecture 1b - Selecting Project -Lecture 2: Project Requirements /Project Examples / What is a good project? |
- Assignment 1: Signup with the discussion group.
- Send me your email to me!
- Must have your
Notebook ready
|
|
4
|
Sep.17
|
- Lecture 3- Engineering Specifications - Student Presentation Based on Assignment
2: Individual projects
|
Submit Assignment 2: Read the slides / Apply for Undergraduate Research Project
|
|
5
|
Sep.21
|
-Other
faculties will present their projects
- Student Presentation - Engineering Requirements (Homework) |
|
|
6
|
Sep.24
|
-Other faculties will present their projects |
|
|
7
|
Oct.1
|
-Green Design -Individual meeting
/ have your notebook ready!
|
|
|
8
|
Oct.8
|
Team project presentation / Team Introduction / client? / How is it Green? / What are the challenges? / Update web
Oct 13, 3:30pm - 5:30pm, Schulz
3001 |
- Select team`s Project Leader\
- Decide on your project (&&) / Form your
team. / Who is your advisor? Faculty
Advisor Meeting Log Sheet |
|
9
|
Oct.15
|
Lecture / Review Problem Statement and Requirements / /Visit the workshop/ Don't be late!
Oct 20, 3:30pm - 5:30pm, Schulz
3001 |
- Assignment 3 - is Due
- Submit your
Webpage link / http://delicious.com/ (Note 4) / YouTube / SlideShare ;
Example of a
good SDP webpage
|
|
10
|
Oct.22
|
Team Presentation / Submit
Project Statement and Engineering Requirements and possible
solution ideas (example)/ What are you going to test?
Lecture: Project Management and Gantt Chart Do the homework (example of Project Schedule) |
- This is the abstract for your project.
- Submit the first draft from Engineering
Requirements
- Submit the first draft of Marketing Requirements;
include all your questions from the client
|
|
11
|
Oct.29
|
Lecture/ Individual meeting
/ have your notebook ready!
|
- 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
|
|
12
|
Nov.5
|
Teams presenting test results/ simulations study. Presentation techniques: Link to video on YouTub |
HW2: Submit Project cost assignment
|
|
13
|
Nov.12
|
Lecture on Teamwork - Do the class assignment
Read about how to Present Effectively
|
- Presentation: December 10 @12-2 pm - Register your project
- Read about PDR_Presentation
Guideline
- All slides must be submitted at least 5 days in advance! |
|
14
|
Nov.19
|
24 and 26
Thanksgiving holiday for Students / No classes; University closed 25th 26th
|
|
|
15
|
Nov.26
|
Lecture on Testing - Do the assignment
|
- Submit list of materials / budget - Design Overview
|
|
16
|
Dec.3
|
|
Testing Assignment is due. Final Draft of presentation slides must be ready! |
|
(*) Here are just some ideas to think about
Advanced
Research Projects and some more
ideas
MS Project Management
Acceptable Projects:
-
Smart Patient Monitoring System
-
Smart Electric
Bike
-
Car-to-car Delay
Tolerant Communication
|
|||
|
Note 1 : Each week teams
are required to submit/post a progress report.
Note 2 : If there is any
change in team member's role the advisor must be notified.
Note 3 : All documents must be posted on the web page
Note 4 : All references must be accompanied with a
summer |
|||
|
ES 493 - Senior Design Project II
|
|||
|
|
|
- Meeting with Individual Members
|
Submit bill of materials (BOM)-
Example of BOM / Include costs / All requested items must be
individually justified.
Fill out the part request
form.
|
|
|
|
Presentation Review
|
Submit first draft of the PDR to all faculty
members
Fill out Equipment
Request Form for your
project
|
|
|
|
PRESENTATION / Register your project
|
Final Presentation is due
Must receive approval of faculty members.
|
|
|
|
Project update
Meeting with Individual Members
|
Final corrections must be submitted
|
|
|
|
|
|