Final programme evaluation · Total marks: 100
| Component | Evidence considered | Max. | Awarded |
|---|
| Programming & computational foundations | Weeks 1–2 reasoning, algorithms, notebooks and coding evidence | 10 | [ ] |
| Data analytics & EDA | Weeks 3–4 practicals, DataForge/EDA evidence and interpretation | 10 | [ ] |
| Machine-learning pipelines & practicals | Weeks 5–6 microprojects, model selection and evaluation evidence | 15 | [ ] |
| Advanced AI foundations | Weeks 7–10 specialization, responsible AI and deployment learning | 10 | [ ] |
| Internship diary & professional discipline | Dated internship diary, documentation and participation record | 10 | [ ] |
| Project — individual contribution | Role, individual diary, commits/artifacts and individual defence | 20 | [ ] |
| Project — group system & report | Group evaluation record, report, repository and final evidence | 15 | [ ] |
| Final defence & presentation | Viva, project story, poster/demo and handling of limitations | 10 | [ ] |
| Final result | 100 | [TOTAL] |
Programme decision: ☐ Completed ☐ Completed with correction window ☐ Completion pending
Evaluator note: [Concise evidence-based note]
Correction requirement / due date: [If applicable]
Student CoordinatorName / date / signature
Programme CoordinatorName / date / signature
Authorised Programme OfficeName / date / signature
Shared system evaluation · Group score: 90 marks
| Criterion | Observable evidence | Max. | Score |
|---|
| Problem framing & acceptance criteria | Stakeholder, constraint, scope, success condition | 10 | [ ] |
| Data/research quality & responsible sourcing | Source traceability, data card, permissions and limitations | 10 | [ ] |
| Architecture & engineering approach | Diagram, reasoning, trade-offs and component boundaries | 15 | [ ] |
| Implementation, repository & reproducibility | Release, README, environment/setup and working evidence | 15 | [ ] |
| Evaluation, testing & limitations | Metric/test cases, error analysis and honest limits | 15 | [ ] |
| Technical report & traceability | Report, citations, figures, evidence and appendices | 10 | [ ] |
| Demonstration, poster & project story | Clear narrative, demo/fallback and presentation quality | 10 | [ ] |
| Deployment readiness & responsible-AI safeguards | Operational boundaries, data/privacy and next validation | 5 | [ ] |
| Group system score | 90 | [TOTAL] |
Required evidence links: Repository [URL] · Report [URL] · Demo [URL] · Slides/Poster [URL]
Panel finding: [Approved / correction required, with specific reason]
Project CoordinatorName / date / signature
Programme CoordinatorName / date / signature
Review PanelName / date / signature
Individual addendum · 10 marks
| Criterion | Student-specific evidence | Max. | Score |
|---|
| Defined role & owned deliverables | [Role / tangible output] | 3 | [ ] |
| Dated evidence | Diary, commits, notebooks, research notes or artifacts [URLs] | 3 | [ ] |
| Technical explanation during viva | Problem, decision, metric and limitation explained by student | 2 | [ ] |
| Collaboration & documentation discipline | Team contribution, handover quality and response to review | 2 | [ ] |
| Individual contribution total | 10 | [TOTAL] |
Viva prompts and evaluator notes
| Prompt | Notes / evidence |
|---|
| What problem did this system address and for whom? | [ ] |
| What did you personally build, investigate or document? | [ ] |
| Why was this method/model/tool chosen? | [ ] |
| What result is supported, and what limitation remains? | [ ] |
| What is the responsible next step? | [ ] |
StudentDeclaration / date
Project CoordinatorReview / date
Programme CoordinatorEvaluation / date
