Expectations about the midterm project

The midterm project is in two parts:

• the project proper (as a .scm file), carried out in groups, and
• a report (as a .pdf file), concisely written in groups.

The reading grid for grading

The .scm file, the form:

• does it load completely?
• is it indented in the standard way?
• does it use the standard naming convention (e.g., the Haskell plural convention for names that denote lists)?
• does it contain comments, and if so of which nature (indicative / analytical)?

The .scm file, the content:

• are there unit-test procedures before all the implementations?
• are all the implementations tested?
• does the syntax checker checks whether the given value is cyclic?
• are simple things done simply?
• are there any extras?
• is the syntax checker self-applicable?

The .pdf file, the form:

• is it original?
• front page: incomplete / out of scope / standard / clever
• page numbers: yes/no
• table of contents: present or absent / uninformative / standard / clever and telling
• introduction: minimalistic / telling / amazing
• each section:
  • with an introduction and a conclusion / without
  • with just code / with a narrative interspersed with code
  • with everything, torrentially / with brevity, measure, or even concision
  • with no narrative / an ordinary narrative / an outstanding narrative
  • with no quotes / with fitting quotes / with ill-fitting quotes
• conclusion: minimalistic / telling / amazing
• remarkably short / medium size / enormous size
• incomplete / OK / with pluses
• was the report spell-checked?

Version

Created [14 Oct 2025]