Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

GCO4500 Honours research project(DISESTABLISHED FB 05/07)

Chief Examiner

This field records the Chief Examiner for unit approval purposes. It does not publish, and can only be edited by Faculty Office staff

To update the published Chief Examiner, you will need to update the Faculty Information/Contact Person field below.

NB: This view restricted to entries modified on or after 19990401000000

Unit Code, Name, Abbreviation

GCO4500 Honours research project(DISESTABLISHED FB 05/07) (13 Dec 2007, 4:21pm) []

Reasons for Introduction

Reasons for Introduction (22 Jul 2004, 5:45pm)

The Honours Project is a 24 CP existing core unit in the honours program of the Bachelor of Information Technology. This proposal completes the unit's Avatar entry.

Reasons for Change (22 Jul 2004, 5:46pm)

The changes are introduced to update the entries for Avatar

Role of Unit (22 Jul 2004, 5:55pm)

The Honours program is a 4th level course offered in both full-time on-campus and part-time distance learning modes. The course is designed to help computing graduates to

  1. acquire an advanced knowledge of selected areas of computing and information technology
  2. develop the research skills needed to undertake a higher degree; or
develop and upgrade their knowledge and skills, in order to enhance their professional competence and keep abreast of new developments and advances in the rapidly changing information technology field.

Relevance of Unit (22 Jul 2004, 6:01pm)

This is a 24 CP core unit of the honours program. This unit requires students to apply the knowledge and skills acquired from other units in the honours program as well as the undergraduate degree to complete an individual project under supervision. The nature of the project can be either developing a significant and functional computer-based system or an in-depth investigation of a relevant topic.

A student wishing to enrol in a project unit, must submit a project proposal to the unit adviser for approval first. Students are allowed to enrol only if the proposed project has been approved by the unit adviser. Once the project has been approved, the student can enrol and begin the project either in semester 1 or semester 2 each year, but not summer semester.

The project must contain at least 25% research component. A project proposal which contain purely developmental work is usually not accepted. A typical research project (100% research component) will include identifying a problem that needs investigation, and designing a research methodology to approach the problem, and implement the methodology and finally evaluating the result. The amount of programming varies from projects to projects.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (22 Jul 2004, 6:11pm)

This unit builds on knowledge and understanding developed in the units throughout honours program as well those that were studied at the undergraduate program. Students will:

  1. understand all stages and process of conducting and carrying out research;
  2. Apply the foundation developed from the completion of the research methods and reading in information technology;

Attitudes, Values and Beliefs (Affective Domain Objectives) (22 Jul 2004, 6:14pm)

This subject aims to develop in students:

  1. the capacity to apply in a practical setting the theoretical work covered in their course
  2. the ability to develop either a significant computing application, from the analysis and design stages, through coding and implementation to evaluation or a significant level of fundamental or applied research.

Practical Skills (Psychomotor Domain Objectives) (22 Jul 2004, 6:24pm)

Keeping in mind the research framework requirement of this unit,students should be able to:

  1. define a problem, and gather data, facts, opinions and information needed to analyse and solve it
  2. outline and evaluate alternative solutions to a system development problem
  3. identify hardware and software requirements for a system document a system design using tools which include system flow charts and data flow diagrams

Unit Content

Recommended Reading (22 Jul 2004, 6:41pm)

Research journals and conference proceedings which contain research publications related to the project work

Teaching Methods

Mode (22 Jul 2004, 6:25pm)

on-campus and off-campus learning

Strategies of Teaching (22 Jul 2004, 6:28pm)

Both on-campus and off-campus students are have an approved research project to work on. Each student is associated with an academic staff of the school who works as his main supervisor. For on-campus there is weekly/fortnightly meetings between the student and the supervisor to monitor the progress of the candidate. For off-campus, the communication is on-line.

Assessment

Strategies of Assessment (22 Jul 2004, 6:31pm)

A student starting a project unit has two options in terms of allocating the percentage of worth to their work. They can choose either:

  1. 100% for the final reports and deliverables, or
  2. Not less than 70% for the final reports and deliverables, and the rest accounts for progress reports.

Assessment Relationship to Objectives (22 Jul 2004, 6:34pm)

The assessment (i.e. final thesis report and the continual evaluation) will test all the learning objectives as listed in the unit objectives

Workloads

Credit Points (22 Jul 2004, 6:35pm)

24 Credit Points

Workload Requirement (22 Jul 2004, 6:37pm)

As this unit accounts for 24 Credit Points out of the total 48 Credit points of the honours program, students are expected to spend at least equal to the work load of two 6CP units per semester. Thus each student should normally spend about 24 hours per week on the project work.

Resource Requirements

Lecture Requirements (22 Jul 2004, 6:39pm)

Each supervisor meets with the student every week/fortnight for monitoring the progress either in office or in a meeting room.

Staff Requirements (22 Jul 2004, 6:43pm)

  • 5 equivalent full time staff for the full year.
  • Software Requirements (21 Oct 2005, 1:04pm)

    Prerequisites

    Corequisites (18 Aug 2004, 10:49am)

    GCO4010

    Level (22 Jul 2004, 6:49pm)

    Level 4

    Frequency of Offering (22 Jul 2004, 6:50pm)

    semester 1 and semester 2 at Gippsland

    Enrolment (22 Jul 2004, 6:54pm)

    Usually about five to ten students are enrolled in the unit

    Location of Offering (22 Jul 2004, 6:55pm)

    Gippsland

    Faculty Information

    Proposer

    Project supervisor to be selected by student in consultation with the honours coordinator

    Approvals

    School: 13 Dec 2007 (Julianna Dawidowicz)
    Faculty Education Committee: 13 Dec 2007 (Julianna Dawidowicz)
    Faculty Board: 13 Dec 2007 (Julianna Dawidowicz)
    ADT:
    Faculty Manager:
    Dean's Advisory Council:
    Other:

    Version History

    22 Jul 2004 Madhusudan Chetty modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RChange; modified ReasonsForIntroduction/RRole; modified ReasonsForIntroduction/RRelevance; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjAffective; modified UnitObjectives/ObjPsychomotor; modified UnitObjectives/ObjPsychomotor; modified UnitObjectives/ObjPsychomotor; modified Classification; modified UnitObjectives/ObjPsychomotor; modified Teaching/Mode; modified Teaching/Strategies; modified Assessment/Strategies; modified Assessment/Objectives; modified Assessment/Objectives; modified Workload/CreditPoints; modified Workload/WorkHours; modified ResourceReqs/LectureReqs; modified UnitContent/RecommendedReading; modified ResourceReqs/StaffReqs; modified Prerequisites/PreReqKnowledge; modified Level; modified Frequency; modified Enrolment; modified Enrolment; modified Enrolment; modified LocationOfOffering; modified FacultyInformation/FIContact; modified FacultyInformation/FICoordinator
    27 Jul 2004 Guojun Lu GCO School Approval, approved by the School Education Committee meeting on 23 July 2004
    18 Aug 2004 Guojun Lu modified Corequisites
    18 Aug 2004 Guojun Lu GCO School Approval, Approved to add Co-requisite GCO4010 after discussion at SEC and FEC
    18 Aug 2004 Ralph Gillon FEC Approval
    16 Sep 2004 Annabelle McDougall FacultyBoard Approval
    17 Oct 2005 David Sole Added Software requrirements template
    21 Oct 2005 David Sole Updated requirements template to new format
    13 Dec 2007 Julianna Dawidowicz modified UnitName
    13 Dec 2007 Julianna Dawidowicz GCO4500 Chief Examiner Approval, ( proxy school approval )
    13 Dec 2007 Julianna Dawidowicz FEC Approval
    13 Dec 2007 Julianna Dawidowicz FacultyBoard Approval - Faculty Board approved the disestablishment of this unit at 05/07 meeting

    This version: