This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
software_engineering_project [2013/09/19 14:43] – created scmfcl | software_engineering_project [2022/10/06 12:02] (current) – removed scmfcl | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== 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, | ||
- | |||
- | ==== Viva Exam ==== | ||
- | |||
- | The viva exam for your Final Year Project will be timetabled any time in the University' | ||
- | |||
- | 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, | ||
- | |||
- | * [[Project Viva]]: A project viva will take place after the exams for every final year project. | ||
- | * [[project_publication|Project Publication]]: | ||
- | |||
- | ===== Project Writing Guide ===== | ||
- | |||
- | * General guides for writing reports: | ||
- | * [[Gathering Material]] | ||
- | * [[Arranging Material and Structuring the Project Report]] | ||
- | * [[Writing a Project Report]] | ||
- | * [[Using Descriptive Devices]] | ||
- | * [[Supporting Material]] | ||
- | * [[Main Recommendations]] | ||
- | * [[Typesetting Rules]]: follow these rules to typeset your interim and final report. | ||
- | * [[Sources for Further Guidance]]: a collection of useful references. | ||
- | |||
- | ===== 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]]: | ||
- | |||
- | ====== Project Coordinator ====== | ||
- | |||
- | [[http:// |