Distributed and Enterprise Software Development (DESD)�UFCFTR-30-3

Term 2 Delivery & Assessment Task 2

DESD UFCFTR-30-3

Term 2 Delivery

DESD UFCFTR-30-3

• 1-hour lecture + 2-hour practice per week

​

• Spring Term (TB2) focuses on:
• Containerisation and Deployment
• Development of Enterprise Systems & Services using Django/Django Rest Framework and Docker
• Practicing Agile Development (Scrum)
• Group work (3 Sprints)

​

• Please make effort to attend all sessions and sign in attendance via My Attendance tool.

Timetable

DESD UFCFTR-30-3

What to cover? (Spring Term – TB2)

• Development with Distributed Computing
• Containerisation
• “Docker” for container development
• Distributed development & deployment
• “Multi-container” for local deployment & deployment
• A Web application as an Enterprise System, which consists of:
• Advance API Development concepts
• Components developed in house
• Components recycled
• Use of persistent data (DBs, e.g. Postgres, MySQL)
• Use of services (web services, micro services)
• Security (Authentication / Authorisation)

​

DESD UFCFTR-30-3

Teaching & Learning Tools (Spring Term – TB2)

• Following agile methodology in project management
• Scrum-like agile management
• Sprint-wise practice and delivery
• Customer is in loop (customer = tutor)
• Three-week Sprints
• Sprint Review to be provided after each sprint
• Use of commonly used tools
• Version control software such as GitHub/GitLab,
• Professional Project Management tools such as Jira, Microsoft Project to be used
• No reports (except Contributions Matrix) required!

​

​

DESD UFCF85-30-3

Practicals (Spring Term – TB2)

• A series of development activities are planned for practical sessions
• Django/Django Rest Framework is chosen to use as development framework
• Docker is to be practiced for containerisation and deployment
• You’re the development team in need 🡪 Teamwork will be practiced and assessed accordingly
• Timetabled in different Sessions, as you are notified;
• In room 3Q44 and 2Q13a

DESD UFCFTR-30-3

Practicals

• Tools to be used are:-
• MS Teams: The working teams are expected to meet up and do practical work collectively using this tool.
• BB Groups: Each group is allocated a space on BB to use, for communication, exchanging data etc.
• GitHub/GitLab: The worked out and developed code is expected to be stored in GitHub repos and to be made available to review.
• A professional project management (e.g., Jira, Microsoft Project, Trello, etc) tool of your choice should be used.
• Others,… based on choice again.

​

DESD UFCFTR-30-3

At the end of each Sprint, a Sprint Review will take place. A 10-minute demo – live/record – your choice!

Assessment Task 2

• Group Project – Enterprise Software Development:
• Assessment Brief will be released on 3^rd February 2026
• Weighing 60%
• Develop/Implement the project based on the same case study of Task 1
• Required Frameworks and Tools: Django/Django Rest Framework, Docker
• Due on last week Spring term (academic Week 38)
• Final Demos will be scheduled in academic Week 39

DESD UFCFTR-30-3

Group Formation Guidelines – �Requirements & Deadlines

• Size: 4–5 members per group (maximum 5).
• Pathway: All members must belong to the same pathway.
• Deadline: You may self-select your group until 14th February 2026.
• Allocation: After this date, any student without a group will be randomly assigned to a new group or added to an existing group with fewer than 5 members.
• Lock Date: Group membership is final once Sprint 1 begins on 16th February 2026.

​

​

DESD UFCFTR-30-3

Group Formation Guidelines – �Cross-Session Logistics

• Formation: Groups may be formed across different practical sessions with explicit consent from the module team – please check with us.
• Scheduling: As groups are required to attend weekly standups with the tutor, members should ideally request a timetable change to align their sessions.
• If a formal change is not possible, the group must agree on a single common session to attend consistently throughout the term and notify the tutor.
• Attendance Code: Please note that attendance codes are strictly linked to your official timetable sessions and will not function for sessions you are not registered to attend.

DESD UFCFTR-30-3

Group Work (Task 2)

• A group project, in-class/online demonstration, of a Python Django/Django Rest application
• The group effort will be assessed. However, individual contributions matter!
• You need to use version control software, GitHub/GitLab, to record your team-works/commits.
• Kanban facility of GitHub is also useful for project management,
• You are expected to work together with your group members during the practical sessions.

DESD UFCFTR-30-3

Group Project (Task 2)

• This assessment will be an opportunity to demonstrate the knowledge and skills you have acquired from the practicals
• Agility in Assessment: Team effort will be assessed in 3 stages:
• First 3 weeks of TB2 –re for preparation and forming groups.
• Sprint 1: Planning, early delivery (15%)
• Sprint 2: Main architecture, rough components (15%)
• Sprint 3: Complete application us delivered (50%)
• Where is the remaining 20%? – Your individual contributions and performance! – See the Assessment specs for more details.

DESD UFCFTR-30-3

Stand-ups will take place in Spring Term – TB2, the best 6 of them contribute to your individual marks!

Feedback

• Formative Feedback:
• We plan to provide feedback to group works during practical sessions. Please ask for feedback if you feel you need more details on practical works.
• Feedback is not only about your mistakes or areas to be improved but also about appreciation of your achievements.
• Summative Feedback:
• Provided once you have submitted your assessment materials. This includes the marks decided for the work with strengths and weaknesses, which justify the mark decided.
• You are entitled to request for feedback 2 weeks after your submissions.

DESD UFCFTR-30-3