Fall 2024 Semester
-
In order to enroll in ELE480, Capstone Design, you will need a Permission Number from Professor Sunak. This will be sent to you on satisfactory completion of the Enrollment Form, which can be downloaded from the link below. Provide full details to all the questions posed in the Form; see the 3 Example Submissions posted below. Take your time to study carefully the Symposium results of the 15 teams during the 2023-2024 academic year; links are provided in the Form. You are asked to select the top 3 projects, to give us more details of your expertise and passion areas in your major. Some projects may be continued during the 2024-2025 academic year; many new ones will be added.
Note: We recommend downloading the form below using Google Chrome.
Mark your calendar! Interviews will be held on Tuesday, September 3, 2024. More details and links for reserving a time slot will be posted early in the summer.
Click here to download form (pdf)
Sample Submissions
Computer Engineer – Click to download sample (pdf).
Electrical Engineer – Click to download sample (pdf).
Double Major (ELE+CPE) – Click to download sample (pdf).
-
See details of the PCB Design Course, which can be used as a 4th Professional Elective by Petition. It will be offered in the Fall 2024 semester, on Thursdays, from 5.15pm to 9pm. Will you be interested to take this course? Last Fall semester, the enrollment in this course were 30 seniors who take this course will be given preference in capstone projects that require PCB Design.) The first class will be Thursday, September 5 at 5:15 pm in FCAE 045.
Permission Number Request
If you are interested in taking the PCB Design course, please email Professor Sunak.
-
Students will have a limited time during their interviews during which to discuss their passion and backgrounds as they pertain to available capstone projects. To assist, the following time breakdown is provided.
It is recommended that students perform practice runs using the below format. Focus on being concise, and refer to specific information when speaking to previous experiences or reasons for project interest. Depending on the length of student presentation during the interview, there may or may not be time allocated for questions by the interview panel.
Proposed time breakdown:
1 min: Why did you select engineering as a career?
1 min: Discuss your passion areas and present skills possessed.
2 min: Discuss your first choice out of the 19 posted: justify with your skills, internships and passion.
2 min: Discuss your second choice out of the 19 posted: justify with your
skills, internships and passion.1 min: Discuss any future career paths and preferred industries.
-
ELECOMP Capstone Design
Logbook FormatLogbooks are property of the sponsoring company. All logbooks must be returned to the Technical Director at the 2023 Capstone Summit.
You must keep a logbook for your project; these will be provided at the first meeting. If you are working on a team project, each person must keep a logbook. All work on the project should be recorded in the logbook as the work is done. Even your rough calculations and thoughts about how to proceed on the project should be entered. The reader should be able to not only reproduce your work from the logbook but also should be able to understand why you made certain choices from your comments in the logbook. 5% of the final grade evaluation is based on your logbook. See the grading breakdown on the website.
First, the logbook serves as a record of design as a record of design ideas, design calculations, experimental procedures and data, library research, diagrams, graphs, photographs, lists, phone numbers, addresses, etc. – the “nuts and bolts” – of the project. The logbook is therefore a means of managing the project.
Second, the logbook is the primary source for progress reports and other technical documents, such as applications for patents, or papers submitted to a professional society, or proposals for new work.
Third, the logbook provides the technical chronology of the project, and thus provides a legal record of work done. This is particularly important when it comes to filing a patent claim, or defending one in court.
Fourth, the logbook becomes indispensable when the work you have done is to be continued by someone else. Frequently you will need to refer to work done on past projects, and a well-written logbook can often save you from repeating an experiment or a calculation.
You will quickly forget work and ideas, so write them down, in detail. Write your logbook as though:
- You are anticipating that someone else will eventually continue your work.
- It may be needed to back patent priority claims in court.
- One day you will be famous, and your logbooks will be made public. For example, see below an excerpt from the logbook of Walter H. Brattain; used as intellectual evidence for the invention of the transistor. (link to logbook pages)
The format of the logbook is as follows:
- The first 6 pages of the logbook must be left blank as they will be used for a Table of Contents, among other sections. Logging begins on page 7.
- All entries to the logbook must written in blue or black ink, and be dated and signed by yourself and a member of your team at the top of the page/entry. All edits, attachments, and revisions to the logbook must be initialed by yourself. Attachments to the logbook bust be initialed in such a manner that the initial overlaps both the attachment and the page.
- The logbook hour log shall be separated into eight (8) sections: Date, Day of the Week, Start Time, End Time, Hours Worked, Cumulative Hours Worked, Pages, and Comments.
- To orientate the logbook to begin the hour log, begin with the logbook in a standard reading position (Front cover top-facing, with the spine of the book on the left-hand side). Flip the book 180 degrees so that the spine is right facing and the top cover is face down. Rotate the book 90 degrees counter clockwise so the spine is facing forward and the top cover is face down. Open the back cover upwards and the last page will be on the bottom half in a landscape orientation. Logging begins on this page and then continues by turning the page upwards. This will be revisited during the first meeting.
- Provision 2×2 squares for all sections excluding date (using the space of the page) and Comments (using all remaining space). Please see the image below for an example.
- The start and end time are to be entered in 24hr format (00:00 – 23:59) and all entries must be in chronological order.
- Comments are generally 2-3 sentences summarizing the work done. This must be insightful and easy to follow.
Example Logbook Page
Log Book Spreadsheet Tool
To assist in your completion of the Log Book, a spreadsheet is available using Google Spreadsheets (Google Drive). You may make a copy of this spreadsheet and edit it with your entries. Note that the spreadsheet is not a substitute for the hand-written logbook and will not be accepted as a substitute. Rather, the tool should be used to mark down your hours quickly so that you may copy them to your logbook at a later date and time.
Download Link: Google Drive
-
ELECOMP Capstone Design
Linear Responsibility Chart (LRC)(source: Dym, Clive L., and Patrick Little. Engineering Design a Project-based Introduction. Chichester: Wiley, 2004. Print.)
Once the tasks that are to be done have been identified in a WBS, a design team has to determine whether or not it has the people, the human resources, to accomplish those tasks. The team also has to decide who will take responsibility for each task. This can be done by building a linear responsibility chart (LRC). The LRC lists the tasks to be managed and accounted for and matches them to any or all of the project participants. Figure 10.6 shows a simplified LRC corresponding with many of the tasks in the beverage container design WBS of Figure 10.3. In addition to all of the top-level tasks, the subtasks associated with several of the lower levels are also given. In practice, it is advisable to show all of the top-level tasks, as well as those subtasks that may require management attention. Because of the evolving nature of design projects, less experienced project managers may want to assign responsibility only for the top-level tasks and the next set of tasks that require the team’s attention. This allows the team’s roles and responsibilities to develop with experience, along with the project.
As we can see in Figure 10.6, there is a row for each task, within which the role, if any, of each project participant is given. These roles do not necessarily mean assuming the primary responsibility. Indeed, most of the participants will play some sort of supporting role for many of the tasks, such as reviewing, consulting, or working at the direction of whoever is responsible. A column is assigned to each of the participants; this allows them to scan down the chart to determine their responsibilities to the project. For example, we see that the client (or the client’s designated liaison) will be called upon to give final approval to the objectives tree, the test protocol, the selected design, and the final report. The liaison must also be consulted during some of the pre-design activities, and will be asked to review various intermediate work products. The client’s research director is somewhat of a resource to the team, and may be consulted at different points of the project, but must be consulted regarding the test protocol. The team’s boss, the director of design, has asserted the right to be kept informed at a number of points in the project, most notably in terms of design reviews. The project also has access to one or more outside experts, who are generally available for consultation and who must review the design and certain other (unspecified) documents.
We also note from the LRC in Figure 10.6 that the team leader does not always have the primary responsibility for the project. It is often the case in team projects that the team leader will not be responsible for tasks that are outside of her technical area of expertise, although she may want. to specify a review or support role in order to remain informed. Sharing responsibility this way is sometimes quite difficult both for team leaders and for teams. Sharing responsibility, which is strongly tied to the storming phase of group formation, requires practice. Therefore, the LRC can be used to make this part of team formation more explicit to the team, and to allow the team to reach consensus on who will be doing what in the project.
The LRC can also be used to let outside stakeholders in a project understand what they are expected to do. In the beverage container example, the client’s research director clearly has an important role to play in the safe conduct of the testing phase. It is very important that this person know early on what is expected, and to be allowed to plan accordingly. Similarly, the outside experts may need to allocate time to ensure availability, and the director of design may need to make resources available to pay for the experts’ time.
Example Charts
-
ELECOMP Capstone Design
Gantt Chart(source: William Durfee, University of Michigan, http://www.me.umn.edu/courses/me2011/handouts/proj_planning.pdf)
Project Planning Basics
A “Project” is a set of activities which ends with specific accomplishment and which has
(1) Non-routine tasks,
(2) Distinct start/finish dates, and
(3) Resource constraints (time/money/people/equipment).“Tasks” are activities which must be completed to achieve project goal. Break the project into tasks and subtasks. Tasks have start and end points, are short relative to the project and are significant (not “going to library”, but rather, “search literature”). Use verb-noun form for naming tasks, e.g. “create drawings” or “build prototype”. Use action verbs such as “create”, “define” and “gather” rather than “will be made”.
Each task has a duration. Very difficult to estimate duration accurately. Doubling your best guess usually works well.
“Milestones” are important checkpoints or interim goals for a project. Can be used to catch scheduling problems early. Name by noun-verb form, e.g. “report due”, “parts ordered”, “prototype complete”. Your plan will evolve so be flexible and update on a regular basis. It also helps to identify risk areas for project, for example things you don’t know how to do but will have to learn. These are risky because you may not have a good sense for how long the task will take. Or, you may not know how long it will take to receive components you purchased for a project.
Gantt Chart Basics
Gantt charts are a project planning tool that can be used to represent the timing of tasks required to complete a project. Because Gantt charts are simple to understand and easy to construct, they are used by most project managers for all but the most complex projects.
In a Gantt chart, each task takes up on row. Dates run along the top in increments of days, weeks or months, depending on the total length of the project. The expected time for each task is represented by a horizontal bar whose left end marks the expected beginning of the task and whose right end marks the expected completion date. Tasks may run sequentially, in parallel or overlapping.
As the project progresses, the chart is updated by filling in the bars to a length proportional to the fraction of work that has been accomplished on the task. This way, one can get a quick reading of project progress by drawing a vertical line through the chart at the current date. Completed tasks lie to the left of the line and are completely filled in. Current tasks cross the line and are behind schedule if their filled-in section is to the left of the line and ahead of schedule if the filled-in section stops to the right of the line. Future tasks lie completely to the right of the line.
In constructing a Gantt chart, keep the tasks to a manageable number (no more than 15 or 20) so that the chart fits on a single page. More complex projects may require subordinate charts which detail the timing of all the subtasks which make up one of the main tasks. For team projects, it often helps to have an additional column containing numbers or initials which identify who on the team is responsible for thetask.
Often the project has important events which you would like to appear on the project timeline, but which are not tasks. For example, you may wish to highlight when a prototype is complete or the date of a design review. You enter these on a Gantt chart as “milestone” events and mark them with a special symbol, often an upside-down triangle. A sample Gantt chart, made in Excel, appears at the end of this document. If today’s date were May 13, Task A would be behind schedule, Task B ahead and Task C right on schedule. The events marked by ‘-M-’ are milestones.
Computer-based Gantt charts
There are many software packages dedicated to project planning. One of the most popular is Microsoft Project. If you have access to Project (for IT students at the University of Minnesota, Project is installed on PCs in the ITlabs ), you should try it out because it is very easy to use, making simple Gantt charts is a breeze, and you can add it as a skill on your resume.
Here is how to make a Gantt chart.
On a piece of scrap paper, make a list of tasks and assign each task tentative start and stop dates (or duration) and the people responsible for the task. Also list important milestones and their dates. If you have more than 15 or 20 tasks, split your project into main tasks and subtasks, then make an overall Gantt chart for the main tasks and separate Gantt charts for the subtasks which make up each main task.
Decide what resolution to use in the timeline. For projects of three months or less, use days, for longer projects use weeks or months, and for very short project use hours. For these instructions, we will assume you have chosen a resolution of days.
Enter the information in MS-Project.
Or, as a last resort, use Excel. After starting Excel, under Page Setup, select landscape orientation, center the chart horizontally and vertically on the page and activate the “fit to one page” button. (Note that if the text comes out too small, you may have to print your chart on two pages and paste together. Even better, adjust the resolution of your date scale or drop less important tasks to make your chart fit comfortably on one page.) Set up the cells using the sample as a guide. Enter appropriate data.
As the project progresses, fill in the light colored bars with solid to denote the fraction of a task that is completed.
Sample Gantt Chart in MS Project
Sample Gantt Task List
Sample Gantt Chart
-
ELECOMP Capstone Design
Resources for Fall SymposiumPresentation Notes (.docx, Google Drive)
Presentation Example Slides (.pptx, Google Drive)
Presentation Example Slides (.pdf, Google Drive)
Presentation Example Slides (Google Slides, Google Drive)
Background Template 1 (.jpg, Google Drive)
Background Template 2 (.jpg, Google Drive)
Background Template 3 (.jpg, Google Drive)
Background Template 4 (.jpg, Google Drive)
Think Big We Do Logo (.gif, Google Drive)
ELECOMP Banner (.png, Google Drive)
Spring 2025 Semester
-
To be posted
-
To be posted
-
To be posted
-
Notice for Spring 2025 Teams
Students are expected to continue proper logging of work within their logbooks. Logbooks are necessary for both justification of work completed as well as evidence for any achievements of the team that the sponsoring company should like to protect. All work and its reasoning should be recorded in a logbook and be properly dated and signed by team members. Formatting for logbooks can be found below.
Failure to maintain logbooks in the spring semester will result in a 5% penalty.
ELECOMP Capstone Design
Logbook FormatLogbooks are property of the sponsoring company. All logbooks must be returned to locker #112 in the ELECOMP Capstone Lab by 2 pm on Friday, April 26th, 2025, for evaluation and dispatch to Technical Directors.
You must keep a logbook for your project; these will be provided at the first meeting. If you are working on a team project, each person must keep a logbook. All work on the project should be recorded in the logbook as the work is done. Even your rough calculations and thoughts about how to proceed on the project should be entered. The reader should be able to not only reproduce your work from the logbook, but also should be able to understand why you made certain choices from your comments in the logbook. First, the logbook serves as a record of design as a record of design ideas, design calculations, experimental procedures and data, library research, diagrams, graphs, photographs, lists, phone numbers, addresses, etc. – the “nuts and bolts” – of the project. The logbook is therefore a means of managing the project. Second, the logbook is the primary source for progress reports and other technical documents, such as applications for patents, or papers submitted to a professional society, or proposals for new work. Third, the logbook provides the technical chronology of the project, and thus provides a legal record of work done. This is particularly important when it comes to filing a patent claim, or defending one in court. Fourth, the logbook becomes indispensable when the work you have done is to be continued by someone else. Frequently you will need to refer to work done on past projects, and a well-written logbook can often save you from repeating an experiment or a calculation. You will quickly forget work and ideas, so write them down, in detail. Write your logbook as though:
- You are anticipating that someone else will eventually continue your work.
- It may be needed to back patent priority claims in court.
- One day you will be famous, and your logbooks will be made public. For example, see below an excerpt from the logbook of Walter H. Brattain; used as intellectual evidence for the invention of the transistor.
The format of the logbook is as follows:
- The first 6 pages of the logbook must be left blank as they will be used for a Table of Contents, among other sections. Logging begins on page 7.
- All entries to the logbook must written in blue or black ink, and be dated and signed by yourself and a member of your team at the top of the page/entry. All edits, attachments, and revisions to the logbook must be initialed by yourself. Attachments to the logbook bust be initialed in such a manner that the initial overlaps both the attachment and the page.
- The logbook hour log shall be separated into eight (8) sections: Date, Day of the Week, Start Time, End Time, Hours Worked, Cumulative Hours Worked, Pages, and Comments.
- To orientate the logbook to begin the hour log, begin with the logbook in a standard reading position (Front cover top-facing, with the spine of the book on the left-hand side). Flip the book 180 degrees so that the spine is right facing and the top cover is face down. Rotate the book 90 degrees counter clockwise so the spine is facing forward and the top cover is face down. Open the back cover upwards and the last page will be on the bottom half in a landscape orientation. Logging begins on this page and then continues by turning the page upwards. This will be revisited during the first meeting.
- Provision 2×2 squares for all sections excluding date (using the space of the page) and Comments (using all remaining space). Please see the image below for an example.
- The start and end time are to be entered in 24hr format (00:00 – 23:59) and all entries must be in chronological order.
- Comments are generally 2-3 sentences summarizing the work done. This must be insightful and easy to follow.
-
To be posted
-
To be posted
-
To be posted
-
To be posted
-
To be posted
-
To be posted
-
To be posted
-
ELECOMP Capstone Design Resources for Summit
Individual Resources
Presentation Notes (.docx, Google Drive) Presentation Example Slides (.pptx, Google Drive) Presentation Example Slides (.pdf, Google Drive) Presentation Example Slides (Google Slides, Google Drive) Background Template 1 (.png, Google Drive) Background Template 2 (.png, Google Drive) Background Template 3 (.png, Google Drive) Think Big We Do Logo (.gif, Google Drive) ELECOMP Logo (.png, Google Drive) ELECOMP Logo, no background (.png, Google Drive)
-
Click here to download Summit Program Sample (pdf).
Program Section Submission Guidelines
In order to correctly construct your team’s program section, you must send the following:
- Project Outcome: You must state either “The Anticipated Best Outcome was achieved” or “The Anticipated Best Outcome was not achieved”.
- Key Accomplishments: Refer to sample for formatting. Note – references to figures within the key accomplishment section must be in bold.
- Figures (maximum 4 images) and figure captions:
- Images must be of high resolution, PNG format.
- Ensure the figure is of high quality. If text is visible in the image, ensure it is of proper size and font for reading.
- Image file name must correspond to the figure caption number.
- Captions must be brief – do not use more than 1-3 sentences.