Capstone Design Project
Example of a bad report -- Don't do this!
Wednesday, Nov 5
This was my weekly meeting. We discussed all of the work that had been done in the previous
week. We discussed the current code, as well as the possibility of an already existent
input file. We also discussed what can be used from previous code and what should be
re-designed. We talked about the final paper required for the class, as well as created an
updated bibliography. We also discussed some of the goals for the next few weeks. We
also set up some future meeting times.
Week 8 work:
- reviewed code
- reviewed input file
- worked on configuring program
- worked on compiling and running program
- obtained economic sources
- reviewed economic sources
- attended meetings
- updated journal
- emailed journal
- The purpose of the weekly reports is not to summarize our weekly meetings. It is to summarize your
efforts outside of our meetings.
- This is not a good level of detail. Most of this report is way too vague. Why were we discussing
the current code? What is it about the previous code that might be useful? What is going to be
re-designed and why? This report mentions future goals but never itemizes them. What are they?
- In the bulletted summary of the work done this week, this report has too much detail. Or rather,
the included details aren't particularly useful. The exact nature of what was accomplished is never
spelled out. And points like "attended meetings" and "emailed journal" are unnecessary. They're just
- There are no justifications (reasons) for why certain decisions are made. Actually, the decisions
themselves aren't clearly listed either.
Back to CSc 498/499 homepage