User Tools


software_engineering_project

Software Engineering Project

This is the main page for information about the 40 credit two-term final year module CM3301.

Below are some guides to help you preparing these deliverables and submitting the reports on PATS. These are still under development, so please discuss the specifics with your supervisor and the project coordinator Frank Langbein.

Project Selection

At the beginning of the third year you are going to select your final year team project. Below are guides on how to propose projects on PATS and how you can see projects suggested by staff.

For software engineering team projects special arrangements apply and you will be notified by e-mail on these. We will arrange a meeting with you to discuss which project each team will be taking on.

Deliverables

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 under your PATS project details.

  • Team Report: You must submit a team report on the requirements specification and project plan in the first semester(by end of week 8 of the first semester, at most 5,000 words per team member, worth 15%).
  • Team Presentation: A team presentation on the project, including a demonstration of system must be submitted in the second semester (in week 8 of the second semester, up to 1h including audience questions and discussions, worth 10%).
  • Individual Report: An individual report on your work on the project must be submitted by the end of the second semester (by the beginning of week 12 of the second semester, at most 20,000 words, worth 75%).
  • Project Viva: A project viva will take place after the exams for every final year project.
  • Project Publication: Details about how to publish your project online in PATS.

For information about how to submit a report via PATS please see the Submission Guide. Note that in order to get an extension to the submission deadline the general coursework submission extension guidelines apply.

Guides

These guides are meant to help you produce good final year project reports. 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 in respect of 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. 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 use PATS, prepare the various deliverables in a suitable format and related technical issues are available in these guides:

  • Submission Guide: General instructions on how to submit the deliverbales via PATS.
  • PDF Guide: Instructions on how to generate PDF files.

Project Coordinator

software_engineering_project.txt · Last modified: 2014/04/03 10:43 by scmfcl