Skip to the content | Change text size
PDF unit guide

FIT4037 Case study - Semester 2, 2010

Chief Examiner:

Ms Susan Foster
Lecturer
Phone: +61 3 990 32404
Fax: +61 3 990 31077

Lecturer(s) / Leader(s):

Caulfield

Ms Susan Foster
Lecturer
Phone: +61 3 990 32404
Fax: +61 3 990 31077

Additional communication information:

Sue Foster

Room H7.58 H Block Caulfield Campus

Caulfield School of IT

Tel: 9903 2404

sue.foster@infotech.monash.edu.au

Introduction

Welcome to FIT4037. This unit aims to introduce students to the skills, tools and techniques required in the development of a realistic business system solution as part of a team. These skills include project planning, quality planning, technical and user documentation, software development and teamwork.

Unit synopsis

The Case study provides the opportunity for students to focus their skills of system analysis and development, software design and development, documentation development and quality, system and software quality, interpersonal relationships and formal and quality documentation in the development of a solution to the Case Study project. Working as members of supervised teams, students undertake the analysis, design, documentation and implementation of an appropriate software system to assist with the resolution of a realistic business problem. As part of their success, teams will decide their methodology, and demonstrate quality planning and project planning skills.

Learning outcomes

At the completion of this unit students will be able to:
  • Implement system analysis skills;
  • Implement quality planning and project planning skills;
  • Provide resolution of a realistic business problem;
  • Implement software design and development skills;
  • Implement software implementation skills;
  • develop documentation.

Contact hours

1 hr seminar/wk, 3 hrs tutorials/wk

Workload

Workload commitments are:

  • one-hour seminar
  • three-hour studio
  • a minimum of 2-3 hours of personal study per one hour of contact time in order to satisfy the reading and assignment expectations.
  • You will need to allocate up to 5 hours per week in some weeks, for use of a computer, including time for newsgroups/discussion groups.

Unit relationships

Prerequisites

FIT9017, FIT9018, FIT9019 and FIT9030
Must be enrolled in course 3309, 0366, 0539, 0360 or 1772

Prohibitions

CSE3900, CSE9020, FIT3015, FIT3048, GCO9800,GCO3500

Teaching and learning method

Teaching approach

In this unit we provide a simulation of a real world systems development experience. Groups of students work as a team with support from tutors and academic staff to develop a system for an industry case. The seminars are developed to address specific issues during system development. The studio sessions are there for students to work on their project and to receive help from tutors and academic staff.

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/

Unit Schedule

Week Date* Topic Key dates
1 19/07/10 Introduction to case study  
2 26/07/10 Forming teams Team project management document
3 02/08/10 IT Projects and Project management  
4 09/08/10 Functional requirements Business case document and requirements
5 16/08/10 Database structures  
6 23/08/10 IT Projects and Risk management  
7 30/08/10 Project testing Functional requirements and design document
8 06/09/10 Technical documents and user manuals  
9 13/09/10 User Manuals and presentation discussion  
10 20/09/10 Team presentations of Prototype functionality Presentations
Mid semester break
11 04/10/10 Developing prototypes Technical documents and user manuals
12 11/10/10 Developing prototypes  
13 18/10/10 Prototype Demonstrations Working prototype

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

Unit Resources

Prescribed text(s) and readings

There is no prescribed text, however a reading list is provided below.

N/A

Recommended text(s) and readings

Yardley, D. (2002) ‘Successful IT Project Delivery’, Addison-Wesley, UK. ISBN 0-201-75606-4

Schwalbe, K. (2004) ‘Information Technology Project Management’, Thomson Course Technology – 3rd (or 4th) Edition ISBN 0-619-15984-7

Curry, J. & Stanford, P. (2005) ‘Practical System Development: A Project-based Approach’, Pearson SprintPrint, Australia ISBN 0-7339-7336-1

Required software and/or hardware

To access weekly lecture/ class materials, you will need an Adobe Acrobat reader, and access to Microsoft Office software (PowerPoint, Word, and Excel) for document preparation.

Equipment and consumables required or provided

Students 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 6 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:

  • lecture notes/ppt slides and
  • weekly tutorial requirements available on the unit web page.

See http://my.monash.edu.au and select Moodle.

CASE STUDY:  You will be supplied with a case study which will be made available in week 1 tutorial.  This case study forms the basis of this course and will require you to work in groups to develop an IT system. 

Assessment

Overview

Practical work: 100%

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.

As the unit does not have a formal examination component students must obtain:

  • at least 50% of the total marks for the unit AND
  • at least 40% of the marks available for each deliverable component including the presentation

If a student does not achieve 40% or more in each of the unit deliverables, 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.

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:
    Team project management document
    Description:
    Specific tasks and marking criteria will be distributed at the beginning of the semester
    Weighting:
    5%
    Criteria for assessment:

    A team project management document will be assessed from a marking criteria prepared by the unit leader.  No hurdle requirements are expected to be handed in with this first deliverable.

    Due date:
    Thursday, 29 July
  • Assignment task 2
    Title:
    Business case document and requirements
    Description:
    Specific tasks and marking criteria will be distributed at the appropriate time
    Weighting:
    10%
    Criteria for assessment:

    Project teams are expected to develop a Business case document.  Templates are provided for ease of use.  The business case will be assessed from a marking criteria developed by the unit leader.

    Project teams are required to also provide hurdle requirements in the form of minutes of meetings, individual timesheets as well as confidential peer reviews.  These are assessable items.  Students may be individually assessed on the level and standard of their  contributions where applicable.

    Due date:
    Thursday 12 August
  • Assignment task 3
    Title:
    Functional Requirements and design document
    Description:
    Specific tasks and marking criteria will be distributed at the appropriate time
    Weighting:
    15%
    Criteria for assessment:

    Each project will be presented using power point slides.  The slides will include screen shots of the partially developed prototype.  Students are marked on presentation skills as well as the appropriateness and clarity of their screens.Students may be individually assessed on the level and standard of their contributions where applicable

    Due date:
    Thursday 2 September
  • Assignment task 4
    Title:
    Presentation of Project
    Description:
    Specific tasks and marking criteria will be distributed at the appropriate time
    Weighting:
    10%
    Criteria for assessment:

    Each project will be presented using power point slides.  The slides will include screen shots of the partially developed prototype.  Students are marked on presentation skills as well as the appropriateness and clarity of their screens.

    Due date:
    Thursday 23 August
  • Assignment task 5
    Title:
    Technical documents and user manuals
    Description:
    Specific tasks and marking criteria will be distributed at the appropriate time
    Weighting:
    30%
    Criteria for assessment:
    Project teams are to prepare technical documents, to include test plan as well as a user manual. These are to be handed into their supervisor on the due date in their labs. These will be marked from a marking criteria. Project teams are required to also provide hurdle requirements in the form of minutes of meetings, individual timesheets as well as confidential peer reviews. These are assessable items. Students may be individually assessed on the level and standard of their contributions where applicable
    Due date:
    Thursday 7 October
  • Assignment task 6
    Title:
    Working Prototype
    Description:
    Specific tasks and marking criteria will be distributed at the appropriate time
    Weighting:
    30%
    Criteria for assessment:
    Project team members will present their prototypes to the student cohort on the due date. The prototypes will be assessed by the unit leader and supervisor from a marking criteria designed by the unit leader at the time project teams present their prototype. Project teams will be given this marking guide closer to the time of their presentation. Project teams are required to also provide hurdle requirements in the form of minutes of meetings, individual timesheets as well as confidential peer reviews. These are assessable items. Students may be individually assessed on the level and standard of their contributions where applicable
    Due date:
    Thursday 21 October

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

Late assignments submitted without an approved extension may be accepted up to one week late at the discretion of the lecturer, but will be penalised at the rate of 10% of total assignment marks per day including weekends. 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:

Informal feedback on progress in labs/tutes

Graded assignments with comments

Interviews

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