Additional Features

This task is different from the others: it follows the Price of Features model, where your team and tutor agree on which extra features you will build and how many points they are worth.
Each feature is priced individually by the tutor. These features are optional but essential if you aim for an excellent (5) grade.

Your goal is to deliver real, working value, demonstrate it clearly, and document it so end users can actually use it.

• There is no upper limit on how many features you can build — only time and sanity.
• Strong teams usually deliver 2–4 priced features.
• Features must remain small enough to finish; avoid multi-week monsters.

The final earned points come from clarity, usability, and demonstration strength:

• The feature solves a real user problem and behaves consistently.
• The video demo is clear, stable, and under time limit.
• Documentation is accurate, readable, and follows the user-doc structure in the course (see User Documentation task).
• The final presentation shows confidence, understanding, and professional communication.
• Minor bugs → small deductions.
  Major usability failures → large deductions.
  Crashes or incomplete features → no price points.

How to Complete

To complete this task, your team must deliver at least one priced additional feature, including all deliverables below:

1. Video demo of the working feature(s)

   • Maximum total length across all extra features: 10 minutes
   • Longer videos will be ignored
   • Show the program running, input → output
   • No code walkthrough, focus on user-visible behavior
   • Clear voice-over, subtitles not acceptable

2. The feature must work correctly

   • It must fulfill its intended user-visible purpose
   • Small errors are allowed, but points will be deducted

3. User-facing documentation

   • Every new extra feature must be clearly described
   • Documentation must be reachable from the project's README.md
   • Place docs under docs/user/ following the same structure as previous tasks

4. Final presentation (10 minutes per team)

   • Present all additional features you delivered
   • Justify why they matter, how they work
   • The presentation is part of the evaluation

5. Feature must be pre-priced by the tutor

   • Before starting development, agree with the tutor on:
     • What exactly you will build
     • How many points it's worth
   • Record this in the feature issue (e.g., “Price agreed with tutor on 2026-04-12, worth 28 points”)

Examples

Example: Team 'ByteBusters' deliver a powerful export feature

They negotiate a 32-point “Export to JSON” feature.
- Clear video demo (2:10) shows loading data → exporting → opening the file.
- Docs explain the file format and steps.
- Their final presentation explains why JSON helps other tools integrate with their system.
Tutor awards full points.

Example: Team 'NullPointers' deliver two small extra features

They implement:
- “Sort entries by title” (18 pt)
- “Random suggestion” (14 pt)
Their demos stay within 10 minutes total.
Both features work but sorting occasionally prints an extra blank line → slight deduction.

Example: Team 'PixelPenguins' over-shoot the time limit

They demo three features in a 14-minute video.
Video will be ignored. They get 0 points for all features.