Module Specification

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.
1. Module Title MSc Project
2. Module Code COMP702
3. Year Session 2023-24
4. Originating Department Computer Science
5. Faculty Fac of Science & Engineering
6. Semester Summer (June-September)
7. CATS Level Level 7 FHEQ
8. CATS Value 60
9. Member of staff with responsibility for the module
Professor PE Dunne Computer Science P.E.Dunne@liverpool.ac.uk
10. Module Moderator
11. Other Contributing Departments  
12. Other Staff Teaching on this Module
Mrs J Birtall School of Electrical Engineering, Electronics and Computer Science Judith.Birtall@liverpool.ac.uk
13. Board of Studies
14. Mode of Delivery
15. Location Main Liverpool City Campus
    Lectures Seminars Tutorials Lab Practicals Fieldwork Placement Other TOTAL
16. Study Hours   1

        1
17.

Private Study

599
18.

TOTAL HOURS

600
 
    Lectures Seminars Tutorials Lab Practicals Fieldwork Placement Other
19. Timetable (if known)            
 
20. Pre-requisites before taking this module (other modules and/or general educational/academic requirements):

COMP516 Research Methods in Computer Science
21. Modules for which this module is a pre-requisite:

 
22. Co-requisite modules:

 
23. Linked Modules:

 
24. Programme(s) (including Year of Study) to which this module is available on a mandatory basis:

25. Programme(s) (including Year of Study) to which this module is available on a required basis:

26. Programme(s) (including Year of Study) to which this module is available on an optional basis:

27. Aims
 

To give students the opportunity to work in a guided but independent fashion to explore a substantial problem in depth, making practical use of principles, techniques and methodologies acquired elsewhere in the programme.
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.

 
28. Learning Outcomes
 

(LO1) After completing the module students should be able to: Investigate and specify a substantial problem in the domain of Computer Science, to place it in the context of related work including, as appropriate, Computer Science reserach, and to produce a plan to address this problem

 

(LO2) 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

 

(LO3) Demonstrate effective time management, self-direction and originality in carrying out a project in the domain of Computer Science

 

(LO4) Locate and make use of information relevant to a given IT project

 

(LO5) Design a solution to a substantial IT problem

 

(LO6) Implement and test potential solutions to IT problems

 

(LO7) Evaluate critically, as relevant to the project, current research and advanced scholarship in Computer Science, evaluate their own work, and participate effectively in the process of peer review of other projects

 

(LO8) Conduct and evaulate critically the project within the professional, legal, social and ethical framework in Computer Science and Sortware Engineering

 

(LO9) Prepare and deliver formal presentations

 

(LO10) Prepare and deliver a demonstration of software

 

(LO11) Structure and write a dissertation describing their project

 

(S1) Communication (oral, written and visual) - Presentation skills – oral

 

(S2) Communication (oral, written and visual) - Presentation skills - written

 

(S3) Communication (oral, written and visual) - Academic writing (inc. referencing skills)

 

(S4) Time and project management - Project planning

 

(S5) Critical thinking and problem solving - Critical analysis

 

(S6) Critical thinking and problem solving - Evaluation

 

(S7) Commercial awareness - Ability to analyse/balance risk and reward

 
29. Teaching and Learning Strategies
 

Teaching Method 1 - Seminar
Description:
Attendance Recorded: Not yet decided

Due to Covid-19, in 2021/22, introductory materials for the project will be delivered online asynchronously and meetings with supervisor will take place online or on-campus in agreement with individual supervisor.

 
30. Syllabus
   

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 the p roject 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:
The critical comparison of some complimentary recent innovations.
The extension or adaptation of some recent innovation so that it becomes in some sense better, e.g. faster, more accurate, requires less storage etc.
The application of some recent innovation to a generic application area where it has not yet been applied.
The combination/concatenation of some recent innovations in a novel manner not previous ly recorded in the literature.

Whatever the case, the key characteristics of the work carried out should be:
Originality: Originality in the application of knowledge, togetherwith a practical application of techniques of research and enquiry.
Generalization: Even when the project has a very specific target, students should address it in a way, which will make the resultspotentially applicable in a broader context.
Critical evaluation: Design decisions made by students in the courseof the project should be made in the context of a critical examination ofalternatives, and the students should subject their results and conclusions to the same rigorous analysis.

All projects should contain the following elements: research, design, realisation and evaluation. Particular projects are allocated on an individual basis.

 
31. Recommended Texts
  Reading lists are managed at readinglists.liverpool.ac.uk. Click here to access the reading lists for this module.
 

Assessment

32. EXAM Duration Timing
(Semester)
% of
final
mark
Resit/resubmission
opportunity
Penalty for late
submission
Notes
   
33. CONTINUOUS Duration Timing
(Semester)
% of
final
mark
Resit/resubmission
opportunity
Penalty for late
submission
Notes
  (702) Dissertation Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Middle of September 0 70
  (702.2) Demonstration/Presentation of Results Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :End of Week 12 (August) 0 15
  (702.1) Specification and Proposed Design Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :End of Week 4 (June) 0 15