Skip to the content | Change text size
PDF unit guide

FIT4037 Case study - Semester 2, 2009

Chief Examiner:

Ms Susan Foster
Phone: +61 3 990 32404

Lecturer(s) / Leader(s):


Ms Susan Foster
Phone: +61 3 990 32404

Additional communication information:

Sue Foster

Room H7.58 H Block Caulfield Campus

Caulfield School of IT

Tel: 9903 2404


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

  1. Implementing system analysis skills
  2. Implementing quality planning and project planning skills
  3. Providing resolution of a realistic business problem.
  4. Implementing software design and development skills
  5. Implementing software implementation skills
  6. Documentation development

Contact hours

2 hours lectures/week, 2 hours tutorials/week


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


FIT9017, FIT9018, FIT9019 and FIT9030.

Must be enrolled in course 3309, 0366, 0539, 0360 or 1772


CSE3900, CSE9020, FIT3015, FIT3048, FIT3119, GCO9800, GCO3500


FIT4037 is a foundation unit in the Graduate Diploma in Computing, the Master of Applied Information Technology and the Master of Information Technology at Caulfield.

You may not study this unit and

FIT4037 CSE9020 FIT3015 FIT3048 FIT3119 GCO9800 GCO3500

or equivalent in your degree.

Teaching and learning method

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,

Tutorial allocation

On-campus students should register for tutorials/laboratories using the Allocate+ system:

Unit Schedule

Week Topic Key dates
1 Introduction, forming teams 20 July 2009
2 Project management for IT projects 27 July 2009
3 Risk management 3 August 2009
4 Functional requirements 10 August 2009
5 Testing 17 August 2009
6 TBA 24 August 2009
7 TBA 31 August 2009
8 Team presentations functional requirements 7 September 2009
9 Team presentations of functional requirements 14 September 2009
10 Final documentation 21 September 2009
Mid semester break
11 TBA 5 October 2009
12 Prototype demonstrations 12 October 2009
13 Prototype Demonstrations 19 October 2009

Unit Resources

Prescribed text(s) and readings

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


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 and select Blackboard.

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



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 44% then a mark of no greater than 44-N will be recorded for the unit.

obtain all of the following:

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

Assignment tasks

Assignment coversheets

Assignment coversheets are available via "Student Forms" on the Faculty website:
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 task 1
    Business Case & Requirements
    Specific tasks and marking criteria will be distributed at the beginning of the semester
    Due date:
    7 August
  • Assignment task 2
    Functional Requirements & Design Document
    Specific tasks and marking criteria will be distributed at the appropriate time
    Due date:
    21 August
  • Assignment task 3
    Testing Document
    Specific tasks and marking criteria will be distributed at the appropriate time
    Due date:
    4 August
  • Assignment task 4
    Technical & User Manuals
    Specific tasks and marking criteria will be distributed at the appropriate time
    Due date:
    18 September
  • Assignment task 5
    Specific tasks and marking criteria will be distributed at the appropriate time
    Due date:
    9 October
  • Assignment task 6
    Working Prototype
    Specific tasks and marking criteria will be distributed at the appropriate time
    Due date:
    16 October
  • Assignment task 7
    Team Project Management Document
    Specific tasks and marking criteria will be distributed at the appropriate time
    Due date:
    19 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:

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.


Please visit the following URL: 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