Capstone History at Wilkes
ABET and Capstone
Elements of the Capstone Design Project Report
Capstone Design Project Guidelines
Capstone Report Format
Oral Presentation Suggestions
Fall Semester Schedule
Spring Semester Schedule
Industrial Advisory Board
Create New Topic
Division of Engineering and Physics
SENIOR PROJECTS ME/EE/EGM - 391/392
Welcome to the Engineering Capstone Website
GENERAL INFORMATION: Required capstone course for all engineering majors
- COORDINATOR: Dr.David Carey
- CONTACT INFO: Phone: 408-4807.
- Email: firstname.lastname@example.org
- OFFICE HRS: Posted on Door. Appointment preferred, see me after class or email to set up.
- CLASS TIME: Tuesday 5:00-5:50pm, BREIS 106
CATALOG DESCRIPTION:: EE/ME/EGM 391/392. Senior Projects Design and development of selected projects in the fields of Electrical and Mechanical Engineering and Engineering Management under the direction of a staff member. Technical as well as economic factors will be considered in the design. A professional paper and detailed progress report are required.
Requirement: Senior standing in engineering.
NOTE: Senior standing means the student has completed ALL Freshman, Sophomore, and Junior level required engineering courses for their major.
The goal of the course is for students to learn the product development process and complete a significant electrical, mechanical hardware and software project. The specific learning objectives are:
- Students will be assigned a mechanical and/or electrical hardware projects. Many projects will have a software component. Teams of size four to six will be formed based on the level of effort required for the assigned project. The projects come from our faculty, staff, Industrial Advisory Board or students. Use the following link to submit project ideas Industrial Project Description Template.
- Student teams will follow a formal development process to complete their project.
- Students will complete requirements, specification and test plan.
- Students will implement their design.
- Students will test the resulting system.
- Students will produce a written final report, poster, and press release describing their project. A final oral presentation and project demonstration is also to be given.
- In the process of meeting the course requirements students will experience all phases of project development and thereby will gain an appreciation of the demands of those project phases.
The course meets once per week for 50 minutes for lecture, supervised group work, exam, or guest lecture.
The course will teach a standard product development process as part of the course. Figure 1 shows the steps of the process. A key step is a prototype demonstration which we insert between design and implementation. At the prototype demonstration, the students must have running code and/or working hardware. An agreement (in the form of a mini-contract) is made between the students and the instructor as to what will be shown at the prototype demonstration.
The first three weeks of the semester are used to learn the product development process and to learn how to achieve the course deliverables.
Design Process Flow Chart
The students are expected to dedicate 3 to 4 hours per week outside of the class for their project.
Grading is A through F and is based on successful completion of deliverables.
The project deliverables are staged through the two semesters. Each deliverable contributes to the student's class grade. The deliverables are:
The design review, final demonstration, and presentations puts together all previous documents in an updated form and includes a formal presentation, press release, and poster. If the company has specific deliverable items requirements they need to identify them in their project request.
- Requirements document (Semester #1, Week 6)
- Specification document (Semester #1, Week 12)
- Schematics (Due date determined by Advisor/Sponsor)
- Mechanical Drawings (Due date determined by Advisor/Sponsor)
- Software Description (Due date determined by Advisor/Sponsor)
- Preliminary Design Review and presentation, 12/12/2015, 0800 (Semester #1, Week 15)
- Prototype demonstration (Semester #2, Week 6)
- Test plan (Semester #2, Week 12)
- Final demonstration and presentation , 4/30/2016, 0800 (Semester #2, Week 15)
For each deliverable, the percentage of overall course grade and the date in which it is due are shown.
Semester #1 - EE/ME/EGM 391 Follow the link to Fall Semester Schedule.
- Requirements Document:
- (Semester #1, week #6) - Do you know what problem you are solving? Do you know what your customer wants? Can you describe to your customer, in your words, that you understand their need? You must clearly and crisply describe the project requirements. Requirements must be numbered so that they can be traced throughout the development project. Page limit is a minimum of 2 pages.
- Specification/Design Document:
- (Semester #1, week #12) Do you know how to solve the problem and meet your requirements? This document should clearly specify the solution and include a design. A design could be a high-level flowchart or a hardware block diagram. The document must include details on the methods what will be used to solve the problem. The reader must be convinced that you have a workable and feasible design. Page limit is 2 pages (but appendices are allowed).
- Practice Presentation:
- (Semester #1, week #14) This is a dry run of your presentation and demonstration. The Faculty Advisor needs to see your power point charts and how you will present them. Your presentation should not, in any case, exceed 30 minutes. Expect lots of feedback and budget time to rework your presentation power point charts for the design review presentation.
- Preliminary Design Review (PDR) Presentation and submission:
- (Semester #1, week #15) Your design review presentation a is given in a public forum at the University. You will deliver your preliminary design submission at this time. The date will be Saturday, December 12, 2015 at 0800, SLC-101 and SLC-166. You will deliver your design recommendation at this time. Your DR submission should contain all of the above documents, your presentation power point charts, your artifact, and any documentation that is required (e.g., user documentation if a software product, preliminary specifications if a hardware product). If the project is sponsored by industry, they should be invited to the presentation.
Semester #2 - EE/ME/EGM 392 Follow the link to Spring Semester Schedule
- Prototype Demonstration:
- (Semester #2, week #6) This is a major checkpoint. You must have something up and running. A prototype is something you can show your customer and ask;Is this what you wanted?; The customer must be able to see that all features are in place (but, perhaps not fully working). For software, a prototype would include all interfaces.
- Test Plan Document:
- (Semester #2, week #12) How do you know you met the requirements (validation)? How do you know that you implemented your specification and design correctly (verification)? Describe your test cases for validation and verification. A test case must include requirement or specification number that is covered, procedure to execute, and expected results. Good test cases should cover expected and unexpected inputs. No page limit, but should be short.
- Capstone Report Format
- Practice Presentation:
- (Semester #2, week #14) This is a dry run of your presentation and demonstration. The Faculty Advisor needs to see your power point charts and how you will present them. Your presentation should not, in any case, exceed 30 minutes. Expect lots of feedback and budget time to rework your presentation power point charts for the design review presentation.
- Final Presentation, demonstration, and submission:
- (Semester #2, week #15) Your final presentation and demonstration is given to your company supporter in a public forum at the University. You will deliver your final design submission at this time. The date will be Saturday, April 30, 2016 at 0800, location SLC-101. Your final submission should contain revised versions of all of the above documents, your presentation power point charts , your artifact, and any final documentation that is required (e.g., user documentation if a software product, complete specifications if a hardware product). Your final submission also includes a poster and a press release. If the project is sponsored by industry, they should be invited to the presentation. Family and friends are also invited to this presentation.
- Poster; The poster is a self-explaining presentation of your project. The poster will be displayed around campus for at least two semesters. The organization of a poster will be discussed in lecture.
- Press release; The press release is a one-page project description suitable for the ≥general public;. Unlike the other deliverables, the press release may be somewhat self-promoting. The writing of a press release will be discussed in lecture.
||Complexity of the Problem
||Chapter 1: Introduction
||Chapter 2: Background
||Chapter 3: Method
||Chapter 4: Analysis
||Final Written Report