Module Details |
The information contained in this module specification was correct at the time of publication but may be subject to change, either during the session because of unforeseen circumstances, or following review of the module at the end of the session. Queries about the module should be directed to the member of staff with responsibility for the module. |
Title | MSC PROJECT | ||
Code | COMP702 | ||
Coordinator |
Dr RA Martin Computer Science Russell.Martin@liverpool.ac.uk |
||
Year | CATS Level | Semester | CATS Value |
Session 2017-18 | Level 7 FHEQ | Summer (June-September) | 60 |
Aims |
|
To give experience of carrying out a large piece of individual work and in producing a dissertation. To enhance communication skills, both oral and written. < span style="display:inline-block" id="ms-rterangepaste-end" /> |
Learning Outcomes |
|
After completing the module students should be able to: |
|
Make use of the qualities and transferable skills necessary for the conduct of a Computer Science project: (i) the exercise of initiative and personal responsibility, (ii) decision making in complex situations, (iii) risk identification (including, as appropriate, commercial and scientific risk), assessment and control, and (iv) the independent learning ability required for continuing professional development |
|
Demonstrate effective time management, self-direction and originality in
carrying out a project in the domain of Computer Science |
|
Locate and make use of information relevant to a given IT project |
|
Design a solution to a substantial IT problem |
|
Implement and test potential solutions to IT problems |
|
Evaluate critically, as relevant to the project, current research and advanced scholarship in Computer Science and evaluate their own work. |
|
Conduct and evaluate critically the project within the professional, legal, social and ethical framework in Computer Science and Sortware Engineering. |
|
Prepare and deliver formal presentations. | |
Prepare and deliver a demonstration of software |
|
Structure and write a dissertation describing their project |
Syllabus |
|
1 |
The main aim of an MSc dissertation project is for a student to develop and demonstrate
autonomy in the management and development of realistic projects in computer science,
either research or application oriented.
Although new technical skills may be acquired, this is not the main aim.
At the end of the project a student should have demonstrated the ability to initiate, plan,
manage and deliver a complete IT project for a customer or research supervisor.
The delivery of the project will include giving interim presentations describing important
stages of the project, and a final dissertation describing the project as a whole.Level M Projects are not necessarily expected to involve original research in the sense of
making new scientific discoveries.
However, at level M there should be some degree of scholarly added value attached to the project
(not in the sense of "what new subject a student may have learned from undertaking the project",
but "what contribution th
e project makes to the knowledge of others") regardless of whether
the project is a practical one or a research oriented one. MSc projects are not required to be fully-fledged research projects in their own right; but should add some seed of original thinking, innovative approach, interesting or beneficial contribution to the existing body of knowledge. The aim is not necessarily "to do something that has never been done before", but to present a new "angle" or "view point" on something that has been done before. For example:
Whatever the case, the key characteristics of the work carried out should be:
|
Teaching and Learning Strategies |
|
Seminar - |
Teaching Schedule |
Lectures | Seminars | Tutorials | Lab Practicals | Fieldwork Placement | Other | TOTAL | |
Study Hours |
1 |
1 | |||||
Timetable (if known) | |||||||
Private Study | 599 | ||||||
TOTAL HOURS | 600 |
Assessment |
||||||
EXAM | Duration | Timing (Semester) |
% of final mark |
Resit/resubmission opportunity |
Penalty for late submission |
Notes |
CONTINUOUS | Duration | Timing (Semester) |
% of final mark |
Resit/resubmission opportunity |
Penalty for late submission |
Notes |
Coursework | Approximately 160 ho | End of Week 4 (June) | 20 | No reassessment opportunity | Standard UoL penalty applies | Specification and Proposed Design There is no reassessment opportunity, In line with University policy |
Coursework | Approximately 320 ho | End of Week 12 (August) | 20 | No reassessment opportunity | Standard UoL penalty applies | Demonstration/Presentation of Results There is no reassessment opportunity, In line with University policy |
Coursework | Approximately 120 ho | Middle of September | 60 | No reassessment opportunity | Standard UoL penalty applies | Dissertation There is no reassessment opportunity, In line with University policy Notes (applying to all assessments) Specification and Proposed Design: Report and demonstration of the design, this work is not marked anonymously. Demonstration/Presentation of Results: Report and demonstration of software (where applicable), this work is not marked anonymously. Dissertation: This work is not marked anonymously. |
Recommended Texts |
|
Reading lists are managed at readinglists.liverpool.ac.uk. Click here to access the reading lists for this module. Explanation of Reading List: |