A Subject Unit Co-ordinator’s Perspective 2nd October 2013

1. A Subject Unit Co-ordinator’s Perspective2nd October 2013 Dr Ian McChesney Faculty of Computing and Engineering

2. Context Computing 16A PG 16B UG J 16C UG C 16D UG M Feb 2013 Oct 2012 Mar 2013 Dec 2012

3. The Subject Unit Coordinator • The main duties of the Subject Unit Co-ordinator are found in Appendix 49 of 2012 PAMR Handbook and are:  • To consult with the Dean regarding completion of re-validation preparation form (CA6) and its return to Academic Office. • To liaise with the Subject Team, Heads of School, Course/Subject Directors, Module Co-ordinators and other teaching staff of the University and external institutions regarding planning, preparation and arrangements for the re-validation event. • To liaise with the Academic Office regarding joint validation arrangements and requirements.  • With the approval of the Dean, to liaise with Professional, Statutory and Regulatory Bodies (PSRB(s)) regarding joint validation arrangements and requirements.  • To support arrangements for site visits through liaison with the Academic Office, Information Services, external panel members and Faculty Head of Collaborative Courses and other staff as appropriate and to co-ordinate the programme for these visits.  • To co-ordinate the preparation and submission of the requisite documentation for consideration by the re-validation panel. • To co-ordinate the Faculty’s response to the re-validation panel’s report and provision of final documentation for approval. http://www.ulster.ac.uk/academicoffice/re-validation.html

4. Approach • Establish key themes • Document templates • Scheduling

5. Establish Key Themes • Read the PAMR! • Reflect on University T&L Strategy • Establish key themes to be addressed, e.g. • employability (EDORT) • study skills • assessment and feedback • industrial input • graduate qualities • external threats • Evolution or revolution? • Review and incorporate PSRB requirements Workshop

6. Document Templates • Module Descriptions, CVs: • based on AO template, circulate Word template with sample styles for e.g. content, assessment, etc. • Consider shared repository for documents in progress, e.g. wiki • For Revalidation Document, build ToC based on PAMR Appendix 20 • In Word, 'Paste Special…' is your friend! • Take responsibility for the style of the document - if something isn't right you need to fix it!

7. Scheduling • Working back from University event, e.g. • Subject workshop Sep 2011 • Faculty Mock (CE) Sep 2012 • University event (CE) Oct 2012 • Allow sufficient time for changes after Faculty mock event • Staff and student briefing prior to formal event • Plan for post event rework - time consuming

8. Other considerations… • Central department support • Industrial input • Other external reference points

9. Central department support… • Staff Development Unit and CHERP offer support, e.g. • advice on documentation, use of student focus groups • Viewpoints project tools for reflectionand curriculum design, e.g. employability across the curriculum in computing • Career Development Centre, EDORT for employability review

10. Industrial Input • Industrial Liaison panel • Employer feedback from placements • Employer survey of skills and technologies • Industrial representation on mock panels

11. Other external reference points • Subject Benchmark • PSRB requirements • External Examiner reports • HE Academy • Practice at other institutions

12. Above all … • Know your PAMR! • Academic Office will keep you right!