Shared project-system evaluation
Problem definition, domain understanding, methodology, architecture, implementation, testing, evidence quality, responsible limitations, deployment readiness and technical communication.
Project dossier / evidence / evaluation / contribution
Review
the work.
Project evaluation belongs beside the problem, method, implementation, evidence and team contribution—not inside a disconnected marks form.
The scoring model
One project score.
Visible individual accountability.
Public visitors can understand the framework. Only authorised coordinators should record marks or expose student-specific outcomes.
Individual contribution & viva
Role clarity, evidence of contribution, technical understanding, response to questions and accountability for the shared result.
The public portfolio should show the rubric and verified project evidence—not private marksheets, student scores, review notes or personal records.
Recommended operating flow
Assessment follows
the project record.
This is the restoration path for a proper project-evaluation desk.
Open the governed project dossier
Confirm identity, problem, team, current state and required deliverables.
Inspect linked evidence
Review repository, report, application, datasets, experiments, diary and public technical record.
Score the shared system
Record the 90-mark project result once, with criterion-level comments and evaluator identity.
Complete individual viva
Add each member’s 10-mark contribution score without changing the shared technical result.
Forward to programme completion
Keep this project result distinct from the already-working individual internship completion evaluation.