Project evaluation

When: immediately after the end-sem exam · lab viva, whole group present

Submit: tag your repo project-final before your slot.

Ceiling

Ceiling	You have	Evidence
10	deployed, hosted, used by people outside your team	live URL + evidence of outside use — analytics, feedback log, or user list
9	deployed MVP, key features working	live URL
8	anything else	—

The ceiling is the maximum. Everything below decides your score within it.

The words your product is about — Order, Slot, Booking, not Manager, Handler, Util. Same format as Lab ⅔.

Term	Definition	Aliases to avoid	Named in code at

Then flagged ambiguities: every place one word means two things, or two words mean one. Say which one wins.

Use the terms from UBIQUITOUS_LANGUAGE.md. A new word for an existing concept is a finding against you.

Five rules your product enforces, in plain English.

Three design decisions, each with:

One boundary — where your core logic stops and the outside world begins, and which dependency it protects you from.

AI use

Rule	Test `file:line`	If untested — what stops you

Then one line each:

A low count costs less than tests that assert nothing.

Any member may be asked about any file:line in either document.

Docs that don't match the code are graded as absent.

Using AI costs nothing. Not being able to explain your own code does.

	Weight
`UBIQUITOUS_LANGUAGE.md` + `DESIGN.md` — terms, decisions, citations, boundary	35%
`TESTING.md` — rules tested, honesty about gaps	35%
Viva — code matches docs, every member can explain	30%