Course

1
Course Unit of Study Portal (CUSP)

• An Overview

2
CUSP Whats it for? Whos it for?

• Student information
• UoS outlines for current students (and future)
• UoS extracts for handbook
• Degree program outlines

• Program management
• Outcomes mapping for accreditation
• Outcomes led program management quality control
• Proposals for new units / new programs

Integrated management of course unit of study
information at teaching management
levels across multiple program contexts
3
CUSP Where does it fit?

• University information management systems four
  key sectors

4
CUSP Where does it fit?

• University systems architecture the fifth sector

5
CUSP How it works
6
CUSP What does it look like?
7
New reporting features
BE (Temporal Mechanics) Generic attribute
development by level and assessment weight
8
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 doesnt require.
• All UoS details months in advance
• Long-wait in queue for update publishing
• Expensive software licenses

9
CUSP Where to find it

• Student/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_at_usyd.edu.au

10
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