Masters Project (60 Credits)

COMP66060 Masters Project (60 Credits) 60 Full year Postgraduate Taught Level 6 Ainur Begalinova Unit coordinator Department of Computer Science 1 FHEQ level (Framework for Higher Education Qualifications) ' Masters/Integrated Masters P4 ' European Credit Transfer & Accumulation System Rating : 30.0 The unit encompasses all aspects of a 60 credit project in advanced computer science.  The unit includes a project selection process, delivery of project skills and ethical/professional considerations, supervision of the work of the project and preparation of a report together with assessment of the project outcomes and learning achieved. Prerequisites: MSc level course units and research methods and professional issues course.Classes3 hours of lectures and activities in period 3 of semester 2 (weeks 1-6)Private study17 hours per week in period 3Project work: 50% of full time in period 4 (weeks 7-12)100% (full time) form end of Semester 2 exams to dissertation submission date (early September)Assessment(i) Project Overview and Plan (2,500 - 3,000 words)(ii)  Dissertation (approximately 17,000 words) Provide the skills to undertake, manage and deliver a technical project of approximately 3 months duration in the broad area of computer science.  Ensure that an appropriate level of professional competence in the realisation of a research project is demonstrated.Provides the skills to communicate the outcome of the work, principally in a written report.  ILO 1: Evaluate project outcomes using appropriate methods and provide a critical analysis of results, including limitations and potential improvements.ILO 2: Identify, evaluate, and analyse relevant academic and professional literature to establish the project context and justify technical decisions.ILO 3: Define the scope of an advanced computer science project and plan its execution over a three-month period, identifying project goals, objectives, risks, and constraints.ILO 4: Design, implement, and evaluate a technically accurate and reliable artefact of appropriate complexity and scope, while demonstrating professional responsibility through ethical, sustainable, and accountable practice.ILO 5: Communicate the project effectively through a video presentation that complements the written report and uses the medium appropriately.ILO 6: Produce a well-structured project report that demonstrates clear academic writing, appropriate use of figures and tables, and correct referencing.ILO 7: Draw clear and well-supported conclusions that relate outcomes to the stated project objectives.ILO 8: Implement the proposed methodology to a standard appropriate for an MSc project, demonstrating technical competence and effective problem solving.ILO 9: Design an appropriate technical methodology that addresses the project goals and is informed by existing research and best practice. Project management Research Written communication Other The lectures and study will cover the following topics:<ul> <li> Project planning / Research methods (3 hours supervised study – 17 hours private study)</li></ul>Introduction to the project and project planning. Define what constitutes a good plan and the important considerations. Understand how to define technical goals and milestones. Appreciate the importance of monitoring progress and adapting the project objectives as in light of progress made and learning gained including risk and contingency planning. <ul> <li> Ethics (3 hours supervised study – 17 hours private study)</li></ul>Students will be introduced to ethical frameworks. These frameworks will be useful in order to judge a number of ethical issues featured in media about AI, autonomous vehicles, software engineering, computer science and social networks. Coursework will involve assessing the ethical issues of a current computer science ethical dilemma using the ethical framework implemented by the School of Computer Science Ethics online tool. <ul> <li> Professional issues (3 hours supervised study – 17 hours private study)</li></ul>What should a CS professional know?Great software failuresHow should a professional talk?Purchasers, users, developersRight’ Decisions RepertoireDesigning in non-functional requirements <ul> <li> Research writing (3 hours supervised study – 17 hours private study)</li></ul>Communicate ideas simply and unambiguously. Getting comments of others on written work. Correctly structuring a report or paper. Use of proper archival references and correct formatting of references. Good use of figures/tables and informative captions. Proper use and formatting of mathematical objects (equations). <ul> <li> Systematic literature review (3 hours supervised study – 17 hours private study)</li></ul>Defining research questionsDeveloping a review protocolIdentifying relevant literatureSelecting studiesExtracting required dataReporting the review <ul> <li> Evaluation (& testing) (3 hours supervised study – 17 hours private study)</li></ul>Methods for empirical evaluation, analysis of evaluation data, testing and profiling.  1) Initial workshop style lecture/activities to understand the basics of project management, ethics and report writing.2) Individual or small group supervision throughout the project duration 4 Dissertation 85% 7 Oral assessment/presentation 15% Project Report: 85% Formative feedback from supervisor. Written feedback from two markers.Video demonstration due at the end of the project: 15% Written feedback from two markers.   MSc Adv Computer Science MSc Adv Computer Science PGDT Taught Component Mandatory MSc Adv Computer Science MSc Artificial Intelligence PGDT Taught Component Mandatory MSc Adv Computer Science Computer Security PGDT Taught Component Mandatory MSc Adv Computer Science Data and Knowledge Management PGDT Taught Component Mandatory MSc Adv Computer Science Digital Biology PGDT Taught Component Mandatory N Recommended texts:   Frank Bott, Professional Issues in Information Technology, 2nd edition, BCS, 2014, (ISBN 9781780171807)   B. Kitchenham et. al. Guidelines for performing systematic literature reviews in software engineering, School of Computer Science and Mathematics, Keele University, 2007. Supplementary reading:·Association for Computing Machinery Code of Ethics and Professional Conduct; <a href="http://www.acm.org/about/code-of-ethics.">http://www.acm.org/about/code-of-ethics.</a>·The Institute of Electrical and Electronics Engineers Code of Ethics; <a href="http://www.ieee.org/about/corporate/governance/p7-8.html">http://www.ieee.org/about/corporate/governance/p7-8.html</a>    H. Zhang, and M. A. Babar, and P. Tell, Identifying relevant studies in software engineering. Information and Software Technology, 53(6), pp.625-637, 2011.   Ian F. Alexander, A Taxonomy of Stakeholders: Human Roles in System Development, Issues and Trends in Technology and Human Interaction, Editor(s): Bernd, Carsten, Stahl (De Montfort University, UK) IRM Press. 25-71 pp., 2007   M. J. Carr, S. L. Konda, Taxonomy-Based Risk Identification, Software 2003   Michael Cavanagh, Second Order Project Management, Routledge, 2012 (ISBN 9781409410942)   Lectures 20 0 580