The course represents a total student workload of 180 hours, distributed as follows:

* 45 hours of contact teaching: 15 three-hour classroom sessions combining lectures, guided practice, and project work.

* 15 hours of office hours with the lecturer: individual consultations, project feedback, technical support, and discussion of architectural decisions.

* 60 hours of independent project work: design, implementation, testing, documentation, and preparation of the individual Django project.

* 60 hours of independent study and preparation: assigned reading, study of technical documentation, short practical exercises, preparation for classroom sessions, revision of course concepts, and preparation of project demonstrations and presentations.

Each three-hour classroom session combines a short theoretical lecture with practical work. A typical session includes:

* Short lecture and discussion: introduction of software design concepts, architectural principles, and practical examples.

* Guided practice: focused programming exercises, design tasks, code analysis, refactoring, or live implementation.

* Individual project work: application of the introduced concepts to the student’s own Django project.

* Review and reflection: code review, architectural discussion, testing, demonstration, and feedback.

Students develop one individual software project throughout the course. The project is implemented incrementally during three five-day micro-sprints. Each sprint introduces a new group of software design concepts and concludes with a working project milestone, a short demonstration, and a review of the student’s implementation and architectural decisions.

Office hours provide students with an opportunity to discuss project scope, resolve technical difficulties, receive individual feedback, and review proposed design decisions. Independent study supports the classroom activities through selected readings, documentation research, practical exercises, and preparation for subsequent project milestones.