Documenting a student engineering project
Document the problem, the revision you built, how you made it and what you measured. Include original photographs, labelled drawings and a clear account of limitations. Separate a proposed benefit from a result that was actually observed, and make supporting files available when you have permission to share them.
Explain the engineering decision
A finished photograph shows an object but rarely explains the work. Introduce the problem, the intended user or context and the main constraint. Describe why the team chose the current approach, including alternatives that materially affected that choice.
Keep the project’s scope visible. An early proof of concept should be labelled as such rather than described as a deployed solution. A proposal, a simulated result and a measurement from hardware are different kinds of evidence.
A reusable case-study structure
- Problem and context: what the team set out to improve.
- Design: drawings, key requirements and the selected approach.
- Build: revision, materials, equipment actually used and significant changes.
- Test: method, conditions, observations and measurements.
- Result: what the evidence supports, including failures.
- Limitations: what has not been tested and what remains uncertain.
- Resources: permitted files, references and the next revision.
Make the evidence easy to inspect
Name image and test files consistently. Captions should explain what the reader is seeing and which revision it represents. Give units for measurements and distinguish a measured value from a design target.
If a result depends on a calculation, record its inputs and method. If a graph is produced from measurements, retain the underlying data. Do not present a photograph of equipment as proof that the project used that equipment.
Prepare a version for public sharing
Check that the team has permission to share photographs, external files and personal details. Remove credentials and private contact information from code and screenshots. Credit external references and identify the role of collaborators accurately.
A useful public page should link to related equipment, workshops or resources only when those connections are real. The aim is a case study another team can learn from, with a clear distinction between demonstrated results and planned improvements.
Try the prototype BOM budget calculator with CSV export or browse the fabrication planning tools.
Related equipment at DTU
Review the equipment page and confirm the setup and access process with staff.