[an error occurred while processing this directive] [an error occurred while processing this directive]
[an error occurred while processing this directive]
[an error occurred while processing this directive]

Dr Shyh Wei Teng
Senior Lecturer
Phone: +61 3 990 26851

Lecturer(s) / Leader(s):

Gippsland

Dr Shyh Wei Teng
Senior Lecturer
Phone: +61 3 990 26851

Introduction

Welcome to GCO3500 Project for semester 2, 2010. This 6 point unit is an elective to the Master of Applied Information Technology degree program in the Faculty of IT. The unit has been designed to provide you with an opportunity to develop a small scale IT system by applying the system analysis, design and programming knowledge you have acquired in units you have already completed in the course.

Unit synopsis

In general, students select a project that involves all aspects of the system development lifecycle; analysis and design, programming, testing and implementation of a solution. Project management aspects of system development are stressed, with the following deliverables required: proposal, definition, feasibility study, project plan, system specification, design report, implementation plan, user documentation, and operational software, to ensure that the project is delivered on time. The student must display a sense of responsibility for the project outcomes and skills for interaction with the client. Requirements include oral presentation(s) to the client and written reports.

Learning outcomes

At the completion of this unit students will have -
  • the capacity to apply in a practical setting the theoretical work covered in the course;
  • the ability to develop a significant computing application, from the analysis and design stages, through coding and implementation to evaluation;
  • the ability to define a problem, and gather data, facts, opinions and information needed to analyse and solve it
  • skills in outlining and evaluating alternative solutions to a system development problem;
  • 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;
  • ability to identify hardware and software requirements for a system;
  • skill in documenting a system design using industry standard documentation tools and procedures;
  • knowledge, understanding and skill to implement a system, including testing and debugging
  • knowledge and skill in evaluating a system, identifying any weakness or possible; enhancements;
  • the abilities and attitudes required to operate effectively as a member of a development team;
  • skills and knowledge to work with clients and communicate effectively with them.

Contact hours

Students are required to spend a minimum of 12 hours per week working on their projects. Regular meetings with the supervisor are also required.

Workload

Students are required to spend a minimum of 12 hours per week working on their projects.  Regular meetings with the supervisor are also required.

Unit relationships

Prerequisites

Completion of all core units

Prohibitions

CSE3900, GCO9800, GCO3700, GCO3800, GCO3819, GCO3900, SYS3500

Teaching and learning method

Teaching approach

When developing the small scale IT system, students are expected to put knowledge and skills acquired from units previously completed in the course into practise.  A supervisor will be allocated to each student to assist the student during the system development.

Timetable information

For information on timetabling for on-campus classes please refer to MUTTS, http://mutts.monash.edu.au/MUTTS/

Tutorial allocation

On-campus students should register for tutorials/laboratories using the Allocate+ system: http://allocate.its.monash.edu.au/

Off-Campus Learning or flexible delivery

Once a supervisor is allocated to an Off-campus learning (OCL) student, the student should establish with the supervisor the best methods of communication to facilitate the weekly meetings and various discussions.  Some examples of communication methods are email, newsgroup, video conferencing, and chat room.

Unit Schedule

Week Date* Topic Key dates
1 19/07/10 Weekly activities are determined by the student's project plan  
2 26/07/10 As per plan  
3 02/08/10 As per plan Report 1 due and Presentation
4 09/08/10 As per plan  
5 16/08/10 As per plan Report 2 due
6 23/08/10 As per plan  
7 30/08/10 As per plan  
8 06/09/10 As per plan  
9 13/09/10 As per plan Report 3 due
10 20/09/10 As per plan  
Mid semester break
11 04/10/10 As per plan  
12 11/10/10 As per plan  
13 18/10/10 As per plan Report 4 & End Product due and Presentation

*Please note that these dates may only apply to Australian campuses of Monash University. Off-shore students need to check the dates with their unit leader.

Improvements to this unit

To assist what is expected from students for each deliverable, detailed report templates, description of each deliverables, as well as expectation of requirements for various grades are further revised.

Unit Resources

Prescribed text(s) and readings

There is no prescribed text for this unit.

However, all prescribed texts and reccommended readings from other units in your major can be used as references.Monash Bookshop and Library.

Recommended text(s) and readings

All prescribed texts and reccommended readings from other units in your major can be used as references.

Required software and/or hardware

There is no software requirement.  However, students must discuss with their allocated supervisors on what software the university can or cannot support.  If the software the client or student would like to use for system development are not available in the university, the client or student is expected to provide the university with the software licenses in order for the supervisor to assess the system.

Equipment and consumables required or provided

Students studying off-campus are required to have the minimum system configuration specified by the faculty as a condition of accepting admission, and regular Internet access. On-campus students, and those studying at supported study locations may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook. You will need to allocate up to 12 hours per week for use of a computer, including time for newsgroups/discussion groups.

Study resources

Study resources we will provide for your study are:

Information on the structure of this unit is available on the unit Website. Outline of the administrative matters for the unit is also available on the Website.

The GCO3500 Website is on the MUSO/Blackboard site, where lecture slides, sample structure of assignments/reports and sample materials will be posted.

Newsgroups/discussion groups that can be linked to from the Unit Homepage.

Assessment

Overview

Practical work, project reports, documents and other project deliverables, two presentations and the project supervisors report

Faculty assessment policy

To pass a unit which includes an examination as part of the assessment a student must obtain:

  • 40% or more in the unit's examination, and
  • 40% or more in the unit's total non-examination assessment, and
  • an overall unit mark of 50% or more.

If a student does not achieve 40% or more in the unit examination or the unit non-examination total assessment, and the total mark for the unit is greater than 50% then a mark of no greater than 49-N will be recorded for the unit.

1. Attempt all assignment tasks.

2. Score 50% or more overall in the unit.

Assignment tasks

Assignment coversheets

Assignment coversheets are available via "Student Forms" on the Faculty website: http://www.infotech.monash.edu.au/resources/student/forms/
You MUST submit a completed coversheet with all assignments, ensuring that the plagiarism declaration section is signed.

Assignment submission and return procedures, and assessment criteria will be specified with each assignment.

Assignment submission and preparation requirements will be detailed in each assignment specification. Submission must be made by the due date otherwise penalties will be enforced. You must negotiate any extensions formally with your campus unit leader via the in-semester special consideration process: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html.

  • Assignment task 1
    Title:
    Progress Report 1
    Description:
    System specifications
    Weighting:
    8%
    Criteria for assessment:

    The criteria used to assess submissions are:

    1. Correctness and understanding - We will look for proper application of principles and modelling techniques related to system development and project management.
    2. Completeness - that you have described in all sections of the report.
    3. Use of evidence and argument - you are able to explain your approach to developing the system.
    4. Presentation - that you have presented your answers in a suitably formatted report style.

    Detailed assessment criteria are released on the unit site.

    Due date:
    2/8/2010
  • Assignment task 2
    Title:
    Presentation 1
    Description:
    System specifications presentation
    Weighting:
    2%
    Criteria for assessment:

    The criteria used to assess presentations are:

    1. Clarity of information presented.
    2. Completeness of the information presented.
    3. Quality of presentation aids (e.g. presentation slides).
    4. Management of the time allocated for the presentation.

    Detailed assessment criteria are released on the unit site.

    Due date:
    2/8/2010
  • Assignment task 3
    Title:
    Progress Report 2
    Description:
    System analysis
    Weighting:
    12%
    Criteria for assessment:

    The criteria used to assess submissions are:

    1. Correctness and understanding - We will look for proper application of principles and modelling techniques related to system development and project management.
    2. Completeness - that you have described in all sections of the report.
    3. Use of evidence and argument - you are able to explain your approach to developing the system.
    4. Presentation - that you have presented your answers in a suitably formatted report style.

    Detailed assessment criteria are released on the unit site.

    Due date:
    20/8/2010
  • Assignment task 4
    Title:
    Progress Report 3
    Description:
    System design
    Weighting:
    8%
    Criteria for assessment:

    The criteria used to assess submissions are:

    1. Correctness and understanding - We will look for proper application of principles and modelling techniques related to system development and project management.
    2. Completeness - that you have described in all sections of the report.
    3. Use of evidence and argument - you are able to explain your approach to developing the system.
    4. Presentation - that you have presented your answers in a suitably formatted report style.

    Detailed assessment criteria are released on the unit site.

    Due date:
    17/9/2010
  • Assignment task 5
    Title:
    Progress Report 4
    Description:
    System implementation
    Weighting:
    17%
    Criteria for assessment:

    The criteria used to assess submissions are:

    1. Correctness and understanding - We will look for proper application of principles and modelling techniques related to system development and project management.
    2. Completeness - that you have described in all sections of the report.
    3. Use of evidence and argument - you are able to explain your approach to developing the system.
    4. Presentation - that you have presented your answers in a suitably formatted report style.

    Detailed assessment criteria are released on the unit site.

    Due date:
    22/10/2010
  • Assignment task 6
    Title:
    End Product
    Description:
    Final working system to be delivered to client.
    Weighting:
    50%
    Criteria for assessment:

    The criteria used to assess submissions are:

    1. Consistency of the system implementation to the system design.
    2. Completeness of the implemented functionalities.
    3. Correctness of the implemented functionalities - how well tested are them?
    4. User friendliness of the system.

    Detailed assessment criteria are released on the unit site.

    Due date:
    22/10/2010
  • Assignment task 7
    Title:
    Final Presentation
    Description:
    Final presentation on the system developed.
    Weighting:
    3%
    Criteria for assessment:

    The criteria used to assess presentations are:

    1. Clarity of information presented.
    2. Completeness of the information presented.
    3. Quality of presentation aids (e.g. presentation slides).
    4. Management of the time allocated for the presentation.

    Detailed assessment criteria are released on the unit site.

    Due date:
    22/10/2010

Due dates and extensions

Please make every effort to submit work by the due dates. It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are not regarded as appropriate reasons for granting extensions. Students are advised to NOT assume that granting of an extension is a matter of course.

Students requesting an extension for any assessment during semester (eg. Assignments, tests or presentations) are required to submit a Special Consideration application form (in-semester exam/assessment task), along with original copies of supporting documentation, directly to their lecturer within two working days before the assessment submission deadline. Lecturers will provide specific outcomes directly to students via email within 2 working days. The lecturer reserves the right to refuse late applications.

A copy of the email or other written communication of an extension must be attached to the assignment submission.

Refer to the Faculty Special consideration webpage or further details and to access application forms: http://www.infotech.monash.edu.au/resources/student/equity/special-consideration.html

Late assignment

Assignments received after the due date will be subject to a penalty of 5% for every day after the due date.

Assignments received later than one week after the due date will not normally be accepted.

Return dates

Students can expect assignments to be returned within two weeks of the submission date or after receipt, whichever is later.

Feedback

Types of feedback you can expect to receive in this unit are:

Graded assignments with comments

Students should also consult regularly with the assigned supervisors for guidance and feedback on the progress of their projects. 

Appendix

Please visit the following URL: http://www.infotech.monash.edu.au/units/appendix.html for further information about:

  • Continuous improvement
  • Unit evaluations
  • Communication, participation and feedback
  • Library access
  • Monash University Studies Online (MUSO)
  • Plagiarism, cheating and collusion
  • Register of counselling about plagiarism
  • Non-discriminatory language
  • Students with disability
  • End of semester special consideration / deferred exams
[an error occurred while processing this directive]