Automating Assessment - a Computer Science Perspective

16.1.2006 - 20.1.2006

The Application of New Technologies to the Delivery of University Computer Science Education

EurIng Dr Mike Joy
Senior Lecturer
Department of Computer Science
University of Warwick
Coventry, UK

Abstract

Technologies which have been developed by the computer science community have tended to be used in other disciplines before being adopted by computer science educators. However, computer science is a discipline in which automation, and the application of novel technologies, should play a large role, due to the nature and content of the material delivered.

This course provides an international perspective on the use of new technologies in computer science education, with an emphasis on assessment within courses delivered at university level. We consider the pedagogic foundations for assessment, and discuss the factors - both technical and extraneous - which affect the computer science curriculum. We present an overview of the types of tools currently used by computer science educators in the assessment process, and use case studies to explore the issues which affect their adoption and effective application.

Indicative syllabus

Pedagogy

What is assessment? Why assess?
Norm vs criterion referenced assessment
Different approaches to grading
Summative and formative assessment

Computer Science

Curriculum issues
Assessment - coursework vs examination
Types of student activity
International and political issues
Programming as the archetypal computer science activity

Assessment tools

Generic vs specific
Measurement tools
Support tools
Validity of assessment

Automating the Assessment of Programming

Black boss vs white box
Style
Freeform vs template
Case studies - CourseMarker, Boss

The Plagiarism Problem

Cheating vs supportive learning
Acceptable behaviour
Case studies - JPlag, Moss, Sherlock, LSA, Turnitin

Supportive Assessment

Peer assessment
Group work
Learning tools
Case studies - Bess

Timetable (each session will be delivered as a seminar)

Monday 16.1.2006

Introduction, syllabus (1h)
Overview of CS Education (2h)

Tuesday

Pedagogy (1h)
CS Curriculum (2h)

Wednesday

Assessing programming (3h)

Thursday

Plagiarism (3h)

Friday

Supportive assessment (2h)
Concluding discussion (1h)

(TBA)

Examination
Practical component

Each participant will do an individual project in one of the main topics. This includes 10-12 pages seminar report on recent literature. In addition, we have several seminar sessions in which they could hand in the first draft of the report and present their findings (e.g., 20 mins / attendant, depending on the number of attendants). The final report could be delivered after all the sessions are over (after a couple of weeks or so).