Note: This unit version is currently being edited and is subject to change!

COMP5702: IT Research Project A (2020 - Semester 1)

Download UoS Outline

Unit: COMP5702: IT Research Project A (12 CP)
Mode: Normal-Day
On Offer: Yes
Level: Postgraduate
Faculty/School: School of Computer Science
Unit Coordinator/s: Dr Kuan, Kevin
Session options: Semester 1, Semester 2
Versions for this Unit:
Campus: Camperdown/Darlington
Pre-Requisites: None.
Prohibitions: COMP5707 OR COMP5708 OR COMP5703. Students enrolling (and eligible) for the IT Research Project are not eligible to enrol in the IT Capstone Project Units.
Brief Handbook Description: The Information Technology Research Project provides an opportunity for students to carry out a defined piece of independent research or design. These skills include the capacity to define a research or design question, show how it relates to existing knowledge and carry out the research or design in a systematic manner. Students will be expected to define an original research project that demonstrates their prior learning in their advanced IT specialist domain (MIT) or the management of IT (MITM) or both technical and IT management domains (MIT/MITM). The results will be presented in a final project presentation and report.

It is not expected that the project outcomes from this unit will represent a significant contribution to new knowledge. The unit aims to provide students with the opportunity to carry out a defined piece of independent research work in a setting and manner that fosters the development of IT skills in research.
Assumed Knowledge: INFO5993. Students should take INFO5993 - Research Methods in IT either concurrently or prior to undertaking this project unit.
Additional Notes: A candidate for the MIT, MITM or MIT / MITM who has completed 24 credit points from Core, Specialist or Foundation units of study may take this unit.

Eligible students for the IT Research project will be required to complete both COMP5702 (12CPS) & COMP5704 (6 CPS), totaling 18 CPS. In addition, students should take INFO5993 - Research Methods in IT either concurrently or prior to undertaking this project unit.

Department permission required for enrolment. COMP5702 and COMP5704 together form the Research thesis of MIT/MITM Research track. The same mark and grade is given for both units after completion of the project.
Department Permission Department permission is required for enrollment in this session.
Lecturer/s: Dr Kuan, Kevin
Timetable: COMP5702 Timetable
Time Commitment:
# Activity Name Hours per Week Sessions per Week Weeks per Semester
1 Research 22.00 1
2 Meeting 2.00 1 13

Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.

Unassigned Outcomes
1. The ability to utilise prior domain knowledge to define and develop a research/development project relevant to an advanced IT specialist domain (MIT) or the management of IT (MITM) or both technical and IT management domains (MIT/MITM).
2. Ability to initiate, formulate and plan an original IT research project based on research and development.
3. Ability to analyse and synthesise information, draw appropriate conclusions and present those conclusions in context, with due consideration of methods and assumptions involved.
4. Demonstrate knowledge of recent IT research literature and possess an ability to apply research to their own project.
5. Ability to document, report and present project work undertaken to engage an academic and/or professional audience.
6. Ability to develop, substantiate and articulate professional positions on issues relevant to the chosen area of practice. Ability to critically reflect on and evaluate the outcomes and process of the project.
7. Ability to plan a semester-long project, incorporating risk mitigation strategies and follow the plan methodically.
Assessment Methods:
# Name Group Weight Due Week Outcomes
1 Project Proposal* No 5.00 Week 5 2, 5,
2 Progress Report #1* Yes 5.00 Week 13 2, 5, 7,
3 Progress Report #2 Yes 5.00 Following Semester 2, 5, 7,
4 Presentation/Seminar* Yes 10.00 Following Semester 1, 3, 4, 5, 6,
5 Final Report/Deliverable Yes 75.00 Following Semester 1, 2, 3, 4, 5, 6, 7,
Assessment Description: * indicates an assessment tasks which must be repeated if a student misses it due to special considerations.

Assessment Overview: The IT Research Project can be in performed in teams or as individual expert who is working with client and other stakeholders, however individual contribution will be assessed.

The main assessment tasks are based on three areas (depending on the nature of the task the first two might be combined into a single document):

(i) the deliverables from the project that would be given to the `client` (who may be external, internal to the School, or even an implied type of person who would desire this work to be done, without there being a concrete individual). Example deliverables could be some software, an installed system, a report discussing some alternatives, an analysis of a marketplace, a design, etc;

(ii) A final report on the project for the supervisor, which would include an account of the purpose and context, a detailed description of the process which took place, an evaluation of the outcomes and the process;

(iii) An oral presentation/seminar of the project outcomes for an audience of both client and supervisor.

Students can work either individually or as part of a group, but will have their individual contribution assessed as part of any group project outcomes.

Students will receive a mark of UCN (Unit Continuing) for IT Research Project A if they have shown sufficient progress to warrant continuing on to IT Research Project B. The final grade for IT Research Project A and B is based on the work done in IT Research Project A and B as a whole. Any marks awarded in IT Research Project A will be incorporated into calculations for the final grade of the two units.

Proposal and Progress Report: Research Plan & Progress Report. A Research Plan and Progress Report of around 15 pages is required from each student. Should include problem/task specification, literature survey, proposed methodology, expected outcomes, progress in first semester and proposed timeline.

Presentation/Seminar: Oral Presentation and Poster. Each student will be required to participate in an individual oral and poster presentations. Presentations will be approximately 15-20 minutes duration. Poster should be printed on an A1 page and summarise the group`s research work, including the main conclusions.

Participation in presentations is compulsory. Failure to deliver a scheduled seminar will result in a fail grade for the project units.

Participation: Management of Research Project. Projects may be undertaken in groups but marking of project management component is based on individual contributions.

Final Report: Two hard-bound copies of the final report should be submitted for marking to the school administration office by end of Week 13 of the final semester of completion. Statement identifying the specific contributions of the student and others must be included. Maximum length is 50 pages (including tables, figures and references, but not appendices). The final report must contain a page stating the specific contributions of the student and that of others involved. While the thesis project work is conducted in groups, the final project itself must be written and submitted individually. Students should closely consult the Project Guidelines handout and Marking Sheet for content and formatting requirements.

Each report is assessed by two people who meet the following requirements: (a) neither of them have played a supervisory role in the research project (b) at least one of them is an academic staff from the School of IT (usually both examiners meet this requirement) (c) one of them is from the research area and is knowledgeable about the topic of the report (d) one of them is from outside the research area.

There may be statistically defensible moderation when combining the marks from each component to ensure consistency of marking between markers, and alignment of final grades with unit outcomes.
Grade Type Description
Minimum Pass Requirement It is a policy of the School of Computer Science that in order to pass this unit, a student must achieve at least 40% in the written examination. For subjects without a final exam, the 40% minimum requirement applies to the corresponding major assessment component specified by the lecturer. A student must also achieve an overall final mark of 50 or more. Any student not meeting these requirements may be given a maximum final mark of no more than 45 regardless of their average.
Grading Schema Final grades in this unit are awarded at levels of HD (High Distinction), D (Distinction), CR (Credit), P (Pass) and F (Fail) as defined by University of Sydney Assessment Policy. Details of the Assessment Policy are available on the Policies website at . Standards for grades in individual assessment tasks and the summative method for obtaining a final mark in the unit will be set out in a marking guide supplied by the unit coordinator.
Policies & Procedures: IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism.

In assessing a piece of submitted work, the School of Computer Science may reproduce it entirely, may provide a copy to another member of faculty, and/or to an external plagiarism checking service or in-house computer program and may also maintain a copy of the assignment for future checking purposes and/or allow an external service to do so.

Other policies

See the policies page of the faculty website at for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies.

Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar

Week Description
Week 1 Project and supervisor negotiation/allocation
Week 2 Complete project and supervisor allocation
Week 3 Project work
Week 4 Project work
Week 5 Project work
Assessment Due: Project Proposal*
Week 6 Project work
Week 7 Project work
Week 8 Project work
Week 9 Project work
Week 10 Project work
Week 11 Project work
Week 12 Project work
Week 13 Project work
Assessment Due: Progress Report #1*
Following Semester Assessment Due: Progress Report #2
Assessment Due: Presentation/Seminar*
Assessment Due: Final Report/Deliverable

Course Relations

The following is a list of courses which have added this Unit to their structure.

Course Year(s) Offered
Master of Information Technology 2015, 2016, 2017, 2018, 2019, 2020
Master of Information Technology Management 2015, 2016, 2017, 2018, 2019, 2020
Master of IT/Master of IT Management 2015, 2016, 2017, 2018, 2019, 2020
Master of Information Technology (till 2014) 2014
Master of Information Technology Management (till 2014) 2011, 2012, 2013, 2014

Course Goals

This unit contributes to the achievement of the following course goals:

Attribute Practiced Assessed
(6) Communication and Inquiry/ Research (Level 5) No 0%
(7) Project and Team Skills (Level 5) No 0%
(8) Professional Effectiveness and Ethical Conduct (Level 5) No 0%
(5) Interdisciplinary, Inclusiveness, Influence (Level 5) No 0%
(4) Design (Level 5) No 0%
(2) Engineering/ IT Specialisation (Level 5) No 0%
(3) Problem Solving and Inventiveness (Level 5) No 0%
(1) Maths/ Science Methods and Tools (Level 5) No 0%

These goals are selected from Engineering & IT Graduate Outcomes Table 2018 which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 2018 for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.