One client project carried from September to Design Day in December, built on a budget of 75 dollars. There is no final exam, and the marks come from ten deliverables and four tests.
Only PD A has a date set by the course. The team writes its own dates for PD B through J inside PD A, against the milestone table below, and is then held to the plan it wrote. The teaching team can impose dates later if that stops working.
One team member submits, as a PDF to Brightspace unless stated otherwise, and the whole team gets that mark. Each deliverable can be resubmitted once after feedback from the teaching assistant or project manager, inside a set window.
| Done | PD | Milestone | When | Weight |
|---|---|---|---|---|
| A | Project plan, and the team's own dates for everything below | Fri 18 Sept Client meeting 1, lab 2 | 5 | |
| B and C | Client meeting 2 | Lab 4 | 10 and 5 | |
| D | Design review in class | Lecture 10 or 11 | 13 | |
| E | Project progress presentation | Lab 6 | 5 | |
| F | Client meeting 3 | Lab 7 | 10 | |
| G | Project work in class | Lecture 19 | 7 | |
| H | Design day and client meeting 4 | Around lab 11 | 15 | |
| I and J | End of course | End of course | 5 and 10 |
D and H carry nearly a third of the deliverable marks between them. D is the in-class design review and H covers Design Day with the fourth client meeting. The weights in the last column compare the deliverables with each other. The project and client evaluation together carry 50 percent of the course.
An AI Attestation item is listed under Project Deliverables. It asks for every prompt with its output, what influenced the work, what was verified and any notes. Writing it as the term goes takes minutes; reconstructing it at the end takes hours.
Attendance is graded. Five labs have work due at 14:30 on the Saturday, before the lab starts.
| Done | Date | Lab | Due at 14:30 that day |
|---|---|---|---|
| Sat 19 Sept | Lab 1, introduction and circuits | — | |
| Sat 26 Sept | Client meeting 1 | Circuits | |
| Sat 3 Oct | Mill and lathe | Shop fundamentals pre-lab | |
| Sat 10 Oct | Client meeting 2 | Mill and lathe | |
| Sat 17 Oct | Arduino and bill of materials | — | |
| Sat 24 Oct | Progress presentations | Arduino and bill of materials | |
| Sat 7 Nov | Soldering | — | |
| Sat 14 Nov | Client meeting 3 | Soldering | |
| Sat 21 Nov | Project work | — | |
| Sat 28 Nov | Project work | — | |
| Sat 5 Dec | Project work, Design Day week | — |
The dates on the Brightspace dropbox and calendar belong to other lab sections. The B4 dates are written into the description text of each lab topic, which is where the table above comes from. Reading week falls 25 to 31 October, which is why there is no lab on 31 October.
The Lab Test day is still unconfirmed. It appears on both 17 and 20 November in the material published so far, and the answer comes from the teaching team.
forms.office.com/r/FF9A621UJw. No date has been stated for it.GNG2101-context.md. Moving them here is a session of its own.The project list is not a topic in the Brightspace content tree. It is a link inside the description text of Content → Project Deliverables → Information for the project, which Brightspace does not render in the topic list. The milestone table and the confidentiality form are in that same module.
Per-section deadlines work the same way, written into each lab topic's description. The dropbox does not show them. Announcements are Prof. Lakhani's main channel, and email is answered within one business day.
The course home is Brightspace organisation unit 602711. Source material stays in the GNG2101 folder on disk, and this page is published from the course-hub repository.