Check-List for a Semester / Diploma project
Project Contract At most 3 weeks after beginning of
the project, fill in a project contract, which contains:
The project contract should be signed by you and the person (assistant or prof)
in charge of the project.
- The objective of the project. Please give a sequence of
objectives, in order of expected completion. Please think
that unexpected difficulties are more likely than unlikely to
arise, and make sure
you have still achieved something. Remember that most projects achieve much less than hoped at the
- The skills to be acquired during the project.
There should be a balance in the time spent acquiring new
skills and developing the project. The project is an
opportunity for you to acquire new skills, but it is not OK if
at the end of the project your only achievement is to have
- The support expected from your assistant
and the times of weekly checkpoints.
- The hardware and
During the Project
Please have a log-book. Keep day-by-day records. Write a very short summary of everything you do:
manipulations, the commands that do not work, the software you
Monday April 23:
downloaded the ns distribution on lrcpc26.
Did the necessary configurations.
Ran validation tests.
Test 24-X4 failed
Probably tcl to be re-installed.
Tuesday April 24:
re-installed tcl and passed ns validation tests.
Learnt ns tutorial.
Project Report You should prepare a project report,
using a word processor. The report should primarily document
the work done. It should contain two parts.
- A main
part, explaining the problem and your solution. About the size of an IEEE transactions paper (i.e. maximum 10
pages in two columns and 11 point font).
- What is the problem you had to solve ? why
it is a problem ? why would any one care about solving it ?
- Describe your solution. Explain the main features, the
ones you believe are most valuable.
- List your achievements, give their nature, quality and
quantity. Distinguish your contribution from what others did before.
For example: I designed an ns model of the VP-TFMCC
protocol, 2500 lines of simple code, 300 lines of high value code. Debugging took 2 weeks.
- What skills did you exercise, what skills did you have to
acquire for the project
- Report on the major events of the project, including unexpected
- Provide a self-assessment (where did you succeed most,
where did you fail)
- An appendix with supporting material:
- Give the background information that is needed to
understand and appreciate your work.
- Give only this
background information (your report is a project achievement
report; it should explain very clearly what you did, but does
not have to be a tutorial on a general topic.)
- Details of source code, simulation results, measurement
- Details about project events.
Presentation You should present your work in a slide
show. Please check the following list. You should target a 30mn
- What is the
problem you had to solve ?
- Give the background information
that is needed to understand and appreciate your work.
Give only this background information.
- What is your solution ?
Explain a representative part in detail.
- List your
achievements, give their nature, quality and quantity.
- what skills did you exercise, what skills
did you have to acquire for the project ?
- Report on the
major events of the project, including unexpected
- Provide a self-assessment.
Archive the project
Put your report and important documents (source code, ps
files, etc) into a compressed file, store it in a permanent
storage area of LCA, and give me the pointer. I will give the
final mark only when I have received all this.