TOOL

Types in Object-Oriented Languages

[TOOL home]

[Course plan]

[Participants]

[Exam project]

[Literature]

[Links]

[Curriculum]

Exam project

The exam consists of a project report. The project must lie within the subject of the course and relate to a substantial part of the course literature. The overall topic should be approved by the lecturer. The project can be completed individually or in groups of any size. It will be evaluated on the 13-scale based on overall quality. A reasonable workload compared to the size of the group is expected. The grading is individual, based on information in the report about who contributed what. It is recommended that you pick a topic that you find exciting and from which you expect to learn a lot. The project work itself can be of many kinds, including
  • Code based, such as implementing or testing type checkers
  • Theory centered, such as defining/extending formal type systems or proving soundnes theorems
  • Comparative, such as bringing in other literature, comparing and discussing
  • Innovative, making up new constructs or patterns of use that improve expressiveness or safety
or any mixture thereof. You should be conscious that the report writing is a non-trivial part of the work. The way you explain, discuss your work and relate to course literature is central in the evaluation. A good strategy to reduce risk is to define a project that you can evolve incrementally, producing for each step a relatively complete report. This way you can adjust your ambitions both ways as the project progresses.

At the last lecture every group should give a short presentation of their project and its status, followed by a short discussion with questions and suggestions from the audience intended to help the group improve their product. On a voluntary basis, groups will then be assigned round-robin to review preliminary versions of each others' reports, providing as valuable and constructive feedback as possible before the final hand-in. Please be respectful of each others' work - the purpose of these review activities is to improve, not evaluate.

The important dates of the exam process are as follows:

May 3All participants belong to a group with a lecturer-approved topic
May 17Project presentations and discussions at the lecture
Review plan established
May 19Preliminary reports exchanged for review (date can be changed by mutual agreement)
May 24Review feedback (date can be changed by mutual agreement)
May 31Final hand-in (pdf, ps, or physical paper) at 12:00 (noon)
June 10Evaluation completed, individual grades sent out

All dates are firm, unless stated otherwise!