CS404aBKK comprises 8 ECTS, or 240 hours of total learner workload across both parts. Part 1 accounts for 60 of those hours: 20 scheduled contact hours across 10 sessions of 2 hours; 8 hours of supervised project review, feedback, and consultation, distributed across the period to 16 October; and 32 hours of independent and team project work. ECTS measures total workload, not classroom time.

The 10 sessions of Part 1 are distributed across the block from 17 August to 4 September 2026, at three to four sessions per week. Each session combines a lecture segment with a supervised studio in which teams apply the concept introduced to their own product; the intervening days are given to team project work.

The distinguishing feature of the unit is a team project that runs continuously for nine weeks, from 17 August to 16 October. The project opens in Session 1 of Part 1 and is developed there through framing, domain modelling, architecture, and a first working slice. Between 7 and 25 September there are no taught sessions: teams continue development independently, supported by scheduled supervised reviews. From 28 September teams continue to develop their product through Part 2, applying to it the delivery, operations, and maintenance practices taught there. Project artefacts are submitted weekly throughout all nine weeks, so that the project forms a continuous record from the first week to the final submission.

Teams build a small software product from a common brief. The broad topic and a set of core requirements are given, but each team shapes its own product within that frame. Weekly artefacts comprise the domain story, user stories and acceptance criteria, the domain model, architecture documentation, source code, and the test suite. Session 10 includes a structured team retrospective with feedback. Participation in the studios and scheduled reviews is essential for successful group work.