Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

GCO3900 Business systems 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

GCO3900 Business systems project (DISESTABLISHED FB 05/07) (13 Dec 2007, 4:14pm) []

Reasons for Introduction

Reasons for Introduction (15 Apr 2004, 1:26pm)

This subject is being introduced to provide a core project subject for the proposed Business Systems major of the Bachelor of Computing. While a similar existing subject is available, namely GCO3800 Industry Project, the nature of the industry based projects undertaken by Business Systems majors may differ, with a greater focus being on the application of information technology in analysing and solving a significant business problem. This may, for example, involve the utilisation of a range of techniques and skills for decision making, including the application of modern software tools in the development of statistical or financial models. It is envisaged that project teams may include some students from other disciplines. For example, the possibility of students taking the Bachelor of Electronic Commence working with students in the Business Systems major to develop an electronic commerce application has been discussed with staff in the Faculty of Business and Economics.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (01 Apr 2004, 5:41pm)

This unit builds on knowledge and understanding developed in core units throughout first and second level studies. Students will:

  1. understand all stages of the process of developing an information system;
  2. understand the roles and responsibilities of clients, system users and developers in a systems development project;
  3. understand how information systems are developed;

Attitudes, Values and Beliefs (Affective Domain Objectives) (01 Apr 2004, 5:42pm)

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 a significant computing application, from the analysis and design stages, through coding and implementation to evaluation.

Practical Skills (Psychomotor Domain Objectives) (01 Apr 2004, 5:43pm)

On completion of this subject students should be able to:

  1. work with clients and communicate effectively with them
  2. define a problem, and gather data, facts, opinions and information needed to analyse and solve it
  3. outline and evaluate alternative solutions to a system development problem
  4. perform a feasibility study that includes estimates of costs, time requirements, a schedule for the development, and the benefits expected from the system
  5. identify hardware and software requirements for a system
  6. document a system design using tools which include system flow charts and data flow diagrams
  7. implement a system, including testing and debugging
  8. evaluate a system, identifying any weakness or possible enhancements

Relationships, Communication and TeamWork (Social Domain Objectives) (01 Apr 2004, 5:44pm)

This subject aims to develop in students:

  1. the ability to operate effectively as a member of a development team.

Unit Content

Summary (01 Apr 2004, 5:45pm)

Students work in project groups (usually six people) on a system development project for a client who may be either internal or external to Monash. In general, projects involve all aspects of the system development lifecycle. Project management aspects of system development are stressed. The requirements of the subject are fulfilled by the team producing an identified set of deliverables, usually a project proposal, project plan, a system specification, user documentation and software. The team must perform software management activities to ensure that the project is delivered on time. Students are required to maintain a development log with a full record of all their project-related activities. 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. Internal students meet formally with the subject adviser each week for seminar presentations and tutorial sessions. In the case of exteral students an individual project or smaller project group (two or three people) may be permitted. Students admitted to the school's industry experience scheme fulfil the unit requirements by undertaking a project with their employer.

Teaching Methods

Mode (01 Apr 2004, 5:46pm)

On-campus, off-campus learning

Strategies of Teaching (01 Apr 2004, 5:47pm)

Students work in project groups (usually six people) on a system development project for a client who may be either internal or external to Monash addressing objectives 1-14. On-campus students meet formally with the subject adviser each week for seminar presentations and tutorial sessions. Off-campus students communicate with the groups superviser electronically and by telephone as well as submitting reports by mail.

The requirements of the subject are fulfilled by the team producing an identified set of deliverables, usually a project proposal, project plan, a system specification, user documentation and software (objectives 1-5). The team must perform software management activities to ensure that the project is delivered on time. Students are required to maintain a development log with a full record of all their project related activities.

In the case of external students an individual project or smaller group (2-3 people) may be permitted. Students admitted to the School's industry experience scheme fulfil the subject requirements by undertaking a project with their employer.

Assessment

Strategies of Assessment (01 Apr 2004, 5:48pm)

Assignments and other assessment modes: 100%

Assessment is entirely by practical work and is based on two seminar presentations, quarterly supervisors reports, supervisor evaluation of the project deliverables, evaluation of the final product by two assessors other than the supervisor, and peer assessment of each team member?s contribution.

Workloads

Credit Points (01 Apr 2004, 5:49pm)

12 credit points

Workload Requirement (01 Apr 2004, 5:50pm)

12 hours per week for 26 weeks. The unit requires two consecutive semesters to complete.

Resource Requirements

Lecture Requirements (01 Apr 2004, 5:50pm)

One seminar room for discussions and presentations for 2 hours per week

Laboratory Requirements (01 Apr 2004, 5:51pm)

Facilities to allow students to complete development of project systems

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

Library Requirements (15 Apr 2004, 1:40pm)

This is an existing unit with a current library approval

Teaching Responsibility (Callista Entry) (01 Apr 2004, 5:51pm)

Gippsland School of Computing & IT 100%

Prerequisites

Prerequisite Units (01 Apr 2004, 5:51pm)

Completion of all second level core units

Prohibitions (01 Apr 2004, 5:52pm)

GCO2819, GCO3819, GCO3700, GCO3800, SYS3030, SYS3550, SYS3500

Level (01 Apr 2004, 5:52pm)

Level 3

Frequency of Offering (01 Apr 2004, 5:53pm)

Semester 1 or semester 2 each year

Location of Offering (15 Apr 2004, 1:41pm)

Gippsland

Faculty Information

Proposer

J Hewson

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

01 Apr 2004 Shyh Teng Updates and checks for 04/04 education committee meeting.
15 Apr 2004 Kim Styles Update of unit adviser, and populating the avatar entry from the paper-based proposal.
15 Apr 2004 Kim Styles GCO School Approval, Approved for transmission to FEC 3/04 by GSCIT EC Meeting 2/04 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
13 Dec 2007 Julianna Dawidowicz modified UnitName
13 Dec 2007 Julianna Dawidowicz GCO3900 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: