OU blog

Personal Blogs

Christopher Douce

Using the cloud to get to the OU campus

Visible to anyone in the world
Edited by Christopher Douce, Thursday, 21 Nov 2019, 11:25

I get to visit the Open University campus in Milton Keynes with alarming regularity and getting there is always a bit of a trauma; I need to take three trains and then a shuttle bus.  After doing this journey for about two years, I’ve managed to get the timing down to a fine art, but sometimes things don’t go as smoothly as you hope:  I sometimes miss the shuttle bus and I have to catch a taxi. 

I can’t help the feeling that catching a taxi, on your own, is an extraordinary extravagance.  About a year ago, when my train was delayed, I got chatting to a fellow train traveller who was sat opposite me in the same carriage.  I noticed that he was rifling through some papers that contained the unmistakeable university logo.

‘Are you heading to Walton Hall?’ I asked.  It turned out that he was, and my fellow traveller, like me, was planning to catch a taxi to the campus.

‘Fancy sharing a cab?’ I asked.

I turned out that my fellow traveller, who I had never met before, had pretty much the same job as I had: he had the job title of staff tutor, but was based in Wales and worked in the Health and Social Care faculty.  He had travelled up to Milton Keynes after spending a night out with friends in London.  If I hadn’t nosily spotted his university papers, we would have incurred double the amount of expenses, and missed out on an opportunity for a nice chat.

Sharing lifts

Hundreds of people work at The Open University campus in Milton Keynes.  There are so many people travelling between the university and the train station that the university puts on a shuttle bus at peak hours - but what happens if you travel outside of peak hours?  The answer is you either catch a cab (which is costly), or you try to catch a local bus which takes ages and is pretty infrequent.

I don’t mind sharing taxi rides with colleagues.  The problem is that because there are so many of them that I don’t know who they are!  Even if I did know who they were, they might be in another carriage and have hailed and taxi and left the station forecourt before I had a chance to catch up with them.

One solution might be to loiter around the taxi rank and bellow: ‘is there anyone here who is going to THE OPEN UNIVERSITY? Does anyone WANT TO SHARE A CAB?!’ and see what happens.  The problem is that since I’m exceptionally English and doing things like this instils in me a morbid fear of being arrested.

Connections

When I was travelling to the campus one morning, an idle thought went through my mind.  I thought: ‘wouldn’t it be good if I could just take out my mobile phone, start an app, and push a button that says “I’m on the train from London to Milton Keynes – and I would be happy to share a lift to the campus if anyone is up for it…”’ 

This imaginary app would then tell me whether there was anyone else who was on the same train as me, or offer me an alert if anyone on the train would like to share a ride to my destination.  Another variation of this would be to try to find strangers to share journeys with, who might be going to roughly the same part of the city that you were travelling to.  To keep it simple, I thought, ‘no, that would just increase the complexity – let’s just think about this in terms of a single organisation’.

I imagined my app would be able to display the first name of fellow travellers, the faculty or department that they were in (which would be really useful in terms of facilitating a conversation), and also have a picture – so you know what a fellow traveller may look like when you get to the taxi rank.

There would be two obvious wins and one positive side effect.  The two wins were economic (it saves the university money), and environmental (less fuel is burnt to get to the campus).  The side effect is that you might be able to have some great chats, which might help you to keep up to date with what’s going on across the university.

Technical questions

So, how might we make this idea a reality?  Well, we need to figure out how to write an app.  Secondly, we need to figure out how to save data (so we can make a record of who is travelling on which train).  Thirdly, we need to get some data somehow (so we can get information about different trains).  Finally, we need to do a bit of ‘data crunching’ somewhere so we can be alerted as to whether there are other people on our train that we could share a lift with.

Creating an app

So, how do we go about creating an app?  The answer is: there are loads of different ways.  You can either create ‘native apps’ or you could create ‘web apps’ using HTML 5 and Javascript. 

When it comes to native apps, you might want to create an app for either an Android phone, or an iPhone.  If you’re thinking of developing an app for an iPhone, you might use xCode, which is a toolset from Apple (where there is a fancy new programming language called Swift). 

If you’re thinking of developing for an Android phone, you might consider using Android Studio, NetBeans (NBAndroid) or MIT AppInventor (I’m sure there are other tools out there!)  The problem, of course, is that some OU staff use Android phones, and some use iPhones.  To attempt to take the pain away from the nightmare of different platforms, there’s something called PhoneGap (but I don’t know too much about that… it’s all new to me!)

Storing data

Assuming that we build an app, then how do we store (and share) data?  This is where the cloud comes in.  The problem is that I don’t want to spend any money setting up services.  Plus, it’s been an absolute age since I’ve done any of that stuff.  Another solution is to make use of services from existing businesses that have already done all the hard work for you.

There are a quite a few different providers.  One of the biggest is Amazon.  Amazon offers a service that allows you to ‘plug into’ their existing computing and network infrastructure, allowing you to create and use your own virtual machines, which then can store data (since these virtual machines can host databases, like MySQL).  Rather than having to pay, host, and power a whole server (which, arguably, is likely to remain idle for quite a lot of time), you can instead pay for how much processor time, network capacity and data storage you consume.  It’s as if a server has become a utility.  Rather than having to worry about backups and whether you need to buy more processing power, this can all be looked after by a third party: you pay for what you use, allowing you to concentrate on the task of writing code and solving your problem.

Of course, you might not want to use Amazon.  If not, there are loads of other cloud data and service providers you might use.  Two of them who come to mind are that of Rackspace and Microsoft.  The interesting thing about Microsoft (and providers who are similar to them), is that you can choose where your virtual servers live.  If most of your customers are located in North America, it probably makes sense (in terms of network performance) to have your virtual servers served from that part of the world.  If more of your users are located in Europe (such as users who are travelling to and from Milton Keynes), you’re likely to want to host your virtual machines in data centres in Europe.

Another thought is: perhaps you don’t want to store your data in machines that are managed by Amazon or Microsoft.  If so, another approach could be to set up your own private cloud (providing you have your own infrastructure to do this, of course).  You might want to do this if your organisation has already invested quite a lot of capital into IT resources, or government or institutional policy dictates that you wish to make sure that your data is only within the remit of a particular jurisdiction.  Everything in life is always a compromise.  You might want to use your own private cloud as opposed to using a public cloud, but a private cloud is likely to cost in terms of hardware, power and administrative overheads.

If I were seriously writing this app, what would I do?  I would ask the IT people in The Open University to see if they have got a cloud system that I could use.  Whilst I wait for them to get back to me (which can sometimes take quite some time) I also might try to experiment and create a prototype using a public cloud provider, since some of them can give you ‘trial accounts’.

Getting data

Let’s say I’m going to a module meeting in Milton Keynes and I’m sat on the 8.46 train from London Euston.  There are two things I need to do: I need to say ‘I’m on this train’, which means storing a record so other people (meaning: other Open University colleagues) can see that I would be up for sharing a taxi, and also recording which train I was on.  The problem is: I don’t want to go through the trouble of entering ‘8.46 from Euston, London Midland’, since I’m lazy and I don’t have too much patience.  Plus, we need to iron out any ambiguity.

One way to solve this problem is see what trains are currently running (because, what happens if my train is delayed?)  Thankfully, Network Rail provides loads of data feeds (Network Rail), which we could use to choose the right train (and, I’m wondering whether we might be able to use the magic of GPS positioning too!)

As a brief aside, being a London resident, I’m a great fan of an app called CityMapper  (CityMapper website).  It gives you loads of information about different bus routes, trains, underground stations, and hooks up to Google Maps so you can see where you’re going.  An interesting question is: how does it work?  One answer lies with the availability of different data feeds, such as the data feeds that Transport for London provides (TfL data feed summary page).  

Why do TfL provide all this data?  The answer is: that TfL are in the business of providing transport, they’re not in the business of creating new apps for new-fangled computing devices: that’s not their core business.  Once feeds are made available, they can be used in new and creative ways.

Back to our ‘taxi ride sharing’ scenario: let’s say we’ve got a group of four people on the train that are prepared to share a ride to the campus, then what happens?  Who is going to make the call to the taxi company?  One thought is that the colleague who instigated a ‘taxi share request’ could do that job.  Or, alternatively, the taxi app might do it for us (if our chosen taxi company has some kind of mechanism to accept taxi bookings from recognised apps). 

Other issues

When we start to think about all this, we come up against questions of user identity and what it means in terms of a mobile device.  Some of my mobile apps make use of my Google+ account, whereas others make use of Facebook.  This can make things a whole lot easier, but it does worry me a little, mostly because I don’t know the extent to which my data is being used (we’re again back to the question of compromise: convenience traded off for ease of use).  One thing that we might want to do is to create our own ‘identity’ management system.

Another issue is that we’re beginning to step into is the currently fashionable area of smart cities (Wikipedia); the possibility that journeys through urban environments can be aided and abetted by the use and sharing of data.  (Not to mention costs and communications).

Final thoughts

Just as I was finishing this blog, the following email popped into my inbox: ‘would anyone like to share a taxi from MK station tomorrow?  I have a choice of trains, the first one arriving MK at 10:02, if that fits with anyone else’s plans?’

I remember this other time when I was travelling to the University of West of England from Paddington to Bristol Parkway train station.  When I got to Bristol Parkway, I had to catch a taxi from the station to the campus.  When I arrived on campus and started to walk where I needed to go, I recognised someone.  That someone was the gentleman who was sitting on the next row along from me.  Again, if only we had known, or had talked, or hadn’t been so English about our early morning journey, we could have shared a taxi together.

A final question is: given all the things that I’ve found out, am I going to go ahead and create this app?  Sadly, I’ve got a whole load of other deadlines to attend to, which means that I can’t afford to invest the time – but I would really like to, and I hope that someone does go ahead and creates it!  I, for one, would really like to give it a try.

In the meantime, what I have decided to do is to make more of an effort to chat to the people who catch the same shuttle bus as I do.  This way, if the train ever gets delayed, I might have more of a clue about who I could share a taxi with. 

Permalink Add your comment
Share post
Christopher Douce

Workshop: using technology for communication and to support learning

Visible to anyone in the world
Edited by Christopher Douce, Friday, 10 Apr 2015, 17:03

On 26 March, I went to two seminars: one about the history of computing, and another one about augmentative and alternative communication.  This is a quick blog summary about the latter event (which can be viewed through YouTube); it’s not a subject I know too much about (and I thought it might be of interest to anyone who might be taking the H810 Accessible on-line learning module which is a part of the MA degree in on-line and distance education).

This event also relates to an internal project called SeGA, which is short for Securing Greater Accessbility.  SeGA is a university initiative that aims to thoroughly embed accessibility practice within the Open University.

Assistive technology

The seminar (or workshop) was presented Marion Stanton from Candle AAC (website). As far as I understood things, Candle AAC a not for profit organisation that offers help and advice about communication technologies for people who have difficulty with movement and communication.  Her talk was focused on technology and approaches that could help people (primarily those who are aged 5 through 18) who have complex needs.  Also, her focus was on general technology rather than the capabilities of specific products.

One of her early presentation slides presented a range of different tools and technologies.  These ranged from low tech communication aids, eye gaze technology, alternative pointing devices (which could be used to replace a mouse), alternative keyboards, optical character recognition, voice recognition, idea mapping software, word prediction and software that can offer support to people who have dyslexia.

An important point that I noted is that everyone is different.  This reminded me of a phrase I heard at another Open University event, that ‘when you’ve met one person who has autism, you’ve met one person who has autism’.

A significant area of focus of the morning was the subject of Augmentative and Alternative Communication (Wikipedia), or AAC for short.  Augmentative means that a technology can be used as well as (or to supplement) speech, and alternative means that a technology can be used instead of speech.  AAC can also be sometimes used as an alternative to writing.

Marion exposed an interesting (and misplaced) assumption, which was, ‘if you give someone an alternative way of communicating, then surely there will be less incentive to use other forms of communication?’ Research suggests that this certainly isn’t the case.  In fact, we were told that it can actually help and can encourage other forms of communication.

During this section of the workshop, we were given what amounted to a brief history of AAC.  (In H810, there is also a section where students are told something about the history of assistive technologies).  We were told about really low tech approaches and shown photographs of incredibly bulky technology. 

Activity and links

We were all asked a seemingly simple question: what is communication?  After some debate in our workshop (sharing views that it was about connection and emotion), we were told that, essentially, there is an expressive side and there is a receptive side.

A related question is: what does someone actually need?  This was a question that connected to the earlier point that everyone is different.  This led us to being briefly introduced to Makaton (Makaton charity website), Signalong (Signalong website), and Paget Gormon (Paget Gorman Society).  It was also interesting to hear about the different levels of technology, i.e. there are low, medium and high technology aids.  High technology aids, we were told, were invariably computing devices or PC based.  An another dimension to high technology aids is that they might be potentially linked to environmental control systems, such as systems within a ‘smart house’, to assist with independent living.  One example might be an interface to open and close curtains, or to control and to set heating levels.

Another links I made a note of was Talking Mats, which has now become an app, Minspeak, Sensory Software, and Widgit.

Choosing the right technology

Given such a wide variety of tools and technologies a difficult question to address is: which one should we choose, or which one is the most appropriate?  Not only does the choice of tools matter, but also how tools are set up and configured for individual users.  A tool might be very suitable but configured inappropriately.  Uncovering the correct settings (and choosing the right tools) requires experienced and expert assessors not making assumptions.

The choice of technology is, of course very dependent upon individual circumstances, and different experts may well give different recommendations.  An important point was that it’s not possible to be an expert in everything.

During the session, we were told about AAC technologies, but also the importance of subject specific learning was also briefly addressed.  One company was mentioned, Splash Software which developed software to help with the learning of mathematics.  (The accessibility of mathematics is also a topic that is briefly covered in H810).  This implicitly points to the complexities inherent in making the important details of academic subjects accessible.  Technology isn’t going be solve everything.  Pedagogy and the selection of appropriate support are important too.

Time is also very important.  A task that might take someone an hour to complete might take another person, using an assistive technology, a whole day to complete.  Assistive technologies permit access and aim to ‘level the playing field’, but all students have to work according to the same module calendar.  This also relates to a point that I picked from colleagues who used to work in JISC TechDIS.  The point was that even if something is technically access, the usability constraints might cause something to become practically inaccessible.

Final thoughts

At the start of the workshop, tablet computers were mentioned.  A point was made that although they’re very useful, tablet computers (or ‘apps’) don’t solve everything: it very much depends on the needs of an individual.  Towards the end of the session, I made a note of another website:  Apps for AAC. 

I found the time to have a quick look at this site and I found it pretty astonishing since it describes a total of over two hundred and sixty different apps of different types.  This, in some way, highlights the challenge.  There are loads of choices, and making a choice (and being aware of what is out there), isn’t easy.  Although I have known of this as a subject (and research) area for quite some time, it is clearly one that is a lot bigger and more wide ranging than I had ever imagined.

Permalink Add your comment
Share post
Christopher Douce

South East region: Associate Lecturer Development Conference, March 2015

Visible to anyone in the world

On 2 March I went to the South East region associate lecturer development conference.  Although the regional office has been closed, it still exists as an important administrative unit within the university.  This time, the conference was held at The River Centre, in Tonbridge, which was a conference venue I had never been to before. 

This blog post aims to summarise the different sessions that I attended during the day, and has been written using notes that I made during the day.  I hope it is useful for those who came along to the event, and other colleagues within the university who might be seeking ideas for their own sessions.

A collaborative approach to teaching a level 1 module

The conference had two workshops; a morning workshop and an afternoon workshop.  The first workshop I went to was by Bill Adler, who tutors on L161 Exploring Languages and Cultures.  The aim of the workshop was just to share some experience of teaching as collaboration. 

L161is a compulsory level 1 (first year equivalent) language studies module that addresses intercultural skills and awareness.  It consists of four different books (one for each block) and a module web site.  Approximately one thousand students at any one time might be studying the module.  Interestingly, the module makes extensive use of on-line forums.  To make this work, tutors are allocated to a number of clusters (which is an idea which immediately made me think of the group tuition policy).  The reason for this is that one thousand students contributing to a single group of discussion forums is clearly too many; some students could be overwhelmed with posts.  A cluster that comprises of around 250 students is likely to be a lot more manageable, and there’s always something that is going on to make it sufficiently interesting.

Bill talked us through two different activities that can take place through his module.  The first was an autobiography of intercultural encounters (Council of Europe website).  We gave this a go, and this led to a reflection about our own cultural identity and what it meant.

The second was how to develop reading skills in a foreign language.  A challenge with this module is that everyone might be learning a different language (you might have students studying French, Spanish, or German, for instance).  A way around this was to choose and activity and a language that isn’t likely to be too familiar to students who are taking the module.  Our challenge (which we accepted) was to try our best to decipher a menu that was written in Welsh, without knowing anything about the language.  After having a go, we swapped strategies, and we discovered that, actually, we could figure out quite a lot!  Different participants used different strategies.

During the session, I made a couple of other notes.  One note was that: different students mean different backgrounds, which mean different skills and perspectives.  Diversity creates richness, and this is a point that is reflected in the module. 

Another note that I made was about the concept of peer monitoring.  Since tutors are working in clusters, there was an opportunity to allow tutors to work more closely together with each other.

The closing activity was to reflect on our own collaborative practice.  I remember the point that working together isn’t too difficult, but true in-depth collaboration takes time to facilitate and develop, since you have to know and trust the other people who you’re working with.

Also, collaboration can mean the sharing of materials.  If one tutor is particularly busy, another one can help to share the load. The broad point of the session was: there are quite a few opportunities for tutor collaboration.  It is, however, important that the staff tutor (or line manager) and module team work together to facilitate that collaboration.

Yet again on correspondence tuition: how do we teach through marking?

Correspondence is a perennial subject in AL development conferences, but I haven’t been to a session about it for quite a while.  In fact, the last one I went to could have been at an event for design ALs over two years ago.

This session was facilitated by Vicky Roupa, who spoke about the research that she carried out as a part of her OpenPAD project.  OpenPAD is a university ‘professional academic development’ programme, and leads to fellowship of the Higher Education Academy. 

Vicky mentioned the Supporting Open Learners reader, a book that I remember reading when I first joined the university.  Vicky made the point that correspondence tuition is, of course, the main form of teaching.  Other points that I noted was that it was important to engage in a dialogue with the student, and that correspondence tuition is an action that is student led.

We were asked a number of questions: what do we teach?  How do we encourage students to engage?  How do we develop writing so it becomes a major key to learning?

An important point was that students don’t always read (or, indeed, know about) the correspondence teaching that they have been given.  Also, students might not understand the feedback that they have been given, or be able to use the guidance.

To try to engage students, one approach is to choose the most important points to focus on.  Our challenge is to choose which comments are best placed to move a student along.  One other tip was to add links to useful resources within the script comments, such as a link to certain sections in the Skills for Study website.

Another point was that receiving feedback from a tutor can be sometimes tough and involves lots of different emotions.  Vicky’s research was all about trying to gather ‘feedback on feedback’.  Her point is that tutors often mark assignments, return them to students, and then never hear back from them.  Closing the feedback loop can have the potential of helping a tutor to learn more about how to improve their teaching practice.  This was connected to an earlier project (which was mentioned at an earlier South East conference), where students are encouraged to talk through their views about feedback.  Information about this project is available from the Languages Open Resource Online repository.

Towards the end of the session, I made a few final notes (and questions) which might resonate with fellow tutors.  These were: ‘are we assessing or are we teaching?’ (it does depend on the design of the module) and ‘avoid judging too much and too powerfully’ (so we can engage in a meaningful dialog with students).

Reflections

This AL development conference seemed to be smaller than other that I’ve been to.   For some reason, the autumn events seem to be a whole lot busier than the spring events.  I would have (personally) liked to have gone to one more session, to see what else was going on, but I do appreciate that timing is always going to be a challenge (tutors, of course, give up a lot of their Saturdays already!)

The biggest take away points of the day came from interactions with the other tutors in the sessions.  I found the activity in the morning session interesting (and fun!), and found the sharing of views about correspondence tuition useful and reassuring.

Permalink Add your comment
Share post
Christopher Douce

HEA new to teaching workshop

Visible to anyone in the world

On 19 February 2015, I went to something called the HEA new to teaching workshop which was a part of a larger HEA ‘transitions conference’.  Now, I’ll be the first to admit that I’m not new to teaching, but there was a bit of the workshop that I was really interested in: a section that was about how to teach introductory programming.  The reason for my interest is that teaching programming is pretty difficult: some students excel, whereas other students struggle.

The session was facilitated by Karen Fraser from the HEA.  I’ve met Karen numerous times before, but I have never been to a session that Karen ran entirely on her own.  Instead, her role has been always to facilitate and introduce other speakers.

The aims of the day were to think about and reflect on our teaching practice, consider different ways of teaching, consider what things we are doing well, and share practice between each other.  This is a quick blog summary of the event.  I’ve written it for a number of reasons: it’s a set of notes that also contains links to useful resources, a way to tell my line managers what I’m getting up to, and to share some personal reflections about the event with Open University and other colleagues.

Professions

Karen opened the session by asking us a couple of questions: ‘is computing a profession?’ and ‘is academia a profession?’  My immediate response to the first question is: yes, because there’s a body called the British Computer Society (BCS.org) which aims to develop the professionalism of those working within the computing and IT industry.

I noted down that the purpose of the HEA is to enhance professionalism in higher education.  There are a number of issues that it addresses: reward and recognition, career progression, and continuing professional development.  In some respects, these areas can be connected to something called the Professional Standards Framework (PSF) where HE professionals can apply to gain different levels of professional recognition.  Karen briefly summarised the PSF, telling us that it contained six aspects of core knowledge, five areas of activity, and four professional values.

Returning to the original question, did we hold the view that higher education is a profession?  From memory, I believe the consensus was that higher education should be viewed as one.  It was also interesting to hear that the HEA has applied for a charter to become a professional society in the same way that the BCS is.

Teaching and learning

It might sound obvious, but one of the key aspects of professionalism in higher education is the need to foster and continually update knowledge and understanding about how students learn, both generally, and within their subject or disciplinary areas.

These key points led us to a discussion about the different types of teaching techniques that we could use in our discipline.  These ranged from the use of role play, applying a technique called action learning and demonstrating, such as showing students what code looks like in a debugger.  At this point I had a thought about the virtues of animations.  When I was industry I learnt a lot when I watched another more experienced programmer at work.  This short discussion was immediately making me think about what might help students to get to grips with the fundamentals of computing.

In my notes, I made the comment: ‘pair programming: advantages and disadvantages’.  I’m not exactly sure what I meant by this, but gently picking apart this theme immediately suggests a broad range of different issues: the importance of continuous learning within the computing and IT industry, the question of what skills industry is looking for and what universities can do to help, and the importance of soft skills in subjects such as IT and computing.

Teaching introductory programming

The next part of the session moved from considering the academic as a profession to the specifics about teaching of introductory programming.

We discussed some of the problems and challenges: students need to know about different programming languages and tools, and there is also the necessity to develop problem solving skills and increase student’s awareness of strategies of programming design and implementation.  A key point was that programming is a creative exercise; it’s all about the solving of new problems.  A perpetual challenge is how to map (or translate) real world problems into code.

Karen showed us a slide that asked a single question: ‘where do students struggle and what do you think their problems are?’  During the resulting discussion, I made a note of the following points: as lecturers we can’t teach programming, we can only help students to learn it; students need to put ‘the hours in’ (since programming is like any skilled activity).  Also, the context for learning is important: we need to explain why we’re doing what we’re doing.

Other key points were: the importance of expectations, inexperience and confidence; the importance of how to decompose problems, and asking students whether they are fundamentally interested in the subject.  An interesting question (to students) could be: ‘are you prepared to be confused?’ and asking students to reflect on their own experience with computing devices and their knowledge of hardware and software.

Some other interesting points related to the activity (or exercise) of ‘making a cup of tea’, to learn the idea of problem decomposition (this, incidentally, is an exercise that some of our Open University TU100 tutors use at a programming day school).  Other skills might include the ability to identify sequences, patterns and steps (along with understanding how to do, and translate into computer code basic arithmetic).  Finally, MOOCs (free on-line courses) were mentioned as possible way to allow students to acquire background knowledge.  One thought was that perhaps a MOOC might help students transition between A-level and degree level study.

Another question was introduced: why is teaching (or learning) programming so difficult?  Some tentative suggestions were that programming is a skill, and it is something that is learnt by doing, and also programming isn’t a prerequisite for computing modules.  There is also the challenge of dealing with the syntax (or structure) of programming languages, and that students might not have experience of important concepts, such as data typing.

We were taken through two other slides: thoughts about problems with students (a lack of analytical, reasoning and planning skills?), and thoughts about problems with lecturers (a disconnect in terms of communication and issues surrounding instructional materials, teaching methods and teaching strategies). These problems can have impacts.  These might be students becoming disillusioned and the waning of enthusiasm which could lead to a failure to attend practical classes.   But what could we (as lecturers or educators) do?  Some thoughts related to the importance of learning design, early identification when students get lost, the importance of fast feedback, and the encouragement of reflection.

All this led to a discussion that had the title: ‘what delivery techniques could we use to engage students and help them understand difficult concepts?’  The group came up with the following thoughts (amongst others):  Use of the institutional virtual learning environment and flipped classrooms (Wikipedia),  the use of small groups, facilitated debates, use of media stories, the creation of animation to demonstrate ideas, translation of algorithms into ‘physical theatre’ (pretending students are different values based on height), use of robots, the idea of ‘code as a performance’ (as something the lecturers, or students create front of others, potentially also demonstrating failure), application of peer assessment, use of in-class question and response systems, helping students to create their own resources, and inviting students to present different ideas to each other.

An important point was made: research (I’m not sure which research!) has shown that students have a hierarchy of pedagogical preferences when it comes to learning programming: students like programming lab sessions more than they like working on projects.  Lectures, it seems, isn’t viewed as an effective way to teach programming.  Thinking back to my own experience as an undergraduate (when I had to learn a programming language called Pascal), I can completely relate to this.

On the subject of peer assessment, we were introduced to a system called Peerwise (University of Auckland).   I hadn’t heard of this system before.  We were shown a brief introductory video about the system (Peerwise website).   I have heard of other peer assessment systems, such as WebPA which (I understand) used to be funded by JISC.  An idle thought is that it would be interesting to do a comprehensive review of these peer assessment systems (since I seem to think there are a few other systems out there).  

After lunch…

A provocative question was posed in the first session after lunch: should programming be taught in the first year of a degree?  An alternative perspective was that perhaps we ought to first teach other subjects, such as data structures and algorithms before moving onto programming.  This way, students get the opportunity to understand more about some of the fundamental concepts of software and computing.  My own view is one that connects back to earlier discussions, namely, that since programming is a fundamental skill, and it’s something that takes a long time to master, we need to give students the experience of what is meant by programming early on in the curriculum.

The next session was about sharing good practice in lecturers.  One of the biggest take away tips from the day was the idea of changing something every fourteen minutes: divide an hour lecture into different sections that are punctuated by videos, run discussion activities or question and answer sessions, get willing students to come to the front of the class, or change the entire tenor (or tone) of a lecture by telling a story or an anecdote, or take a bit of time to introduce other resources, such as MOOCs.   Another thought is to ask students to prepare something for a tutorial (but always remember that you’ve done this! On the subject of videos, we were offered an example: a clip entitled The Friendship Algorithm (YouTube) from the comedy series The Big Bang Theory.

The workshop ended with a chat about a range of different issues.  We chatted about the importance of reflection so we can understand more about our performance as lecturers, and also the importance of reflecting on what our students have learnt from our teaching practice.  Another topic was the importance of feedback, and how feedback is perceived by students. 

A final take away point was a reference to a paper by Chickering and Gamson entitled Seven Principles for Good Practice in Undergraduate Education (Washington news centre, PDF).  Although there isn’t anything in this paper that struck me as substantially new (which was published around twenty five years ago), it does represent a neat set of principles that can be fairly easily remembered and internalised.  When I was looking through the paper, one thought was: ‘how might these principles be translated or adapted to the on-line distance education context?’ or ‘what attributes of a module design might adhere to these principles?’

Final thoughts

Not long after I joined this session, Karen said to me, ‘you’re not new to teaching, are you Chris?’ In some respects this question was a challenge.  It was also a challenge that immediately led to a reflection.  The answer was: ‘I’m not new to teaching, but I’m here to see if there is anything new I can learn’.  

I was there for two reasons.  The first reason is that one of my jobs is to help to induct new tutors to the university and to help to run associate lecturer development sessions, which means it would be useful to know how the HEA does things.  Secondly, as mentioned earlier, I have an interest in the teaching of introductory computing and programming.

The whole day turned out to be useful: Karen’s discussion about the professionalisation of higher education was interesting and informative, and the day turned out to be a useful opportunity to share teaching practice and to learn about new resources.  By the end of the day I ended up coming out of the session with more questions than I went in with.  This, of course, is a sign of a good day.

Permalink Add your comment
Share post
Christopher Douce

Experiencing a T216 Cisco day school

Visible to anyone in the world
Edited by Christopher Douce, Friday, 20 Feb 2015, 14:13

On 17 January I found the time to attend a T216 (OU website) day school that was hosted at London Metropolitan university.  T216 is a module that is all about Cisco networking and, in some respects, it’s a little bit different to other OU modules, but it’s different in a good way. 

Students who study T216 can gain credits towards their degrees whilst at the same time taking a set of vendor exams that allows them to gain a widely recognised industrial qualification.  You study one module, and have the potential to gain two different outcomes.

Labs

Another way that T216 differs to other OU modules is that students are required to attend a number of compulsory lab sessions.  These lab sessions are opportunities for students to get their hands on real Cisco equipment: the same type of equipment that powers much of the internet.

I have to confess that I’m not a network engineer, but have been a student of networking in the past.  I first studied it as an undergraduate (when things were very different) and then briefly went down the Microsoft systems engineer certification route, but I’ve always known that the official Cisco certifications are a whole lot more demanding.

When I worked in industry, I once made a case to develop a product that could be used to help to teach the fundamentals of computer networking, using a set of tiny PC-like computers.  When I was heading to this event, I remembered these old ideas and I had two questions in my mind. The first was: what is the Cisco way of teaching networking and, secondly, what might happen in a Cisco lab.

The teaching bit

I met my colleague in the foyer of the university and I was quickly taken to teaching lab where a lecture was taking place.  I found a seat at one of the empty workstations and started to listen, hoping I would understand something.

‘How do switches learn mac addresses?’ our instructor asked.  The class was still pretty quiet: the students hadn’t yet warmed up yet.  I knew what a ‘mac’ address was: it’s a unique id that is used to identify a network node.  You can have them on either Ethernet cards and are used by wireless devices (as far as I know), but in this context, the lecturer was only talking about wired networks.  I also knew what a switch was too: it’s a device that decides where different signals (or frames) should be transmitted to.  Switches have ‘ports’, which are linked to physical cables (if I’ve got this right!)

The answer was: the switch populates the CAM tables, and if it doesn’t know where to send something, the switch transmits everything on every port by doing a broadcast, so it gets to behave a bit like a ‘hub’.  Broadcasting also happens if a CAM table gets full, and this is something that hackers can exploit.  To deal with this, there’s also something called port security.  To make things even more complicated, there are different types of port security too.

Within fifteen minutes, my head was exploding with in-depth technical detail.  I was also reminded about the different layers of the ISO 7-layer networking model (‘a switch is a layer 2 device whereas a hub is a layer 1 device’): I was being reminded about parts of my undergraduate studies.

During the teaching part of the day, we were introduced to the concept of a VLAN and its benefits, and the concept of ‘VLAN trunks’. I also made a note of the glorious phrase ‘a router on a stick’. 

On the subject of packet routing and routers (which was a ‘level 3’ device, apparently), other concepts were introduced, such as a ‘routing table’ and different types of dynamic routing protocols, which had names like: EIGRP (enhanced interior gateway routing protocol), OSPF (open shortest path first) and RIP (routing information protocol).  These protocols were different in terms of the extent to which they were connected to vendors, and the way they approached ‘cost’.  Cost, in networking terms (it seemed) could be considered in terms of networking distance, or state (or quality?) of a link.

I appreciate all this sounds pretty hard-core technical, but what does all this mean?  Routing protocols (as far as I understand) are important, since they convey the status of the network to the other magic devices that keep the internet working.  If there is a bit of the internet that stops working, it’s important that other devices know about it, so they can channel packets around the bits of it that are having problems.

During this part of the class, I had another flashback to my undergrad years, where I studied different types of computer algorithms.  One of those algorithms, called Dijkstra’s Algorithm, was all about finding the quickest path through a network.  His algorithm can be used to help your satnav to find the shortest route to a destination, or to find your way around the London Underground Tube map.  It can also be used to direct internet traffic.  If you’re interested in this kind of stuff, I recommend you have a quick look at M269 Algorithms, Data Structures and Computability.  In computing (as with networks) everything is connected (in one way or another!)

Other ‘teaching bits’ included information about something called an ‘access control list’ (which allows for network filtering), DHCP (an abbreviation for Dynamic Host Configuration Protocol) and NAT (network address translation).  This connected to the point that there are two different internet standards: IPv4 and IPv6.  Please don’t ask me about IPv6, because I don’t know too much about it, but what I do know is that NAT is like a ‘fix’ to get around the problem that there are more internet enabled devices in the world than there are IPv4 internet addresses.  There’s also something called PAD, or port-address translation (but I don’t know too much about).

In essence, we were being taught about the nuts and bolts of the internet and how it worked.  It’s all very well hearing theory, but nothing beats actually playing with physical hardware.  That’s when the lab session comes in.

The playing bit

We had a task to do: we had to connect three different routers together, configure them, and get them talking to each other.  The routers (along with ancillary hardware, such as racks of switches and cabling) were situated in different parts of the lab.  After our tutors described our task, we were all encouraged to go up to the racks to try to figure out what was what: we had an opportunity to eyeball and touch real physical Cisco hardware.

I followed the cables between the different devices and asked some questions about the various interfaces.  I could see how it was set up.  I was also informed that the hardware was set up in ‘a raw state’ that meant that we had to send commands to them, to try to get them speaking to each other.

I sat down at a computer workstation.  I then figured out that a workstation had a link to one (or more) of the routers.  Each workstation was pretending to be a really old ‘dumb terminal’, which was the kind of interface you needed to use to talk to the router.

Our tutors gave us a handout, and a glossary of commands, and it was left up to us to figure out how to get the routers working together.  Thankfully, I was paired up with someone who knew how to issue the device with instructions.  Between us, we figured out how to send a ‘reset’ command and give it a name.

After quite a bit of head scratching, asking questions and mild cursing, I suddenly understood what was going on.  There were three routers.  Each router was connected to a separate terminal (or workstation) where we had to issue different sets of commands.  I was trying to be clever and think that you could do everything from a single computer – but, there were clear pedagogic reasons why it was designed this way: to keep it simple, so we could more easily figure out what was going on.  (Or, at least, this was my hypothesis!)

Half an hour later, we had all the routers (pretty much) talking to each other, which was our first assignment (which was what everyone would have done at the end of the previous day school).  Other groups in the lab session (who were more familiar with the commands that they needed to issue) were storming ahead, spotting mistakes in the script, and forging a path to the next assignment.

Since I was there just to observe and to learn, and I was becoming increasingly confused (and I had another appointment), I decided to call it a day.

Final notes

The teaching bit was great, and the lab bit was good fun, but there was a huge amount of detail to take in over a very short period of time.  I managed to understand some stuff, but quite a lot of the detail passed me by – especially when it came to working with the actual hardware.  This, of course, relates to the importance of the labs.  Nothing really beats an opportunity to work with real kit (and also to work with other students who are going through the same learning process that you are).

Although I left early, I did feel that I would be able to master a lot of what was being covered during the day school.  This made me wonder: I wonder if the other day schools might be different.  Also, since I found the stuff so geekily interesting, I had another question, which was: could I find the time to officially study this module? 

At the moment, time, is a challenge.  I’m currently embroiled in writing up three different teaching and learning research projects.  Once I get these out of the way (and another couple of side projects I’m working on), I’m sorely tempted to give T216 a go.

Permalink Add your comment
Share post
Christopher Douce

Psychology of Programming Interest Group : work in progress meeting: Day 2

Visible to anyone in the world
Edited by Christopher Douce, Monday, 10 July 2023, 16:43

Teaching programming at a distance

The first presentation of the second day was by yours truly.  I gave a short talk about a university funded project that aims to understand more about the teaching experience of Open University associate lecturers who are tutoring on the TT284 Web Technologies  module.

One of the purposes of the project was to understand issues particular to the learning (and teaching) of programming.  An area of particular interest is the transition between the first level modules (which use some visual programming language) to the second level modules which require students to pay more attention to other issues, such as language syntax.

I wasn’t able to present any firm findings at this stage (since I keep getting sucked into the idiosyncrasies of my day job), except that three themes that were emerging were that some students can struggle with understanding what PHP is and how it works, confusion about Javascript, and the perpetual battle to understand regular expressions (which is, I believe, an issue that pretty all developers, expert or novice, seem to have)

The question and answer session was interesting.  There was some chat about a coding DoJos (group coding sessions), the use of MOOCs (FutureLearn and the Kahn Academy), and how get students talking to each other.

Holistic programming teaching at Middlesex

Franco Raimondi’s talk was rather different to all the others: he showed us some robots (real hardware!) that he used in his teaching.  They had an interesting design, using both Raspberry Pi devices that were connected to Arduino microcontrollers.

One question was: why use both?  The Arduinos are used to control analogue input, but the heart of the control is managed (as far as can understand it) by the Raspberry Pi devices.  Students then have the challenge of how to design and implement a communication protocol between the Pi and the sub-component.  I personally think this is a great approach: students are exposed to different devices and learn more about their purpose.  When I had a job in industry, one thing that I had to do is figure out how to get one embedded controller talking to another: Franco’s robots would have helped me a lot to figure out how to do this.  More information about the robots can be found by taking a look at the MIddlesex Robotic plaTfOrm: MIRTO website

Okay, so there is an interesting robot, but how are they used in practice?  Franco described a series of lectures, design workshops, programming workshops and physical computing workshops.  In the workshops (if my notes are correct!) students are asked to solve different problems, such as to write a line following algorithm where the robot has to cater for 90 degree turns, and to complete different line circuits as fast as possible.  Students could also implement control algorithms, such as PID controllers (Wikipedia) (which again takes me back to the days when I worked in industry for a while), remote control and managing the taking of cameras by controlling the Raspberry Pi.

What I found really interesting was that the platform (and the workshops) made use of a programming language called Racket (Wikipedia).  Racket is a language that I had not heard of before, but apparently it has roots in the Lisp language.  In some respects, I commend the choice (because it’s great to expose students to different programming paradigms), but on the other hand, there is something to be said for getting to grips with tools that are used in industry.  I guess this just goes to show that whenever you come along to workshop like these, you always learn new stuff.

Towards the end of Franco’s session, he spoke about a system to record Student Observable Behaviours, which then led onto a discussion about learning objectives.  Apparently, the use of ‘observable student behaviours’ is something that Middlesex use, perhaps as a part of their assessment strategy.  We were shown a web-based tool that lecturers can use to gather evidence of student engagement and activity.

I don’t know what this relates to, but I also made a note of a place called The Crystal  (Crystal website), which was also described as the Siemens technology centre.  As soon as I looked into it, I realise that I had once seen it before: on a cable car ride across the Thames.  I now know how to get to The Crystal if ever I need to visit it!

I enjoyed Franco’s session: he covered a lot of ‘tech stuff’ in a very short time.  Students at Middlesex are clearly challenged and are clearly kept busy! 

One thought is that different computing courses and degrees cover different topics and perspectives.  When I was heading home from the workshop I remembered that The Open University covered a bit about robots too on a first year undergraduate module that has the code: TM129 Technologies in Practice (OU website).  Students are also presented with the challenge of creating a line following robot.  Rather than using real robots, a simulated one is used (but, students can get to see real ones if you come along to an engineering day school).

Measuring programming achievement after a first course

The next presentation was by Ed Currie who presented what were described as ‘thoughts and preliminary research’.  One of the key thoughts (and one that I found most interesting) was why some students find programming so difficult.  One note that I have made is that we can’t teach it, students can only learn programming.  It’s not up to us; it’s up to them, and our job (as lecturers and teachers) it to facilitate the learning.

Ed mentioned the idea of Threshold concepts (Wikipedia) by Meyer and Land.  I’ve made a note of the point that ‘sequence is a threshold concept’ (when it comes to programming).  I remembered hearing the phrase before from a colleague who was doing what I think was some research to see what happened when students grappled with key ‘threshold concepts’.

Two great phrases that I’ve noted down are ‘neo-piagetian stages’ and ‘flip classroom’ (Wikipedia).  In some respects the OU has always been doing ‘flipped classrooms’, i.e. students study some material and the go to a face to face tutorial to apply what has learnt, either in terms of solving a problem, or through facilitated discussions.

I don’t know what the context was or where this came from, but I also made the note ‘sharing of learning stories’.  This might have just been an idle idea during Ed’s talk, or something that Ed had said.  When it comes to learning how to do computer programming, I’ve got my own story (which might well be insufferably dull!), and I’m sure that other people have their stories.  Perhaps something could be gained (in terms of learning strategies and approaches) if we find the space to discuss and share how we know what we know.

Reflections on teaching design patterns

The final presentation of the day and final presentation of the workshop was by Carl Evans, who is a lecturer at Middlesex.  Carl talked about his work on an MSc module and his experience of creating and presenting a module about software design patterns.

In computer science and software engineering, Design Patterns is one of my favourite topics.  A couple of points that Carl made really resonated with me.  One was that ‘industry needs architects, not just programmers’.  Another great point (and one that I totally subscribe to) is that there is an increasing expectation (from industry) that graduates can work with frameworks as well as know how to use programming languages. In some ways, this point connected up with Thomas’s keynote.

Carl mentioned Sun/Oracle certifications, the use of layered architectures, and frameworks called Spring (Wikipedia) and Hibernate (Wikipedia) that I have heard of, but have never used in anger.  A quick look into these frameworks quickly shows that design patterns feature pretty prominently.

A really questions are: how do we best teach patterns, and where do we start?  Is there a pattern about how to teach patterns?  I noted down that a refresher about the object-oriented approach is useful, before taking students through different categories of patterns, such as object creation patterns, enterprise patterns, data access patterns, and compound patterns (I was writing everything down pretty quickly at this point, so I might not have managed to the nuances of everything that was said).

Carl also told us about a site called Design Patterns Library which I don’t think I’ve seen before.  One book that was referenced was Head First Design Patterns by O’Reilly.  There seems to be a claim going around that says that these ‘head first’ books are based on ‘neuroscience’ (but I’ve yet to find out exactly what exactly this means: claims like that immediately make me sceptical!)  Either way, anything that helps to make important technical concepts understandable is a good thing.

Final thoughts

I don’t know how many Psychology of Programming Work In Progress events I’ve been to, but it’s been quite a few.  This might have been my fourth or fifth.   I have enjoyed every single one, and I enjoyed this one at Middlesex University too.  It was well organised, friendly and thought provoking.  The talks were really interesting, covering distance learning, errors, notation, robots, challenge of teaching object-oriented programming and a whole load of other subjects too.  The great thing about these events is that you never know what you’re going to get, which means that you never really know what you’re going to learn (and this can be, invariably, a very good thing too).

From my perspective, the event helped to strengthen an opinion I have, which is that we need to figure out how to help students (and practicing programmers) how to best understand and work with software frameworks.  This issue is not only a computing education issue, but also, significantly, a psychology of programming issue.  The first subject that I studied when I discovered this subfield of computing (or of psychology, depending on your ‘home’ discipline) was the topic of program (or software) comprehension.  It’s clear from this short workshop that this continues to be (for me) an important topic. 

Permalink Add your comment
Share post
Christopher Douce

Psychology of Programming Interest Group : work in progress meeting: Day 1

Visible to anyone in the world
Edited by Christopher Douce, Monday, 10 July 2023, 16:42

On 8 January 2015 I went to a mini-workshop: the Psychology of Programming Interest Group (PPIG) Work in Progress meeting.  I’ve had an affiliation with PPIG for what must be at least fifteen years and I try to visit their meetings whenever I can.  In some sense, returning to the PPIG meetings is like returning to a comfortable academic home: you regain enthusiasm for the research interests that you once held (and have an opportunity to say hello some familiar faces too).

This 2015 WIP event (as it is colloquially known) was held at the University of Middlesex in Hendon Town Hall and skilfully organised by Richard Bornat, who is a PPIG community regular. This short series of two blog post aims to summarise what were my own highlights.

Keynote talk: Thomas Green

The opening keynote was by Thomas Green, who is one of the founders of the group.  Thomas told us what the group was about and emphasised the point that the group doesn’t just discuss research into programming, but also the activities that surround programming (and psychology too).  Subjects for investigation have involved pair programming and explorations into the sociological and anthropological.  Other research subjects have included computer science education and pedagogy, and studies into the relationship between personality and programming.

Thomas is known for creating (or discovering) the cognitive dimensions of notations framework (Wikipedia).  His framework can be used to help us think about programming language design and user interfaces.  Thomas described it as ‘ambitious in scope, [and a framework that] addresses any kind of information artefact’. Simply put, Cognitive Dimensions is a set of principles that helps us to think about stuff.

To explain, Thomas gave us a couple of examples. One of the dimensions is viscosity (which is my personal favourite!)  Viscosity is, of course, an attribute of liquids: the higher the viscosity, the harder it is to push you hand through a liquid (for example) – I think I’ve got that the right way round!   When it comes to the dimensions, this can be understood in terms of ‘changes’ to something (or, to move a system from one state to another).  To make one change (to an information artefact), you might have to do a whole bunch of smaller changes before you get to your desired outcome.

Another dimension is: hidden dependencies. An example of this is the links or connections that might exist between the different cells of spreadsheets. You can’t immediately see what the connections between different cells might be, but you need to understand them if you’re going to understand and work with a spreadsheet.

This is all very well and good, but how does this relate to programming that we find in the real world?  Thomas gave us a number of examples of computer code used with a content management system (CMS).  Why study content management systems?  Thomas had some good answers: they were widely used, often are pretty difficulty to get your head around (which is certainly true!), and they haven’t been studied very much.

If you’re interested in content management systems, this Wikipedia page presents an amazing list of different content management systems (Wikipedia).  On the same subject of geek lists, this is another favourite of mine: comparison of web application frameworks (Wikipedia).  You can spend hours looking though these different pages.  These two summary links clearly show how big the ‘CMS space’ is.  (As an aside, if you have too much time on your hands, there’s also a List of Cakes and a List of Lists)

An interesting point that Thomas made (which is one that resonates with my own experience), is that they all claim they are ‘easy to use’.  Two examples that were spoken about were Wordpress (Wikipedia) and Drupal (Wikipedia).  For the purposes of Thomas’s presentation, we looked at the Perch (CMS website), a CMS that I had never heard of before.  The point was clear: Thomas’s framework can be used applied to study CMS’s and web frameworks.

After being mildly baffled with screens filled with code that used lots of angle brackets, there was a brief question and answer session.  I think I made a comment that I chose a CMS based on the quality of the on-line tuition videos.  My decisions were not based on language efficiency, but how easily I could see how to create something that similar to what I wanted to do.  (I’ve often wondered about whether we could look to the murky world of media studies to learn about why some tools become more popular than others: there’s a whole other dimension of CMS systems that could be explored).  There was also brief discussion about design patterns, since many of them make use of the model-view controller pattern.

It was pretty thought provoking stuff.  When it comes to content management systems, I can’t help but think there’s an opportunity to use them as a vehicle to conduct research into the creation, development and sustainability of software communities.

Active error: examining error detection and recovery in software development

Tamara Lopez gave the first talk of the day, and within minutes of starting her talk, I had started to remember some research I looked at over fifteen years ago.  Tamara’s research was all about human error and programming.  As Tamara was speaking, I thought to myself, ‘I wonder whether she has heard of a researcher called James Reason.  The answer came within minutes: of course she had.

Reason wrote a book called Human Error and carried out research into active errors (mistakes that happen in ‘real time’) and latent errors (which remain undetected within a system or product for considerable time).  Have you ever bought a chocolate bar, unwrapped it from its wrapper and then thrown the chocolate bar away?  Have you ever walked into a room and immediately thought, ‘why am I here?’  I recently put my keys in my fridge for no apparent reason.  These, I guess, are examples of active errors.

The aim of Tamara’s research was to perform a naturalistic observation of error in programming, and gather reports of error occurrence.  Understanding the characteristics of error can, of course, allow us to understand more about it and why error arises.

Tamara used a great method.  She was studying pair programming data videos that had been published on the internet through a website called Pairwith.us (website).  The developers were working on a project to adapt some kind of testing tool.  Tamara analysed the errors in terms of incidents and themes.  Some keywords that I picked up from Tamara’s talk were temporal, material and social.  A good talk and interesting research.

Visual Analytics as End-User Programming

The second research talk was by Advait Sarkar who had travelled from the University of Cambridge.  Advait gave a demonstration of some software that he had put together.  The focus of his prototype appeared to relate to the area of data analytics, specifically, how the area of machine learning might be connected to a spreadsheet environment.

Following this session (and Advait’s demonstration) there was there quite a bit of discussion about different machine learning approaches such as decision trees and neural networks; subjects that I hadn’t really touched on or explored in any great depth since I was an undergraduate.  Advait’s presentation wasn’t really in my area of expertise but it’s good to be exposed to different areas.

SQ and EQ and programming, revisited

The next talk was by Melanie Coles from Bournemouth University.  I remember Melanie from other PPIG events, so it was great to see her again.  It was interesting to hear that her talk related to some earlier research that she presented at PPIG back in 2007 (if I’ve understood this correctly).

The title of her talk was: ‘SQ and EQ and programming’ So, what exactly does SQ and EQ mean?  I understand them as rough and broad measures of personality.  EQ is an abbreviation for Empathy Quotient. Simply put, EQ is a measure of someone’s drive to identify with other peoples’ feelings and emotions. SQ, on the other hand, means Systemising Quotient. It is the extent to which people have a drive to understand rules governing things.

I’ve made a very rough note that Melanie related both measures to work carried out by Simon Baron-Cohen, who works in the area of autism research.  I’ve made another note in my notepad that there are tensions between these traits, along with the sentence, ‘scientists score higher in AQ than non-scientists’.

Some studies seem to suggest a correlation between the role of programming and these traits.  Other studies, on the other hand, don’t show anything.  The message coming through is that you don’t have to be high on the AQ scale to become a programmer.

I don’t know that this means, but I’ve made another note that reads ‘polite grumpiness about sterotypes’ which might have been scribbled down during the question and answer session.  I have no idea who was expressing polite grumpiness, or which stereotypes were being discussed.  I do, however, feel that this expression should still stand and has some validity.  A sensible rule is that if you’re going to take issue with stereotypes, you’ll go a lot further if you politely disagree rather than go around shouting about them.  I should also add, that I have no idea how this paragraph relates to Melanie’s very good (and very clear) presentation.  All this said, some really interesting ideas and (some exceedingly polite) discussions.

A great end to the first day!

Permalink Add your comment
Share post
Christopher Douce

Accessibility training away-day

Visible to anyone in the world

This is quick blog post about an event that I went to in November 2014.  I know that this feels like a long way away, but I haven’t forgotten about this event: it was one that was pretty memorable (but more of that later).

The event was an away day for the Faculty of Arts; it was a training day, and the afternoon (which was the bit that I went to) had a very particular focus: accessibility and disability issues; specifically, what certain members of the university could practically do to help students.  Although some of the fine details are now a bit sketchy (due to the relentless passage of time), I did make some notes, so here’s a quick summary of the sessions that I (sort of) gate crashed.

Barriers and reasonable adjustments

The first afternoon session was by Heather Kelly and Laila Burton.  It began with some numbers: about 12% of students in the Open University have declared a disability (for the faculty of arts, this number is slightly higher, at 15%).  In terms of raw numbers, I think we’re looking at around ten thousand students.  To put things into perspective, other universities can have that same number of students across every faculty.

Every university is legally required to make ‘reasonable adjustments’ to educational materials to ensure that they can be consumed by students who have disabilities. 

The presenters asked us an important question: who is responsible for making these reasonable adjustments?  There were a number of answers: the module team, associate lecturers, the securing greater access team, and others too!  An important principle (from what I remember from another presentation) is that those people who are in a position to make an adjustment should just go ahead and do it.  This is a principle that relates to tutors, those who line manage tutors, and those support the delivery of a module, and members of a module team.

All this said, what actually does ‘reasonable adjustment’ actually mean and when we do we have to make one?  There are a number of things that need to be taken into consideration: is the student at a substantial disadvantage because of their disability? Is it practical and effective to provide an adjustment?  Is the adjustment something that could be provided as a part of the disabled student’s allowance?  If not, can an adjustment be provided that is reasonable in terms of costs and/or resources?

To understand the concept of reasonable adjustment further we were asked to discuss a number of scenarios in small groups.  Our group looked at two scenarios: the case of students using the library website, and the question of whether a different assignment question could be offered if a student objected on religious grounds.  By discussing these scenarios I learnt that the library can offer a service to help students with literature searches.  When it came to the assessment issue, an adjustment was not considered to be reasonable if it meant that a fundamental learning objective would not be assessed.

Towards the end of the session we were told about different sources of advice and support.  The university has a number of accessibility specialists (some of whom work within each faculty).  There is also the disability resources team, and a group called the accessibility referrals panel (ARP).  The ARP is a university body that comprises of a number of experts who can offer some advice on accessibility issues.  For instance, if anyone isn’t sure about whether an adjustment is appropriate, it can be referred to the panel, which can then form a judgement about the best course of action.

A final point was about the importance of recording decisions.  This is important during module production or module presentation, or put another way (in non-OU speak), when a module is being designed or written, or when it is being delivered to students.  Recording your decisions has two purposes.  Firstly, the university has a trail of what has been done should reasonable adjustment decisions ever be challenged.  Secondly, it allows experiences and cases to be shared with others.

Disability advisory service

After a short break, we had an option of choosing from a number of parallel sessions.  I went to the session that was facilitated by Julie Young, manager of the disability advisory service.  Julie spoke about the support for disabled students and the role of the service. We were told that the service can offer specialist advice for dyslexia, mental health issues, visual and hearing impairments.

During the session I made a note of the term ‘assessment’.  Assessment, in this context, isn’t an assignment that a student has to complete or any kind of exam.  Instead, an assessment is (as far as I understand it) is a discussion that enables a professionally trained assessor to understand the impact of one or more impairments on study.  Assessments can lead to recommendations of assistive technologies, and also the creation of a useful record (or disability ‘marker’) which can then offer information for tutors, helping them to understand what reasonable adjustments might be necessary.

Visit to the access bus

After another break, it was time to brave the elements and head outside to ‘the access bus’.  Despite this event being more than a few months ago, I have one overriding memory of this part of the day: it was bitterly cold.  A large van was parked in the hotel car park.  The van had been converted to what is, essentially, a mobile office that was is packed with different types of technology.  This mobile office can be used to carry out assessments: it is where students (and potential students) have opportunity to play with and learn about different types of assistive technologies.

During our short time on the bus we were shown different types of keyboards, different types of assistive software (such as screen readers and screen magnifiers), and some speech recognition software.  I have played with screen magnifiers and screen reader software before, and some other software called Read and Write that can be useful to some students who have dyslexia.  I was, however, quite fascinated by the speech recognition software and I was impressed by its performance.  (This said, it was demonstrated by a skilled operator, and had been pre-configured so that it could recognise a particular voice).  I left the session thinking, ‘I wonder whether I could ever use voice recognition software’.  I’ve never tried to.  I have deliberately avoided it.  But perhaps I ought to pluck up the courage to give it a go.

A personal tale

The final session of the day was by a member of the university who also does a bit of stand-up comedy on the London open mic circuit.  The comic started by confessing that he had a hidden disability: a speech impediment, a stammer.  He told a short story about how he started on the open-mic circuit, and he told us a little about who inspired him: a friend who is now eighty, and a professional comic who gave a performance at the Disabled Student Services conference three or four years ago.  This then led to a ten minute stand-up comedy routine that was about the day to day challenges of dealing with that particular hidden disability.  There is a huge risk with doing things like this: it could either go terribly, or it could go well; telling jokes in the workplace could get the presenter getting into all kinds of trouble.

My confession is that I was the comic. 

Had anyone told me four years ago I would be at that event, giving a talk to the arts faculty about my weird hobby, talking about my struggles with talking, I would have said they were delusional. 

The story and my performance connected to a point that I wanted to make: when given sufficient support and motivation by others we can surprise ourselves by doing things that we never thought we would be able to.  By considering issues relating to disability, the design of modules and what reasonable adjustments we might be able to make, we all collectively learning what needed to be done to make things easier for all learners. 

In some ways, the event was about what we could do, both individually and collectively, to help others to achieve.  In other respects, the away day was also about connecting to others, and getting a little bit of motivation too.  I was glad to be a part of it.

Final thoughts

There were a couple of key points that I took away from the day: a reminder about the principles of reasonable adjustment and a reminder about who to ask when you need help about something.  It was also a reminder about how seriously the university treats these issues.  It was also interesting to look around the access bus.  I remember from this session that the faculty staff that went along to this event had loads of questions about different bits of technology, what they did, and how they worked.

Another useful part of the day was, in essence, a reminder.  A reminder that if you don’t know how to tackle a particular problem, then there colleagues within the institution who might be able to offer some useful help and advice.

 

Permalink
Share post
Christopher Douce

Mental health awareness day: London regional centre

Visible to anyone in the world
Edited by Christopher Douce, Thursday, 28 Feb 2019, 12:08

Every year the London region equality and diversity group runs an event.  Over the last two years we’ve run an event about ‘place, location and travel’, and have held an event about creative aging.  This year, the group ran an event on 13 November 2014 about mental health and well-being.  The day was split into two parts.

Part 1 : Participative display

A couple of months before the event we erected two display boards in the university café area.  These boards were to form what we called a ‘participative display’.  Each board had a slightly different purpose.  One board was all about sharing stories, experiences and acknowledging the contributions that people who have mental health issues have made to society.  The second display board was all about ‘resilience’; things that we can all do to ensure that we maintain good mental health.  The rear of this first board was also used to share more factual information about mental health issues.  We put up papers and articles.  I remember there was one article from Science magazine about the prevalence of depression.

When the boards had been put up, the group sent an email around the office telling everyone what the boards were all about, and how everyone might contribute.  To get the whole display, a couple of group members ‘seeded’ the display by adding some broad headings, some thoughts and some initial ideas.

The email messages and the ‘seeding’ did the trick.  As the months passed, different contributions were made.  The contributions included information about writers, academics and performers.  Other contributions had a slightly more personal tone; these were stories of people who had been touched, in some way or another, by mental illness.  The board became a catalyst for sharing.

Part 2 : Mental health and wellbeing

On the day of the event, we had asked a university colleague, Emma Greenstein, to come and speak to us.  Emma works for the university disability advisory service as the university mental health adviser.  Her job is to work with staff to help to offer support for students who have mental health difficulties.  I’ve had to chat to Emma a number of times and she has helped me out on a number of occasions.

Emma intended that her talk was to be interactive.  A part of her talk was to bust some myths, introduce us to some facts and terminology.  Emma introduced us to a model called ‘the mental health continuum’.  This was a simple model that had two axes: one axis that goes from 'diagnosis of mental illness' through to 'no diagnosed mental illness' (I should also mention that the model is about rating the severity of a mental illness).  The other axis goes from 'flourishing mental well being' through to 'poor mental well-being'.  (I have read that this model comes from a paper from Tudor entitled, ‘Mental Health Promotion’).  Here's a diagram that is pretty similar to the one that Emma used on the day:

Mental health model diagram

The model enables us to think beyond diagnostic labels, which can easily over simplify things.  A really interesting point that was raised was that we can all experience mental health difficulties.  The term ‘difficulties’ can mean feeling worries or anxiety, through to the experience of feelings of grief or loss.

Another interesting point that was made (and also emphasised) was the differences between people.  Emma said: ‘If you’ve supported one student with schizophrenia, you’ve supported one student with schizophrenia’.  It was a phrase that I’ve heard before, but in relation with students who experience different conditions.  Its use in this context emphasised the importance and need to treat and consider everyone as individuals.

During the session we were shown a short video:  I had a black dog, his name was depression (YouTube).  The video comes from a book that one of my favourite friends had once shown to me.  It’s a book that one of my colleagues had also brought along to the session.

We returned to the mental health continuum where we were asked two questions: ‘where are you now?’ and ‘where have you used to be?’  It didn’t take me too long to identify two points in two different places.  There was an important point here: that we can move between different points on the continuum.

On the subject of change, we were introduced a series of three short films that were made as a part of the recent Time to change campaign (campaign website).  The first film has the title speaking up (YouTube).  There are two other clips: you can recover (YouTube), and stronger, better, person (YouTube).  These videos are pretty short and pretty watchable too.

If we can place ourselves on a continuum, then a related question is: what can we do to promote our own resilience?  We were directed to a site called Mind Apples (mindapples.org) which I understand was created by a web developer.  The idea is really simple: there’s a lot of talk about the importance of eating five fruit and vegetables per day.  (I do struggle to do this, mostly due to the overabundance of cake that there seems to be at the OU office in London, but I’m not complaining!)  If we consider doing five good things for the body, why shouldn’t we consider doing five good things for our mind?  The idea is: what five things make you happy? Or what five things should you be doing that could make a positive difference to your mental well-being?  The website phrases it in a better way by asking: ‘what do you do regularly to take care of your mind?

A point I noted was that our actions and choices are important.

Final thoughts

At the end of Emma’s session, something really interesting happened: colleagues who had made contributions to our participative display were asked whether they wanted to say something about what they had added.  This gave way to a series of amazing impromptu talks about a range of different issues, worries, concerns and experiences.  Everyone took the time to listen. In that space and situation, what was said was both important and interesting. In an atmosphere of respect and mutual support, we began to talk about mental health, mental well-being and resilience.  Suddenly, these subjects didn’t seem so hard.

After the talks, we all broke off for some lunch. The equality and diversity group had made a special trip to the supermarket to buy some bread, cheese, salad, some juices and other goodies to accompany awesome home-cooked food that some of our colleagues had prepared. There seemed to be a consensus amongst those of us who helped to run the event: this had been the best, most challenging, and most useful event that we had run. Our participative display worked.

Acknowledgements: Many thanks to Emma Greenstein who commented on an earlier version of this post, and all my colleagues who worked on the event and made amazing contributions.

Permalink Add your comment
Share post
Christopher Douce

AL Development Conference: University of Sussex

Visible to anyone in the world
Edited by Christopher Douce, Monday, 12 Apr 2021, 18:33

On 8 November 2014 I attended the South East region (region 13) associate lecturer development conference held at the University of Sussex.  I felt that this was a really important event to attend, since it was to be the ‘final’ conference that was organised from the regional centre in East Grinstead.  All future conference would be run from the London region that has been re-christened as ‘London and the South East’.

One of the main reasons I wanted to go was to meet some of my colleagues who were leaving the university.  In some ways, it was a really sad day, but in another way, it presented an opportunity for the AL community to offer loud and vociferous thanks for all the great work colleagues from the region had carried out over very many years.

MCT session

The first session of the day was spent in our faculty groups.  The MCT session addressed three topics.  Other than details about the impending closure, the first topic was about changes to AL line management.  The second was about the development of a Group Tuition Policy.  The third and final section was a talk from an AL colleague about a research project about the use of language.

Changes in line management

A really important item was that the line management for some associate lecturers is changing.  What this means is that a line manager for a tutor might be located in a different part of the country.  The reason for this change (which is taking place in the Engineering and Innovation and the Computing and Communications department) is that a line manager will become increasingly specialised in terms of the subjects and topics that they look after.  I view this as a really positive thing: it has the potential to allow line managers (staff tutors) to respond to both student and tutor queries more quickly and efficiently, and enable them to develop more expertise in a smaller number of courses.

Group tuition policy

The university has been working on something called a ‘group tuition policy’.  From my reading of the policy, it seems to have two main objectives.  The first is to offer students flexibility and choice, i.e. they can choose to attend either on-line or face to face tutorials.  The second is that by grouping different sets of students together, it is hoped that tutors end up with more busy tutorials, and this can have a positive effect for everyone: more students means more opinions, which then can mean more learning.  One of the ideas is that students are given information about learning events before a module begins.  To make the policy a reality the university has to make some changes to its tutorial finder system.

During the session we looked at the policy and had a discussion about what we thought about it and how it might potentially impact on our tutoring.

Language use and retention in TU100

The final part of the morning session was presented by Associate Lecturer Heath Morris who tutors on TU100 My Digital Life (OU website).  Heather has been working on a university funded project that has been looking at the use of language in correspondence tuition, in particular, the summary comments that are provided by tutors.  TU100 is a particularly important module since it places quite a bit of emphasis on the development of skills, such as numeracy and academic writing.  OU students can come from very different background, which makes this aspect of teaching and learning all the more important.  The main question is: how do tutors use language and in what way might this language affect students?

Heather mentioned something called an ‘appraisal framework’, which I think is a framework used to assess the types of language used in assignment feedback.  I’ve made a note that it comprises of three different aspects: affect (which conveys emotion), judgement (which is an evaluation of behaviour or work performed) and appreciation (evaluation).  Other key words that I’ve noted from Heather’s presentation include student tenacity (which relate to the evaluation of effort?), and student capacity (which relates to the evaluation of capability). 

A set of questions for the research project are: does the use of language affect performance and retention?  Do those who score low leave?  To what extent would more positive feedback be useful?  Would it helped if we had just decided to give students a ring on the phone to have a chat with them?  What tools or checklists might be useful?

My own view on the language question is that surely good language and detailed explanations can have a positive effect on student retention, but there’s a big difference between having a gut feeling about something and actually showing something empirically.

I thought Heather’s presentation was great.  I would really like her to run a similar session in the London region.  Another thought was: perhaps we could run an AL development event that is specific to TU100 that covers the use of language and also lets us discuss the group tuition policy.  The underlined a simple outcome from attending these AL development conferences: they expose us to new things and help us to come up with new ideas that will help both tutors and students like.

Workshop: Scientix: the community for science education in Europe

The first workshop I went to was ran by Richard Walden.  Richard’s session was split into two parts.  The first was about an EU funded project called Scientix (project website) that he was involved with.  The project is described as an initiative to create a ‘community for science education in Europe, promotes and supports Europe-wide collaboration among STEM (science, technology, engineering and maths) teachers, education researchers, policymakers and other STEM education professionals.’  Scientix offers training resources, access to research, information about applications and opportunities for networking.  There’s also a link to something called the European School Net (EUN website) which I had vaguely heard of before.  If you’re interested in STEM teaching, both sites might be worth having a quick look at.

The second part of Richard’s session was all about how to improve student’s scores in tests without doing a lot of extra work.  To prepare us for this section, he split us into two groups: one group was asked to write about what we did on holiday, and the second group was asked to write about the anxieties that we might feel if we had to go ahead and complete a time limited quiz.  We were then all given a quiz to complete.

The idea was simple, and draws on research by a researcher called Gerardo Ramirez (UCLA website) : by writing about our exam anxieties, we explicitly articulate them, and this can help them to be reduced.  High levels of exam anxiety, can, of course, drastically affect exam performance.  There is an equally simple theory:  if we’re anxious, we occupy our short term memory with our anxieties. Since our short term memory is strictly limited, this will impact on our ability to understand and work through exam questions.  Short term memory, we were also told, is really important when it comes to retrieving essential information from long term memory.  (Having studied aspects of cognitive psychology many moons ago, I found all this especially interesting).

If you’re interested in this subject, I’ve also dug out the following YouTube lecture (YouTube) by Sian Beilock (who Ramirez’s co-author) who talks about some of the science behind this research.  (It’s quite a long video; there may well be some shorter videos out there).

Richard’s reason for sharing this research was simple: perhaps it’s worthwhile telling our students about this research, and the potential benefits that writing about fears and anxieties may provide.  I think it’s a great idea.

Modelling reflexivity in the teaching-learning relationship through distance learning tools

This final workshop of the day, facilitated by fellow tutor, Emily Skye, was rather different to all of the others.  I was attracted to it due to the word ‘reflexivity’ in the title; it was a term that I first came across when I was studying some social science modules, but my memory of it and how it could be used was a bit rusty: I was looking for a refresher.  Straight away, I discovered that the workshop had a very different structure: it was more of an open facilitated discussion rather than a formal ‘talk’.  All participants sat in a rough circle and shared something about ourselves, why we found this particular session of interest, and also something about our understanding of the term reflexivity.

I soon learnt that it might well be one of those terms that has different definitions based on the context it is used.  In essence, I understand that it is about understanding and thinking about yourself and how it relates to a particular context; it is about being self-aware.  It also relates to your own identity.  You can, for example, very easily hide behind a label that is attributed to a role or profession.

Being self-aware, and thinking about our effect on others (and how we are thinking about others) has the potential to help to inform our teaching and learning.  Through selectively sharing, we have the potential to build up trust, which can help us to encourage learners to look at new subjects, issues and areas.  Also, being reflexive also allows us to acknowledge the difficulties of learning, to be empathetic towards the challenges students face and connect with the emotional perspective of learning.

One of the big challenges in the distance education context is the extent to which we are able to relate and understand our students, especially when our interactions may be limited to only key points during a module presentation.  I introduced a term from computer (or, perhaps human-computer interaction) which was: emotional bandwidth.  When we interact with each other through on-line tools such as discussion forums we can easily misunderstand situations and expressions of emotion.

I found this session especially interesting because it was so different to the other sessions I had been to before.  Although I was initially rather worried by the layout of all the chairs, I quickly became relaxed.  It was also great to learn a little bit more about some of my associate lecturer colleagues.

Final thoughts

Like many AL development conferences that have been run by Region 13, this one went very smoothly.  Delegate packs were organised, there were clear signs on rooms, and it was exceptionally well attended.  One part of the day stood out for me, and this was when the Associate Lecturers gave the staff at East Grinstead a standing ovation to both thank them for all their hard work, and to recognise the work that they have given to the university.  There were tears.  I’m glad I was able to be there.

Not only did I learn new things, I took with me some idea that I then transferred to the London AL development conference that was running the following week.  This just went to emphasise my view that regional difference and diversity was (and is) a good thing.

Permalink Add your comment
Share post
Christopher Douce

Different ways to use OU Live

Visible to anyone in the world
Edited by Christopher Douce, Saturday, 24 Feb 2024, 17:38

From time to time I use a system called OU Live.  OU Live is a software application that tutors use to deliver learning events (such as tutorials) through their computer.  It’s taken me quite some time to get used to it because teaching through OU Live is very different to teaching face to face. 

When I first learnt about OU Live it immediately stuck me that there were loads of things that that you could do in during face to face tutorials that you certainly can’t do in OU Live.  I really enjoy planning and running face to face tutorials; they are a great opportunity to share your enthusiasm about the subject that you’re teaching.  They are also a great opportunity to learn from your students and to immediately understand what aspects of your tuition works and what aspects don’t work. 

Teaching ‘electronically’ is very different: it’s harder to get a more direct connection with your students and it’s also difficult to know whether certain concepts are understood well enough so you can move to other topics: it’s more difficult to see ‘the whites of their eyes’!

Over time, I have been persuaded that OU Live offers some really great opportunities for students.  Although you can do things in face to face settings that you can’t do in OU Live, I’ve also come to see that the opposite is also true: you can do things in OU Live sessions that you can’t in face to face sessions.  I’ve also realised that one of the challenges for the university is how to share best practice in how to use OU Live not only between tutors, but also between module teams.

This blog post aims to summarise my understanding of different ways that OU Live can be used; it is a post that connects with the broad idea of ‘OU Live pedagogy’.  It aims to share some ideas about how it can be used during the presentation of an OU module.  Some of these approaches have been picked up by chatting with colleagues, and others are methods that are currently used today.  I’ve also added a couple of approaches that I’ve invented (but other people might have also thought of them too).

In essence, I’m posting this as a really rough ‘grab bag’ of tentatively named pedagogic tools that I hope someone might find useful.  If you have any comments, or have accidentally found this useful, do get in touch.

On-line tutorials

When I first started to use OU Live I used it to replace face-to-face tutorials.  There are two situations where I’ve needed to do this.  One of the modules that I tutor is completely on-line; students can be from different parts of the country (or even different parts of the world).  In this situation, face to face tutorials are obviously impossible: the only thing that we can do is to run OU Live sessions. 

Another situation was where I wasn’t able to physically get to a tutorial due to a scheduling clash.  Unfortunately, it wasn’t possible to reschedule the event for the weekend since the new date would then be too close to the TMA cut-off date.  To get around this problem, I decided to run an evening OU Live tutorial, which I then recorded.  I was pretty surprised that a good number of students came along to the session (including some students who were never able to get to the face to face sessions).

In some respects, an OU Live tutorial can become a bit like a face to face tutorial (if you plan it well).  A tutor can present materials, do some talking, set up activities, ask for student responses, and even get students to work on a shared task by putting them into ‘breakout rooms’: there is a lot that is similar.  There are, however, some differences.  OU Live sessions can be pretty tiring for the tutor.  A tutor can’t just ‘glance across’ a classroom to see what is going on.  Instead, a tutor has to engage with a cognitively demanding interface and very regularly request students to ‘do stuff’, to ensure that their attention is maintained.  Tutors might also be faced with technical issues of challenges to contend with, i.e. some students might not have microphone headsets, they might have connected up the microphone jack to the headphone jack, or they might have set the volume setting so low that they can’t hear anything at all.

Another point is that sometimes the material designed for a face to face session might not be easily transferrable to an OU Live session because it just isn’t appropriate.  Students can’t write things on pieces of paper and exchange notes, or move to an empty space in a room (with the intention of demonstrating a physical concept or idea).  For an OU Live tutorial to work and work well, tutors (and, arguably the module team), need to come up with a learning design that is appropriate for the on-line environment.  Also, tutors and students need to be given some time so that they become familiar with the on-line environment.

I believe that an OU Live session can replace certain aspects of a face to face session, as long as they are designed with a lot of care and attention.  A final point is that an OU Live session shouldn’t go on for as long as a face to face session.  Longer sessions, for some reasons, just don’t seem to feel right.  We all need a break from looking into a screen.

Demo tutorials

A couple of months ago, I was alerted to some OU Live training materials (OU VLE) which shows how you might use OU Live during tutorial sessions (you might have to have ‘tutor permissions’ to be able to see these).  These exemplar sessions cover a range of different subjects, and they are quite short (around ten minutes), which means that you don’t have to go through an entire tutorial.  If you can access these, I do recommend them.

The first one is entitled ‘Working with metre in poetry’ makes use of highlighter and a web tour (from around the seven minutes mark).  The next session, entitled ‘Multisensory pronunciation training’ was all about learning German.  What was really nice about this one was the way that the ‘put your hand’ button was used and how the tutor used the webcam.

A subject that is close to my heart has the title, ‘Writing and running simple code’.  This makes use of the application sharing feature from around the two minute mark.  I also liked ‘Finding and using secondary sources in legal essay writing’, where the whiteboard was used from around the three minute mark.  I really like the way that ‘click and drag’ is used.

There are, of course, other exemplars.  Do have a look; it’s a really good resource.

On-line debate

A week or so ago I was chatting with a really experienced tutor who said that he really enjoys running OU Live sessions.  He told me that he had teamed up with another tutor.  ‘We have a debate’, he said.  ‘One of us takes one view, and the other tutor takes an opposing view.  Our students love it!’ 

This struck me as a whole other way to use OU Live.  TV programmes like Newsnight have a very familiar format.  OU Live not only allows us to create a ‘virtual TV studio’, but it also allows us to create a situation where the ‘virtual TV audience’ can ask the experts some questions.  Another thought is that we could potentially create situations where students can (and should) be encouraged to challenge the points of views that are exposed by the experts.

From my perspective, I would really like to see an example of how this might work.  There are aspects of technology and computing education where ‘the debate’ format might work.  Another point to bear in mind is that to get the best out of these opportunities, module teams need to be considering these opportunities when they are designing modules.

Recording a lecture

Running an on-line tutorial can be a tough business; there’s a lot going on.  You’ve got slides, different OU Live tools, students talking, problems with microphones, text messages appearing and also the need to manage and control activities. 

During the presentation of a module a tutor might discover that some students might struggle with a certain topic.  Rather than to offer comments through a discussion forum, or perhaps a group email, another approach is to run, and to also potentially record, a short lecture.  OU Live can be used to record a short session that can be considered to be akin to a ‘video podcast’.

When a session has been recorded, tutors can then refer students to the resource in their correspondence tuition, as well as during examination preparation sessions. 

I used this approach to run a revision session for M364 Fundamentals of Interaction Design.  I kept getting scuppered by technology.  The first time I ran the revision session there was a power outage at the university which meant that students couldn’t login to my session.  The second time I ran the session, I discovered that I couldn’t use the record button, and after the session students contacted me asking when a recording would be available.   The third time I ran the session, I just made a recording; there were no students.  When I had finished the recording and I had made it available to everyone, I let all the students know by making a post to the module discussion forum.

One question is: how long should a ‘recorded lecture session’ last?  Unfortunately, I don’t have any research to back this up, but when it comes to student engagement my instinct is to try to keep them pretty short.  This is something that I ought to look into.

Focused Demo

The idea of a ‘focused demo’ pretty much follows on from the idea of a lecture.  Quite a few computing modules make use of some specialist software, such as programming environments such as Eclipse, Netbeans or Sense (you don’t have to worry about what these are, just know that they’re special bits of software).  For design and engineering modules, students might have to use tools such as Open Design Studio.  Some students might find that some of these pieces of software pretty baffling to use, especially if they’ve never seen them before.

One approach to help students is to ‘show’ them how to use a piece of software.  OU Live has got a great facility called ‘application sharing’, which means that you can show students what you see on your screen.  You might show students how to begin to use a software tool during an on-line tutorial, but there’s always the risk that things might go wrong, i.e. an internet connection might go down, or a big and complex bit of software might begin to misbehave. 

Rather than doing a ‘live’ demo (which is, ultimately, a really good thing to always try to do), another idea is to record what could be loosely called a ‘focussed demo’, i.e. you could show students how to use a particular bit of a software system by recording a quick demo using OU Live. 

If you’re teaching programming, you could also use this approach to show how to solve a particular problem.

Drop in session for students

I remember when I was an undergrad our human-computer interaction lecturer said to everyone, ‘I’ll be in my office on a Wednesday afternoon between these times… if you have any questions about anything, just pop in to see me: I’ll be very happy to have a chat’.  I thought it was a great way to encourage informal discussions about the course, and the materials.

After having a chat with my colleague from the South East region, I discovered that she used the exact same approach to support her students.  Rather than running a face to face ‘drop in session’, she ran a virtual one.

The way it worked was that she would advertise times when she would be available for a chat in her tutor OU Live room, and students could just turn up if they wanted a chat about anything. She would keep an eye on what was going on in the room whilst doing other things: exactly the same way that it used to work when I was an undergraduate.

What I really liked about this approach was how informal it is. There is no plan or agenda, but it clearly suggests to students that they can ‘drop by’ and gain some support if they need to.  I haven’t tried this approach in my own tutoring, but I am certainly going to!

Additional support session

For students who struggle with some aspects of a module the university can offer something called an ‘additional support session’.  This usually takes the form of a one to one session between a student and a tutor.  There are different ways that an additional support session could be run.  One way is to run a face to face session at a regional centre (or another venue that could be booked by the university).  Another approach might be to have a telephone session.  A third way is to run an additional support session through OU Live.

One of the main advantages of using OU Live for an additional support session is that both the student and the tutor can make use of the whiteboard.  In some cases, a tutor might decide to prepare a couple of slides so the tutor can work through some of the ideas that a student might be struggling with.  This might be particularly useful with arts subject, languages (where a tutor might write things onto a whiteboard), or even mathematics, where a tutor might take a student through how to solve an equation, or work through other mathematical ideas.

In the big scheme of things, face to face is always better than on-line, but on-line can certainly be (with adequate planning) significantly better than the telephone.  One question that should be asked if one is faced with running an OU Live session is: ‘how can I make the best use of this tool to help this particular student?’  One way to get a feel for how to approach a session is to take the time to explicitly ask the student which areas to focus on.   When we know a bit more, we can use the time that we have a whole lot more effectively.

Session between students

After recording the M364 revision session that I mentioned earlier, I noticed an interesting discussion on one of the module discussion forums.  One student proposed the idea of an ‘on-line chat’ in a module wide OU Live room.  I seem to remember that this started a short debate between tutors about whether students should be left alone in an on-line space that is operated by the university.

In a face to face university, students chat with each other in university owned common rooms and corridors all the time, so why shouldn’t this happen in an on-line space?  The tough thing about distance learning is the isolation, so it seemed like a really good idea to allow students to chat to each other about a forthcoming (or impending) exam.

I sense that different people have different views about the use of on-line spaces, but I also can see that module team members, forum moderators, or curriculum managers might be able to play a role in facilitating (or seeding) student led discussions through on-line rooms.  Plus, in some modules where group work is essential, I sense that the use of OU Live has the potential to play a pivotal role.

Final thoughts…

One of the things that I really like about OU Live is that you can record sessions which is one of the things that you can’t easily do in a face to face session: if you’ve missed a face to face session, it means that you’ve missed it.  The recording facility gives tutor the power to create new types of potentially transitory learning resources that have the potential to help students in a number of different ways.

Recordings

My own (personal) view about recording is that we should record everything, since this has the potential to help the widest number of students.  Also, if a tutor makes a recording of an on-line tutor, students need be clearly told that they will be recorded: they should be given sufficient information to help them to make a decision about whether they wish to come along to a ‘live’ on-line session.

There are differing views about recording OU Live tutorials.  One argument is that if they are recorded, students won’t bother turning up; they’ll just watch the tutorial.  A counter argument to this is: if they don’t come along then they won’t be able to influence the tutorial in a way that will allow them to get their best possible learning.  A recording, I argue, should show students what they’re missing so they become suitably motivated to come along to the next live session.

Another argument is that if a session is recorded then students might be less likely to participate during a session.  This might well be the case, but I don’t see this as a very strong argument.  It’s very easy to forget that a recording is being made, and if there are exceptional points that a student wishes to share with a tutor then perhaps an on-line session isn’t the best place.

A final argument that I’ve heard is: ‘a tutorial is a tutorial; if you want to record something that students can access as a resource, then perhaps it should be recorded as just that: a resource’.  My point is that there isn’t any reason why we can’t do both.  OU Live allows us to do this, and there’s no reason why tutors can’t reference one type of resource from another.  During a ‘lecture’, you might hear the recorded phrase, ‘… and it was exactly this point that we covered during our earlier on-line tutorial’ (which students then might be tempted to go and listen to).

As far as I am aware, there isn’t yet any explicit faculty wide guidance about the recording of OU Live sessions, but I hope that there will be some one day.  When it comes to recording, my argument is very simple: we should use technology to help as many students as we can, irrespective of when and at what time they study.  Recordings of OU Live sessions can help with this, but I accept that there are important debates to resolve, especially the ethical dimension.

Module teams

One of the main points of this blog is that OU Live can be used in very different ways.  A lot can be done, but to get the best out of it, tutors (and staff tutors, who manage tutors) need a steer to understand how OU Live can be best used in the context of a module.  From the module team perspective, it’s important to offer explicit guidance to tutors about how it should and could be used.

Also, there is no reason why module teams cannot run their own OU Live sessions.  An OU Live session run by a module team should, of course, have a very different feel to any OU Live sessions that are run by tutors.  One idea is that a module team might run a series of ‘introductory lectures’ for a module: one at the start of a module, and one at the start of each major block.  This could be distinct from the sessions that tutors run which is all about small group work.

The module teams also have an important role to play in offering advice and guidance to tutors about the types of activities they consider to be useful.  At the beginning of a module presentation, the module team are the experts, and the tutors will occasionally need help in terms of understanding what to do in terms of how to effectively design a pedagogically engaging on-line tutorial.  Suggestions from the module team, perhaps working in collaboration with experienced tutors, can be invaluable.

Using OU Live for research

OU Live can be also used for research.  I’ve been recently been involved with an internal research project that has been all about understanding tutor experience on on-line modules.  The approach that the researchers (who were fellow associate lecturers) took was really interesting: they used OU Live to as a way to not only to help to facilitate a research interview, but also to record a research interview too.  The tutors managed to convert the recorded sessions into MP3 format and pass them onto me for analysis.

Group Tuition Policy

The university has recently been working on something called a ‘group tuition policy’, which is a university wide policy that aims to improve the learning opportunities that are available for students.  I’ve yet to fully appreciate the full significance of this policy, but one thing that I have heard is that students will be offered different types of session so that they will be able to attend a wider variety of learning events.  In the ‘new world’ of the group tuition policy, there may be on-line equivalents of face to face sessions.  I fully expect there to be a need to ‘group’ tutors together for on-line sessions in a way that my faculty currently groups together tutors for some face to face events.

Concluding points

This blog has considered the different ways that OU Live can and has been used.  I’ve heard it said that technology can move and develop a lot faster than pedagogy.  Put another way: we’re still figuring out how to most effectively teach using these new interactive tools.  As I mentioned earlier: you can do some things in face to face tutorials than you can in on-line tutorials.

It has personally taken me quite a bit of time to understand that there are a whole range of different interesting, exciting and dynamic opportunities that couldn’t have been possible if you only adopted face-to-face teaching.  A continued challenge that we have to collectively grapple with is how to effectively manage the important blend between the two.

Permalink Add your comment
Share post
Christopher Douce

Using the Kindle for research and studying

Visible to anyone in the world
Edited by Christopher Douce, Monday, 3 Nov 2014, 15:03

I have to confess, that when it comes to some technologies, I am a bit of a laggard.  It was only very recently that decided to get to grips with understanding the mysterious world of eReaders.  I have two excuses: the first is that there’s just so much ‘tech’ to keep on top of, which means that it’s difficult to know what to do next (which is actually a pretty lame excuse), and secondly, I’ve always been a bit sceptical about the screen quality of eReaders.

About a month ago, I requested a new book from the University library to do some preparatory reading for a new course I’m involved with.  The library turned around my request pretty quickly, but they also sent me an email that suggested that I’ve got some figuring out to do.  It was: ‘we only supply that text book in eBook format’.  No dead tree variety?  No, apparently they don’t do that anymore.

Back at home, I searched around for a box that contained a discarded Christmas present that one of my relatives had received and had then given to me after a couple of months; it was an Amazon Kindle.  After figuring out how to give it some power, the first thing I did was connect it up to my Amazon account.  I was gradually finding my way into being a ‘contemporary reader’.

This blog might be useful for anyone who has to use these eReader devices for their studies.  It might also be useful for any of my colleagues who have to battle with the mixture of convenience and frustration that accompanies the use of eReaders. 

I say ‘eReaders’, what I actually mean is ‘Kindle’, for now.  And when I say ‘Kindle’, is actually the really old ones with keyboards and black and white screen, and not any those new-fangled colour models.

The first section is all about figuring out how to read a text book.  The second section is all about how to download Open University on-line materials to your device (so you can read it on the go).  Some of the OU courses are presented entirely on line.  Two examples of this are: TT284 Web technologies, and H810 Accessible on-line learning: supporting disabled students. I describe how you might (potentially) go about downloading an on-line course to your device, so you can get ahead with your studies.

The third part is a bit of useful fun.  I asked myself the question, ‘I wonder what books I can get hold of for free?’  The answer is, ‘actually, quite a few’.  In the final section I share a few tips about how to download books that are out of copyright.  I, for one, haven’t been a great reader of the classics (I’ve been too busy messing around with computers; another lame excuse), but there are loads that are clearly available.

Working with text books

Apparently, the OU has a website called Mobile Connections, which offers some guidance about the use of mobile devices (OU website) and pointers to mobile strategy documents.  This is all very well, but how do I get a text book onto my device.

After clicking around the university library and attempting to access the text book that I wanted to ‘take out’, I was presented with the following message: "Patrons using iPads, iPhones or Android devices can download and read EBL content via the free Bluefire reader app. "  Now, I don’t have an iPad or an iPhone, and I’ve explicitly made a decision not to read any textbooks on my Android phone simply because my eyes are not up to it.  I haven’t heard about the Bluefire app, but the Bluefire website may or not be useful.

Another part of the library message was that "Downloaded EBL ebooks can also be transferred to any portable ebook reader that supports Adobe Digital Editions (ADE). There's a list of these compatible devices on the ADE website"

I had never heard of Adobe Digital Editions before but I’ve managed to find an Adobe website that offers a bit of information.  I had a good look on the ‘compatible devices’ list and my Kindle device wasn’t listed, which was pretty frustrating (to put it mildly).

All this frustration highlighted a division between two different formats: one called ePub and another called mobi.  Apparently ePub is an open standard, whereas mobi is owned by Amazon.  I soon saw that you couldn’t put ePubs on my Kindle, which was a bit rubbish.

 I asked myself two inevitable questions: ‘is it possible to convert an ePub to a mobi, and if you can, how do you do it?’  Thankfully, the internet is a wonderful thing, and I soon found a product called Calibre (website).  Calibre is described as a ‘free and open source e-book library management application developed by users of e-books for users of e-books’.  It’s a tool that you can download onto your PC, put an ePub in one side, and get a Kindle mobi book out of the other (with a bit of clicking and messing around in between).

 One thing that Calibre can’t do is take account of DRM.  DRM, or digital rights management, is used to protect media from being copied between different devices (which is why you need software like the Amazon Digital Editions).  If your ePub is protected by DRM (or, someone has said that you can’t copy it), then you can’t convert from one format to another.

For sake of argument, let’s say you’ve got a freely available text book that is useful with your module.  How do you go about transferring it to your Kindle?  In my naivety, I thought I could use the ‘old school’ technique of plugging it into the USB port of my computer and dragging files around.  Unfortunately, due to local OU system policies, staff cannot to write data to external USB devices due to an information security management policy.   As soon as I connected up my Kindle, I was presented with a message that read, ‘do you want to encrypt your device?’  If you’re ever asked that question in response to any e-reader you have, say ‘no’ straight away.  Thankfully, I did have the foresight to say no, as otherwise my Kindle would have probably been rendered useless.

Since I was unable to transfer my mobi files directly from my PC to my Kindle, how should I do it?  The answer came from a colleague: you email the books or any files that you want to read through your device to your Kindle account.  When you’ve done this, and you turn on your Kindle, magic happens, your document is downloaded.  If you’re interested, Amazon have some helpful pages (Amazon website).

Working with OU resources

More and more OU resources are being made available in Kindle and ePub formats.  This, I believe, can only be described as a ‘very good thing’ since some of the OU books can be pretty bulky.  When you’re working with an eReader, you can sometimes put all your module materials on your device.  When I go to tutorials, I tend to bring all the OU books with me – but rather than carrying them, I have them all preloaded on a Kindle.  This said, I am a great fan of paper; you can do things on paper that you can’t do with electronic devices and visa-versa, i.e. you can search for a term in an eBook, and you can scribble in your books with different coloured pens (and stick things between pages).

Not long after starting to mess around with my Kindle I realised I could do exactly the same with the other module materials I need to work with from time to time. I quickly realised that there would be a problem: things would start to get pretty confusing if I had all the different eBooks in one place on my Kindle.  Thankfully, there is a concept of a category.

After emailing a load of different mobi books to my Kindle, I noticed that my ‘TT284 category’ (I thought it was a good idea to group resources based on module code) became quickly overloaded, and I noticed that the default display order was the order in which the books were downloaded in.  Although this was useful, I got myself into a bit of a muddle with the download sequence.  I soon realised that it’s possible to change the ordering according to the title which made for a really nice sequence of module materials.

I’ve now got categories for all of the different modules I have downloaded resources for: H810, TT284 and M364 Fundamentals of Interaction Design.  For M364, I have a mobi version of the assignment booklet, and PDF copies of the four blocks.  I don’t, however, have a copy of the set text. 

The M364 set text is huge, and it’s a real pain to carry around, and students have regularly asked whether there are electronic versions that they could download.  Unfortunately, publishers are only just beginning to catch up with the new ways in which institutions and students consume their materials.  For now, we’ve got to battle on with a mixture of paper text books and OU materials which can be provided in a digital format.

Free books!

After months of it being in a box on my shelf, I’ve finally figured out how to use my Kindle.  Now that it’s jam packed with learning resources and I’m getting used to its screen (which isn’t too bad), I started to think about how I might use it to read stuff ‘for fun’, i.e. using it to read novels and non-fiction.

I quickly remembered Project Gutenberg which was a project dedicated to digitising books that were out of copyright.  I took another quick look at this and discovered that they now had books in eBook format, which was great news.  A quick look around took me to an interesting page called the Best Books Ever Listings (Project Gutenberg) I also discovered all these different ‘bookshelves’ organised by topic.  I really recommend that you have a good look around.

Another really good source of free (or really cheap) books is Amazon.  Within minutes of looking around I found a number of classics that I had never read before.  I clicked on a ‘buy’ button, and these new books were delivered to my device.  (Plus, since an eBook doesn’t have a cover, you can download some particularly racy books and read them when you’re on the train and no one would be any the wiser…!)

And finally…

As I said earlier, it sometimes takes me a while to get on top of a technology; I used to be someone who always wanted to mess around with the latest technologies and gadgets.

I don’t really know why it’s taken me so long to get to grips with eReaders.  I’m someone who likes the feel and smell, and flexibility of physical books.  This said, I’ve come to see that eReaders can give learners a flexibility that they never had before; an ability to carry everything around easily, and the ability to search for terms and phrases.  When a lot of material has moved ‘on-line’, eReaders can help us to access content in a convenient way without being always tied to a computer.  I think this is a really good thing.

I’m someone who loves to make notes.  One thing that you can’t do (very easily) is make scribbly notes on eBook pages, but that is okay: I’ll just have to figure out some new study strategies.

The more that you look at something, the more you think about different possibilities.  Looking at the Kindle has caused me to ask myself a further question, which is: how might you create an eBook from scratch?

Permalink 2 comments (latest comment by Leticia Briscoe, Tuesday, 29 Oct 2019, 21:44)
Share post
Christopher Douce

Chris’s Exam tips – Part 2 : During the exam

Visible to anyone in the world
Edited by Christopher Douce, Sunday, 8 May 2022, 14:41

This is the second in a series of two blog posts about revising and taking exams.  The last post was about exam revision tips.  This post is slightly different: it’s about how to tackle the exam on exam day.  Some of these might sound to be mind-bogglingly obvious, but sometimes it’s good to say stuff that is obvious.

1. Read the exam paper

This first tip is certainly one of those ‘school of the blindingly obvious’ tips, but it’s also one that is blindingly important, especially if you’re going to use some kind of strategy to work through the exam paper. 

A really important bit of any exam paper is the examination rubric; the instructions at the front of the exam that tells you which questions to answer.  Ideally, you should be in a situation where you know exactly what it is going to be (since you’ve already had a good look at a number of past exam papers).  The rubric shouldn’t change (it would be very surprising if it did), but it’s always a good idea to read it carefully to make sure you know what it is asking of you.

Reading the rules is really important: what you don’t want to do is to spend too much time answering questions that you don’t need to answer.

If you’re someone, like me, who hates exams, one thing to do is to spend a couple of minutes looking over some of the questions.  This way, you get a feel for what you have to do.  Also, when you see questions you can clearly answer, this will start to put you at ease (and you will know how to answer some questions, since you’ve been revising hard).

2. Pick an easy question to start with if you are stuck

Exams can be pretty stressful.  When we’re under stress, we can experience that feeling when our minds go blank, where we think that we can’t remember anything.  The reality is that we can remember everything that we’ve revised - we’ve just got to find a way to access it.

A really good way to ‘get going’ on an exam is to start with an easy question; a question that you know that you can answer.  As soon as you’ve started to write an answer, you usually start to remember things.

3. Think about and apply your strategy

Time is really important.  Three hours can pass in a flash.  One approach to exams is to try to gather up as many ‘easy marks’ as you can as possible.  This strategy can help you to free up more time to focus on the tougher questions that could take a whole lot longer. 

One good question to ask yourself is which questions you’re going to tackle in what order.  There is no reason why you can’t tackle questions in a different order to the sequence that they are presented in (unless there is a very good reason, of course!)

When I was an undergrad, someone told me that you could ‘break the exam rubric’, which means that there are these instance where you might want to answer more questions that are asked of you.  If there is an exam paper that says ‘answer two out of the five questions that are given’, there’s no reason why you can’t go ahead and answer three, for example. You might choose to ‘hedge your bets’ by perhaps choosing two of your strongest questions, followed by another question that you think you might do well at (providing you have the time, of course!)

If you ‘break the rubric’ what usually happens is that the examiner has to mark everything, and you get the marks for the questions that you do best at.  Don’t worry about making the examiner work.  Make them sweat.  It’s your exam, so you should feel free to answer as many questions as you can answer.  

4. Try to get into the mind of those who wrote the exam

Ask yourself the question: what is it that they’re trying to get at?  The module team will invariably looking for evidence that you understand a particular concept or idea, so try to communicate your knowledge and understandings as clearly as you can.  Write full sentences, use keywords, or leave bullet points.  If it helps, draw a diagram of make a table.  Underline some of the key concepts, for example.

If you’ve revised well, you should be able to see echoes of the module learning objectives within each exam paper.  Working through past exam papers helps you get into the dark and devious psyche of those who wrote the exam paper.  Look at the questions carefully: are they trying to assess your knowledge of a concept, or are they encouraging you to apply your knowledge in some way to solve a particular problem?

5. Write anything

This bit of advice sounds a bit crazy. If you find yourself in a situation where you are not sure how to answer a question, write down anything. What I mean is write down concepts, ideas, or keywords that you think might relate to the question that is being asked. The process of writing down ‘anything’ may trigger other thoughts and memories that may help you to connect with the question that you’re answering.  Plus, if you write down ‘anything that might be connected to the question’, there’s a chance that you might get some marks.  Writing ‘anything’ says to an examiner that you know ‘something’.

The reason why I think this bit of advice is important comes from my experience of being an examiner.  The role of an examiner is always to give you marks, not to take away marks from you.  There are these instances where I’ve seen exam papers that had big sections that were empty.  I always find it sad when I see blank spaces in an exam paper: a blank space or an empty question is a missed opportunity.

Even if you’re not sure what the question means, or what the exam team is looking for, put something down. If you put something down, there’s a chance you might get some marks. If you don’t put anything down, you certainly won’t get any marks. It’s always worth the risk.

6. Use all the time that you have available

The time that you have in the exam hall is your time, so do feel free to use all of it.  Call me weird, but I’ve always sat out an exam to the end.  In the time that you have, don’t miss sections out, take time to check through what you’ve written and ask the question ‘is there anything that I could add to this question to convince the examiner that I know my stuff?’  Sometimes you can discover that there is another way of answering a question, or it’s possible to add a further perspective.  Like I mentioned earlier: make the examiner work!

If you need another couple of answer booklets to present your knowledge and understanding, that’s fine: these should be available.  Put up your hand and ask the invigilator for some more paper.

7. Never cross out big sections

Sometimes you need to make some notes, do some rough working out for a maths or engineering problem, or write a short essay plan.  If need to make some ‘notes’ about anything, never cross them out.  Instead, leave a comment to tell the examiner how your notes are connected to a particular question.

If you put a line through a section of writing on your exam script, this tells the examiner that you don’t want a particular section to be considered as a part of your answer.  Let the examiner decide what is important and what is not: give them the opportunity to give you marks.

8. Go celebrate!

Do you remember that I mentioned ‘goal setting’ in the last blog?  Set a goal to do something after you’ve completed an exam.  Exams are stressful and take up a lot of time and energy.  When you’ve finished, go and do that something special that you promised yourself: you deserve it!

And finally…

These tips work for me.  Different people, of course, will have very different tips.  Why not ask other students what they do?  Also, there are some really good resources out there that you might find useful. 

One resource that I really recommend is The Good Study Guide by Andrew Northedge.  If you have access to this book, check out chapter 12, ‘preparing for examinations’.

Another set of really good resources is the Revising and Examination section of the Skills for Study website.  Do take a bit of time to go through these resources.  It contains some really good ideas.

Once again, good luck in your exams!

Permalink Add your comment
Share post
Christopher Douce

Chris’s Exam tips – Part 1: Revision

Visible to anyone in the world
Edited by Christopher Douce, Sunday, 8 May 2022, 14:44

I hate exams, and I’m sure there are many people out there who have exactly the same view, but I’ve come to see them as a necessary evil.  The more exams I’ve taken in my life, the less I’m fazed by them.

This series of two blog posts represents a summary of all the bits of revision advice and exam related tips that I have used and discovered during my career as a student, both within the Open University and at other institutions. This first post is all about revising.  The second post offers some tips for when you take your exam.

If you’ve got an exam in the not so distant future, I hope these two blog posts are useful!  Also, feel free to print out, share, or do whatever you want with these tips.  If you find them useful, that’s great!  Do feel free to send me a message; it’ll be great to hear from you.

1. Get organised

The moment you know the date of an exam, put it in your diary so you know when it is.  The very act of recording it will help you to remember it.  This date is usually immutable; it cannot be moved.  Locate all your study material, and find a good place to study.  Also, have a think about the times and places when you can study.

2. Make notes of module materials

When you’ve sorted everything out, you might be a bit surprised with how much course materials there is.  Make notes of the key sections in a module.  The process of making notes will make things go into your head.  A really good technique is to paraphrase (or rephrase) concepts; putting things in your own words is an invaluable skill, and it’s exactly this kind of skill that you will need to use in an exam.

If you have a set of notes for a block, or section of a module, try to makes notes of your notes.  Try to make notes so you can represent the entire module on a single A4 sheet of paper.  When you’ve done this, all the other details will be in your head (so you won’t need any more materials).

If you’re doing that commute, considering writing some of the key ideas on cards.  Create notes in whatever form works for you.

3. Little and often

I remember being told this tip when I was preparing from my GCSE exams: don’t try to cram, instead, try to revise in ‘chunks’.  This is great advice.  Cramming, or trying to desperately to learn everything the night before can just leave you worried and tired.  If you’re tired from reading course materials at 3am in the morning, the likelihood is that you’re not going to give your best exam performance.

Instead, try to revise when you can.  Figure out what ‘dead time’ you have in your day, and try to use the time that you find. 

When I was revising, I always set myself an overly ambitious goal of, say, revising for an hour.  If I’m being honest, I never really managed to do an entire hour: my mind would start to drift away from the subject I was studying; I would start to look out the window, think about my shopping and wonder whether I ought to do my hoovering.   It’s at that point you need to get away from the books because your brain is telling you something: you need a break.  A good break, where you do something different, will help you to remember more stuff.

4. Find the best time (and place) that works for you

Some people are early birds, other people are night owls.  Which are you?

Knowing what time of the day works best for you can really help you to get on top of everything.  If you find that you work best in the morning, one thought is to make sure that you’re ready to ‘hit the books’ in the morning when you wake up.

Finding a good revision space is really important; find somewhere that is quiet and free from distractions.  Let your friends and family know what you’re doing so they know not to disturb you (except for the times when they pop in to deliver a supportive cup of tea or coffee).

5. Think about creating a revision timetable (or habit)

This really is one of those ‘take it or leave it’ tips.  My own view is that life is too short to make a timetable, but what is important is the creation of a revision habit.  I used to try to revise at exactly the same time every day, between 10 and 11 in the morning.  I didn’t do this because I was obsessive or weird (although some people might argue otherwise!), it was because I knew that that this was the time when I was more likely to remember and understand things.

The thing with creating a timetable or creating a habit is that when you have either of these, not doing what you said that you would be doing has the potential to make you feel guilty (and guilt, of course, can be a motivator to prevent you from doing the same bad things again).  Another idea is to tell other people that you’re doing revision at a particular time, so they can then ask you the inevitable question of, ‘shouldn’t you be doing the revision that you told me about?’ when your housemate or partner catches you watching some game show on the television.

6. Find as many exam papers as you can stomach

Can you get access to past exam papers?  If so, try to get hold of a good number of them.  Don’t go too mad and download loads.  If you get hold of too many, there’s a good chance you might lose the will to live and start to judge your own sanity. Instead, go back between 3 to 5 years, depending on the module.  If you go back any further there’s a possibility that your module or course might have changed, and you wouldn’t want to waste your time looking at exam papers that are not going to be useful.

When you’ve got a past exam paper, give it a read through; get a feel for its structure and how it’s laid out.  The last thing you want is for the exam paper to surprise you on the day of your exam – this could happen if you don’t take the time to prepare.

When you’re looking at the papers, ask the question, ‘what learning do you think the examiners are trying to look for?’  If your module has published any learning outcomes, try to relate or connect these to the outcomes.

Work through a number of past exam papers from beginning to end, but hold one back (you could use one exam paper as a ‘timed exam’, which you could time yourself).  When you’re working through the exam paper, refer to the module or course materials – try to write the best answer you can.  If there’s something that you don’t quite understand, try to take this opportunity to learn what it is the exam questions are asking about.

If you get stuck, ask your tutor for help and guidance.  They don’t mind answering questions.  In fact, they’re paid to answer your questions, so feel free to use them as a resource.

7. Figure out your personal exam strategy

Now that you’ve got a whole bunch of exam papers, ask yourself what bits of the exam are you most comfortable with.  What does the rubric at the front of the paper say?  (The text at the start of a paper that tells you what questions you should answer).  Do you have to answer every question, or do you have a choice?  If you have a choice about what to answer, this might suggest what aspects of revision to concentrate on.

If there’s a part of an exam paper that you find either confusing or boring, think about whether there are other parts that might be a bit more interesting.  Think about what questions motivate you.  The more motivated you are, the better your revision will go.

Time in the exam hall is limited.  This means that you might also want to think about which questions you might be able to answer more quickly than others.  If you think about your ‘exam answering strategy’ before you see the real exam paper, you’ll feel a whole lot more comfortable on the day.

8. Seek out examination preparation tutorials or events

I’ve got a confession to make: it takes me ages to read things, and when I do, I don’t always take in what is written down.  I find that I can learn a whole lot better if I listen to either audio recordings or, better still, go to lectures.

If your module has got any examination preparation or revision tutorial events scheduled, then do what you can to go to them.  They are invaluable.  Also, the fact that you choose to sit down in a room with a bunch of other people for a few hours means that you can’t easily escape: you have no choice but to concentrate on what is happening within the tutorial or day school.

Another benefit of going to revision preparation sessions is that you can often be motivated by other students who are in a similar situation as you. 

Use your tutor; ask him or her as many questions as you need to.  Tutorial revision sessions can be invaluable.  Even if you have to travel quite a long way to get to one of them, do your best to get to one.

9. Invent your own exam questions

Each module is divided into a number of different blocks.   Each block usually contains a set of learning objectives.  These objectives are really useful since they are connected to both the assignments that you complete, and your end of module exam.

If you’ve worked through all your past exam papers and you’re starting to become thoroughly bored, why not look at the learning objectives and try to invent your own exam questions?  This is a really great thing to do; you stretch not just your creativity but also your knowledge of the concepts that are presented within your module.

10. Set a personal goal

When you’re revising, set a goal.  When you’ve achieve a goal, reward yourself with a treat.  The treat could be just about anything, but make sure that it is personal to you and your life.  Your treat might range from a walk to your local park, or perhaps as something as simple as a cup of tea and a biscuit after you’ve waded through a whole chapter on Java programming, for instance.

The bigger the piece of revision, the bigger the treat could be.  If you’ve finished going through an entire block from beginning to end, then choose something that makes you feel happy.  Revision is work, and it’s hard work, right?  If you have something to look forward to, it might become slightly easier.

11. Make time for yourself

I think this tip is really important: be good to yourself.  Taking exams is a tough business, and you’re the only one who is going to get through them; it’s really important to take care of yourself.   Don’t forget to have fun.  You’re not going to be able to revise to the best of your abilities if you’re always stressed or worried.

I remember this time when I was a second year undergraduate student.  The second year results are, of course, really important when it comes to your overall degree classification.  I had been revising hard, and if I’m honest, I was pretty sick of it.  There was some parts of my studying that wasn’t going very well, and I was getting a bit frustrated and taking it out on other people who were around me.

In the middle of the revision period, I decided to go out to the student union to have a bit of fun.  It wasn’t as busy as it usually was (because everyone was revising), but it turned out to be a brilliant night.  The next day, I felt a whole lot more relaxed: I needed a bit of time out.

I guess what I’m trying to say is remember to find time to relax; try to forget about all your revision for a bit.  Do whatever it is that you need to do so that you can relax.  We all do different things, so find that thing that works for you.  It helps you gain a bit of perspective.

12. Prepare for the day

Taking a bit of time to look into the practical issues that surround your exam is going to take a lot of stress away when it comes to the day.  A big question to ask really early on is: where is your exam going to be taking place?  Follow up questions are: how can I get there, and how long is it going to take me.  Since I hate being late for things, I usually plan to get a train or a bus that is a before the one that I should catch if I wanted to arrive on time.  Usually, it means that I get to places ridiculously early!

There are a couple of advantages about being ridiculously early: you, of course, add a bit of contingency into your journey if things go wrong (if the train is delayed), plus, it gives you time to check out the exam centre and become familiar with the place.  Being early (but not too early!) can give you some precious relaxation time.

If you’re someone who needs to do some last minute reading before the exam, it’s okay to do this, but do constrain yourself to your notes, rather than huge text books (which are just going to stress you out).

Also, make sure that you’ve got everything you need: make sure that you’ve got all the pens, pencils and erasers that you might need.  A really good tip that I was told once was: ‘always take a spare pen with you; the last thing that you want is to start panicking if your pen stops working when you’re in the exam hall’.  Make sure that you have a bottle of water and maybe even something to each.  One of my guilty secrets is that I’ve taken a chocolate bar into some exam halls so I can get an energy boost.  One word of advice is: don’t take crisps into exam halls.  Invigilators get very unhappy about crisps!

And finally…

These are my tips, and other people will say different things and give different advice.  Also, some people will, no doubt, disagree with some of these thoughts – but, that is okay: we’re all different, and we all study in different ways.

I’ll leave with a question: what is your favourite revision tip?  If someone asked you for the single biggest tip that you would give someone, what would it be?

Good luck with your revision!

Permalink Add your comment
Share post
Christopher Douce

First MCT Student Support Team Conference

Visible to anyone in the world

I drafted this blog post some time ago, but it got temporarily shelved due to the reality of day to day work.  I never forgot about it, though!  I still feel it’s important to share, since it relates to an important (and on-going) change within the university: the development and implementation of the Faculty of Mathematics Computing and Technology (MCT) Student Support Team (SST).

Introductory bit

Nineteenth of July 2014 was the date of the first ever Faculty of Mathematics Computing and Technology (MCT) Student Support Team (SST) conference that was held at The Open University campus in Milton Keynes.  Although this blog is written primarily for my colleagues, fellow tutors and students might find this summary useful since everyone has been subject to different amounts of change within the university.

The SST comprises of learning support staff (who are based in Birmingham and Nottingham), associate lecturers and central academics.  The idea behind an SST is to create a grouping of people who have more detailed knowledge of how to support students who are studying a particular subject, so we can improve the way that students are supported.  The ideas behind SSTs predate the increased focus on programmes of study due to the availability of student loans for part time students.

Although the SST staff for MCT are based in two regions, all the other Open University regions remain fundamentally important to the operation of the university: they remain centres from where tutorials and day schools are run, outreach events are facilitated, and students can have additional support sessions with tutors (and students can drop in to look at module materials).  They are also essential places from where continued AL development and training occurs.  Without these centres, tutors would not have sufficient training to allow them to offer excellent teaching and learning experiences to their students.

This blog starts with a summary of the plenary or introduction session, and is then followed by a session about retention.  There is then a brief description of session that was specific to the department of Computing and Communications.  This is then followed by an AL development session about disabled student services (this might be of interest to some students who study H810).  The day ends with a session about ‘tutor staff development’.

Introduction plenary

Our former Associate dean for regions and nations introduced the conference and welcomed us all to the SST.  We were shown a bunch of graphs that gave us a bit of context.  I remember that one of the graphs was about the number of students who are studying at a study intensity that is equivalent to full time students (which is a way to allow the OU to be compared to other institution).  In terms of full time equivalent (FTE) students, the number of students in MCT is broadly similar to the number of students in the Faculty of Art and the Faculty of Social Sciences.

An important point is that undergraduate computing and IT modules currently represent the biggest group in the faculty with 60% students registering for a BSc in Computing and IT.  By way of perspective, there are 13K FTE students in the whole of MCT, whereas Birkbeck (as a whole institution) has a total of 17K students.  We were given even more mind blowing stats: there are 1,200 associate lecturers in MCT, who teach a total of 2,900 contracts.

Retention and progression (of students between different modules) is considered to be an important strategy.  One figure that I made a note of was that there was a target of 75% of all students moving to the next module (unfortunately, I didn’t note whether this was related to level one modules only).

Our associate dean also spoke about other university priorities, such as helping to design student interventions (to make study easier), the student induction process (to help students become more familiar with the process of studying) and the development of the OU virtual learning environment (to make smart use of data).  On the subject of interventions, one great intervention that I heard was the SST proactively calling students discuss their study intentions if they have registered for an excessive number of modules.

One of the most important elements of OU study is the relationship between a student and their tutor.  The situation used to be that a student was left to their own devices at the end of a module.  The SST can now talk to a student between modules.

We heard about future plans.  Apparently there is some work afoot to improve the induction process.  For quite a while, I’ve heard about a new induction website, but I really do think there’s an opportunity to do more to help students become familiar with how to ‘survive’ when being a distance learning student. 

Future university activities include an attempt to diversity income, and continuing alignment of associate lecturer services to student services.  Also, quite recently, there has been internal debate regarding a new group tuition policy (which I hope to share some information about to ALs as soon as the details have been defined).

MCT Level 1 retention review

The next part of the day was by a colleague who spoke about a retention review project.  A really interesting fact I learnt was that module presentations that start in October have slightly higher retention figures than modules that begin in February.  I have no idea why!

I’ll do my best to summarise some of the key points that were made.  A really important concern was how well students are prepared for study.  If a student comes to the university without have any prior qualifications, this means that they less likely to complete.  There might be a range of different factors that influence this, such as available study time, workload, and other points, such as a lack of confidence (writing from experience as a former OU student, it takes time to ‘figure out’ how to consume the learning resources that we get from the university.

The one really important point that that has made the difference is: our tutors.  Proactive contact with an associate lecturer can really help to improve retention.

I’ve made a note of some recommendations: it’s important to have consistent module advice, we need to have effective subject specific advice, and have a solid induction programme to incorporate the development of on-line study skills.  The characteristics of a module and its design can make a different too: module teams to consider workload, to carefully consider assessment, and study events should be designed in to the module structure.

According to my notes, the review also offered some really practical suggestions, such as the SSTs could explicitly contact students without previous qualifications (but there’s also a tension between balancing the need to answer the phone in response to incoming student queries, and the willingness to initiate positive interventions: everything has a cost, and everything takes time).

I also made a note of the importance of student support:  AL development is to prioritise soft skills training for ALs (and perhaps points such as using the phone).

Over the last year, the university has made available something called a ‘student support tool’, which brings the associate lecturer closer to the systems that the university uses.  Whilst such tools are great, there is a question which needs to be asked, which is: how can any tool be used effectively.  Again, it’s back to the importance of helping to train and develop our brilliant associate lecturers to make sure that they are as well-equipped as they can ever be to support their students.

Computing and IT session

The next session in the day was by John Woodthorpe, academic lead for Computing and IT.  John opened the question by asking us a question:  ‘Put up your hands if you’re a member of the SST!’  His point was simple: we’re all members! We all have an important role to play.

John asked a rhetorical question about what the members of the SST in Birmingham and Nottingham are doing.  He answered this by providing a long list of activities.  The helped to book and organise exams at different venues, offered study and course choice advice, wrote disability profiles, and were always developing relationships with different members of the faculty.

During the session I made note of the phrase: ‘pre-emption, proactivity, prevention’, which seems like a good way to encapsulate different important aspects of study support.

One gap that has been identified is the need to develop a more comprehensive and structured approach to resubmission support, i.e. what happens if a student doesn’t pass an exam.  At the moment, students could call the SST and request a special session, but not all students know that they may be entitled to this support.  The SST is trying to tighten up resubmission support, aiming to offer more support for students beyond the boundaries of individual modules.

Disabled Student Services

After the faculty session, we were offered a number of different session choices.  I chose a session which was all about disabled student services.  I was interested to hear how the new SST would help MCT students who have disabilities.

We were introduced to different models of disability: the medical model and the social model.  A really interesting point was that people who have disabilities can have a ‘fluid sense of identity’.  What I think this means is that some disabilities may be transitory (such as a physical injury, such as a broken leg), and others may be episodic (such as ME).

We were also introduced to the Equality act 2010, which identifies a number of protected groups.  We were also told about different types of discrimination.  These are direct and indirect discrimination (which I had heard of), but there is also discrimination by association, i.e. discrimination might arise against someone if they have significant caring responsibilities.

We had a discussion about on-line tutorial materials, reasonable adjustments, and the provision of advice and guidance (of which, module accessibility guides play an important role).  We also spoke about the importance of contacting students directly to enquire about the extent of any adjustments that might be necessary, and also the role of examination boards.

Another area that was covered was the Disabled students allowance (DSA).  The DSA covers three areas: ergonomic furniture, personal support (such as non-medical helpers), and travel.  The DSA no longer funds standard electronic devices such as computers since they are now deemed to be an essential part of academic life, but funding for upgrades are permissible.  One really important point is that DSA is only available for students who are studying 30 points and a registered for a qualification (in Scotland this is 60 points).

Non-medical helpers can be really helpful for some students; they can make the difference between a module being accessible and a module being inaccessible.  A non-medical helper always works on behalf of the student: there is a contact between the student and the helper; tutors (or the university) are not able to speak directly to a helper – this relationship is fully controlled by the student.

AL Staff Development: The art of the possible

This final session of the day was all about how we should collectively think about associate lecturer development now that we’re in the new world of the student support team.  This session was facilitated by fellow staff tutor and tutor, Frances Chetwynd.

Associate lecturer broadly takes on two types: generic development (which is about how to perform teaching and learning, to make use of technology, and to be aware of university initiatives and developments), and module specific (sharing good practice about teaching certain subjects).  Now that we’re moving into broad teams, there are opportunities in terms of large subject (or, even programme) specific events.

Like all good tutorials, Frances’s session was very interactive.  We were given sets of post it notes to propose new ideas.  Pink post-it notes were about face-to-face AL development ideas, orange post it notes were about on-line (or other) types of development sessions.  When we had written down our ideas, we stuck them on different sheets of paper that had broad different category headings.

Frances also gave us ten stickers (which were in the form of ‘gold stars’), allowing us to collectively vote for the ideas that we liked best. 

The ones that I’ve noted down are: a session about ‘coding at different levels’ (which could be like some kind of internal symposium), Teaching Sense on TU100 (apparently there is a 10% tutor churn on TU100), making sure that we Record module briefings, and sessions about qualification overviews (or, future plans for modules).  There were loads more ideas, but I haven’t noted them all down.

Reflections

It was a busy day!  One thing that was really good about the conference was that it put the work of the SST and the MCT faculty in context (I had not heard of some of the numbers that our associate dean mentioned) and also helped to emphasise how much change has been going on within the university in the last few years.  It almost allowed us to ‘take stock’ of where we were. 

The session on AL staff development really got me thinking.  I came up with a number of ideas about different types of events that might potentially help tutors from across the UK who tutor on specific modules.  One thing that keeps coming to mind is that there is also more potential in terms of how the student support team members can feed directly into module teams.  I can’t help but feel that these new structures can help different bits of the university to work closer together, and that can only be a good thing.

All this said, it’s still very early days for the student support team and I guess I’m one of many who are still finding their feel in terms of what we do, how we work, and how we communicate with each other.  It also strikes me that although the university has been reorganised along slightly different lines, the notion of a geographic region or ‘place’ remains very important.  The development sessions that are run within our regional centres for our associate lecturers are invaluable.  Developments in information and communication technology has made the SST possible, which means now it’s up to us to figure out how to best take advantages of the opportunities it offers us.

Permalink Add your comment
Share post
Christopher Douce

TM354 Software Engineering: briefing

Visible to anyone in the world
Edited by Christopher Douce, Monday, 11 Sept 2023, 16:27

On Saturday 27 September I went to a briefing for a new OU module, TM354 Software Engineering.   I have to secretly confess that I was quite looking forward to this event for a number of reasons: I haven’t studied software engineering with the OU (which meant that I was curious), I have good memories of my software engineering classes from my undergraduate days and I also used to do what was loosely called software engineering when I had a job in industry.  A big question that I had was: ‘to what extent is it different to the stuff that I studied as an undergrad?’  The answer was: ‘quite a bit was different, but then again, there was quite a bit that was the same too’.

I remember my old undergrad lecturer introducing software engineering by saying something like, ‘this module covers all the important computer stuff that isn’t in any of the other modules’.   It seemed like an incredibly simple description (and one that is also a bit controversial), but it is one that has stuck in my mind.  In my mind, software engineering is a whole lot more than just being other stuff.

This blog post summary of the event is mostly intended for the tutors who came along to the day, but I hope it might be useful for anyone else who might be interested in either studying or tutoring the module.  There’s information about the module structure, something about the software that we use, and also something about the scheduling of the tutorials.

Module structure

TM354 has three blocks, which are also printed books.  These are: Block 1 – from domain to requirements, Block 2 – from analysis to design, and Block 3 – from architecture to product.  An important aspect to the module is a set of case studies.  The module is also supported by a module website and, interestingly, a software tool called ShareSpace that enables students to share different sketches or designs.  (This is a version of a tool that has been used in other modules such as U101, the undergraduate design module, and T174, an introduction to engineering module).

Block 1 : from domain to requirements

Each block contains a bunch of units.  The first unit is entitled ‘approaches to software development’, which, I believe, draws a distinction between plan driven software development and agile software development.  I’ve also noted down the phrase ‘modelling with software engineering’.  It’s great to see agile mentioned in this block, as well as modelling.  When I worked in industry as a developer, we used bits of both.

The second unit is called requirements concepts.  This covers functional requirements, non-functional (I’m guessing this is things like ‘compatibility with existing systems’ and ‘maintainability’ – but I could be wrong, since I’ve not been through the module materials yet), testing, and what and how to document.  Another note I’ve made is: ‘perspectives on agile documentation’.

Unit three is from domain modelling to requirements.  Apparently this is all about business rules and processes, and capturing requirements with use cases.  Prototyping is also mentioned.  (These are both terms that would be familiar with students who have taken the M364 Interaction Design module).  Unit four is all about the case study (of which I have to confess that I don’t know anything about!)

Block 2: from analysis to design

Unit five is about structural modelling of domain versus the solution.  Unit six is about dynamic modelling, which includes design by contract.  Unfortunately, my notes were getting a bit weak at this point, but I seem to remember thinking, ‘ahh… I wonder if this relates to the way that I used to put assertions in my code when I was a coder’.  This introduction was piquing my interest.

Unit seven was entitled, ‘more dynamic modelling’, specifically covering states and activities, and capturing complex interactions.  Apparently the black art of ‘state machines’ are also covered in this bit.  (In my undergrad days, state machine were only covered in the completely baffling programming languages course) .  Unit eight then moves onto the second part of the case study which might contain domain modelling, analysis and design.

Block 3: from architecture to product

This block jumped out at me as being the most interesting (but this reflects my own interests).  Unit nine was about ‘architecture, patterns and reuse’.  Architecture and requirements, I’ve noted, ‘go hand in hand’.  In this section there’s something about architectural views and reuse in the small and reuse in the large.  During the briefing there was a discussion about architectural styles, frameworks and software design patterns.

When I was an undergrad, software patterns hadn’t been discovered yet.  It’s great to see them in this module, since they are a really important subject.  I used to tell people that patterns are like sets of abstractions that allow people to talk about software.  I think everyone who is a serious software developer should know something about patterns.

Unit ten seems to take a wider perspective, talking about ‘building blocks and enterprise architectures’.  Other topics include component based development, services and service oriented architectures (which is a topic that is touched upon in another module, and also potentially the forthcoming TM352 module that covers cloud computing).

Unit eleven is about quality, verification, metrics and testing.  My undergrad module contained loads of material on metrics and reliability, and testing was covered only in a fairly theoretical way, but I understand that test-driven development is covered in this module (which is a topic that is linked to agile methods).  I’ll be interested to look at the metrics bit when this bit of the module is finalised.

The final unit takes us back to the case study.  Apparently we look at architectural views and patterns.  Apparently there are also a set of further topics that are looked.  I’m guessing that students might well have to go digging for papers in the OU’s huge on-line library.

Software

I’ve mentioned ShareSpace, which is all about sharing of software models with other students (modelling is an important skill), to enable students to gain experience of group work and to see what other students are doing and creating: software development invariably happens in teams.  Another important bit of software is an open source IDE (integrated development environment) called NetBeans.  I’m not sure how NetBeans is going to be used in this module, but it is used across a number of different OU modules, so it should be familiar to some TM354 students.

Assessment

TM354 comprises of three tutor marked assignments, a formative quiz at the end of every unit (that students are strongly encouraged to complete), and an end of module exam.  The exam comprises of two parts: a part that has questions about concepts, and a second bit that contains longer questions (I can’t say any more than this, since I don’t know what the exam looks like!)

Tutorials

Each tutor is required to deliver two hours of face to face tuition, and eight hours of on-line sessions through OU Live (as far as I understand).  In the London region, we have three tutors, so what we’re doing is we’re having all the groups come to the same events and we’re having each tutor deliver a face to face session to support students through every block and every TMA. 

We’re also planning on explicitly scheduling six hours of OU Live time, leaving two hours that the tutor can use at his or her discretion throughout the module (so, if there are a group of students who struggle with concepts such as metrics, design by contract, or patterns, a couple of short ad-hoc sessions can be scheduled). 

All the OU Live sessions will be presented through a regional OU Live room.  This means that students in one tutor group can visit a session that is delivered by another London tutor.  The benefit of explicitly scheduling these sessions in advance is that all these events are presented within the student’s module calendar (so they can’t say that they didn’t know about them!)  All these plans are roughly in line with the new tuition strategy policy that is coming from the higher levels of the university.  A final thought regarding the on-line sessions is that it is recommended that tutors record them, so students can listen to the events (and potentially go through subjects that they find difficult) after an event has taken place.

A final note that I’ve made in my notebook is ‘tutorial resources sharing (thread to share)’.  This is connected to a tutor’s forum that all TM354 tutors should have access to.  I think there should be a thread somewhere that is all about the sharing of both on-line and off-line (face to face) tutorial resources.

Permalink Add your comment
Share post
Christopher Douce

Teaching and learning programming for mobile and tablet devices: London Metropolitan University

Visible to anyone in the world

On 24 July 2014, I went to a Higher Education Academy sponsored event at London Metropolitan University.  The event was all about programming mobile devices, and it was the third time I had been to this event.  The previous time I went along, I spoke about a new module: TT284 Web Technologies (OU website).  This time I had two purposes: to share something about the beginnings of a new module TM352 Web, Mobile and Cloud (or, more specifically, its main objectives) and to learn what other institutions are getting up to.

A case study…

The first presentation of the day was by Yanguo Jing from London Met (who has organised the event) and Alastair Craig.  They presented ‘a case study of the delivery of a year 12 summer school on mobile app development’ (I had to ask what ‘year 12’ meant: and it means 16 or 17 year olds…): this was a part of an outreach event that London Met run (where students were selected random to participate).

They described some of the challenges that they faced.  Firstly, the students who joined the summer school sometimes had no programming knowledge, and they had to make the summer school fun.  A really big challenge was to try to scaffold the learning so that the students could create something presentable by the end of the week.

At this HEA event last year, a new programming system called TouchDevelop was introduced.  TouchDevelop is a ‘touch friendly’ programming language from Microsoft Research.  (You can check out the kind of apps that have been created by visiting the apps section of the TouchDevelop site).

The language features a touch screen programming interface that is especially design to work with mobile devices; it allows users to choose only the programming constructs that can be selected (it is also graphical in the same sense that Scratch is).  One really interesting aspect of the system is that you don’t have to install anything.  TouchDevelop also creates HTML 5 code, which means that it can be run on a wide range of different devices.

The summer school lasts for a week.  The summer school begins with an introduction to the tool and a discussion of syntax.  The next two days are all about the basics of a game and the game engine.   The fourth day the students are asked to create their own game, and on the fifth day, students are asked to present their games to each other.  Masters level students acted as supervisors. One point was that it seemed that some students (who had some prior programming experience, invariably using Scratch) got ahead with everything.

A fundamental question is, ‘how do you teach people in 18 hours when you don’t know what they know?’  The trick, apparently, is to get them to do things.

Some discussion questions were: ‘is it a good idea [to run this kind of summer school]?’, and ‘does your department do something similar’, and ‘how might you scale up this type of outreach activity?’

One thing that I learnt from the discussion is that there is a new version of Scratch available.  This first presentation ended with a discussion about MOOCs, and the point was made that MOOCs are very different to outreach.

Considering the cloud: teaching mobile, cloud computing and the web

The second presentation of the day was by yours truly.  The aim of the presentation was to talk about some of the areas that a new module about cloud computing may (or may not) cover.  Towards the end of the presentation, I asked all the delegates the following questions:

  • What do you think needs to be taught (cloud, mobile, web?)
  • How might you teach these concepts?
  • What might the challenges be?
  • How might you carry out assessments?
  • How do we protect and inform about change?

As everyone discussed these questions, I made a few notes.  One of the fundamental challenges (with an OU course) is to choose technologies that are not going to age quickly.  ‘The cloud’ is a really fast moving area where there appears to be continual change and innovation; new software services and releases are coming out all of the time.  One way to counter against this is to teach the underlying concepts and not just information about the services.

Another approach is to perhaps concentrate on building a learning community.  Developers and technical specialists invariably live within a community that shares technical knowledge and expertise.  It might be interesting and useful to expose learners to the dynamics of these environments.

An interesting point was both mobile and web platforms are just different ways to consume resources.  Increasingly the ‘web’ is being equated to HTML 5, and HTML 5 is increasingly being embedded within mobile devices.

On the subject of teaching, one delegate made a really interesting and relevant point.  He said, ‘I’ve given up lecturing… half of them just turn off’.  When it comes to teaching the development of mobile apps the thing to do is to split students in to small groups; it is the learning by doing that really counts.

When it comes to assessment, one delegate said, ‘you’ve got to have a project – if you can’t develop an app, then you fail’, and it’s important to get continual updates on progress.  Other approaches might include the use of computer marked multiple-choice questions, and writing about the bigger reflections and lessons from the module.

Poster session

By way of a brief interlude, Yanguo introduced a series of posters that had been put on the wall of the meeting room.  The posters were all about different apps that students had created.  There were two indoor navigation apps, an app for parking (which made me remember one of my blog-rants about poor interaction design), some kind of ‘cash register’ virtual payment app, a food checker or testing app, and a museum guide app.

Bringing the cloud into the classroom

The third presentation of the day was by Paul Boocock, from Staffordshire University.  Paul mentioned that undergrad students are introduced to a range of different platforms: iOS, Android and Windows (if I’ve understood things correctly).  For postgraduate students, there are a number of interesting sounding modules, such as Android app development and Advanced location aware app development.  These link into different mobile technology postgraduate qualifications (Staffs University), such as their Mobile Device Application Development MSc, Postgraduate Certificate (PgCert) and their Postgraduate Diploma (PgDip).

One of the big recent changes to their curriculum is that Staffs is now including ‘the cloud’ into the different mobile modules.  One thing that I should mention is that the concept of ‘the cloud’ is understood in terms of public clouds (as opposed to private clouds that are hosted by the university).

Paul treated us with some pictures of data centres, and said ‘[the cloud] is changing how we teaching this stuff’.  He left us with an interesting idea: ‘what used to take 30 days to get up and running can now be achieved in 30 minutes’.  The point was simple: you no longer need to buy, configure and commission servers.  The benefits of ‘the cloud’ include potential lower costs, scaling and the potential of gaining global reach.  In some respects, it might become more difficult to become more directly exposed to the physical hardware that runs systems.

We were introduced a term that was unfamiliar to me: cloud computing patterns.  The term relates to the way that cloud systems can be consumed as opposed to how they are designed.  Some patterns include on/off, i.e. an application might experience high levels of demand for a while (a bit like batch jobs), that a product or system might take off very quickly (so there would be increases in demand), or there might be predicable or unpredictable bursts of traffic (such as within computer games, for example).

Paul also talked about different platforms.  He mentioned a good number that I had heard of (but I’m not intimately familiar with).  These were Amazon (of course), Microsoft, Rackspace, HP Public cloud, and Google Cloud.  Given that his focus was on public clouds for teaching purposes, he discounted HP and Rackspace (I think due to cost), and then considered Amazon.

Amazon apparently offer something called educational grants (Amazon website), which allow educators to gain free credits to allow computing students to use their services.  The trade is that students who use the Amazon systems will be able to take their skills directly into the workplace.  Apparently, you can tell them how many students you have, and then they sort out the number of licences (or credits).

We learnt that Microsoft (of course) run a similar scheme, which enable students to use Azure academic passes (Microsoft Azure website).  Google was not considered as an alternative since there are no current discounts for non-profit organisations.  In the case of Staffordshire, Paul opted for Microsoft mainly because they had already made an investment into Microsoft tools and environment.

Before a live coding demo, which featured a pre-built service (from what I’ve noted) we were given a brief description of the different Azure components (or Azure services).  These were: compute, app services, data services, and network (this reminded me that I’ve come across similar terms when looking at the open source equivalent called OpenStack).

At the end of Paul’s session there was a lot of time for discussion.

Points of discussion included the challenge of working with different SDKs, and the emphasis on design patterns.  On the masters course, student were asked to create an interactive chat app that wasn’t not too dissimilar to the hugely popular WhatsApp.

Of course, there are always challenges that educators need to be mindful of.  These include the need to change modules without increasing their difficulties, and the question of how to assess everything if everything exists in the cloud (and students create services using lots of template code).  One way to do this is, of course, to ask students to write a reflective report about what they did to get a sense of what they understand.

All in all, it was both really interesting and really useful to know how another institution had successfully tackled the introduction of programming the cloud into their computing curriculum.

Developing digital literacies

The fourth talk of the day was by Terry McAndrew, which had the subtitle, ‘how students can quickly create interactive media resources for your curriculum’. Terry spoke about the broad subject of ‘digital literacy’ which can be defined as ‘the ability to effectively engage with a range of digital technologies to create, navigate and manipulate information’.  Terry mentioned a resource known as a JISC Digital Literacy InfoKit (JISC website).   The key contains seven different areas, which are: information literacy, media literacy, communication and collaboration, career and identify management (which I understand to be a new bit), ICT literacy, learning skills and digital scholarship.  A two year digital literacy programme (JISC) was also mentioned.

Interestingly, Yanguo mentioned some digital literacy resources that were available from London Met.  There’s also another bunch of digital literacy resources from the University of Southampton.  All these different resources made me realise that perhaps this is an area that I really need to catch up on.

Another part of Tony’s presentation centred upon accessibility.  Tony mentioned a tool called Xerte (University of Nottingham) which can be used to create accessible digital material which can be delivered through a virtual learning environment to different devices.  It’s a tool that is sometimes used by students who are studying a module that I tutor, H810 Accessible online learning: supporting disabled students (OU website).  The content that is delivered is presented using HTML 5, but the editor uses Adobe Flash (we were, however, told that there are plans afoot to develop an HTML 5 based editing environment).

Two other interesting links (and projects) mentioned were JORUM, a repository of digital educational material that can be shared between different institutions.  JORUM has been going for quite a while, and I hadn’t heard it mention for quite some time.  Having a quick look at the JORUM site quickly tells me that it has changed quite a bit since I first looked at it properly (which must have been around six or seven years ago).  The second reference was to a project called ACTOER, which is an abbreviation for Accessibility Challenges and Techniques for Open Educational Resources (of which Terry, who is based at TechDis, is the project manager).

I enjoyed Terry’s talk, and I found his presentation of different digital literacy resources useful, but there was little about the learning and teaching of how to program mobile devices.  This said, accessibility is always really important, and it’s something that designers of curriculum need to always be mindful of: I welcomed Terry’s reminders.

Alignment of mobile learning agenda with learning and teaching strategies in HEIs

The final presentation of the day was by Remy Olasoji from the University of East London.  From what I remember, I understand Remy to be an expert in the field of requirements engineering.  He presentation was about taking lessons from requirement engineering to try to understand how best to make use of mobile technology.

A final question of the day was, ‘how do we drive the mobile agenda forward?’  A simple answer was: ‘mobile is already happening – it’s driving forward of its own accord’.  One challenge lies with figuring out how to teach the fundamentals of mobile technologies to enable students to be thoroughly equipped and prepared when they have to work with new and changing devices.  Another challenge lies with figuring out how to best make use of devices to help students with their studies.

Reflections

All in all, a useful event; it’s always useful to hear what happens within other institutions and to learn about what challenges educators need to overcome.  One area that I would like to have heard more discussion about is information and data security.  The ‘cloud’ exposes these issues quite naturally, along with issues that relate to business and management.

Permalink Add your comment
Share post
Christopher Douce

New Technology Day - June 2014

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 8 Oct 2019, 17:42

This post is a quick summary of a New Technology Day event that took place at The Open University London regional centre on Saturday 14 June 2014.  I’ve written this post for a number of reasons: for my esteemed colleagues who came along to the day, so that I help to remember what happened on the day, so that I can share with my bosses what I’m getting up to on a day to day basis, and for anyone else who might be remotely interested.

One of the challenges that accompanies working in the area of technology, particularly information technology and computing, is that the pace of change is pretty relentless.  There are always new innovations, development and applications.  There are always new businesses doing new things, and using new techniques.  Keeping up with ‘the new stuff’ is a tough business.  If you spent all your time looking at what was ‘new’ out there, we simply wouldn’t get any work done – but we need to be understanding ‘the new’, so we can teach and relate to others who are using ‘all this new stuff’.

The idea for this day came from a really simple idea.  It was to ask colleagues the question, ‘have you heard of any new technology stuff recently?  If so, can you tell me about it?’  Rather than having a hard and fast ‘training’ agenda the idea was to create a space (perhaps a bit like an informal seminar) to allow us to have an opportunity to share views and chat, and to learn from each other.

Cloud computing

After a brief introduction, I kicked off with the first presentation, which was all about cloud computing.  A couple of weeks back, I went to a conference that was all about an open source ‘cloud operating system’ called OpenStack as a part of some work I was doing for a module team.  The key points from the presentation are described in a series of two blog posts (OU Blog)

Towards the end of the presentation, I mentioned a new term called Fog Computing.  This is where ‘the cloud’ is moved to the location where the data is consumed.  This is particularly useful in instances where fast access times are required.  It was interesting to hear that some companies might also be doing something similar.  One example might be companies that deliver pay-on-demand streaming video.  It obviously doesn’t make a lot of sense if the movies that you want to see are located on another continent; your viewing experience may well be compromised by unforeseen network problems and changes in traffic.

It was useful to present this since it helped to clarify some of my understandings, and I also hoped that others found it interesting too.  Whilst the concept of a ‘cloud’ isn’t new (I remember people talking about the magic of an X.25 cloud), the technologies that realise it are pretty new.   I also shared a new term that I had forgotten I had written on one of my slides: the concept of a devop – someone who is also a developer and an operator.

JuxtaLearn project

The second presentation was about the JuxtaLearn project, by Liz Hartnett, who was unable to attend.  Liz, however, still was able to make an impact on the event since she had gone the extra mile to make an MP3 recording of her entire presentation.  Her talk adopted the PechaKucha format.  This is where a presenter uses 20 slides which change every 20 seconds.  Since her slide deck was setup to change automatically, it worked really well.

We learnt about the concept of the threshold concept (which can be connected to the concept of computer programming) and saw how videos could be made with small project groups.  I (personally) connected this with activities that are performed on two different modules: TU100 My Digital Life, and T215 Communication and Information Technologies, which both ask students to make a presentation (or animation).

OU Live and pedagogy

The next talk of the day was by Mandy Honeyman, who also adopted the PechaKucha format.  Mandy talked about a perennial topic, which is the connection between OU Live and pedagogy.  I find this topic really interesting (for the main reason that I haven’t yet ‘nailed’ my OU Live practice within this format, but it’s something that I’m continuing to work on).  I can’t speak for other people, but it has taken me quite a bit of time to feel comfortable ‘teaching’ using OU Live, and I’m always interesting in learning further tips.

Mandy has taken the time and trouble to make a version of her presentation available on YouTube.  So, I’ve you’ve got the time (and you were not at the event), do give this a look.  (She prepared it using PowerPoint, and recorded it using her mobile phone).

The biggest tip that I’ve made a note of is the importance of ‘keeping yourself out of it’, or ‘taking yourself out of it [the OU Live session]’.  When confronted by silence it’s easy to feel compelled to fill it with our own chatter, especially in situations where students are choosing not to use the audio channel.

One really interesting point that came out during the discussion was how important it is to try to show how to use OU Live right at the start of their journey with the OU.  I don’t think this is done as it could be at the moment.  I feel that level 1 tutors are implicitly given the challenging task of getting students up to speed with OU Live, but they will already have a lot on their hands in terms of the academic side of things.  I can’t help think that we could be doing a bit better when it comes to helping students become familiar with what is increasingly become a really important part of OU teaching and learning.

It was also mentioned that application sharing can run quite slowly (especially if you do lots of scrolling) – and one related thought is that this might well impact on the teaching and learning of programming.

A final point that I’ll add is that OU Live can be used in a variety of different way.  One way is to use it to record a mini-lecture, which students can see during their own time.  After they’ve seen them, they can then attend a non-recorded discussion seminar.  I’ve also heard of it being used to facilitate ‘drop in sessions’ over a period of a couple of hours (which I’ve heard is an approach that can work really well).

Two personal reflections that connect to this session include: we always need good clear guidance from the module team about how they expect tutors to use OU Live, and secondly, we should always remember to give tutors permission to use the tool in the ways that make the best use of their skills and abilities, i.e. to say, ‘it’s okay to go ahead and try stuff; this is the only way you can develop your skills’.

The March of the MOOCs

Rodney Buckland, a self-confessed MOOCaholic, gave the final presentation of the morning.  The term MOOC is an abbreviation for Massive Open Online Course.  From the sound of it, Rodney has taken loads.  (Did he really say ‘forty’?  I think he probably did!)

He mentioned some of the most popular platforms.  These include: Coursera, Udacity and FutureLearn (which is a collaboration between the OU and other universities).  Rodney also mentioned a swathe of less well known MOOC platforms, such as NovoEd.   A really interesting link that Rodney mentioned was a site called MOOCList which is described as ‘an aggregator (directory) of Massive Open Online Courses (MOOCs) from different providers’. 

Rodney spoke about his experience of taking a module entitled, ‘Science of the solar system’.  He said that the lecturer had really pushed his students. ‘This was a real surprise to me; this was a real third level physics module’.

A really important point was that MOOCs represented an area that was moving phenomenally quickly.  After his talk had finished there was quite a lot of discussion about a wide range of issues, ranging from the completion rates (which were very low), to the people who studied MOOCs (a good number of them already had degrees), and to the extent to which they can complement university study.  It was certainly thought provoking stuff.

Assistive technology for the visually impaired: past, present and future

The first presentation after lunch was by my colleague Richard Walker.  Richard is a visually impaired tutor who has worked with visually impaired students.  He made the really important point that if an associate lecturer works for an average of about ten years, there is a very significant chance that a tutor will encounter a student who has a visual impairment.  Drawing on his previous presentation, there is an important point that it is fundamentally important to be aware of some of the challenges that visually impaired students can face.

Richard recently interviewed a student who has a visual impairment by email.  Being a persuasive chap, Richard asked me to help out: I read out the role of his student from an interview transcript.  The point (to me) was very clear: students can be faced with a whole range of different issues that we may not be aware of, and everything can take quite a lot longer.

Another part of Richard’s presentation (which connects the present and the future) was all mobile apps.  We were introduced to the colour recogniser app, and another app called EyeMusic (iTunes) which converts a scene to sound.   Another really interesting idea is the concept of the Finger Reader from the Fluid Interface group at MIT.

A really enjoyable part of Richard’s session was when he encouraged everyone to explore the accessibility sessions of their smartphones.  Whilst it was easy to turn the accessibility settings on (so your iPhone spoke to you), it proved to be a lot more difficult to turn the settings off.  For a few minutes, our meeting room was filled with a cacophony of robotic voices that proved to be difficult to silence.

Towards utopia or back to 1984

The penultimate session of the day was facilitated by Jonathan Jewell. Jonathan’s session had a more philosophical tone to it.  I’ve made a note of an opening question which was ‘how right or wrong were we when predicting the future?’

Jonathan referenced the works of Orwell, Thomas More (Wikipedia) and a vision of a dystopian future depicted in THX 1138, George Lucas’s first film.  Other subjects included economic geography (a term that I hadn’t heard before), and the question of whether Moore’s Law (that the number of transistors in a microprocessor doubles every two years) would continue.  On this subject, I have sometimes wondered about what the effect of software design may be if and when Moore’s law fails to continue to hold.

Other interesting points included the concept of the technological singularity and a connection to a recent news item (BBC) where a computer was claimed to have passed the Turing test.

A great phrase was infobesity – that we’re all overloaded with too much information.  This connects to a related phrase that I have heard of before, which is the ‘attention economy’.  Jonathan made a similar point that information is not to much a scare resource.  Instead, we’re limited in terms of what information we can attend to.

We were also given some interesting thoughts which point towards the future.  Everything seems to have become an app: computing is now undeniably mobile.  A final thought I’ve noted down is Jonathan’s quote from security expert, Bruce Schneider: ‘surveillance is the business model of the internet’.  This links to the theme of Big Data (Wikipedia).  Thought provoking stuff!

Limits of Computing

The final talk of the day was by Paul Piwek.  Paul works as a Senior Lecturer in the Department of Computing and Communications at The Open University.  Paul works on a number of module teams, and has played an important role in the development of a new module: M269 Algorithms, Data Structures and Computability.  It is a course that allows students to learn about some of the important fundamentals of computer science.

Paul’s brief was to talk about new technologies – and chose to explore this by considering the important question of ‘what are the limits of computability?’  This question is really important in computer science, since it connects to the related questions: ‘what exactly can we do with computers?’ and ‘what can they actually be used to calculate?’

Paul linked the title of his talk to the work of Alan Turing, specifically an important paper entitled, ‘on computable numbers’.  Paul then went onto talk about the differences between problems and algorithms, introduced the concept of the Turing Machine and spoke about a technique called proof by contradiction.

Some problems can take a long time to be solved.  When it comes to computing, speed is (obviously) really important.  An interesting question is: how might we go faster?  One thought is to look towards the subject of quantum computing (an area that I know nothing about; the page that I’ve linked to causes a bit of intellectual panic!)

Finally, Paul directed us to a Canadian company called DWave that is performing research into the area.

Reflections

After all the presentations had come to an end we all had a brief opportunity to chat.  Topics included location awareness and security, digital forensics, social media, the question of equality and access to the internet.  We could have chatted for a whole lot longer than we did.

It was a fun day, and I really would like to run another ‘new technology day’ at some point (I’ve just got to put my thinking hat on regarding the best dates and times).  I felt that there was a great mix of presentations and I personally really liked the mix of talks about technology and education.  It was a great opportunity to learn about new stuff.

By way of additional information, there is also going to be a London regional ‘research day’ for associate lecturers.  This event is going to take place during the day time on Tuesday 9 September 2014.  This event will be cross-faculty, cross-disciplinary event, so it’s likely that there might be a wide range of different events.  If you would like some more information about all this, don’t hesitate to get in touch, and I’ll point you towards my colleague Katy who is planning this event.

Permalink 1 comment (latest comment by Mandy Honeyman, Tuesday, 17 June 2014, 15:40)
Share post
Christopher Douce

OpenStack conference, June 2014 (part 2 of 2)

Visible to anyone in the world
Edited by Christopher Douce, Saturday, 7 June 2014, 13:21

This blog post is the second of two that summarises an OpenStack conference that I attended on 4 June in London. 

This second half of the conference had two parallel sessions.  Delegates could either go to the stream that was intended for novices (which is what I did), or go to a more technical session. 

I was quite tempted by the technical session, especially by a presentation that was all about what it means to be an OpenStack developer.  One of the key points that I did pick up on was that you need to know the Python language to be an OpenStack developer, which is a language that is used within the OU’s data structures and algorithms module, M269 Algorithms, data structures and computability

Introduction to OpenStack

The first session of the afternoon was by Kevin Jackson who works at Rackspace.

Kevin said that OpenStack and Linux are sometimes spoken about in similar terms.  Both can be created from distributions, and both are supported by companies that can offer consultancy support and help to move products forward. ‘OpenStack is like a pile of nuts’, said Kevin, and the nuts represent different components.

So, what are the nuts?  Nova is a compute engine, which hosts a virtual machine running in a Hypervisor.  I now understand that a hypervisor can host one or more virtual machine.  You might have a web server and your application code running within this bit of OpenStack.

Neutron is all about networking.  In some respects, Neutron is a virtual network that has been all written in code.  There is more about this in later presentations.  If you have different parts of an OpenStack implementation, Neutron allows the different bits to talk to each other; it pretends to be a physical network.

Swift is an object store, which is something that was spoken about during an earlier presentation.  Despite my earlier description, Swift isn’t really like a traditional file system.  Apparently, it can be ‘rack or cabinet aware’, to take account of the design of your physical data centre.

Cinder is another kind of storage; block storage.  As mentioned earlier, to all intents and purposes, Cinder looks like a ‘drive’ to a virtual machine.  I understand a situation where you might have multiple virtual machines accessing the same block storage device.

Ceilometer is a component that was described as telemetry.  This is a block which can apparently say how much bandwidth is being used.  (I don’t know how to describe what ‘bandwidth’ is in this instance – does it relate to the network, the available capacity within a VM, or the whole installation?  This is a distinct gap in my understanding).

Heat is all about orchestration.  Heat monitors ‘the cloud’, or its environment.  Kevin said, ‘if it knows all about your environment and suddenly you have two VMs and not three, it creates a third one’. This orchestration piece was described as a recipe for how your system operates.

All these bits and pieces are controlled by a web interface called Horizon, which I assume makes calls to the APIs of each of these components.  You can use Horizon to look at the components of the network, for example.  I have to confess to being a bit confused about the distinction between JuJu and this standard piece of OpenStack – this is another question that I need to ask myself.

At the end of Kevin’s presentation, I’ve made a note of a question from the floor which was: ‘why should I go open source and not go for a proprietary solution?’  The answer was interesting: you can get locked into a vendor if you choose a proprietary solution.  If you use an open source solution, such as OpenStack you can move your ‘cloud’ different providers, say, from Rackspace to HP.  With Amazon web services, you’re stuck with using Amazon web services.  In some respects, these arguments echo arguments that are given in favour of Linux and other open source products.  The most compelling arguments are, of course, freedom and choice.

A further question was, ‘how mainstream is this going to go?’  The answer was, ‘there’s many companies around the globe who are using OpenStack as a solution’, but I think it was also said that OpenStack is just one of many different solutions that exist.

OpenStack and Storage made easy at Lush Cosmetics

The second presentation of the day was made by Jim Liddle who works for a cloud consultancy called Storage Made Easy.

Jim presented a case study about his work with Lush Cosmetics.  I’ve made note of a number of important requirements: the data that is stored to the cloud should be encrypted, and there should be ways to help facilitate auditing and governance (of the cloud). 

It’s interesting that the subject of governance was explicitly addressed in this case study.  The importance of ‘institutional control’ and the need to carry out checks and balances is one of reasons why organisations might choose private clouds over public clouds. In the case of Lush, two key drivers included the cost per user, and the need to keep their data within the UK.

A new TLA that I heard was OVF (Wikipedia), an abbreviation for Open Virtualization Format, and is a way to package virtual machines in a way that is not tied to any particular hypervisor (VM container), or architecture.  Other technologies and terms that were referred to included: MySQL, which is touched on in TT284 Web Technologies (OU), Apache, MemCached (Wikipedia) and CentOS.

Deploying Windows Workloads into OpenStack using JuJu

A lot of the presentations had a strong Linux flavour to them.  Linux, of course, isn’t the only platform that can be used to power clouds. Alessandro Pilotti from Cloudbase solutions spoke on the connections between Windows and OpenStack.

Terms that cropped up during his presentation included Hyper-V (a hypervisor from Microsoft), KVM (Kernel based virtual machine, which is Linux hypervisor), MaaS (metal as a service, an Ubuntu term), GRE Tunnels (GRE being an abbreviation for Generic Routing Encapsulation), NVGRE (Network Virtualization using Generic Routing Encapsulation), and RDP (Remote Desktop Protocol).

It was all pretty complicated, and even though I’m reasonably technical, this was at a whole other level of detail.  Clicking through some of the above links soon takes me into a world of networking and products that are pretty new to me.  This clearly suggests that there is a whole lot of ‘new technology’ out there that I need to try to make a bit of sense of, and this, of course, takes time.

Alessandro also treated us to a live video link that showed a set of four small computers that were all hooked up together (I have no idea what these small desktop computers without screens were called; they used to have a special name).  The idea was to show LEDs flashing to demonstrate some remote rebooting going on.

This demo didn’t quite work out as planned, but it did get me thinking: to really learn how to do cloud stuff, a good idea would be to spend time actually playing with bits of physical hardware. This way you can understand the relationships between logical and physical architectures.  The challenge, of course, is finding the time to get the kit together, and to do the learning.

Using Swift in Entertaining Ways

This presentation was made by a number of people from Sohonet a company that offers cloud services to the film and TV industry.  An interesting application of cloud computing is film and video post-production, the part of production where when recordings are digitally edited and manipulated. An interesting challenge is that when it comes to video post-production we’re talking about huge quantities of data, and data that needs to be kept safe and secure.

Sohonet operates two clusters that are geographically separate.  Data needs to be held over different timescales, i.e. short, medium and long-term, depending upon the needs of a particular project.

A number of interesting products and companies were mentioned during this talk.  These include Expandrive where an OpenStack Swift component can become a network drive.  Panzura was mentioned in terms of Swift as a network appliance.  Zmanda and Cloudberrylab were all about backup and recovery.  Interesting stuff; again, a lot to take in.

Bridges and Tunnels – a drive through OpenStack networking

Mark McClain from the OpenStack foundation, talked about the networking side of things, specifically, the OpenStack networking component that is called Neutron.  Even though I didn’t understand all of it, I really enjoyed this presentation.  On a technical level, it was very dense; it contained a lot of detail.

Mark spoke about some of the challenges of using the cloud.  These included a high density of servers, the difficulties of scaling and the need for on-demand services.  A way to tackle some of these challenges is to use network virtualisation and something called overlay tunnelling (but I’m not quite sure what that means!)

Not only can virtual machines talk to virtual drives (such as the block storage service, Cinder), but they can also talk to a virtual network.  The design goals of the network component were to have a small core, and to have a pluggable open architecture which is configurable and extensible.  You can have DHCP configuration agents and can specify network traffic rules.  Neutron is also (apparently) backed by a database and a message queue.  (I also heard that there is a REST interface, if I’ve understood it correctly and my notes haven’t been mangled in the rush to write everything down).

A lot of network hardware can now be encoded within software (which links back nicely to the point about abstraction that I mentioned in the first block).  One example is something called Openvswitch (project website).  I’ve also noted down that you can have a load balancer as a service, a VPN as a service and a firewall as a service (as highlighted by the earlier vArmour talk).

Hybrid cloud workloads

The final talk of the day was by Monty Taylor who is also from the OpenStack foundation.  A hybrid cloud is a cloud that is a combination of public and private clouds (which could, arguably be termed an ‘ecosystem of clouds’).  Since it was the end of the day, my brain was full, and I was unable to take a lot more on board.

Reflections

All this was pretty interesting and overwhelming stuff.  I remember one delegate saying, ‘this is all very good, but it’s all those stupid names that confuse me’.  I certainly understand where he was coming from, but when it comes to talking about technical stuff, the names are pretty important: they allow developers to share understandings.  I’m thankful for those names, although each name does take quite a bit of remembering.

One of the first things I did after the conference was to go look on YouTube.  I thought, ‘there’s got to be some videos that helps me to get a bit more of an understanding of everything’, and I wasn’t to be disappointed – there are loads.  Moving forward, I need to find some time to look through some of these.

One of the things that I’ll be looking for (and something that I would have liked to see in the conference) was a little bit more detail about case studies that explicitly show how parts of the architecture work.  We were told that virtual machines can spin up in situations where we need to attend to more demand, but perhaps the detail of the case studies or explanations passed me by.

This is a really important point.  Some aspects of software development are changing.  I’ve always held the view that good software developers need to have an appreciation of system administration (or the ‘operations’ side of things).  When I had a job in industry there was always a separation between the systems administrators and the developers.  When the developers are done, they throw software over the wall to the admins who deploy the software.

This conference introduced me to a new term: a devop – part developer, part programmer.  Devops need to know systems stuff and programming stuff.  This is a reflection of software being used at new levels of abstraction: we now have concepts such as network as a service, and software defined security.  Cloud developers (and those who are responsible for keeping clouds running) are system software developers, but they can also be (and have to understand) application development too. 

A devop needs a very wide skill set: they need to know about networks, hardware, operating systems, and different types of data store.  They might also need to know about a range of different scripting languages, and other languages such as Python.  All these skills take time (and effort) to acquire.  A devop is a tough and challenging job, not only due to the inherent complexity of different components, but also due to the speed that technologies change and evolve.

When I arrived at the conference, I knew next to nothing about what OpenStack was all about, and who was using it.  By the end of the conference I ended up knowing the names of some of its really important components; mists of confusion had started to lift.  There is, however, a huge amount of detail to get my head around, and one of the things that I’m also going to do is to look at some user stories (OpenStack foundation).  This, I think, will help to consolidate some of my learning.

Permalink Add your comment
Share post
Christopher Douce

OpenStack conference, June 2014 (part 1 of 2)

Visible to anyone in the world
Edited by Christopher Douce, Friday, 6 June 2014, 17:43

On 4 June, I went to an event that was all about something called OpenStack.  OpenStack is an open source software framework that is used to create cloud computing systems.  The main purpose of this blog is to share my notes with some of my colleagues, but also to some of the people who I met during the conference.  Plus, it might well be of interest to others too.

Cloud computing is, as far as I understand it, a broad terms that relates to the consumption and use of computing resources over a network.  There are a couple of different types of cloud: there are public clouds (which are run by large companies such as Amazon and Google), private clouds (which are run by a single organisation), and hybrid clouds (which is a combination of public and private clouds).  There’s also the concept of a community cloud - this is where different organisations come together and share a cloud, or resources that are delivered through a cloud.

This is all very well, but what kind of computing resources are we talking about?  As far as I know, there are a couple.  There’s software as a service (or SaaS).  There’s PaaS, meaning, Platform as a Service, and there’s IaaS, which is Infrastructure as a Service.  Software as a Service is where you offer software through a web page, and you don’t ever touch the application code underneath.  Infrastructure as a Service is where you might be able to manage a series of ‘computers’ or servers remotely though the cloud.  More often than not, these computers are running in something called virtual machines.

These concepts were pretty much prerequisites for understanding what on earth everyone was talking about during the day.  I also picked up on a whole bunch of new terms that were new to me, and I’ll mention these as I go.

Opening Keynote : The OpenStack Foundation

Mark Collier opened the conference.  Mark works for the OpenStack Foundation (OpenStack website). During his keynote he introduced us some of the parts that make up OpenStack (a storage part, a compute part and a networking part), and said that there is a new software release every six months.  To date there are in the order of approximately 1.2k developers.  The community was said to comprise of approximately 350 companies (such as RedHat, IBM, HP, RackSpace) and 16k individual members.

Mark asked the question: ‘what are we trying to solve?’  He then went onto quote Mark Andreessen who said, ‘software is eating the world’.  Software, Mark said, is said to be transforming the economy and disrupting industries. 

One of the most important tools in computer science is abstraction.  OpenStack represents a way to create a software defined data centre (a whole new level of abstraction), which allows you to engineer flexibility to enable organisations to move faster and software systems to scale more quickly.

Mark mentioned a range of different companies who are using OpenStack.  These could be considered to be superusers (and there’s a corresponding superuser page on the OpenStack website which presents a range of different case studies).  Superusers include organisations such as Sony, Disney and Bloomberg, for example.

I remember that Mark said that OpenStack is a combination of open source software and cloud computing.  Another link that I noted down was to something called the OpenStack marketplace (OpenStack website).  Looking on this website shows a whole range of different Cloud distributions (many of which come from companies that offer Linux distributions).

Keynote: Canonical, Ubuntu and OpenStack

Mark Shuttleworth from Canonical (Canonical website) offered an industry perspective.  Canonical develops and supports Ubuntu which is a widely used Linux distribution.  (It is used, as far as I can remember in the TM129 Technologies in Practice module).  As well as running on the desktop, Ubuntu is widely used on the server side, running within data centres.  A statistic I’ve noted down is that Ubuntu accounts for ‘70% of guest workloads’.  What this means is that we’re talking about instances of the Linux operating system that have been configured and packaged by Ubuntu (that are running on a server within a datacentre, somewhere).

A competitor to Ubuntu is another Linux distribution called CentOS.  There is, of course, also Microsoft Windows Server.  When you use public cloud networks, such as those provided by Amazon, I understand that you’re offered a choice of the operating system that you want to ‘host’ or run.

An interesting quote is, ‘building your cloud is a bit like building your own mainframe – users will always want it to be working’.  We also heard of something called OpenStack Interoperability Laboratory.  Clouds can be built hundreds of times a day, we were told – with different combinations of technology from different vendors.  ‘Iteration is the only way to understand the optimal architecture for your use case’.

A really important aspect of cloud computing is the way that a configuration can dynamically adapt to changing circumstances (and user demands).  The term for how this is achieved (in the cloud computing world) seems to be ‘orchestration’.  In OpenStack, there is a tool called JuJu (Wikipedia).  JuJu enables (through a dashboard interface) different combinations of components to be defined.  There is a concept of a ‘charm’ (which was described as scripts which contain some operational coding).  If you would like to look at what it is all about, there’s a website called JuJu Charms that I’ve yet to spend time exploring.

I’ve also noted down something called a Service Orchestration Framework, which lets you place services where you want, and on what services.  There are some reference installations for certain types of cloud installations (which reminds me of the idea of ‘design patterns’ in software).

Mark referred to a range of different technologies during his talk, some of which I had only very briefly heard of.  One technology that was referred to time and time again was the concept of the hypervisor (Wikipedia).  I understand this to be a container (either hardware or software) that runs one or more virtual machines.  Other terms that he mentioned or introduced include KVM (Kernel-based virtual machine), Ceph (a way to offer shared storage), and MaaS, or Metal as a Service (Ubuntu), which ‘brings the language of the cloud to physical servers’.

A further bunch of mind boggling technical terms that were mentioned include ‘lightweight hyppervisors’ such as LXC (LinuX Containers), Hadoop, which is a data storage framework, and TOSCA (Wikipedia), which is an abbreviation for Topology and Orchestration Specification for Cloud Applications.  In terms of databases, some new (and NoSQL) technologies that were mentioned included MongoDB and Cassandra.

At this point, it struck me how much technologies have changed in such an incredibly short time, reminding me that we live in interesting times.

Keynote: Agile infrastructure built in OpenStack

The second keynote of the day was by John Griffith, Project Technical Lead, SolidFire.  John’s presentation had the compelling subtitle: ‘building the next generation data centre with OpenStack’.

A lot of people started using Amazon, who I understand to be the most successful public cloud provider, to use IT resources more efficiently.  There are, of course, other providers such as Google compute engine (Google), Windows Azure (Microsoft), and SoftLayer (which appears to be an IBM company).

A number of years ago, at an OU postgrad event, I overheard a discussion between two IT professionals that began with the question, ‘so, what are the latest developments in servers?’  The reply was something about server consolidation: putting multiple services on a single machine, so you can use that one machine (a physical computer or server) more efficiently.  This could be achieved by using virtual machines, but you can only do so much with virtual machines.  What happens if you run out of processing power?  You need to either get a faster machine, or move one of your virtual machines to another machine that might be under-utilised.

The next generation data centre will be multi-tenant (which means multiple customers or organisations using the same hardware), have mixed workloads (I don't really know what this means), and have shared infrastructure.  A key aspect is that an infrastructure can become software defined, as opposed to hardware defined, and the capacity of a cloud configuration or setup can change depending upon local demand.

There were a number of attributes of cloud systems.  I think there were: agility, predictability, scalability and automation.

In the cloud world applications can span many virtual machines, and data can be stored in scalable databases that are structured in many tiers.  The components (that make up a cloud installation) can be configured and managed through sets of predefined interfaces (or APIs).  I also made a note of a mobile app that can be used to manage certain OpenStack clouds.  One example of this is the Cloud mobile app from Rackspace.

Another interesting quote was, ‘[the] datacentre is one big computer and OpenStack is the operating system’.  Combining servers together has potential benefits in terms of power consumption, cooling and the server footprint.

One thing that developers need to bear in mind is how to create applications.  Another point was: consider scalability and plan for failure.  A big challenge lies with uncovering and deciphering what all the options are.  Should you use, for example, block storage services, or object storage?  What are the relative advantages and disadvantages of each?

Parts of this presentation started to demystify some of the terms that have baffled me from the start.  Cinder was, for example, is OpenStack’s block storage.  Looking outwards from the operating system, a block storage device could be a hard disk, or a USB drive.  Cinder, in effect, mimics what a hard drive looks at, and you can store stuff to a Cinder service as if it was a disk drive.  Swift is an object database where you can store object.  So, you might think of it in terms of sets of directories, the contents of which are replicated over different hard drives to ensure resilience and redundancy.

There is a difference between a service that is an abstraction to store and work with data, and how physical data is actually stored.  To make these components work with actual devices, there are a range of different plug-ins.

Presentation: vArmour

I have to admit that I found this presentation thoroughly baffling.  I had no idea what was being presented until I finally picked up on the word ‘firewall’, and the penny dropped: if a system architecture is defined in software, the notion of a firewall as a physical device suddenly becomes very old fashioned, if not a little bit quaint.

In the cloud world, it’s possible to have something a ‘software firewall’.  A term that I noted down was ‘software defined security’.  Through SDS, you can define what traffic is permissible between nodes and what isn’t, but in the ‘real world’ of physical servers, I’m assuming that physical ‘top layer’ firewalls are important too.

I also came across two new terms (or metaphors) that seem to make a bit of sense in the ‘cloud world’.  Data could, for example, move in a north-south direction, meaning it goes up and down through various layers.  If you’ve got east-west movement of data, it means you’re dealing with a situation where you might have a number of different virtual machines (that might have been created to respond to end user demand), which may share data between each other.  The question is: how do you maintain security when the nature of a configuration might dynamically change? 

Another dimension to security which crossed my mind was the need for auditability and disaster recovery, and both were subjects that were touched upon by other presenters.

In essence, I understood vArmour to be a commercial software defined security product that works akin to a firewall that can be used within a cloud system.

Presentation: The search for the cloud’s ‘God Particle’

Chris Jackson, who works for Rackspace (a company which has the tagline ‘the open cloud company’), gave the final presentation before we all broke for lunch.  Chris confessed to being a physicist (as well as a geek) and referred to research at CERN to find ‘the God particle’.  I also seem to remember him mentioning that CloudStack was used by CERN; there’s an interesting superuser case study (OpenStack website), for those who might be interested.

Here’s the question: if there is a theory that can describe the nature of matter, is there a theory that might explain why a cloud solution might not be adopted?  (He admitted that this was a bit of fun!)  He presented three different theories and asked us to vote on which were, perhaps, the most significant.

The first was: application.  Some applications can be rather fragile, and might need a lot of cosseting, whereas other forms of application might be very robust; they’re all different.  Cloud applications, it is argued, embrace chaos and build failure into applications.  Perhaps the precise character of certain applications might not lend it to being a cloud application?

Theory two: integration.  There could be the challenge of integration and connection with existing systems, which might themselves have different characteristics. 

The third theory is all about operations.  This is more about the culture of an organisation.

So, which theory is the reason why organisations don’t adopt a cloud solution?  The answer is: quite possibly all of them.

Permalink Add your comment
Share post
Christopher Douce

Disabled student services conference 2014 – day 2

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 22 Jan 2019, 09:39

Keynote: positive thinking

The first keynote of the day was by motivational speaker, David Hodgson.  The title of his session was, ‘the four key ways to happiness and success’ (which was a really very ambitious title, if you ask me!)  I’ve seen David talk before at a staff development day in London, where he encouraged us to reflect upon our Myers-Briggs personality profile.  Apparently, this was the focus of a later workshop that he ran later during the morning.

So, what are the four key ways?  Thankfully, I was sufficiently caffeinated to be able to take a note of them.  They are: (1) know yourself (and the great things that you’re capable of), (2) having self-belief, (3) have a plan (of some kind), and (4) have a growth attitude.   Of course, I’m paraphrasing, but, all in all, these are pretty good points to think about.

David also presented us with a quote from Abraham Maslow, who proposed his eponymous Hierarchy of Needs (Wikipedia).  The quote goes:  ‘If you plan on being anything less than you are capable of being, you will probably be unhappy all the days of your life.’  Maslow might have accompanied that quote with a wagging finger and the words, ‘you really need to sort yourself out’.  I had these words rattling around my head for next two days.

Workshop: Learning design for accessibility

The first workshop of the day was facilitated by Lisette Toetenel and Annie Bryan from the OU’s Institute of Educational Technology.  The focus of the event was a learning design tool that IET had created to help module teams consider different pedagogic approaches.  It has been embedded into the module design process, which means that module chairs have to signify that they’ve engaged with IET’s learning design framework.  Through my involvement with a new module, I had heard a little about it, but I didn’t know the detail.

Learning design was defined as, ‘the practice of planning, sequencing and managing learning activities’, usually using ICT tools to support both design and delivery.  An important point was that both accessibility and important areas such as employability skills need to be considered from the outset (or be ‘woven into’ a design) and certainly not ‘bolted on’ as an after-thought.

The learning design framework is embedded into a tool, which takes the form of a template that either module members or a module chair has to complete.  Its objective is to improve quality, sharing of good practice, speed up decision making process, and manage (and plan) student workload.  The tool has an accompanying Learning Design website  (but you might have to be a member of the university to view this).

During the workshop we were divided up into different tables and asked to read through a scenario.  Our table was given an ‘environmental sciences’ scenario.  We were asked three questions: ‘what exactly do students do [in the scenario], and how do (or might) they spend their time?’ and what accessibility problems they might be confronted with.

The point was clear: it’s important to consider potential barriers to learning as early and as soon as you can.

Keynote: SpLDs – The Elephant in the Counselling Room: recognising dyspraxia in adults

The final keynote of the conference was given by Maxine Roper (personal website).  Maxine describes herself as freelance journalist and writer, and a member of the dyspraxia foundation.

One of the main themes of her keynote was the relationship between dyspraxia and mental health.  Now, I’ll be the first to say that I don’t know very much about dyspraxia.  Here’s what I’ve found on the Dyspraxia Foundation website: ‘Dyspraxia, a form of developmental coordination disorder (DCD) is a common disorder affecting fine and/or gross motor coordination, in children and adults. … dyspraxia [can also refer] to those people who have additional problems planning, organising and carrying out movements in the right order in everyday situations.’

I was struck by how honest and personal Maxine’s talk was.  Dyspraxis is, of course, a hidden disability.  Maxine said that dyspraxics are good at hiding their difficulities and their differences, and spoke at length about the psychological impact.  An interesting statistic is that ‘a dyspraxic child is 4 times more likely to develop significant psychological problems by the age of 16’ (from the Dyspraxia Foundation).

Some of the effects can include seeing other people more capable, being ‘over givers’ with a view to maintaining friendships, but other people might go the other way and become unnecessarily aggressive (as a strategy to covering up ‘difference’).  Sometimes people may get reactive depression in response to the continual challenge of coping.

I found Maxine’s description of the psychological impact of having a hidden disability fascinating – it is a subject that I could very easily relate to because I also have a hidden disability (and one that I have also tried a long time to hide).  This made me ask myself an obvious question that might well have an obvious answer, which was ‘are these thoughts, and the psychological impact common across other types of hidden disabilities?’ 

So, what might the solutions be?  Maxine offered a number of answers: one solution could be to raise awareness.  This would mean awareness amongst students, and amongst student councillors and those who offer support and guidance.

I noted down another sentence that was really interesting and important, and this was the point about coping strategies.  People develop coping strategies to get by, but these coping strategies might not necessarily be the most appropriate or best approach to adopt.  In some cases it might necessary to unpick layers of accumulated strategies to move forward, and doing this has the potential to be really tough.

Maxine’s presentation contained a lot of points, and one of the key one for me (the elephant in the room), was that it’s important to always deal with the person as a whole, and that perhaps there might be (sometimes) other reasons why students might be struggling.

Workshop : Through new eyes – understanding the experience of blind and partially sighted learners

The final workshop of the conference was given by my colleague Richard Walker, who works as an associate lecturer for the Maths Computing and Technology Faculty.  Like Maxine’s keynote, Richard’s spoke from his own experience, and I found his story and descriptions compelling and insightful.

Richard told us that he had worked with a number of blind and partially sighted students over the years.  He challenged us with an interesting statistic: if we consider the number of people in the general population who have visual impairments, and if an associate lecturer tutors a subject for around ten or so years, this means there is a 90% chance that a tutor will encounter a student who has a visual impairment.  The message is clear: we need to be thinking about how to support our students, which also means how we need to support our associate lecturers too.

Richard has had a stroke which has affected his vision.  Overnight, he became a partially sighted tutor.  ‘This changed how I saw the world’, he said. 

One of his comments has clearly stuck in my mind.  Richard said that when he was in hospital he immediately wanted to get back to work.  Richard later started a blog to document and share his experiences, and I’ve also made a note of him saying that he ‘couldn’t wait to start my new career’, and ‘when I got home from hospital I wanted to download some software so I can continue to be an Open University tutor’.

Richard spoke about the human visual system, which was fascinating stuff, where he talked about the working of the eye and our peripheral vision.  He presented simulations of different visual impairments though a series of carefully drawn PowerPoint slides.    On the subject of PowerPoint, he also spoke briefly about how to make PowerPoint accessible.  His tips were: keep bullet points very short, choose background and foreground colours that have a good contrast, and ensure that you have figure descriptions.

I was struck by Richard’s can-do attitude (and I’m sure others were too).  He said, ‘the whole world looks a bit different, and I like learning new stuff, so I learnt it’.  An implication of becoming partially sighted was that this affected his ability it read.  It was a skill that had to be re-learnt or re-discovered, which sounds like a pretty significant feat.  ‘I just kept looking at the lines, and I’ve learnt to read again.  You just experiment [with how to move your eyes] and you see what works’.

When faced the change in his vision, he contacted his staff tutor for advice, and some accommodations were put in place.  Another point that stood out for me was the importance of trust; his line manager clearly trusted Richard’s judgement about what he could and could not do.

Sharing experience

Richard tutors on a module called M250 Object-oriented programming (OU website).  When student study M250 they write small programs using a software development environment.    Richard made the observation that some software development environments can be ‘hostile to assistive technology’, such as screen readers.

Richard is currently tutoring a student who has a visual impairment.  To learn more about the student’s experience, he interviewed the student by email – this led to creation of a ‘script’.  With help from a workshop delegate, Richard re-enacted his interview, where he asked about challenges, assistive technologies, study strategies and what could be done to improve things. We learnt about the use of Daisy talking books (Wikipedia), the fact that everything takes longer, about strategies for interactive with computers, and the design of ‘dead tree’ books that could be read using a scanner.  After the performance, we were set an activity to share views about what we learnt from the interview (if I remember correctly).

Towards the end of the workshop, Richard facilitated a short discussion about new forms of assistive technologies and ubiquitous computing, and how devices such as Google Glass might be useful; thought provoking stuff.

I enjoyed Richard’s session; it was delivered with an infectious enthusiasm and a personal perspective.  The final words that I’ve noted down in my notebook are: ‘it’s not because I’ve got a strength of character, it’s because I love my work … you just have got to get on with it’

Reflections

Like all the others, this year’s disabled student services conference was both useful and enjoyable.  These events represent an invaluable opportunity to learn new things, to network with colleagues, and to take time out from the day job to reflect on the challenges that learner’s face (and what we might be able to do to make things easier).

For me, there were a couple of highlights.  The first was Keith’s understated but utterly engaging keynote.  The second was Richard Walkers workshop: I had never seen Richard ‘in action’ before, and he did a great job of facilitation.  In terms of learning, I learnt a lot from Maxine’s talk, and it was really interesting to reflect upon the emotional and psychological impact that a hidden disability can have on someone.  I feel it’s an issue that is easily overlooked, and is something that I’ll continue to mull over.  In some respects, it has emphasised, to me, how demanding and important the role of learning support advisors role is to the university.

One question that I have asked myself is: ‘what else could be done within the conference?’  This, I think, is a pretty difficult question to ask, since everything was organised very well, and the whole event was very well attended.

One thought is about drama.  Richard’s session contained a hint of drama, where he used a fellow delegate to read a script of his email interview.  I’ve attended a number of excellent sessions in the East Grinstead region (which is now, sadly, going to be closed) that made use of ‘forum theatre’.  Perhaps this is an approach that could be used to allow us to expose issues and question our own understandings of the needs of our students.  Much food for thought.

Permalink 1 comment (latest comment by Jonathan Vernon, Wednesday, 28 May 2014, 14:13)
Share post
Christopher Douce

Disabled student services conference 2014 – day 1

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 22 Jan 2019, 09:40

I recently attended the university’s disabled student services conference held between 13 and 14 May 2014.  I think this was the third time I’ve been to this event, and every time I go I always learn something new.

This is a quick blog summary of the sessions I attended.  I guess this summary serves a number of purposes.  Firstly, it’s a summary of some of the continuing professional development I’ve been getting up to this year.  Secondly, it might be of interest to any of my students who might be studying H810 accessible e-learning (OU website).  Thirdly, it might be useful to some of my colleagues, or for anyone who accidentally stumbles across this series of two posts.

The complexities of co-occurrence

The first session of the day was presented by my colleague Jonathan Jewell, who works as an associate lecturer for a least three different faculties.  My first thought was, ‘what is meant by co-occurrence?’ - it wasn’t a term I had heard before.  I quickly figured out that it means that a person can have a number of different conditions at the same time.  A big part of his session was about what this might mean in terms of understanding a profile that contains quite a lot of information.

During Jonathan’s session I remember a debate about the terms ‘student-centred’ and ‘person-centred’.  The point was that although a student might be studying a particular module, they are on a programme, and this can, of course relate to a broader set of personal objectives that they might hold.

Every student who discloses a disability may have their own disability profile. The aim of the profile is tell a tutor something about their students to help them to understand what adjustments (in terms of their tuition) they could make.

During Jonathan’s session we looked at a sample profile and thought about it in terms of its strengths and weaknesses.  Our group concluded that the profile we were given contained a lot of information.  A particular weakness was that it contained a lot of quite technical jargon that was quite hard to understand.  A later task was to devise a ‘tutor plan of action’ based on the profile.  A clear point that was mentioned was the importance of establishing early contact with students to ensure that they feel comfortable and supported.

Towards the end of the session, I remember a debate that student profiles can change; some disabilities are temporary.  I also understand that there are now clearer university guidelines about how profiles should be written; a profile written today might be different to how it was written a couple of years ago.

Keynote: REAL services to assist students who identify with Asperger syndrome (AS)

The first keynote of the day was by Nichola Martin who I understand works for the University of Cambridge.  The ‘REAL’ bit of her presentation title is an abbreviation for: reliable, empathic, anticipatory and logical – this idea is that we should be these attributes when we work with people who identify with having Asperger syndrome (AS).  Very early on during her presentation she made the key point that ‘if you’ve met one person with AS, you’ve only met one person with AS’. 

Nichola also exposed us to stereotypes from the media, which she asked us to question.  The use of language is fundamentally important too, i.e. the term ‘condition’ is better than ‘disorder’ which suggests that something is fundamentally wrong.  Another interesting point is that the characteristics of people can change over time, a point that neatly connects back to the previous session about the changing nature of student profiles.

A big part of Nichola’s presentation was to share some findings from a research project that studied the views of students.  Its aim was to develop a model of best practice for student with AS, improve access to diagnosis, raise awareness and develop networks.

One really important point is about the importance of clear language; always be clear in what you either say or write.  An important point that I have noted is that if we make accommodations for one group, this is likely to help all students.  Stating clear assumptions in a clear and respectful way is, of course, useful for everyone. 

Another point is that institutions can be difficult to negotiate, particularly during the early stage of study.  If things are chaotic at the beginning of university study, it might be difficult to get back onto an even keel.  Some challenges that students might face can include finding their way through new social environments.  I’ve noted down a quote which goes, ‘my main barriers have been social and I find large groups of people I don’t know intimidating – as a result, I rarely attend lectures and often feel alone’.

There were some really interesting points about disability and identity which deserve further reflection.  Some students choose not to disclose and don’t go anywhere near the disability services part of the university.  Students may not want ‘special services’, since this hints at the notion of ‘othering’, or the emphasis of difference.  If people don’t want to talk about their personal circumstances, that is entirely their right.

We were told that Asperger’s and autism are terms that are used interchangeably, and this is reflected in the most recent publication of the DSM (Wikipedia, Diagnostic and Statistical Manual of Mental Disorders).

There were a number of things that were new to me, such as The Autism Act 2009 (National Autistic Society), and The Autism Strategy 2010 (National Autistic Society), which has been recently updated.  Another interesting and useful link is a video interview produced by the National Autistic Society (YouTube).   It was also great to hear that Nichola also mentioned OU module SK124 understanding the autism spectrum (OU website). 

All in all, a thought provoking talk.

Workshop: Student Support Teams and Disabled Students Support

The next event I went to was a workshop where different members of the newly formed student support teams (SSTs) were brought together to discuss the challenges of supporting students who have disabilities.  Again, the subject of student profiles was also discussed.

My own perspective (regarding student support teams) is one that has been really positive.  Whenever I’ve come across an issue when I needed to help a student (or a tutor) with a particular problem, I’ve always been able to speak with a learning support advisor who have always been unstintingly helpful.  I personally feel that now there are more people who I can speak to regarding advice and guidance.

Keynote: The life of a mouth artist

The final keynote of the day was a really enjoyable and insightful talk by artist, Keith Jansz.  Keith began by telling us about his background.  After being involved in a car accident, in which he was significantly paralysed, he started to learn how to draw and paint after being given a book about mouth artists by his mother in law. 

Keith spoke how he learnt how to paint, describing the process that he went through.  Being someone who has a low opinion of my own abilities when it comes to using a pencil, I found his story fascinating.  I enjoyed Keith’s descriptions of light, colour, and the creative process. What struck me were the links between creativity, learning and self-expression; all dimensions that are inextricably intertwined. 

I thought his talk was a perfect keynote for this conference.   It was only afterwards that the implicit connections between Keith’s talk and the connections with university study became apparent. Learning, whatever form it may take, can be both life changing and life affirming.

During the conference, there was an accompanying exhibition of Keith’s work.  You can also view a number of his paintings on his website.

Permalink Add your comment
Share post
Christopher Douce

Ten Forum Tips

Visible to anyone in the world

I spend quite a lot of time using on-line discussion forums that are used as a part of a number of Open University modules I have a connection with.  I also wear a number of different ‘hats’; as well as being an Open University tutor, I also spend time visiting forums that are run by other Open University tutors in my role as a staff tutor.

A couple of years ago, I was sent a copy of a book called e-moderating (book website) by Gilly Salmon, who used to work at the Open University business school.  The e-moderating book is really useful in situations where the discussion forums constitute a very central part of the teaching and learning experience.  Salmon offers a raft of useful tips and offers us a helpful five stage model (which can be used to understand the different types of interaction and activities that can take place within a forum).

Different modules use discussion forums in different ways.  In some modules, such as H810 Accessible on-line learning they are absolutely central to the module experience.  In other modules, say, M364 Interaction Design, they tend to adopt more of a ‘supporting’ rather than a ‘knowledge creation’ role.

Just before breaking for Christmas and the New Year, I started (quite randomly) to write a list of what I thought would be my own ‘killer tips’ to help tutors with forums.  This is what I’ve come up with so far.

1. Be overly polite

One phrase that I really like is ‘emotional bandwidth’.  In a discussion forum, we’re usually dealing with raw text (although we can pepper our posts with emoticons and pictures). 

This means that we have quite a ‘narrow’ or ‘low’ emotional bandwidth; our words and phrases can be very easily misunderstood and misinterpreted by others, especially in situations when we’re asking questions with the objective of trying to learn some new concept or idea.  Since our words are always ambiguous, it’s important to be overly polite.   

Be more polite than you would be in real life!

2. Acknowledge every introduction

The start of a module is really important.  The first days or weeks represent our chance to ‘set the tone’.  If we set the right tone, it’s possible to create momentum, to allow our discussion forums to attract interaction and conversation.

A good idea at the start of a module is to begin an ‘introduction’ thread.  Start this thread by posting your own introduction: set an example.  When other introductions are posted, take the time to send a reply to (or acknowledge) each one.

3. Use pins

Some discussion forums have a feature that allows you to ‘pin’ a discussion thread to the top of a forum. 

The act of ‘pinning’ a thread highlights it as something that is important.  Pins can be really useful to highlight discussions that are current or important (such as an activity that needs to be completed to prepare for an assignment, for example).  Subsequently, it’s important not to pin everything.  If you do, students will be unclear about what is important and what is not and this risk hiding important discussions. 

Use ‘pinned threads’ in a judicious way and regularly change what threads are pinned (as a module progresses) – this suggests that a forum is alive and active.

4. Tell your students to subscribe

There are a couple of ways to check the OU discussion forums.  One way is to login regularly and see whether anyone has made any new posts.  Another way is to receive email updates, either from individual threads or from whole discussion forums.  At the start of a module presentation, it’s a good idea to tell your student group to subscribe to all the forums that are used within a module.  One way to do this is by sending a group email.  When a student has subscribed they are sent an email whenever anyone makes a post or sends a reply (the email also contains a copy of the message that was posted).

One of the really good things about using emails to keep track of forums is that it’s possible to set up ‘rules’ on an email client.  For example, whenever a forum related email is received, it might be possible to transfer it to a folder based on the module code that is contained within the message subject.  This way, you can keep on top of things without overloading your inbox.

5. Encourage and confirm

Busy forums are likely to be the best forums.  One approach to try to create a busy forum is to do your best to offer continual encouragement; acknowledge a good post and emphasise key points that have been raised.  (Salmon writes about weaving together and summarising a number of different discussions). 

Another really great thing to do is to seek further confirmation or clarifications.  You might respond to a message by writing something like, ‘does this answer your question?’  This keeps a discussion alive and offers participants an opportunity to present alternative or different perspectives.

6. Push information about TMAs

Tutor marked assignments (TMAs) are really important.  As soon as a TMA is submitted, students will generally expect them back within 10 working days (which is the university guideline).  Sometimes TMAs are returned earlier, and in some situations (with permission from the staff tutor), it can take a bit longer.  A forum can be used to provide ‘push’ updates to students about how marking is progressing.  Once a TMA cut-off date has been met, a tutor could start a forum thread entitled, ‘TMA x marking update’. 

When you’re approximately half way through the marking, one idea is to make a post to this thread telling them.  Also, if your students have subscribed, they’ll automatically receive the updates.  This reduces pre-TMA result anxiety (for the students), since everyone is kept in the loop about what is happening.  (The thread can also be used to post some general feedback, if this is something that is recommended by the module team).

7. Advertise tutorials

Open University tutorials can be either face to face (at a study centre, which might be at a local university or college), or can take place on line through a system called OU Live.  A post to a discussion forum can be used to remind students about tutorials.   They can also be used to offer some guidance to students to help them to prepare for the session.  You could also ask whether students (in your group) have any particular subjects or topics that they would like to be discussed or explored.

After the tutorial, a forum can be used to share handouts that were used during either an on-line session or a day school.  It also offers students an opportunity to have a discussion about any issues that (perhaps) were not fully understood.  Also, during a tutorial, a tutor might set up or suggest a long running research task.

There are a number of advantages of connecting tutorials to forum discussions.  Those people who could not attend can benefit from any resources that were used during an event.  It also allows a wider set of opinions and views to be elicited from a greater number of students.

8. Provide links

A subject or topic doesn’t begin and end with the module materials.  During the presentation of a module, you might inadvertently see a TV programme that addresses some of the themes that are connected to a particular topic of study.  A forum is a great way to contextualise a module by connecting it to current stories in the media and one way you can do this is by either posting links to a news story (or series of stories), or perhaps by starting a discussion.

As well as sharing news stories, you can also use discussion forums to alert students to some of the study skills resources that have been developed by the Open University.  There are also some library resources that might be useful too.  Other resources might include OpenLearn resources, for example.  A forum is a great way to direct students to a wide array of useful and helpful materials.  You might also want to ask other tutors (using the tutors’ forum) about whether any other tutors have suggestions or ideas.

9. Visit other forums

Every tutor does things slightly different; no tutor is exactly the same, and this is a good thing.  If you tutor on a module, there’s a possibility that you might be able to view another tutor’s discussion forum.  If you have the time, do visit another tutor’s forum.  Some good questions to ask are: ‘at a glance, do the students look engaged?’ or ‘how busy is this forum?’  Other questions might be, ‘what exactly is the tutor doing?’ and ‘ how are they asking questions?’  This allows you to get a view on how well a forum is being run.  When you see a busy and well run forum, ask the question: ‘is the tutor doing something special here?’  If so, what is it?  Sometimes, of course, certain cohorts can just be pretty quiet; some years are more busy than others.

After visiting a forum, the best questions to ask are, ‘what have I learnt?’ and ‘is there anything that I could or should be doing with my forum?’

10. Form forum habits

The more that you’re active on a forum, the more useful a forum can become for students.  Find some time, every day, or every couple of days, to read through and respond to forum posts.  This will keep your forums fresh and alive; they may even acquire a ‘stickiness’ of their own and become pages that students are drawn to time and time again.

Summary

This quick blog post summarises a number of ‘forum tips’ that I’ve discovered over the last couple of years of working with different modules.  Some of these ideas have, of course, been shaped by the e-moderating book that I have mentioned earlier.  E-moderating is a book that is useful for some modules and not others since different modules use forums in slightly different ways.  Although a module team might use a forum in a particular way, it is always going to be up to you, a tutor, to take ownership of this important learning space.

Finally, if you would like to add to these tips (or even disagree with them), please don’t hesitate to let me know!

Permalink 1 comment (latest comment by Ravina Talbot, Sunday, 3 Feb 2019, 15:44)
Share post
Christopher Douce

eSTEeM Conference – Milton Keynes, May 2014

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 20 May 2014, 09:50

On 5 May 2014, I was at Milton Keynes again.  I had something called a module team meeting in the morning.  In the afternoon I attended an OU funded conference that had the title (or abbreviation) eSTEeM (project website).

eSTEeM is an initiative to conduct research into STEM education.  STEM is an abbreviation for Science Technology Engineering and Mathematics.  Since I have some connections with some computing modules, which can cross the subjects of Engineering and Mathematics, I decided to submit a proposal that had the objective of learning more about the tutor’s experience of teaching computer programming.  The aim was simple: if we learn more about the tutor’s challenges, we can support them better, and subsequently they will be able to support the students better too.

I have been lucky enough to receive a small amount of funding from the university.  This, of course, is great news, but it also means that I’ve got even more work to do!  (But I’m not complaining - I accept that it’s all self-inflicted, and it’s work that will allow us to get at some insights).  If you’re interested, here’s some further information about the project (eSTEeM website).

A 'pilot' project

The ‘understanding the tutors and the students when they do programming’ project is a qualitative study.  In this case, it means that I’ll be analysing a number of interviews with tutors.  I’ll be the first to admit that it’s been quite a while since I have done any qualitative research, so I felt that I needed to refamiliarise myself with what I needed to do by, perhaps, running a pilot study.

It wasn’t long before I had an idea that could become a substantive piece of research in its own right. I realised that there was an opportunity to run a ‘focus group’ to ask tutors about their experience of tutoring on another module: T320 Ebusiness Technologies (OU website).  The idea was that the outcome from this study could feed directly into discussions about a new module.

During my slot at the conference, rather than talking about my research about programming (which was still at the planning stage), I talked about T320 research, that was just about finished.  I say finished, when what I actually mean is ‘transcribed’; there is a lot more analysis to do.  What has struck me was how generous tutors are with both their opinions and their time.  Their views will really help when it comes to designing and planning the future module that I have a connection.

Final thoughts and links

In case you’re interested, here’s a link to the conference programme.

What struck me was how much ‘internal research’ was there was going on; there are certainly a lot of projects to look through.  From my perspective, I’m certainly looking forward to making a contribution to the next conference and sharing results from the web technologies and programming research project with colleagues.   The other great thing about getting my head into research again is that when you have one idea about what to look at, you suddenly find that get a whole bunch of other ideas.

Permalink Add your comment
Share post
Christopher Douce

Widening Participation through Curriculum Conference (day 2 of 2)

Visible to anyone in the world
Edited by Christopher Douce, Wednesday, 24 Apr 2019, 17:29

The second day of the conference was to be slightly different to the first; there were fewer sessions, and there were a number of ‘talking circle’ workshop events to go to.  On the first day I arrived at the conference ridiculously early (I was used to the habit of travelling to Milton Keynes in time for meetings, and catching a scheduled bus to the campus).   On the second day, I was glad to discover that I wasn’t the first delegate to arrive.

Opening remarks

The second day was opened by Professor Musa Mihsein from the OU.  He presented an interesting story of how he became to work at the university as a PVC.  Musa talked about changes to funding, making the point that there has also been a change in the use of language.  There is more of a need to ‘maximise impact’.  The accompanying question is, of course, ‘how can we best evaluate projects and programs?’

A couple of points I noted down was that we haven’t got a full understanding of curriculum and its role within the institution, and that collaborations are important.  There is also a continual need to communicate in different ways to policy makers.

Keynote 4: Liberating the curriculum

The first keynote of the day was by Kelly Coate, Senior Lecturer in Higher Education, from Kings College, London.  Kelly’s talk was interesting since it spoke directly to the ‘curriculum’ part of conference title.  She has been researching about curriculum for the last 20 years and made the point that, ‘decisions about curriculum are decisions about what we can think’ (if I’ve taken that down correctly).

Here’s some of my notes: we’re accustomed to certain view of what ‘curriculum’.  The word derives from a Latin word that means to run/to proceed.  This makes a lot of sense: most participants make it to the finish line, there are often a couple of really high scorers and a couple who are, perhaps, left behind. 

If we dig around in history, the notion of curriculum used to be associated with the ‘liberal arts’.  This contains the disciplines of grammar, logic, rhetoric, music theory, astronomy, arithmetic, and geometry, with the word liberal being derived from libra, meaning ‘free’.

Kelly’s talk gave way an interesting twist.  Since she studies what people are studying, she was asked to comment on a story that Miley Cyrus was to be the subject of a university course.  If you’re interested, here’s a related news story: Back to twerk … Miley Cyrus to be studied on new university course (The Guardian).   Thinking about it for a moment, the subject of Miley can readily be used to facilitate discussions about femininity, power, exploitation, celebrity,sexuality…

A bit of theorising is always useful.  We could thing about curriculum in three different domains: knowing, acting and being. Importance of relating teaching to the now, which opens up the possibility of students considering suggesting their own curricula by performing research into how ‘the now’ relates to the broad subject area.

Another way of thinking about curriculum might be in terms of gravity and density.  Gravity is the extent to which a subject can be related to a particular context.  Density relates to how much theory there is (some subject can be incredibly theoretical).  I really like these metaphors: they’re a really good (and powerful) way to think about how a lecturer or teacher might be able to ‘ground’ a particular concept or idea.

We were briefly taken through a couple of ideas about learning and pedagogy.  The first one was the transmission model (which, I think, was described as being thoroughly discredited), where a lecturer or teacher stands in the front of the class and talks, and the students magically absorb everything. The second idea (which I really need to take some time out to look at) is actor-network theory (wikipedia).  Apparently it’s about thinking about systems and networks and how things are linked through objects and connections.  (This is all transcribed directly from my notes - I need to understand in a whole lot more than I do at the moment!)

I’ve also made a note about a researcher called Jan Nespor  who has applied actor-network theory to study physics and business studies classes.  The example was that lecturers can orchestrate totally different experiences, and these might be connected with the demands and needs of a particular discipline (if I’ve understood things correctly!)

I’ve made a note of some interesting points that were made by the delegates at the end of Kelly’s speech.  One point was that different subjects have different cultures of learning, i.e. some subjects might consider professional knowledge to be very important.  Musa mentioned the importance of problem-based learning, particularly in subjects such as engineering. 

Session 3: Innovation in design and pedagogy

There was only one presentation in the third session which was all about pedagogy.  This was entitled ‘Creating inclusive university curriculum: implementing universal design for learning in an enabling programme’, by Stuart Dinmore and Jennifer Stokes.  The presentation was all about how to make use of universal design principles within a module.  We were introduced to what UD is (that it emerges from developments in design and architecture), that it aims to create artefacts that are useful for everyone, regardless of disability.

Connecting their presentation to wider issues, there are two competing (yet complementary) accessibility approaches: individualised design and universal design.  There is also the way in which accessibility can be facilitated by the use of helpers, to enable learners to gain access to materials and learning experiences.

It was great that this presentation explicitly spoke to the accessibility and disability dimension of WP, also connecting to the importance of technology.  During Stuart and Jennifer’s presentation, I was continually trying to relate their experiences with my own experience of tutoring on the OU module, H810 Accessible online learning: supporting disabled students (OU web page)

Talking circle

I chose to attend innovation in design and pedagogy.  I do admit that I did get a bit ‘ranty’ (in a gentle way) during this session.  This was a good opportunity to chat about some of the issues that were raised and to properly meet some of the fellow delegates.  Some of the views that I expressed within this session are featured in the reflection section that follows.

Closing keynote:  class, culture and access to higher education

The closing keynote was by John Storan from the University of East London.  John’s keynote was a welcome difference; it had a richly personal tone.  He introduced us to members of his family (who were projected onto a screen using PowerPoint), and talked us through the early years of his life, and his journey into teacher training college, whilst constantly reflecting on notions of difference.

He also spoke about a really interesting OU connection too.  John was a participant in a study that gave way to a book entitled, Family and kinship in East London (Wikipedia), by Michael Yong and Peter Willmott.  (This is one of those interesting looking books that I’m definitely going to be reading – again, further homework from this conference).  ‘We were the subject’, John told us.  He also went onto make the point about the connections between lived experience, research, policy and curriculum.

I’ve made a note in my notebook of the phrase, ‘not clever, able enough’.  I have also been subject to what I now know to be ‘imposter syndrome’.  In the question and answer session, I’ve made a note about that the codes of language can easily become barriers.

Reflections

One of the really unexpected things about this conference was the way that it accidentally encouraged me to think about my own journey to and through higher education.  Although for much of my early life I didn’t live in an area that would feature highly in any WP initiatives, higher education was an unfamiliar world to my immediate family.

Of course, my journey and my choices end up being quite nuanced when I start to pick apart the details of my biography, but I think there was one intervention that made a lasting impression.  This intervention was a single speech given by a member of staff at my former college about the opportunity that university study gave.  I remember coming away thinking, ‘I’m going to apply; I have nothing to lose, and everything to gain’.  A number of my peers thought the same.

The conference presented a number of different perspectives: the importance of assessing the effectiveness of interventions and the importance of theory, how to design WP curriculum, how to make curriculum accessible, and how to make materials engaging for different groups.  One aspect that I thought was lacking was that of the voices of the students.  It’s all very well discussing between ourselves what we think that we should be doing, but I felt it would be really valuable to hear the views of students. 

An area that would be particularly useful is to hear about instances of failure, or to hear about what went wrong when students tried university level study but couldn’t complete for some reason.  There are some really rich narratives that have the potential to tell researchers in WP and curriculum a lot about what institutions (and individuals) need to do.  The challenge, of course, is finding those people who would like to come forward and share their views.

In the sessions that I attended, there were clear discussions about class, socio-economic status and disability, but there seemed to be an opportunity to discuss more about ethnicity.  Quantitative research has shown that there is an attainment gap.   There was an opportunity for some qualitative discussions and more sharing of views regarding this subject.

Another thought relates to the number of keynote speeches.  Keynote speeches are really important, and it was great that they were varied – and they are very important in tone and agenda setting, but more paper sessions (and perhaps a plenary discussion?) might expose different issues and allow more contacts to be made.

I appreciate that these final reflections sound a bit ‘whingey’; they’re not intended to be.  WP is an important issue, and from the amount of follow-up homework I’ve got to do this clearly tells me that the conference was a great success. 

In some ways I guess the conference was slightly different to what I had expected (in terms of the debate and discussions).  I was expecting it to be slightly less ‘academic’ and slightly more practitioner focussed (or oriented to those who deal with WP issues on a day to day basis).   The unexpected difference, however, was very welcome; I’ve learnt some new stuff.

Permalink Add your comment
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: 2264687