Course & Unit of Study Portal (CUSP)

An Overview

CUSP: What’s it for? Who’s it for?

Student information

1. UoS outlines for current students (and future)

2. UoS extracts for handbook

3. Degree program outlines

Program management

1. Outcomes mapping for accreditation

2. Outcomes led program management & quality control

3. Proposals for new units / new programs

Integrated management of course & unit of study

information at teaching & management levels

across multiple program contexts

Integrated management of course & unit of study

information at teaching & management levels

across multiple program contexts

CUSP: Where does it fit? University information management systems – four key sectors

CUSP: Where does it fit? University systems architecture – the fifth sector

CUSP: How it works

CUSP: What does it look like?

New reporting features

BE (Temporal Mechanics): Generic attribute development by level and assessment weight

CUSP: What it requires . . . Clarity & focus in generic attributes & performance levels Clarity & focus in UoS learning outcomes and teaching methods

Clarity & focus in UoS information strategy (what goes where!)

Program leadership Program support staff (admin & educational design)

. . . and doesn’t require.

All UoS details months in advance Long-wait in queue for update publishing

Expensive software licenses

CUSP: Where to find itStudent/public view Go to http:/cusp.usyd.edu.au/engineering Browse via degree lists or Students menu

For a closer look Email Tim Lever tlever@usyd.edu.au

CUSP: Where it comes from.Acknowledgements due to: Engineering/IT Intranet UoS Database

Version 1 (2003) Version 2 (2008)

CUSP Project Team Engineering & IT (Doug Auld, David Airey, Tim Lever, Richard Gluga)

Architecture, Design & Planning (Rob Saunders, Chris Smith, Victoria Jackson Wyatt)

Health Sciences (Jac Smit, Karen Ho) Funded by TIES 2009 with matching contributions from Faculties of Health Sciences, Engineering & IT, Architecture, Design & Planning