Site Tools


software_engineering_project

This is an old revision of the document!


Software Engineering Project 2013/14

This page contains details for the CM3301 module. For this module you will have to produce the following marked deliverables:

  • Team report (requirements specification and project plan) in week 8, first semester, worth 15% of the total module mark.
  • Presentation to include demonstration of system in week 8, second semester, woth 10% of the total module mark.
  • Final report of up to 25,000 words and viva due at the end of the second semester, worth 75% of the total module mark.

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 module leader Frank Langbein.

Viva Exam

The viva exam for your Final Year Project will be timetabled any time in the University's Examinations period. You must therefore remain available at the University until the end of the Examinations. You should NOT arrange any holidays, employment or other commitments until after this date. The timetable for the viva exams will be published as soon as possible after the submission deadline.

Note, that not attending your viva exam will result in you failing the module (unless you have extenuating circumstances in which case the viva exam will be rescheduled).

Note to supervisors and moderators, you also must be available during that time period (Let Helen Williams know about any planned, unavoidable absences).

Project 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.

  • 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.

Project Writing Guide

Technical Guides

Please find further information below on how to use PATS, prepare the various deliverables in a suitable format and related technical issues.

  • Submission Guide: General instructions on how to submit the reports and plans for your final year project via PATS.
  • PDF Guide: Instructions on how to create PDF files required for all submissions via PATS.
  • Checksums: Instructions on how to generate file checksums to verify your submissions and for alternative submission mechanisms (as described in the Submission Guide).

Project Coordinator

software_engineering_project.1379598218.txt.gz ยท Last modified: 2013/09/19 14:43 by scmfcl