Capstone project examples include a UIC student’s photography project about endangered animals, a Purdue team’s manufacturing study, and a Notre Dame student’s comparison of beverage cups. You can explore these through a public video feature, a student poster, and a research abstract.
This guide includes three documented university projects and 12 illustrative project briefs. Compare their deliverables, evaluation methods, and resource requirements, then adapt an option to your department’s rubric. The worked examples also show how to report a failed test and interpret environmental measurements without overstating the findings.
Jump to: University projects · Briefs by major · Worked evidence example · FAQs
Three Real Capstone Projects From US Universities
These projects are documented on university websites. Each source provides a different view of the work: a video feature, poster, or abstract is not a complete final report.
The lessons and suggested evidence below are editorial interpretations, not claims about additional materials the students submitted. Inclusion does not imply university endorsement of FileMakr.
1. Creative Photography: “Gone Too Soon” at UIC
The University of Illinois Chicago features Rahul Kakarlapudi’s “Gone Too Soon.” UIC describes how he combined manual photography with his computer science background to create work about endangered animals disappearing from the wild.
What you can inspect: Watch Rahul discuss the project on the UIC Honors College capstone samples page. The video feature is public. UIC’s separate student-file collection requires a UIC NetID and Box account, and some entries contain only part of a project.
What students can learn: A capstone can connect technical interests with creative communication. Explain the subject research, creative decisions, and relationship between the finished work and the academic objective.
Evidence to consider for your own project: A curated portfolio, documented creative process, source acknowledgments, and a reflective explanation appropriate to the course.
2. Manufacturing Improvement: Inventus Power at Purdue
Purdue’s Inventus Power manufacturing project examined production of a wearable battery. The team documented time studies, bottlenecks, a gasket prototype, automation issues, and layout recommendations.
What you can inspect: The public Purdue manufacturing improvement poster (PDF) reports production of approximately 12 batteries per hour against a target of 16. It also records a failed prototype: glue adhered to the gasket. Further material testing appears as a recommendation.
The baseline, target, and failed prototype describe different kinds of evidence. The poster’s production target should not be presented as an achieved result.
What students can learn: An unsuccessful prototype can contribute useful evidence when you explain what failed and how the finding changes the next design decision.
Evidence to consider for your own project: Process diagrams, measurement records, prototype documentation, and recommendations linked to observed conditions. Report production improvements as achieved only when follow-up measurements support that claim.
3. Sustainable Beverage Distribution: “Cup Drop” at Notre Dame
Lauren White’s 2025 “Cup Drop” project examined aluminum beverage cups for Notre Dame’s Compton Family Ice Arena.
What you can inspect: The public Notre Dame project abstract describes a life cycle assessment comparing single-use aluminum cups with plastic and paper, including environmental and financial considerations. Its sustainability conclusion depends on achieving a 90% recycling rate; the abstract does not report an achieved arena recycling rate.
What students can learn: A narrow operational decision can support substantial research. Keep the condition attached to the conclusion when summarizing a finding.
Evidence to consider for your own project: An alternatives comparison, documented inputs, assessment boundaries, and sensitivity analysis showing which assumptions could change the recommendation.
How Does a Capstone Idea Become a Finished Submission?
A capstone applies knowledge and skills from a degree program to a substantial academic project. The final output may be an application, research paper, prototype, policy brief, business recommendation, or creative work.
| Stage | Equipment-checkout example |
|---|---|
| Project idea | Build a system for borrowing campus equipment. |
| Project proposal | Define users, reservation rules, deliverables, methods, evaluation, and exclusions. |
| Completed submission | Provide the implemented system, supporting report, actual test results, limitations, and required presentation. |
For broader background on formats and course expectations, see FileMakr’s capstone project overview.
Compare 12 Capstone Project Briefs by Major
Examples 4–15 are illustrative briefs, not completed student projects or reported FileMakr case studies. Adapt their suggested submissions and evaluation methods with your instructor.
| No. | Major or field | Suggested project | Suggested submission |
|---|---|---|---|
| 4 | Computer science | Campus equipment checkout | Application and test report |
| 5 | Data science | Building electricity forecasting | Reproducible analysis |
| 6 | Cybersecurity | Isolated security monitoring lab | Detection rules and evaluation |
| 7 | Business | Campus refill-store feasibility | Business recommendation |
| 8 | Marketing | Nonprofit awareness campaign | Campaign materials and evaluation plan |
| 9 | Engineering | Room-condition monitoring | Prototype and technical report |
| 10 | Nursing | Patient-education evidence review | Evidence table and teaching resource |
| 11 | Public health | Community resource map | Directory and coverage analysis |
| 12 | Education | Digital literacy curriculum | Lessons and assessment rubric |
| 13 | Environmental studies | Campus waste audit | Measurements and recommendations |
| 14 | Public policy | Bus-service access analysis | Maps and policy brief |
| 15 | Humanities/design | Local-history digital exhibit | Curated exhibit and commentary |
Compare dependencies as carefully as subject matter. Hardware projects need components and reference measurements. Client projects need access and timely feedback. Public-data and archival projects need usable sources, appropriate permissions, and a question those sources can answer.
Twelve Capstone Project Briefs You Can Adapt
4. Campus Equipment Checkout System
Problem: A department needs a consistent way to manage equipment reservations, loans, and returns.
Deliverable: Build an application covering one department’s inventory, student reservations, and staff checkout workflows.
Evaluation: Test overlapping reservations, unauthorized inventory changes, overdue items, and returned equipment becoming available again.
Scope boundary: Exclude payments and campus-wide integrations from the initial version. Sample records can support functional testing, but claims about departmental efficiency require appropriate user or operational evidence.
Explore related software engineering capstone project ideas.
5. Building Electricity Forecasting
Problem: A facilities team wants to estimate future electricity demand.
Deliverable: Prepare a documented dataset, a simple baseline forecast, a comparison model, and a reproducible results notebook.
Evaluation: Hold out the latest block of readings. Train using earlier records and compare your model with a simple forecast, such as demand at the same hour one week earlier. Use the same test periods and error measure for both approaches. Show a period when the baseline performs better, if one occurs.
Key dependency: Confirm usable historical data before committing. Explain missing readings, unusual events, and their effects on the conclusions. Keep model selection separate from the final held-out evaluation.
6. Security Monitoring in an Isolated Lab
Problem: A simulated network needs visibility into selected suspicious events.
Deliverable: Configure logging, develop detection rules, and document controlled test scenarios.
Evaluation: Record detected events, missed events, and false alerts during ordinary activity. Keep enough logs for another reviewer to reproduce your findings.
Scope boundary: Use systems you own or are explicitly authorized to test. Limit the project to a defined set of events.
Compare additional cybersecurity capstone project ideas.
7. Campus Refill-Store Feasibility Study
Problem: A campus organization wants to assess a refill-store concept before committing resources.
Deliverable: Produce a market assessment, operating model, cost estimates, and a recommendation.
Evaluation: Calculate break-even conditions and show how the recommendation changes with demand, rent, or supplier costs.
Evidence boundary: Separate verified prices and observed information from assumptions. Projected demand is not demonstrated sales, and an unfavorable recommendation can still be a valid project outcome.
8. Nonprofit Awareness Campaign
Problem: A nonprofit wants people to understand one of its services more clearly.
Deliverable: Develop audience profiles, message alternatives, sample campaign materials, and a measurement plan.
Evaluation: Use approved audience feedback to assess comprehension, relevance, and the clarity of the next action.
Scope boundary: If the campaign does not launch, evaluate the materials themselves. Do not claim increased donations or service use from a design review alone.
9. Room-Condition Monitoring Prototype
Problem: A study room or laboratory needs basic temperature and humidity monitoring.
Deliverable: Assemble a sensor prototype, enclosure design, data display, and technical documentation.
Evaluation: Compare readings with a suitable reference and test behavior during connectivity or power interruptions. Document the conditions, discrepancies, and missing readings.
Key dependency: Secure the components and reference equipment early. Describe the result as an educational prototype unless further validation supports broader use.
10. Patient-Education Evidence Review
Problem: A faculty-approved nursing topic needs an accessible educational resource.
Deliverable: Prepare a literature review, evidence table, and draft teaching material.
Evaluation: Document search and selection methods, appraise the included evidence, and obtain faculty review of the resource.
Scope boundary: Keep the project within the approved academic brief. A reviewed handout does not establish improved patient outcomes; that would require a separately designed and approved evaluation.
11. Community Resource Map
Problem: Residents have difficulty locating food assistance or other community services.
Deliverable: Create a searchable directory and map using public or permissioned information.
Evaluation: Check locations, service descriptions, hours, and update dates against source records. Analyze which areas or service categories have incomplete coverage.
Scope boundary: Begin with one locality and a defined service category. Record uncertain entries rather than presenting an incomplete directory as comprehensive.
12. Digital Literacy Curriculum
Problem: A defined learner group needs support with a specific digital skill.
Deliverable: Design a short lesson sequence, activities, teaching materials, and an assessment rubric.
Evaluation: Map every activity to a learning objective. Use an approved pilot, if feasible, to examine learner performance and revise the materials.
Evidence boundary: Without a pilot, report the findings of curriculum review rather than claiming demonstrated learning gains.
13. Campus Waste Audit
Problem: One campus location needs evidence about the composition of its waste stream.
Deliverable: Produce a sampling plan, categorized measurements, and recommendations.
Evaluation: Use consistent categories and document collection dates, measurement procedures, and unusual conditions.
Key dependency: Arrange site access and an approved collection procedure before beginning. Explain whether limited sampling dates or special events restrict how widely the findings apply.
Worked calculation—illustrative figures, not collected campus data:
| Sample | Food waste | Total waste | Food share by weight |
|---|---|---|---|
| A | 2.4 kg | 8 kg | 30% |
| B | 1.2 kg | 12 kg | 10% |
| Combined | 3.6 kg | 20 kg | 18% |
The combined food-waste share is: (2.4 + 1.2) ÷ (8 + 12) × 100 = 18%.
A simple average of 30% and 10% gives 20%, which does not represent the combined waste because the samples have different total weights.
Defensible interpretation: Food makes up 18% by weight of these two samples. A campus-wide estimate would require a sampling plan covering relevant locations and dates. State what additional sampling you would need before recommending a broader intervention.
14. Bus-Service Access Analysis
Problem: A community wants to understand transit access to selected destinations.
Deliverable: Prepare maps, a reproducible analysis, and a policy brief.
Evaluation: Compare access under stated walking-distance, timetable, and time-of-day assumptions. Explain how changing these assumptions affects the findings.
Evidence boundary: Scheduled access and observed reliability answer different questions. Without actual service-performance data, avoid conclusions about buses consistently arriving on time.
15. Local-History Digital Exhibit
Problem: A local historical topic needs an accessible public presentation.
Deliverable: Build a curated exhibit with source descriptions, interpretive text, and accessible navigation.
Evaluation: Check the provenance and reproduction permissions for each item. Ask a reviewer to reach an exhibit item using only a keyboard and assess whether its image description conveys the detail discussed in the caption. Record these as specific checks, not a complete accessibility assessment.
Scope boundary: Select a focused period, place, or theme. A smaller collection with clear interpretation and reliable attribution can provide a stronger academic contribution than a large collection with uncertain origins.
Worked Example: How to Document and Interpret Capstone Evidence
This example expands Example 4 to show how a submission connects objectives, evidence, and conclusions. It is a teaching example; no implementation or executed test results are being claimed.
Define the Scope of the Claim
Proposed project: Campus Equipment Checkout System for a University Media Department.
Included: Student and staff roles, equipment records, reservations, checkout, returns, and overdue status.
Excluded: Online payments, purchasing, university-wide account integration, and predictive maintenance.
Evaluation question: Does the system enforce the defined borrowing rules under the tested conditions?
This question supports a functional evaluation. It does not, by itself, establish that the system saves staff time or improves student satisfaction.
Connect Each Objective to Evidence
| Objective | Deliverable | Evidence to submit |
|---|---|---|
| Prevent conflicting bookings | Reservation workflow | Repeatable tests for overlapping requests |
| Restrict inventory changes | Staff permissions | Tests showing student actions are denied |
| Track equipment availability | Checkout and return records | Transaction records linked to the correct item |
| Explain design decisions | Report and system diagrams | Requirements mapped to design choices |
| Support independent evaluation | Setup and test instructions | Sample records and reproducible procedures |
Keep Expected and Actual Results Separate
Test: Attempt to reserve equipment during an existing confirmed booking.
Setup: CAM-01 has a confirmed reservation from 10:00 a.m. to noon on the selected date. Under this example’s borrowing policy, confirmed reservations block overlapping bookings for the same item.
Action: A second, authorized student submits an otherwise valid reservation request for CAM-01 from 11:00 a.m. to 1:00 p.m. that day.
Expected result: The system rejects the request because its time interval overlaps the confirmed booking. The original reservation remains unchanged, and the system stores no second confirmed booking.
Actual result: ____________________
Complete only after executing the test.
Evidence: Record the software version and test setup. Save the request, response, relevant database state before and after the action, and a screenshot where useful.
Report a Failed Test Honestly
Suppose the second student sees a rejection message, but the reservation list contains two confirmed bookings for CAM-01. Record the test as failed. The interface message does not establish that the borrowing rule was enforced.
Save both reservation records, identify the violated rule, and describe the observed behavior. After a fix, rerun the same test and retain both results so the reviewer can follow the change. Record the retest as passed or failed according to the evidence.
| Evidence available | Conclusion it supports | Conclusion it does not support |
|---|---|---|
| Rejection message alone | The interface displayed an error | No conflicting record was stored |
| Request, response, and stored records | Whether this attempt preserved the booking rule | All possible conflicts are prevented |
| Documented passing retest after a fix, including the software version, setup, response, and stored records | The revised version passed the specified test under the recorded conditions | The application is defect-free |
Test simultaneous requests separately. Passing a sequential conflict test does not establish how the system behaves when two requests arrive together.
Assemble the Submission
Subject to your course requirements, include:
- The application and installation instructions.
- A report covering the problem, related work, design, implementation, and evaluation.
- A requirements-to-test matrix.
- Test records with expected and actual results.
- Known limitations and unresolved defects.
- Presentation or demonstration materials.
- A statement identifying each team member’s contribution.
How to Choose and Adapt an Example
- Translate Your Rubric Into Required Evidence
Identify what the course assesses: research, design, implementation, analysis, reflection, or presentation.
Output: A checklist linking each assessment requirement to something you will submit.
- Compare Two Feasible Options
For each option, record the main deliverable, required resources, largest uncertainty, and evaluation method.
If electricity records are unavailable but historical materials are accessible with suitable permissions, a digital exhibit may have fewer unresolved dependencies. Your academic interests and rubric still determine whether it is suitable.
Output: A short comparison explaining your choice.
- Test the Most Uncertain Dependency
Inspect a dataset, review representative source material, test a component under the intended conditions, or confirm usable client access before committing to the full project.
Output: Evidence that the essential resource is usable, or a revised plan if it is not.
- Define Scope and Your Own Contribution
Specify the setting, users, research question, included work, and exclusions. Explain what you will design, investigate, interpret, or evaluate yourself.
Use FileMakr’s capstone scope guide to organize these boundaries.
Output: A one-page scope suitable for supervisor review.
- Plan Evaluation and Submission Together
Reserve time for testing or analysis, documentation, feedback, revision, and presentation.
FileMakr’s capstone proposal guide provides planning guidance you can adapt to your department’s required format.
Output: A proposal with milestones defined by reviewable results.
Before submitting the proposal, name one finding that would change your recommendation. A refill-store study can reasonably conclude that expected demand is too low to launch. A forecasting study can conclude that the simpler baseline is the better choice.
Frequently Asked Questions
What makes a capstone example useful to study?
Look for the connection between the project’s question, method, final output, and evidence. A polished interface or attractive poster shows only part of the work. Check whether the source explains what was evaluated, what happened, and what remains uncertain.
What are simple capstone project examples?
A focused digital exhibit, public-data analysis, small checkout application, or bounded curriculum project may offer manageable scope. “Simple” should mean limited dependencies and clear boundaries while still meeting the academic depth required by your program.
Which capstone projects can I complete without a client?
Public-data analysis, an isolated software or security prototype, a literature-based project, or an archival exhibit may be possible without an external client. Confirm source access, permissions, and whether your course requires a sponsor or real users.
Where can I find completed capstone reports or posters?
University repositories and departmental showcases are useful starting points. For paired materials, see Matthew S. Foster’s University of Michigan project, Tailoring Performance-Led Aircraft Design to Efficiency Using Multidisciplinary Design Optimization, through its Deep Blue repository record.
Compare the honors capstone final report (PDF) with the project poster (PDF). Read the poster for an overview, then use the report to examine the methods and supporting evidence. If a direct download fails, try the repository record.
These supplementary materials sit outside the numbered 15 examples.
Can I complete a capstone project in one semester?
Possibly, if its scope fits the course schedule and essential resources are available. Estimate the complete workload, including evaluation, documentation, revision, and presentation. A technically small project can become difficult when permissions or data arrive late.
Does every capstone require original research?
Requirements vary by program. Applied and creative projects may use evidence reviews, design comparisons, or evaluation without taking the form of a traditional research thesis. Confirm the expected contribution with your instructor.
How can I adapt an existing capstone idea?
Define a specific problem, justify your choices, and evaluate your contribution. Cite reused sources and components, and follow your institution’s rules. Changing a title or interface alone does not explain what new work you completed.
How do I show my individual contribution in a team project?
Maintain a contribution record connecting your responsibilities to inspectable work: analysis, designs, code changes, test evidence, writing, or decisions. Explain both your individual contribution and how it fits the shared result.
Choose Two Examples to Discuss With Your Supervisor
For each option, write down the deliverable, the resource you need first, and the evidence you could submit. Take both to your supervisor.
Once you agree on the scope, use the capstone project timeline guide to schedule the work.
How This Guide Was Prepared
The three featured university projects are documented in a student video feature, a team poster, and a project abstract. FileMakr’s 12 briefs, waste-audit calculation, and equipment-checkout test record are teaching examples. The hypothetical figures and proposed tests are not reported student outcomes or evidence of firsthand implementation.