Value enhancing 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. The tutor has a maximum budget of 180 points for each team. 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. For this, you will need to create a Project Demonstration Video in which you show all implemented Value Enhancing Features.
- 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.
- 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.
Frequently Asked Question
How does the grading system work?
Grading is based on the features you implement, with point values determined by the price you and your tutor agreed upon in the corresponding GitLab issue.
What earns me full points on a feature?
You receive full points when the feature works perfectly, matches the project description, and provides a genuinely helpful experience for the user.
How do minor bugs affect my score?
Small mistakes, typos, or minor text errors will result in the loss of a few points (usually below 10 points).
What happens if a feature has major usability failures?
If a feature is broken, extremely difficult to use, or fails to meet basic usability standards, you will lose a significant number of points (usually more than 10 points).
What is the penalty for crashes or unfinished work?
If a feature causes the program to crash or fails to finish its intended job, you will receive 0 points for that specific feature.
Example: Missing a Feature in the Video
A team built all 4 of their agreed features in their repository. However, in their YouTube video, they only recorded and showcased 3 of them. Because the 4th feature was completely missing from the video, they received full points for the 3 visible features but 0 points for the missing one, even though the code for it was fully finished in GitLab.
Example: Showing an Incomplete Scenario
A team created an interactive mini-game feature where the player can either win or lose. In their video, they showed the player losing the game, but they never showed a winning scenario. Because they did not prove that the winning path works correctly, they lost a few points for an incomplete demonstration.
Example: Program Crash During Demo
A team wanted to show their "Save and Load System" feature. In the video, saving the game worked perfectly. However, when the narrator clicked the "Load" button, the program froze and crashed to the desktop. Because the feature crashed during the demonstration, the team received 0 points for that entire feature.