Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

FIT3026 Information Technology Project 2 (DISESTABLISHED FEC 2/08)

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

FIT3026 Information Technology Project 2 (DISESTABLISHED FEC 2/08) (22 May 2008, 11:59am) [IT Project 2 (10 Jun 2005, 08:47am)]

Reasons for Introduction

Reasons for Introduction (09 May 2006, 5:38pm)

FIT3026 Information Technology Project 2 is introduced as a new unit for the Bachelor of Information Technology and Systems (BITS). Specifically, FIT3026 will be the second of two core project units in the Applications Development and Networks major and the Business Systems major of BITS.

FIT3026 is basically a new unit introduced to replace the second half of GCO3800, a 12-point project core unit for the Bachelor of Information Technology with all the three majors: Systems Development, Business Systems and Network Technology. The first half of GCO3800 will be replaced by FIT3025 (Information Technology Project 1).

FIT3026 is designed to provide students an opportunity to work in groups on a project development for a client who may be either internal or external to Monash. Projects involve all aspects of the system development lifecycle. Project management is stressed. Requirements are fulfilled by the team producing an identified set of deliverables, usually a project proposal, project plan, a system specification, user documentation and operational software. The team must ensure that the project is delivered on time. Each member of the team must demonstrate a significant contribution to the team effort, and display a sense of responsibility for the project outcome. The school's industry experience scheme fulfils the unit requirements.

This unit draws on the knowledge, technologies and tools learnt from the previous units of analysis, design, implementation and project management of information systems.

Please note that this unit is set up with two credit point components. The first partner unit (FIT3025), which a student must obtained a grade 'SFR' (Satisfied Faculty Requirements) before allowing to start on this unit, is set up with 6 Enrolled Credit Points and Zero Achievable Credit Points. This unit (FIT3026) is set up with 6 Enrolled Credit Points and 12 Achievable Credit Points. What this does is that students have 6 Enrolled Credit point load in each semester but they do not get the academic credit until successfully passing this unit (only then 12 Achievable Credit Points are awwarded). Equally, a fail in this unit is effectively a fail in both units. As a result, a student getting a pass grade (e.g. HD) in this unit (FIT3026) will get that grade towards the whole 12 CPs.

Reasons for Change (16 Mar 2005, 11:20am)

As per "Reasons for Introduction"

Role of Unit (10 Jun 2005, 08:50am)

FIT3026 completes the project sequence commenced with FIT3025. This unit with its partner, draws on the knowledge, technologies and tools learnt from the previous units of analysis, design, implementation and project management of information systems.

Relationship of Unit (10 Jun 2005, 09:25am)

Project units are core in each of the BITS majors.

Relevance of Unit (12 Jun 2006, 10:32pm)

Each of the first and second level units taken by students in the "Applications Development & Networks" and the "Business Systems" major only provide them with knowledge in a specific area of information system development. FIT3025 provides students with the opportunity to put together knowledge from different units into the development of an information system for real clients. This unit also requires students to work in project teams. This unit exposes students to potential tasks and issues in their future employment.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (16 Mar 2005, 11:23am)

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) (09 Jun 2005, 09:44am)

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) (16 Mar 2005, 11:25am)

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) (16 Mar 2005, 11:26am)

This subject aims to develop in students:

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

Unit Content

Summary (10 Jun 2005, 08:46am)

ASCED Field of Education: 020305 Systems Analysis and Design

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 external 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.

Handbook Summary (11 Jul 2005, 4:18pm)

Students work in groups on a project development for a client who may be either internal or external to Monash. Projects involve all aspects of the system development lifecycle but will focus more heavily in system design and implementation. Project management is also stressed. Requirements are fulfilled by the team producing an identified set of deliverables, such as user documentation and operational software. The team must ensure that the project is delivered on time. Each member of the team must demonstrate a significant contribution to the team effort, and display a sense of responsibility for the project outcome. The school's industry experience scheme fulfils the unit requirements.

Teaching Methods

Mode (16 Mar 2005, 11:27am)

On-campus, off-campus learning

Strategies of Teaching (16 Mar 2005, 11:28am)

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. 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. 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.

Teaching Methods Relationship to Objectives (10 Jun 2005, 09:25am)

All learning objectives for the unit are addressed in the context of the team project work.

Assessment

Strategies of Assessment (09 Jun 2005, 09:47am)

Assignments and other assessment modes: 100%

Assessment is entirely based on the practical work and the amount of collaborative effort within the team.

It is based on one seminar presentation, 2 supervisor reports, supervisor evaluation of the project deliverables and peer assessment of each team member's contribution.

Assessment Relationship to Objectives (16 Mar 2005, 11:31am)

With respective to the objectives stated above, this unit assesses:

Workloads

Credit Points (07 Mar 2006, 10:42am)

6 Enrolled Credit Points & 12 Achievable Credit Points

If a student has obtained a grade 'SFR' for the first partner unit (FIT3025) but failed this unit, the correct grade given is N. This means that zero achievable credit points is given for both FIT3025 & FIT3026. The student will need to redo both FIT3025 and FIT3026.

If a student has obtained a grade 'SFR' for the first partner unit (FIT3025) and has also successfully completed this unit, a grade in the range of {P, C, D & HD} is given to reflect the student's overall performance throughout both units (FIT3025 & FIT3026).

Workload Requirement (16 Mar 2005, 11:34am)

Students are expected to spend 12 hours per week on their project. The unit requires 1 semester to complete.

Resource Requirements

Lecture Requirements (16 Mar 2005, 11:34am)

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

Laboratory Requirements (16 Mar 2005, 11:35am)

Facilities to allow students to complete development of project systems

Staff Requirements (10 Jun 2005, 09:01am)

Between 0.5 - 1.0 EAS at each location each semester to manage the FIT3025, FIT3026 projects according to number of groups. Individual groups are generally supervised by other individual academic staff.

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

Generally the standard student operating environment is sufficient. Requirements in excess of this are to be provided by the client.

Library Requirements (10 Jun 2005, 09:03am)

Sufficient copies of the recommended reading.

Teaching Responsibility (Callista Entry) (08 Jul 2005, 10:33am)

FIT

Implications for CASPA (10 Jun 2005, 09:06am)

N/A

Interfaculty Involvement (10 Jun 2005, 09:06am)

N/A

Interschool Involvement (10 Jun 2005, 09:05am)

Delivery of the unit will be coordinated between the three locations of offering by the chief examiner

Other Resource Requirements (10 Jun 2005, 09:06am)

Other resource requirements specific to each project are provided by the client.

Prerequisites

Prerequisite Units (10 Jun 2005, 09:08am)

FIT3025 in the immediately preceeding academic semester.

Corequisites (10 Jun 2005, 09:16am)

Prohibitions (10 Jun 2005, 09:15am)

GCO2819, GCO3819, GCO3700, GCO3800, GCO3900, GCO3800A, CPE3200, CPE3300, CSE3200, IMS3000, (Translation set: GCO3800A)

Alias Titles (10 Jun 2005, 09:17am)

N/A

Level (16 Mar 2005, 11:42am)

Level 3

Proposed year of Introduction (for new units) (10 Jun 2005, 09:22am)

Semester 2 2006 Gippsland and Malaysia, in 2007 South Africa

Frequency of Offering (08 Jul 2005, 10:33am)

Semester 1 and semester 2 each year at each location of offering.

Enrolment (10 Jun 2005, 09:20am)

Gippsland: 60

Malaysia: tba

South Africa: tba

Location of Offering (10 Jun 2005, 09:19am)

Gippsland, Malaysia, South Africa

Faculty Information

Proposer

Shyh Teng

Approvals

School: 22 May 2008 (Julianna Dawidowicz)
Faculty Education Committee: 22 May 2008 (Julianna Dawidowicz)
Faculty Board: 22 May 2008 (Julianna Dawidowicz)
ADT:
Faculty Manager:
Dean's Advisory Council:
Other:

Version History

16 Mar 2005 Shyh Teng FIT3013 introduced as a new unit for the BITS at FIT Gippsland campus.
11 Apr 2005 Shyh Teng changes made after copying contents from FIT3013 to FIT3026
09 Jun 2005 Christine Jessup modified ReasonsForIntroduction/RIntro; modified UnitObjectives/ObjAffective; modified Assessment/Strategies
10 Jun 2005 Kim Styles Addition of ASCED Code, general editing, submission to FEC.
08 Jul 2005 Ralph Gillon Teaching Responsibility: Amened to read FIT. Frequency of Offering: Deleted reference to Summer semester.
11 Jul 2005 Shyh Teng modified UnitContent/HandbookSummary
11 Jul 2005 Madhusudan Chetty Checked handbook entry, teaching responsbility and frequency of offering
12 Jul 2005 Geraldine DCosta Approved for Submission
12 Jul 2005 Geraldine DCosta FIT School Approval, Approved for submission FEC Mtg 5/05
12 Jul 2005 Geraldine DCosta FEC Approval
21 Jul 2005 Annabelle McDougall FacultyBoard Approval
17 Oct 2005 David Sole Added Software requrirements template
21 Oct 2005 David Sole Updated requirements template to new format
07 Mar 2006 Shyh Teng modified ReasonsForIntroduction/RIntro & Workload/CreditPoints to reflect the accurate credit points system of this unit (FIT3026) and its parnter unit (FIT3025).
09 May 2006 Shyh Teng modified ReasonsForIntroduction/RIntro
09 May 2006 Kai Ting modified ReasonsForIntroduction/RIntro
24 May 2006 Kai Ting
24 May 2006 Geraldine DCosta FIT School Approval, Approved for submission FEC Mtg 3/06
12 Jun 2006 Shyh Teng modified ReasonsForIntroduction/RRelevance
13 Jun 2006 Shyh Teng
13 Jun 2006 Geraldine DCosta FIT School Approval, Approved for submission FEC Mtg 3/06
19 Jun 2006 Ralph Gillon FEC Approval
30 Jun 2006 Ralph Gillon FacultyBoard Approval
22 May 2008 Julianna Dawidowicz modified UnitName FEC 2/08 approved disestablishment of FIT3026 as the unit is no longer part of the BITS Gippsland majors. It has been replaced by FIT3048 Industrial Experience Project.
22 May 2008 Julianna Dawidowicz FIT3026 Chief Examiner Approval, ( proxy school approval )
22 May 2008 Julianna Dawidowicz FEC Approval
22 May 2008 Julianna Dawidowicz FacultyBoard Approval - FEC 2/08 approved the disestablishment of this unit. Faculty Board Approval has been added to aid administration in Monatar.

This version: