Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

GCO3819 Computing project

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

GCO3819 Computing project []

Reasons for Introduction

Reasons for Introduction (27 May 2004, 09:33am)

A new unit offered as part of the creation of a new on-campus master's program. This program is similar to the current MAIT.

Role of Unit (16 Apr 2004, 3:39pm)

This is a 6 point project taken over two semesters, designed for students enrolled in double degrees, who are unable to fit the standard 12 point project into their program.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (05 Apr 2004, 8:01pm)

This subject aims to develop in students:

  1. the capacity to apply in a practical setting the theoretical work covered in the course
  2. the ability to develop a significant computing application, from the analysis and design stages, through coding and implementation to evaluation
  3. the abilities and attitudes required to operate effectively as a member of a development team.
  4. skills and knowledge to work with clients and communicate effectively with them
  5. the ability to define a problem, and gather data, facts, opinions and information needed to analyse and solve it
  6. skills in outlining and evaluating alternative solutions to a system development problem
  7. knowledge and skill to perform a feasibility study that includes estimates of costs, time requirements, a schedule for the development, and the benefits expected from the system
  8. ability to identify hardware and software requirements for a system
  9. skill in documenting a system design using industry standard documentation tools and procedures
  10. knowledge, understanding and skill to implement a system, including testing and debugging
  11. knowledge and skill in evaluating a system, identifying any weakness or possible enhancements

Unit Content

Teaching Methods

Mode (15 Apr 2004, 4:07pm)

Distance Learning

Strategies of Teaching (15 Apr 2004, 4:08pm)

Students work individually or in small project groups (up to 3 people) (objective 3) on a system development project for a client who may be either internal or external to Monash. Each project is supervised by an academic staff member (objectives 1-4).

In general projects involve all aspects of the system development life cycle, and are scoped to ensure that they are achievable in one semester. Project management aspects of system development are stressed. The requirements of the subject are fulfilled by the student or team producing an identified set of deliverables, usually a project proposal, project plan, a system specification, user documentation and software. The student or team must perform software management activities to ensure that the project is delivered on time.(objectives 1,2, 5-11)

Students are required to maintain a development log with a full record of all their project related activities. In team projects, each member of the team must demonstrate a significant contribution to the team effort, a sense of responsibility for the project outcome and skills for interaction with the client.

Assessment

Strategies of Assessment (05 Apr 2004, 8:02pm)

Practical work (project reports, documents and other project deliverables, two presentations and the project supervisor's report: 100%

Assessment Relationship to Objectives (05 Apr 2004, 8:02pm)

The assessment documentation and practical activities assess objectives 1 - 11.

Workloads

Credit Points (15 Apr 2004, 4:09pm)

6 credit points

Resource Requirements

Lecture Requirements (15 Apr 2004, 4:09pm)

N/A

Tutorial Requirements (15 Apr 2004, 4:10pm)

N/A

Laboratory Requirements (15 Apr 2004, 4:10pm)

N/A

Staff Requirements (15 Apr 2004, 4:11pm)

Lecturer x 0.2 to coordinate projects over semesters 1 and 2

Software Requirements (21 Oct 2005, 1:04pm)

Library Requirements (15 Apr 2004, 4:12pm)

This existing unit has library requirements already defined and approved.

Teaching Responsibility (Callista Entry) (15 Apr 2004, 4:12pm)

Gippsland School of Computing & IT 100%

Prerequisites

Prerequisite Units (15 Apr 2004, 4:13pm)

Completion of all core units

Prohibitions (15 Apr 2004, 4:15pm)

GCO2819, GCO9800, GCO3700, GCO3800, GCO3900, SYS3030, SYS3550, SYS3500

Frequency of Offering (15 Apr 2004, 4:16pm)

Semester 1 and semester 2 of every year

Location of Offering (15 Apr 2004, 4:17pm)

Gippsland

Faculty Information

Proposer

J Hewson

Approvals

School: 16 Apr 2004 (Kim Styles)
Faculty Education Committee: 13 May 2004 (Denise Martin)
Faculty Board: 25 May 2004 (Annabelle McDougall)
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

05 Apr 2004 Choon-Fook Lau modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjText; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjCognitive; modified Assessment/Strategies; modified Assessment/Objectives; modified FacultyInformation/FIContact; modified FacultyInformation/FICoordinator
15 Apr 2004 Choon-Fook Lau modified Teaching/Mode; modified Teaching/Strategies; modified Teaching/Strategies; modified Workload/CreditPoints; modified ResourceReqs/LectureReqs; modified ResourceReqs/TutorialReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/LibraryReqs; modified ResourceReqs/SchoolReqs; modified Prerequisites/PreReqUnits; modified Prohibitions; modified Frequency; modified LocationOfOffering
16 Apr 2004 Kim Styles Entry of the unit into the Avatar, and update of the unit adviser.
16 Apr 2004 Kim Styles GCO School Approval, Approved for transmission to FEC 3/04 by GSCIT Education Committee Meeting 2/04 on 5/4/04.
13 May 2004 Denise Martin FEC Approval
25 May 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

This version: