OU blog

Personal Blogs

Christopher Douce

Computing education practice conference: Durham, January 2019

Visible to anyone in the world
Edited by Christopher Douce, Thursday, 24 Jan 2019, 10:29

I first visited the Computing education practice (CEP) conference, held at the University of Durham, back in 2017 (OU blog). I felt that it was a really nice event, with a broad range of subjects and a particular focus on opportunities of chatting to computer science educators from a number of other universities. 

What follows is a quick blog summary of the second CEP conference that I attended on 8 January 2019 along with a set of accompanying thoughts, reflections and useful weblinks. I’ve written all this so I can remember what happened, and also on the off chance that anyone else doing research in computer science education might find this of interest. 

Welcome and keynote

The opening keynote was by Andrew McGettrick, emeritus professor from the University of Strathclyde. Andrew told us all about various reports; he mentioned the Committee on European Computing Education Map of Informatics in European Schools and the US Computer Science for All initiative (ACM). There is also something called the Informatics for All Strategy from ACM Europe which presents recommendations for teacher training. Returning to the UK, the Joint Mathematical Council of the UK has published Digital Technologies and Mathematics Education (2011, PDF)

I noted down a couple of themes that Andrew highlighted, namely, the changing face of computing and the increased perceived importance of subjects such as machine learning. An importance question that was asked was: how do you help (or pressure) countries to focus on the development of computer science education?

I don’t know whether I missed it in Andrew’s talk, but I did feel that there was an opportunity to talk about the more recent work of the Royal Society about Computing Education in Schools (Royal Society website) and the Shadbolt Review of Computer Sciences Degree Accreditation and Graduate Employability (PDF)

Session 1: Projects

The first presentation, Supervisor Recommendation Tool for Computer Science Projects was by Kasim Terzic, University of St Andrews. In essence, Kasim’s talk was about a computer science project that was used to manage the allocation of computer science projects. It worked by getting different bits of information from different sources: staff advertise dissertation topics and provide information about their research interests by submitting papers to the institutional research repository. The inputs to the system were keywords and project proposals and the outputs were supervisor recommendations. Whilst Kasim was speaking, I thought of the OU project module, TM470.

Next up was Laura Heels and Marie Devlin from Newcastle University who spoke about: Investigating the Role Choice of Female Students in a Software Engineering Team Project. This presentation began by emphasising that there is a big gender disparity in STEM and computing subjects. Their research asked a simple question: what roles do students take when doing some important computing group work? In their findings, for one year more females chose programming roles, but by and large the trend is (if I’ve noted this down properly) that the males tend to choose the programming role.

I especially enjoyed this second presentation since it made me reflect on my own experience of group work as an undergraduate. I remember being thrown together in a group, and having to choose our own roles and responsibilities. I remember some of the conflicts, and the need to make pragmatic decisions for the good of the project. I also remember how the team supported me when I came to give a group presentation. I certainly felt that role identity and choice was an interesting topic to be studying.

Session 2: Pedagogy

Stewart Powell from Swansea University talked about: Teaching Computing via a School Placement. The motivation for his talk and the work that accompanied it was compelling, and directly linked back to some of the themes introduced by the keynote, namely: CS grads might not see teaching as a career path; they may lack confidence and competence. Here there is a link to the importance of soft skills, and a further implicit link to the Shadbolt report. Stewart introduced the module: it took place during one semester in year 3, and allowed students to gain an understanding of what it means to be a teacher.

The next presentation in this session, by Tristan Henderson, University of St Andrews was all about Teaching Data Ethics, a new postgraduate module. Tristan described the motivation for the module: that there are always lots of controversies; every day there is something happening. A phrase I noted down was: ‘I’ve moved away from thinking that technology is a solution for everything’. A further point that ethics can be a topic that can be difficult to teach. Subjects in the module included: privacy, aspects of law, machine learning, ethics in practice and ethics in research. We were also told about the Royal Statistical Society Data Ethics Special Interest Group.

As Tristan was talking, I thought of a related OU postgraduate module called M811 Information Security (Open University), which touches upon some of the topics that Tristan highlighted, but with a more direct focus on security. All in all, a very engaging and thought provoking presentation. I really liked the focus on the fact that Data Ethics (and Information Security) are such important contemporary issues.

Alcwyn Parker from Falmouth University returned to the theme of group work with the presentation: Nurturing Collaboration in an Undergraduate Computing Course with Robot-themed Team Training and Team Building. I noted down that ‘group work is [an] integral part of the student’s education’. I also noted down the terms: communities of practice, and cognitive apprenticeship, where students are encouraged to observe, practice and reflect. One of the things that I liked about this presentation was a very explicit link between education theory and practice.

The final presentation had the title: Papertian Mathetics with Concept Map Stories and was given by  Amanda Banks Gatenby from the Manchester Institute of Education. I’m familiar with Papert through his book Mindstorms (Wikipedia). I was interested to hear that the word Mathetics was defined as the ‘art of learning’ (which is distinct from pedagogy, which is about the art of teaching). The presentation described how concept maps are created and described by students.

Session 3: Data and data security

One of the challenges of teaching computing is that sometimes solutions to problems can be easily found through internet searches.  Rosanne English from the University of Strathclyde gave a number of suggestions about how to solve this challenge through her presentation: Designing Computer Security Assessments to Reduce Plagiarism. Two key points were: (1) create your own assessment resources (if you use photographs as data, take them yourself, since they won’t already exist on the internet), and (2) focus less on marking the code, and more on marking student reflections.

Charles Boisvert from Sheffield Hallam University gave us a ‘lack-of-progress report’ regarding the challenges of Teaching relational database fundamentals. I noted down the idea of Nifty Assignments (Stanford University) and SQLLite, which is a SQL engine that can be used within a web browser which is used within Charles’s TestSQL website.

Data Protection and Privacy Regulations as an Inter-Active-Constructive Practice was presented by Joseph Maguire from University of Glasgow. Joseph talked about active learning, the flipped classroom and ‘jigsaw learning design’. 

Session 4: Engagement

James Davenport from the University of Bath kicked off the first afternoon session. James introduced The Institute of Coding: Addressing the UK Digital Skills Crisis (Institute of Coding website). I noted down five themes, which are led by different partners and universities: (1) university learners, (2) the digital workforce, (3) digitising professions, (4) widening participation, and (5) underpinning digital skills. James’s presentation followed by a talk by an OU colleague called Patricia Charlton, who spoke about the OU’s involvement in the Institute of Coding (OU website).

James gave two presentation in this session. His second was entitled: Teaching of Computing to Mathematics Students. In some ways, this talk reminded me of my own experiences studying discrete maths as an undergraduate (which was something that I found pretty difficult). James made an interesting point, which was: ‘the debate isn’t whether the maths department should teach programming, but how it should be taught’. This phrase made me remember a blog I wrote, Teaching programming across STEM, about the different ways that programming is taught in different parts of the OU.

The final talk in this session, Improving professionalism in first year computer science students, related to a paper by Shelagh Keogh, Jill Bradnum and Emma Anderson from Northumbria University. Some key points I noted down were: professionalism is socially constructed, that it’s something that you can’t teach – instead, it’s something that students much adopt. We were told about a skills audit, students were given one to one sessions, and they were asked to rate themselves across professional competencies so students can consider (and be responsible for) their own professional development. 

Session 5: Programming

The first presentation in the final session was by Paul Piwek from the The Open University who spoke about Learning to program: from problems to code. Paul is a module chair for the module TM112 Introduction to Computing and Information Technology 2 (Open University website), and his paper (and accompanying presentation) was co-authored by Michel Wermelinger, Robin Laney and Richard Walker.

TM112 introduces students to text based programming using Python. He presented the rationale behind the module design, explaining that were was emphasis on abstraction, worked examples and patterns. Also, students were asked to use English to perform problem decomposition. Further information about the approach that is adopted has been shared through the Computing at School community site.

Neil Gordon from the University of Hull presented: A Flexible Approach to Introductory Programming. Some of the challenges that colleagues can face include the wide variety of background of students, the gender disparity in the subject, and attainment and progression. Neil directed us to Woodfield report, and I note that there is a HEA document, entitled Issues in retention and attainment in Computer Science (PDF).

The final presentation was by David Croft who spoke about Computing with Codio at Coventry University. Codio is a cloud based tool that can be used to help with the teaching of programming.

Final thoughts

As I mentioned in the introduction, this was the second CEP conference that I’ve been to. This one was slightly different than the first; rather than having a set of parallel sessions, all the presentations took place in a single lecture theatre. I also felt the event had a slightly more formal tone, since all papers presented during the conference were also published through the ACM digital library

There are, of course, advantages and disadvantages to formality. The tie up with the ACM provides a formal and official record of the conference, but the large lecture room takes away some of the intimacy and potential for informal debate and discussion that can be so useful for both presenters and delegates at these kind of debates.

When it comes to sharing of education practice, and talking about the challenges that teachers face when working with groups of students, I personally prefer the informal over the formal. This said, I fully appreciate the pressure that institutions and individuals face regarding publishing (which is something that I’ve alluded to in a previous blog).

These points made, I still think this is really nice conference, and even though the organisers have made a step towards formalising both the conference and the community, there is still space and opportunities to share and make connections with fellow practitioners. I also thought that the titles of the themes were well chosen.

A question I asked myself at the end of the conference was: what are the main themes or topics that are important at the moment. One thought is that there are certain areas of focus that are current and important. These include the subject of: cybersecurity (in all its various forms), data science and machine learning. Another important theme may lie in the subject of professionalisation and continuing professional development. There is an implicit links to the themes that are mentioned in the various pieces of research that were highlighted by our keynote: the significance of gender, the teaching in schools, and the development of soft skills. From a day conference, I can see that there is a lot that is going on, but I also see that there is a lot that needs to be done too.

Acknowledgements

Attendance at this event was made possible thanks to the OU Technology and Education Research Group (TERG blog). Many thanks to the group convener, Karen Kear.

Permalink Add your comment
Share post
Christopher Douce

Computing Education Practice Conference

Visible to anyone in the world
Edited by Christopher Douce, Monday, 27 Feb 2017, 10:44

On 11 January 2017 I had the opportunity to attend a one day computer science education conference that was held at the University of Durham. It had been a long time since I had been to Durham. The last time had been in the late 1990s when I attended a workshop on program comprehension; other than the cathedral, I wondered whether I recognised any of the streets or landmarks. Unfortunately, I didn’t have the time to explore; it was a packed day.

What follows is a personal ‘take’ on the conference. It is, by its nature, selective; the conference attracted loads of submissions and had a number of parallel sessions. By the end of the day I was pretty tired and overwhelmed, but also inspired too.

Keynote: Sally Fincher

Sally Fincher’s keynote had the title ‘how can we talk about practice?’ Sally, who is a professor at the University of Kent, made the point that academics attribute value to abstract knowledge. She gave us an example of a chemistry paper, which communicated lots of detail in a very prescriptive and defined way. Teaching practice, Sally argued, is not like abstract knowledge; you cannot easily replicate it (and you’re not rewarded if you share it). She made the point that a paper is a terrible way to document teaching.

An accompanying question is: what would a good representation of practice look like? The challenge is that teaching is knowledge that is situated and embodied. There have been some attempts to describe or formalise learning designs but they don’t have an ‘experiential section’ and they rarely systematically described practice. 

Another question is: what does it mean to describe practice? It can include the rich description of detail, or the provision of narrative. Sally referenced the work of Elizabeth Shove, a sociologist who wrote a book entitled ‘every day practices’. A description might include the integration of different elements: meanings, skills and materials. Put another way, this could also be: stories, skills and stuff. 

An issue is that most of our documents about teaching and learning relate to skills, which can be embodied into learning objectives. An important element of practice, the stories and ‘stuff’ is very easily over looked. A thought that came to my mind as Sally was talking was: perhaps the stories are case studies? 

I made the note of the following phrase: abstractions detached from practice doesn’t help. An accompany thought is and the detail of stories represent the largest challenge; meanings of stories are implicit in the context in which they occur.

Are there any solutions to challenge of sharing our teaching expertise? Sally offers her own take on this through a textbook called Computer Science Project Work (Springer). The book presents a structure that contains a number of important sections, such as a section that can be called ‘what we did’; the structure aims to present something more than the stuff and skills. (I hope I’ve got this right!) Practice, I noted, is also about know how.

Towards the end of her keynote, I picked up on a number of themes that were especially relevant during the day: employability, engagement, curriculum design, and the importance and relevance of industrial placements.

What model versus how model: an effective way to teach computing and engineering programs

The first session I attended was by Muhammad Zeeshan Shakir from the University of the West of Scotland. The ‘how’ of teaching can be achieved by using show and tell activities. These can also be used to show students the benefit of what they’re learning. I’ve made a note of the phrases: workshops, the use of a research inspired seminar, practical implementation tasks and visits to industry. Flipped classrooms, it was argued, can be used to explain the ‘what’.

During this session I noted down a reference to something called Heterogeneous Ability-Centered Team Building (IEEE Xplore), or H-ACT-B. A key issue when it comes to groups is how to assess individual and team performance. As this was mentioned, I started to reminisce about my own undergraduate experiences of group work, where we had the challenge of working on a software maintenance project. It was an experience that still lives with me to this day.

Enhancing student engagement

This next presentation, by Ashil Ali and Raj Ramachandran spoke about the issue of student (dis)engagement, especially during long lectures. A point was made that students are wedded to their devices. A suggestion was to try to get students to engage through the devices that they are wedded to. A key phrase I noted was: ‘hijack the students’ distractions’.

A framework for CS educational research practice

Sue White, from the University of Southampton, mentioned an event that I had never heard of before, but should have done: the ACM International Computing Education Research (ICER) conference (ACM website). She also mentioned an academic that I had been told about whilst studying for my PGCE: Biggs. I noted questions about who the student is, a question about what the teacher does, and what the student does. This is, of course, linked to the important subject of the student voice (and that we need to listen to it, whilst at the same time balancing the need to support and further the discipline).

Some interesting pedagogical and computing terms that were mentioned, which included Ben-Ari and social constructivism (ACM digital library), Kolb’s learning cycle, and Laurillard’s conversational framework. I was also reminded of the ACM special interest group on Computer Science Education (ACM)

A bad analogy is like a pigeonhole

Stephen Doswell from Durham asked an interesting question: how can we assess the effectiveness of our [teaching] analogies? I noted down the phrase: analogies are only effective when properly used and the source domain is familiar to a learner. I remember that Stephen talked about a popular computer security text book and considered the way that analogies had aged (and the way that some older analogies might now be difficult to understand).

This presentation reminded me of a talk that I did over ten years ago at the Psychology of Programming Interest Groups called Metaphors we program by (PPIG). I remember it being a fun talk to do, and the accompanying paper was also pretty fun to write (although its analysis wasn’t very systematic!) I think the underlying point is the importance of considering where the learner is at, and how we can best try to convey difficult concepts.

Developing responsive personalised learning

The final session of the morning was by Samina Kawal from Oxford Brookes University. The focus of the presentation was an ebusiness module that used an approach called ‘integrative assessment’. I noted down that an idea was that coursework was used across different modules. Interestingly, there were programme level learning outcomes (whereas I am more familiar with understanding learning outcomes that are at the level of the module).

Afternoon keynote: understanding the TEF

The afternoon keynote had a really pragmatic feel to it. We were asked the question: ‘how can the HEA support the quest for teaching excellent?’ The teaching excellence is, ultimately, about making higher education into more of a market place, where students are consumers. Underpinning all this is the philosophy that education has economic benefit for the individual as opposed to being a public good that can help society as a whole. The TEF will lead to ‘badges’ that allow students to very simplistically compare one institution with another. An important point is that all institutions are different because of the environments in which they inhabit. From memory, I didn't come away from this session much the wiser.

Professional ethics in education: the need for radical change

Denise Oram, from Glyndwr University was a member of the ACM Committee of Professional Ethics. Her point was simple yet very compelling: professional attitudes and ethics is very important within computing and IT since the technologies that we create and implement have impact on people. Some interesting subjects include the internet of things, intelligent machines and eHealth. Students might, of course, ask: why do I need to know about this stuff? One approach to answer this question is to make use of debates to expose issues.

During this session I made a note of the BCS Computing at School website, a reference to something called models of ethical compliance and the way that the study of ethics (with respect to computing) connects to a wide range of subject, including: law, environment, philosophy, sociology and psychology.

Sketching design using the five design sheets methodology

Design, of course, is another subjects that is connected to and associated with computing and IT. Jonathan Roberts from Bangor university presents a design method that uses five different sheets of paper which encourages users to ‘think, design, build and evaluate’. There were references to related approaches and topics, such as the idea of using ‘6 thinking hats’, the importance of sketching and the distinction between convergent vs divergent thinking. A point was made that perhaps design should feature in the CS curriculum.

During this session, I thought of a number of OU modules that I know about and have looked at, such as U101 Design Thinking, T217 Design Essentials (its predecessor module taught about different design thinking approaches), and a higher level module T317 Innovation designing for change. I also thought about TM356 Interaction design and the user experience which touches upon design thinking. More information about TM356 can be found by looking at a series of accompanying blog posts (OU blog).

Embedding cybersecurity in the computer science curriculum

Alastair Irons from Northumbria university began by offering a bit of context: that cybersecurity it important, that it is a subject that is garnering a lot of attention, and there is the view that there is a significant skills gap; I made a note that two million posts are to be filled by 2020.

To solve this challenge, government and industry are looking to schools, colleges and universities for cybersecurity talent. I made a note of a statistic: 62% of employers couldn’t fill cybersecurity jobs.

An interesting reference is a document entitled: cybersecurity principles and learning outcomes for computer science and IT related degrees (PDF) Some accompanying questions were: (1) how will or could cybersecurity be embedded in your curriculum? (2) what support is needed or would be helpful? and (3) how might practioners engage in a community of practice (CoP)? I noted that this session led to some interesting debates: should cybersecurity be an undergraduate or a postgraduate subject? Also, to what extent are institutions developing degree apprenticeship qualifications?

Success in CS education: the challenge of keeping students

Neil Gordon, from the University of Hull, emphasised a number of important challenges. Computing and IT is a popular subject but some students are performing poorly. Neil referenced something called the Shadbolt review of computer sciences degree accreditation and graduate employability (PDF). I haven’t had time to read the report (since it is very long), but the executive summary points to higher than expected unemployment of new graduates, a point which ‘is at odds with significant demand from employers and the needs of the burgeoning digital economy’ (p.3). 

Neil touched on a number of different subjects and areas, including the known gender imbalance, the Computing at School Curriculum, streaming students by programming skills, the importance of attainment and retention, using innovative pedagogies (such as gamification) and improving community engagement.

Design and implementation of a web broadcasting learning platform

The final presentation that I attended was by John Busch. It took me a few minutes to understand what John’s presentation was all about, but as soon as I grasped it, I was very interested. In essence, John’s talk was about how to use and apply technology to help with the running of very large programming laboratories.

One of the most powerful approaches to learn programming has been to watch someone else at work, and to also copy what they’re doing, so you get ‘a feel’ for the instructions, commands and constructs that can be used. You shouldn’t just watch or listen: you need to ‘do’ and build.

If you’re delivering a session in a huge laboratory with one hundred and fifty students there are two fundamental problems (1) students can’t see what you’re doing if you’re projecting code on a big whiteboard at the front of the class, and (2) everyone learns at different speeds: some students might be lost, whereas others might be bored. One solution could be to run programming webcasts that each student in the lab can see how code is made, and also provide some functionality where a student can seek help at different times.

We were told about a number of different technologies, such as open cast, Fuze, Saba, Adobe Connect and something called Screenleap. I made note of other stuff, such as Open Broadcaster Software. Other bits of tech were mentioned, such as Nginx with RTMP (Wikipedia) A system called iLecture was created that allowed students to raise ‘support tickets’ to allow a student to ask a lecturer to look at the code that was being created.

I found all this fascinating; a home grown solution made up of bits of Open Source software that allowed lecturers to enable students and lecturers to share screens, to enable students to study the nuts and bolts of programming. It made me return to thoughts about ‘programming as performance’ and the need to find some kind of theoretical foundation.

Reflections

My own talk was about something called the Open University group tuition policy. Not only does this have the potential to allow students to access a wider range of learning events (if implemented well), it also gives associate lecturers the opportunity to work more closely together through creating something like a ‘community of practice’. In some ways, the conference was about creating that same community, but for a wider group of computer science educators. 

I only went to relatively small number of presentations, since there were three parallel sessions throughout the day. I was struck by the diversity of the presentations, and was given a welcome reminder about how exciting Computing and IT is as a subject. This excitement comes from the fact that it now touches so many other subjects and disciplines.

Permalink
Share post

This blog might contain posts that are only visible to logged-in users, or where only logged-in users can comment. If you have an account on the system, please log in for full access.

Total visits to this blog: 1976377