What your team is building
A software product — database, HCI, graphics, visual programming, compilers — built for a real user group and launched.
Your block's convener. Dr Nasreen Jawaid.
You submit one piece of work, and each course that marks it looks at a different dimension, out of 15. At most eight courses mark one team file. A course you take that falls outside those eight sets you a lens note instead — an individual piece on the same project from that course's angle, 3,000 words, same rubric, out of 15, with a viva out of 5. No student carries more than two: from a third, that course marks your viva out of 20 instead.
30 sessional work — a team mark of 15 from each course that marks your file, plus your own viva of 5, held in class in the Presentations & Viva week, plus your teacher's quizzes and assignments 10
30 the mid-term
40 the final
This replaces most coursework, not classes.
The projects in this block
Your team chooses one of these in session 6, with your convener. At most two teams take the same project, and only on different sites or areas. The full question, the work and the required pieces for each project are in the Ideas Book. Each line below says what your team leaves behind by December, and the skill you take away.
| Project | What exists by December | Skill |
|---|---|---|
| The Citizen Complaint AppReports to: Greenwich University Administration · Cantonment Board Clifton | A working complaint app piloted with real users, its code and user guide handed to the body that agreed to the pilot. | building and user-testing a database-backed app |
| A Point-of-Sale for KiranasReports to: SMEDA | A free offline Urdu point-of-sale with a khata ledger, used daily by the pilot shops and published, with findings handed to SMEDA. | observing users before building software |
| Urdu Programming LanguageReports to: Sindh School Education Dept | An Urdu-keyword teaching language, compiler and right-to-left editor trialled with first-time coders, its report handed to the Sindh School Education Department. | designing a language and writing its compiler |
| Project | What exists by December | Skill |
|---|---|---|
| The Campus WayfinderReports to: Greenwich University Student Affairs Office | A searchable campus map with code, data and user guide, handed to the Student Affairs Office and in use if it accepts. | writing a lexer and parser for a query language |
What each course marks
| Code | Course | What this course marks — 15 marks |
|---|---|---|
| GCCC554 | Compiler Construction Haris Yaseen | This course marks the language layer of the product: the grammar or input specification the team defined, the scanner and parser that implement it, the checks that catch bad input before it reaches a user, and the test evidence that the layer is correct. 15 marks, team. |
| GCCG562 | HCI & Computer Graphics Haris Yaseen | This course marks the interface: the user research behind it, the prototype and how it changed after testing, the usability test run with real participants and reported properly, the accessibility check, and the quality of anything the product renders. 15 marks, team. |
| GCCS691 | Advanced Programming – Visual Prog Haris Yaseen | This course marks the application itself: the architecture, the quality of the code, the interface a stranger has to use without help, the tests and the version-control history, and whether the deployed product actually works when it is opened cold. 15 marks, team. |
| GCDS552 | Database Systems Dr Nasreen | This course marks the data layer: the conceptual model, the normalised schema and its justification, the quality and performance of the queries the product actually runs, the transaction and backup arrangements, and the handling of any personal data collected. 15 marks, team. |
What to hand in
- GCCC554 Compiler Construction — A hosted, working application by session 11 in which this course's part — the parser, translator, rules engine or query layer — is running in production, with its grammar, test suite and AI declaration attached.
- GCCG562 HCI & Computer Graphics — A hosted, working interface by session 11 — the deployed product's front end, its prototype history, the usability test report naming participants, tasks and findings, and an accessibility check — filed with AI declaration.
- GCCS691 Advanced Programming – Visual Prog — A hosted, working application by session 11 that anyone with the link can use — with its source repository and commit history, its tests, a live deployment URL and a short architecture note — submitted with AI declaration.
- GCDS552 Database Systems — A hosted, working product by session 11 with a live database behind it — schema script, seed data, the five queries that matter with their execution plans, and a completed backup-and-restore run — filed with AI declaration.
How big the file is
The written file is 3,000 words for every member, plus or minus ten per cent — 15,000 words for a team of five, 12,000 for four, 9,000 for three — plus the artefacts: the evidence or data log with its instrument, interview notes and consent log, any program with its tests, the pitch deck, the AI declaration, the draft-to-final revision log, the two-page brief for the body the project reports to, delivered by the team, and the handover page (data, methods, what next year's team should do). In the venture and client lanes the live thing itself is the largest artefact. Each member owns one section of 3,000 words with their name on it, one artefact they built, and one part they can defend alone at viva. A lens note is 3,000 words on the same project. The full format is in "The Folio — required format", in the portal.
Dates
Rules for this lane
What counts as done
A live offer that a stranger could buy from, and at least one paying customer who is not a relative or a classmate, evidenced by a receipt or transaction record with the customer's identity removed.
Money
The University funds each venture team with Rs 25,000; how to draw it is announced by the Office of the Vice Chancellor before Session 7, when the build starts. Everything your customers pay goes into a University account opened for your team and held by Finance; refunds and the Rs 25,000 are paid from the same account. No takings are kept in a personal account or wallet. Every rupee in and out is accounted for, with receipts, in the venture file; unspent funds are returned. You may also raise sponsorship on top. The University is not a party to your venture and carries no liability for it.
Legal ground
No company is registered at this stage. You operate as a sole-proprietor offer; customer payments go into the University account Finance holds for your team, never a personal wallet. The University is not a party to your venture and carries no liability for it. You may not contract in the University's name.
Sign-off
Food, health, cosmetic and childcare offers need written approval, given through the portal, before anything is offered for sale.
Marks
Your mark does not depend on how much you sell. It depends on the evidence behind the gap, the quality of what you built, what the market told you, and the honesty of your post-mortem. A venture that fails and is analysed well can earn full marks.
Two teams to a project, at most
No project is taken by more than two teams, and two teams share one only on different sites or areas. Your convener records your choice in session 6 and may refuse a third team.
Before you leave campus
Whatever your lane: no team collects data before its ethics screen is cleared, and no team leaves campus before the fieldwork gate opens on Saturday 10 October, the duty phone exists and the team has signed out on the sign-out sheet. The duty number is on your field card.
Using AI
You are expected to use Claude and similar tools — to research, to build, to draft, to model numbers. Three rules. Check everything a tool gives you before you use it, and record the check. Declare what you used in the AI declaration bound into the file, as the HEC Framework on the Use of Generative AI Tools (2026) requires. Be able to explain, at the viva, everything your team built. Work you cannot explain is not credited to you. Undeclared use, or use to fabricate data, references or results, is academic misconduct. Never put real client, patient or examinee data, or anything identifying a real person, into a tool.
