This field is relevant for new units only and should provide a rationale for the introduction of the unit. If you are making changes to a unit enter the rationale in the Reasons for Change section.

Example: FIT1002 is a core unit introduced as part of the common core for first year undergraduates in the Faculty of Information Technology (FIT) for 2006

Relevant for unit changes and must be provided each time a unit is updated. If data has been entered in this section previously, DO NOT delete that entry, as the version and history for changes is needed.

Please provide details of the rationale for the proposed change. Include the date the change/s should be implemented.

Example: Code for this unit has been changed from CSE9018 to FIT9018 in accordance with new faculty procedures. Change to be implemented from Semester 1, 2010.

Note: Please ensure that this field is updated each time changes are submitted for committee approval. The date that the change should be implemented MUST be included to guide the approval process and ensure correct reporting to the University Education Committee.

M.P. v2

Explain the role of this unit in relation to the relevant courses. Of particular, relevance should be a statement of how the unit objectives align with the course objectives. Explain the relationship of the new unit with any existing similar faculty units. What does this unit offer that is not provided by other units? Explain the relevance of this unit in relation to the Faculty's strategic and educational objectives.

Example: FIT1001 Computer Systems forms part of the common core for first year undergraduate FIT students. Its key objectives are to prepare students so that they will:

• Understand the basic internal architecture and operation of a computer and its peripherals
• Understand the basics of operating system software and its support for software development tools
• Understand critical factors that affect computer performance.

This unit replaces CSE2318 Data Communications and Computer Networks, previously an elective in the BCS, BSE and BCS double degrees, under the revised degree structure and will be introduced in 2007 as part of the level 2 roll out. This unit exposes students to as many of the currently popular eBusiness technologies as possible so that their design and implementation decisions in the future will be informed and therefore produce successful systems with a high degree of probability.

Following discussions at FEC 6/12, and as part of Monash implementation of the AQF, all Courses and Units are to use 'Learning Outcomes' rather than 'Objectives'. The following resource was developed as a guide to assist staff in writing learning outcomes that align with the AQF Handbook. https://www.intranet.monash/it/governance/quick-links/ade/course-unit-development/writing-unit-learning-outcomes.pdf

Outcomes should be listed in a numbered list, with approximately four to eight outcomes. They should be 'achievable', 'measurable' and 'assessable', commencing with an active verb.

Example:

1. Recognise and distinguish theories and models relating to recordkeeping and archiving
2. Assess and synthesise diverse information for integrative project management
3. Use data modelling and database development tools
4. Interpret and critique a variety of project management methodologies offered by various professional bodies

First year level units would typically have outcomes at lower levels of the cognitive domain (remembering, understanding, applying), whilst third year or higher-level units would be expected to have outcomes at the higher levels of the cognitive domain (applying, analyzing, evaluating, creating).

Following committee approval, any changes to this field are manually entered into the handbook. The unit guide will automatically extract this approved data for subsequent unit guides.

Note: If changes are made to this field mid-semester they will not be reflected in the current unit guide. Once a unit guide is approved at the start of the semester, it no longer interacts with the handbook data.

Note: For help with Writing Unit Learning Outcomes, see http://intranet.monash.edu.au/infotech/about/committees-groups/ade/course-unit-development/writing-unit-learning-outcomes.pdf

J.M v1

The ASCED code should be listed here as it is a mandatory field. ASCED codes are available at: http://www.opq.monash.edu.au/ups/statistics/glossary/destpac/2007/Student/Help/appendixe/section_appendixe.htm

The ASCED code controls the student fee for the unit and is the basis of government funding. Changes to ASCED impact can impact on funding arrangements and student fees. Include only the number of the code. Any change to this field is a major change and may have financial implications for the Faculty.

The FIT Data Integrity Officer will take information entered in this field (following FEC approval) and enter it in Callista.

Note: No unit can be created in Callista without an ASCED code.

The synopsis should be a coherent, explanatory description. Do not provide a list of topics. Following committee approval, any changes to this field are manually entered into the handbook. The unit guide will automatically extract this approved data for subsequent unit guides.

Example: This unit together with FIT3009 e-Business systems provides a top-to-bottom coverage of eBusiness Systems. The emphasis in this unit (FIT2013 e-Business technologies) is on the technologies used to implement eBusiness Systems i.e. the low level of such systems. Although this unit is entirely suitable for a future developer of eBusiness Systems it's optimally targeted at future managers of such development. Thus practical exercises will be illustrative rather than industrial strength and technology issues will be given equal coverage with technology details.

The primary aim of the unit is to familiarise students with as many of the currently popular eBusiness technologies as possible so that their design and implementation decisions in the future will be informed and therefore produce successful systems with a high degree of probability.

Note: Only specify for NEW UNITS, after which time information should be maintained in the unit guide.

Publication details should be provided using the format set out in the APA Style Guide at: http://www.lib.monash.edu/tutorials/citing/infotech.html It is recognised that changes to readings are frequent and thus this information should be kept up to date in the unit guide. Academics should ensure that the library and the bookshop are kept up to date with any changes to prescribed readings.

Example: Mook, D. (2004). Classic experiments in psychology. Westport, CT: Greenwood.

Select from: on-campus, off-campus or both or online.

If the proposed change includes a variation of mode you should consult with your Head of School and gain approval before proceeding with the proposal.

Note: Changes to this field will be flagged as potentially 'affecting students' enrolment'. This means that if changes are made before WES re-enrolment in October then the change will not take affect until the following year. IF this is urgent and requires implementation prior to this time please provide justification, along with date of proposed implementation, in the reason for change. These reasons will then be forwarded to the relevant committee for urgent consideration of amendments for early implementation.

Only enter teaching arrangements that differ from the standard, lectures and tutorials. For example, where a unit has team teaching arrangements.

List the assessment tasks, percentage contribution of each task to final unit result and unit learning outcomes assessed for each task. e.g.

Note: Additional unit hurdle requirements need to be recorded and receive committee approval via Monatar. These will be added to the Handbook.

Where there is no formal examination, the method of authenticating a student's work needs to be included in the Monatar->Assessment summary e.g. students are closely supervised; students are assessed via interview; students produce a portfolio of work that is monitored by teaching staff.

The standard unit is 6 credit points. Include just the number. This is a mandatory field in Callista. Credit points determine the fee payable for that unit, the level of funding for the faculty and the credit points attributed for student progression in their course.

Example: 6

Note: Changes to this field will be flagged as potentially 'affecting students' enrolment'. This means that if changes are made before WES re-enrolment in October then the change will not take affect until the following year. IF this is urgent and requires implementation prior to this time please provide justification, along with date of proposed implementation, in the reason for change. These reasons will then be forwarded to the relevant committee for urgent consideration of amendments for early implementation.

Each unit should have a consistent format. Information from this field is used in the handbook and by timetabling officers. A 6 point single semester subject requires an average 12 hours per week for an average student to get an average mark. The Undergraduate Program Committee 3/09 recommended a change to the contact hours, specifying that units must have four (4) teaching hours (lectures/ tutorials/labs). Any variation will require a rationale and approval by UGPC. FEC 4/09 have approved the following guideline for graduate and postgraduate programs: The standard class contact time for a graduate unit is a two-hour lecture and a two-hour tutorial or laboratory session. The length of tutorials for postgraduate coursework units is to be determined by the Chief Examiner based on the nature and requirements of the unit.

Following committee approval, any changes to this field are manually entered into the handbook. The unit guide will automatically extract this approved data for subsequent unit guides. Timetabling officers will also use this information to schedule room requirements each semester. (Syllabus +)

Note: Changes to this field will be flagged as potentially 'affecting students' enrolment'. This means that if changes are made before WES re-enrolment in October then the change will not take affect until the following year. IF this is urgent and requires implementation prior to this time please provide justification, along with date of proposed implementation, in the reason for change. These reasons will then be forwarded to the relevant committee for urgent consideration of amendments for early implementation.

Example: Workload requirements consisting of three parts:

Minimum total expected workload equals 12 hours per week comprising:

(a) Contact hours for on-campus students:

• Two hours lectures
• Two hours laboratories

(b) Study schedule for off-campus students:

• Off-campus students generally do not attend lecture, tutorial and laboratory sessions, however should plan to spend equivalent time working through resources and participating in discussions

(c) Additional requirements (all students):

• A minimum of 8 hours of personal study per week for completing lab/tutorial activities, assignments, private studyt and revision.

Only enter information in this field when you have a special room request. The assumption will be that ALL units need hi-tech theatres so no need to specify. If contact hours says "laboratory" or 'tutorial", then the unit is automatically scheduled in a normal lab or flat tute room. Only if something extra is required, such as a Studio or a particular lab (crash and burn lab) should it be specified. Timetabling officers will refer to this information.

Example: Part 1 in tute (1hr), Part 2 in lab (2 hrs). This arrangement may vary campus to campus. Laboratories must follow tutorials.

Note: Changes to this field will be flagged as potentially 'affecting students' enrolment'. This means that if changes are made before WES re-enrolment in October then the change will not take affect until the following year. IF this is urgent and requires implementation prior to this time please provide justification, along with date of proposed implementation, in the reason for change. These reasons will then be forwarded to the relevant committee for urgent consideration of amendments for early implementation.

FIT is the usual entry in this field. It is not necessary to differentiate between any of the Faculty's campuses. Where the unit is taught by a different Centre or Faculty, specify the name of that area.

Example: FIT

Provide details of involvement of other faculties if relevant.

The Faculty CSP Officer uses this information to set rules for the unit, so it needs to be unambiguous. Please express it as if you were defining it for publication and expecting challenges from students as to its meaning. Use parenthesis to make order of evaluation specific. A list of units separated by commas will be taken to mean all units are required. Following committee approval, any changes to this field are manually entered into the handbook and Callista.

Example: FIT1007 or GCO1812 or GCO9808

Taking the above example another (but incorrect) presentation of the prerequisites could have been: FIT1007, GCO1812, GCO9808 This could be interpreted in a number of different ways such as: FIT1007 and GCO1812 and GCO9808 OR FIT1007 or GCO1812 or GCO9808

Note: Adding a prerequisite to this field will mean that the change is flagged as potentially 'affecting students' enrolment'. This means that if changes are made before WES re-enrolment in October then the change will not take affect until the following year. IF this is urgent and requires implementation prior to this time please provide justification, along with date of proposed implementation, in the reason for change. These reasons will then be forwarded to the relevant committee for urgent consideration of amendments for early implementation.

Note: Prerequisite knowledge can NOT be enforced and is to be used as a guide only.

This is designed to convey to students (via the handbook) that there are prerequisites that cannot be defined in terms of units completed/passed. It covers things such as Chinese Language in the teaching of Chinese language information technology or Excel in a unit where teaching assumes familiarity with this software. Do not list knowledge areas already assumed by the definition of the prerequisite unit/s. Limit the amount of information in this field, noting that only a maximum of one-two sentence/s will be imported into the handbook.

Example: FIT3104 Chinese language information technology: The unit will be taught in English, but students need to have a good knowledge of written Chinese.

Specify the Chief Examiner for the unit or other academic to contact regarding the unit. No titles, first then last name.

Example: John Hurst