This is an old revision of the document!
This is the main page for information about the 40 credit two-semester software engineering project module CM3301.
At the start of the module you will be given a list of group projects proposed by some members of staff. You will be asked to indicate your preferences for the projects based on the descriptions. You may also want to ask the members of staff proposing projects for more details or clarify anything in the description. By the middle of week 1 you will have to submit your preferences and we will then assign you to a team, based on your preferences and past performance to achieve a good balance of skills for each team. Each team will have an assigned project with one supervisor who initially will be interacting with the team as a whole and later on have individual meetings with each member to discuss their part of the project. Each team will also have a moderator assigned to them.
You will be notified via learning central announcements and e-mails on the detailed arrangements and deadlines. The overall module arrangements and projects will also be discussed with you in the lectures.
This is an overview of the expected deliverables and related tasks you have to execute for your project. Details on these deliverables and tasks are available on the linked pages. You also find the required deliverables with their submission deadlines on learning central.
Reports and presentation material will have to be submitted on learning central. For details see the instructions for the assignments there.
These guides are meant to help you produce good final year project reports. They are generic and have to be adapted to your specific module and project requirements. A good report is one that presents your project work concisely and effectively. It should contain various materials relevant to the work you have undertaken for your project; it should be organised into a logical framework; and it should be supported by written material that follows well-established academic conventions in a consistent fashion.
An important point to remember is that the report should describe your work. Large chunks of bookwork describing standard material are unnecessary. You should simply refer to such material where necessary - assume that your reader is a competent computer or information systems theorist or practitioner as suitable in the wider context of your project. The guidelines here are arranged roughly in the order that you will need them.
Your project supervisor will guide you on what it is reasonable to expect a project in your chosen topic to deliver. However, all projects are required to justify all decisions made at every stage of research and the development of appropriate deliverables, including the choice of approach.
Further information on how to prepare the various deliverables in a suitable format and related technical issues are available in these guides: