This is the repository for the 2026-7 Software Engineering Project, where we'll release the Weekly Workbooks. These have the teaching information, lecture slides and tasks you'll need to complete every week.
The Assessments folder incudes the guide to the presentations, information about how we assess you and the Release checklist that you'll need to upload after each release (MVP, Beta and Final Releases).
Useful things has information that might be useful, like where you can work as a team, how to book rooms to meet clients and how to get software, tech services and hardware for your project.
The main SPE-UoB organisation contains all the student repos from the past few years, so you can look at what other students have done in SEP and see what other teams are doing this year.
We also have the Knowledge hub with information on various topics that previous years' students have written for us, including how to do common tasks.
The ILOs are what you are assessed on. For SEP, the ILOs are:
| On completion of this unit, students will be able to: * Develop software systems within a mature and repeatable Software Development process. * Apply Agile Principles & Practices in the development of systems of significant scale. * Select and employ development support tools (as appropriate to the project being undertaken). * Apply basic principles of project management. * Work effectively within real-world development contexts and with clients. * Collaborate effectively within small teams. * Identify the presence of (and employ techniques to mitigate the impact of) project uncertainty and risk. |
There is more information about how you will be assessed in the assessments folder.
Please check your timetable for the lectures, workshops and drop-ins.
The MVP, Beta and Final Release dates are the latest possible dates - you should arrange a time to meet your client to hand over the releases and get feedback before these dates.
| Week | Date | Event |
|---|---|---|
| 9 | 19 November 2026 | MVP Release to client and Blackboard submission |
| 10 | 23-7 November 2026 | Formative MVP vivas |
| 15 | 1 February 2026 | SEP Testing Day |
| 16 | TBC | Testathon |
| 17 | 18 February 2027 | Beta Release to client and Blackboard submission |
| 18 | Reading Week | |
| 19 | 1-6 March 2027 | Formative Beta Release vivas |
| 20 | TBC | Testathon |
| 23 | 19 April 2027 | SEP poster day and client celebration |
| 24 | 29 April 2027 | Final Release to client and Blackboard submission |
| Exam period | 4-22 May 2027 | Final summative vivas |
Viva dates will be added to your timetable nearer the time.
It is important that your email address is correct in the gitconfigs, so that Github can match up your commits with your account.
There is more information about setting up your commit email address in this GitHub doc
You can check if your set-up is correct by trying git config --list and if it's not set up properly, user.email will be either not there or empty. Which could be fixed with
git config --global user.email "name@domain.example"
If you've tried this and your commits still aren't being logged correctly, ask in the Teams Q&A channel and one of the TAs will help you.
If you have questions or problems that your mentor can't help with in the mentor meetings:
- ask in the Teams Q&A channel
- come to the Drop Ins on Fridays
- or contact Jialin Deng.