This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| large_one_term_individual_project [2014/01/13 13:51] – [Deliverables] scmfcl | large_one_term_individual_project [2015/09/24 16:24] (current) – removed scmfcl | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Large One Term Individual Project ====== | ||
| - | |||
| - | This is the main page for information about the 40 credit one-term final year module [[http:// | ||
| - | |||
| - | ===== Project Selection ===== | ||
| - | |||
| - | In term 2 of the second year you are going to select your final year project. Below are guides on how to write and select your project using PATS. | ||
| - | |||
| - | * [[Project Proposals]]: | ||
| - | * [[Project Selection]]: | ||
| - | * [[Project Supervision]]: | ||
| - | * [[Supervisors]]:: | ||
| - | |||
| - | ===== 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. | ||
| - | |||
| - | * [[Initial Plan]]: You must submit an initial plan, which is marked by your supervisor and moderator at the start of the semester (in week 1, at most 2,000 words, worth 5%). | ||
| - | * [[Project Report]]: A final report must be submitted at the end of the semester (at most 25,000 words, worth 95%) | ||
| - | * [[Project Viva]]: A project viva will take place after the exams for every final year project. | ||
| - | * [[Project Publication]]: | ||
| - | |||
| - | ===== 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, | ||
| - | |||
| - | * 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 final report. | ||
| - | * [[Sources for Further Guidance]]: a collection of useful references. | ||
| - | |||
| - | 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. | ||