Full year units will be affected by the Higher Education reforms, which become effective 1/1/2005. Under these reforms, there will only be one census date for these units. This will mean students will incur the charge for the full unit if they withdraw after the census date, and they will accrue all the student load in the first semester of their enrolment. Students will also have the load associated with full year units deducted from their ?Student Learning Entitlement?, which is a fixed 7 year period for all eligible students. Potential impacts of this include fees and financial hardship issues, and implications of under/over enrolling eg/DIMIA requirements, Ausstudy, eligibility for concession cards etc.

The full year industrial experience project unit CPE3100 is to be replaced by this unit (CPE3300) and CPE3200 so that students are not disadvantaged by these reforms.

This unit forms the first half of the Industrial Experience Project, which is a core requirement in both the Bachelor of Network Computing and the Bachelor of Internet Systems and Commerce.

Students will be expected to complete this unit in the semester immediately following the semester in which they completed CPE3200. Both CPE3200 and CPE3300 should be completed on the same industry project (with the same client) and run across 2 consecutive semesters.

Industry relevance is considered a key objective of both the Bachelor of Network Computing and the Bachelor of Internet Systems and Commerce. The Industrial Experience Project prepares students for entry into the workforce.

On the successful completion of this unit students should gain some practical experience on an IT project for an industrial client and should be able to:

• Control system development through suitable project management tools. This will involve the ongoing identification of necessary tasks during the development, and the estimation of task duration and scheduling of these tasks.
• Show managerial judgement over the development process.
• Perform all technical tasks in a professional and competent manner.
• Work effectively and co-operatively within a team environment.

Upon the successful completion of this unit, students should be able to work effectively and co-operatively in a team environment.

As part of this unit, students continue to follow a systems development lifecycle (as started in CPE3200) and produce the following major deliverables:

• Construction for set review milestones
• Test Strategy Document
• UAT Documentation
• Presentation
• Final System Document
• Final System CD
• Working application according to the client requirements

Schwalbe, K. (2000), Information Technology Project Management, Thomson Learning, Cambridge

This subject involves students continuing to work as part of a project team on an industry project as started in CPE3200. The teaching modes used throughout the semester include:

• Lectures - To introduce students to the subject requirements a lecture is scheduled at the start of the semester.
• Reviews - All major deliverables/milestones produced throughout the project are reviewed by a panel of industry and academic personnel.
• Meetings - Weekly meetings are held with an allocated group supervisor and fortnightly (approx) meeting are held with the team's industry client.
• Presentation - A final presentation is performed in front of peers and supervisors.

Students are taught through:

• the distribution of templates for all major project deliverables.
• weekly meetings with supervisors (who provide guidance on the content of deliverables, project management and development techniques).
• regular reviews by industry experts and academic staff of all major deliverables and system components.

Use of templates:

• By providing standard templates for major deliverables, students are given the framework to which they can fit their project requirements. Each template provides examples of the information required so that students can understand the requirements of all sections within deliverables.

Supervisor Meetings:

• Supervisors provide industry experience and suggestions for improvement to major deliverables. Reviews of work and progress checks are also performed during these meetings to ensure projects are completed on time.

Major Reviews:

• Reviews of draft documents and system components are performed to provide feedback to students that will assist them to achieve a successful implementation.

Project Work:

• By working in a team environment, students will realise the importance of working co-operatively and the impact their work has on others.

All major deliverables are assigned a grade as follows:

• Project Management, 20%
• Construction Review 1, 10%
• Construction Review 2, 10%
• Test Strategy Document, 10%
• UAT, 10%
• Final System, 30%
• Final System Document, 5%
• Monash WEB, 5%

In additon, supervisor and client feedback is also reviewed as part of the assessment on teamwork and communication skills.

Each of the assessed deliverables are major components of any IT development. Their assessment weighting is assigned based on the complexity and importance of the deliverable in relation to the overall project success. All unit objectives are addressed through the development and delivery of the project.

Client and Supervisor evaluations provide essential assessment of the individual's contributions and teamwork throughout the project.

It is expected that the students spend 12 hours per week on their project. Each week the team will attend either:

• 1.0hr meeting with the team Supervisor; or
• 0.5hr formal review at major milestones; or
• 0.5hr presentation

The remainder of the assigned time will be spent on assigned project tasks.

A lecture theatre is required for introductory lectures and presentations held throughout the project.

None required.

An industrial experience laboratory is provided by the School of Network Computing for students to develop project deliverables, load and test systems, participate in reviews and hold meetings.

The subject requires:

• 1 Co-Ordinator to oversee the subject
• A Supervisor allocated to each project team

• Software Title:
• Vendor:
• Version:
• OS: MS Windows XP ( ) and/or LINUX ( )
• License Details: (A valid software license certificate/s or Vendor permission must be available upon request if the software is to be installed for teaching)
• Are we currently licensed: Yes ( ) or No ( ) (If unsure, please check with your local IT support )
• If (Yes), who is the contact person for this software?:
• If (No), will the software license be arranged by: Staff member requesting the software ( ) or Technical Services* ( ) ? *If the latter is selected, please discuss your requirement/s with myself ASAP, prior to finalising your request, as there could be financial or resourcing implications.
• Is the software to be installed and accessed from a: Client/Workstation ( ), or Server ( ) ?
• Type of license: Site License ( ), Freeware ( ), FOSS (Free and Open Source Software) ( ), Shareware ( ), Lab based ( ) # of Licenses needed ____
• In what week will you commence using the software in class? Semester 1 (Week ___ ) and/or Semester 2 (Week ___ ):
• Nominated Staff For Acceptance Testing Software: (Name) (Phone) (Email)
• Additional Information: Special Requirements, Software Configuration/Installation Requirements, etc:

Basic software requirements are provided by the School of Network Computing from current resources. Specialist software for individual projects is provided by the project client.

No change to existing requirements.

100% School of Network Computing.

None

None

None

None.

CPE3200