Capstone Deliverable's Content
Talk to your advisor about what the reporting requirements
he or she has for you.
If you are doing an industry-sponsored internship, you may not be able
to list specific deliverables and will list generic reports.
If you know what you will deliver, then list the specifics as the
deliverables instead of generic reports.
These reports will be of various frequency (e.g., weekly, monthly)
and complexity. Regardless, here are some
general guidelines regarding reports that you may find helpful.
When doing research or a project, you give deliverables on the
specifics of your work. These will be detailed information.
If you are doing an industry-sponsored capstone, deliverables are
often different from research or doing a project as details may
be proprietary information. Give context to whatever information
is relayed in reports. Reports may include:
- Discussion of what you have been learning/investigating
- Pseudocode or code
- Requirements, design, design pros/cons
- Diagrams with explanation
- Testing plans, testing results
- Website with some explanation (for example, why you chose
the technologies you did, or why you designed as you did)
The reports/deliverables don't need to be long, just clear.
Meta-information helps as well, especially in the final report which
often includes reflection on your experience. For example, describe:
- What did you learn? What do you wish you would have learned?
- How did you enjoy what you're doing?
- Things that went well? Things that didn't go well?
Things you would change if you did it over?
- Was the mentoring handled well? Why or why not?
- What were the challenges in your project? Did you have to
communicate with non-technical people? If so, how did it go?
- Problems? Cool things?
- If industry-sponsored, would you like to continue working at
your internship company? Why or why not?