OU blog

Personal Blogs

Christopher Douce

eSTEeM annual conference: TEL in practice

Visible to anyone in the world

On 16 April, I went to the first day of the Open University’s eSTEeM conference.  eSTEeM is an Open University initiative to bring ‘together academics in Science, Technology, Engineering and Mathematics (STEM) to promote innovation, scholarship and enterprise in open and distance learning’.  The eSTEeM website offers loads of information about the different projects that are funded through the initiative. Before trying to summarise my ‘take’ on the whole event, I should also add that TEL (which is in the title of the event) is an abbreviation for Technology Enhanced Learning.

Opening keynote

Due to travel timing, I missed the opening address, but I managed to get to the opening keynote, which had the title ‘Using technology in teaching and learning: it is scholarly?’ by Linda Price from the Institute of Educational Technology. My immediate instinct to this question was to say ‘yes’, but the point to Linda’s talk was to encourage us all to think about what scholarship means when it comes to TEL.

An interesting point was that educators and institutions used to be the gatekeepers of knowledge, but technology has enabled some information (and knowledge) to become open.  Two examples of this is with the availability of Open Educational Resources (or OERs), and the increase in the number of open access journals.

Linda’s talk offered us a useful caution, that ‘technology will never save us from poor teaching, it will make things worse’.   Another point was about the importance of learner motivation, and that if technology is not properly integrated into a module then there’s a likelihood that it isn’t to be used (or, used poorly).

Another thought is that technology might not be the problem, but pedagogy might be.  Or, in other words, we need to develop our understanding about how best to use new.  Three important questions are: How do we make choices (of what technology to use)?  What evidence is there? Are we looking at opinion based practice or evidence informed practice?

Connecting to the ‘scholarly’ part of her title, we were told about a number of scholarly principles.  These were: the importance of goals, preparation, methods, results, presentation and critique.  These can also be connected with different scholarly approaches, such as the need to thoroughly analyse a problem, understand the context, review the literature, setting aims and objectives, designing of teaching and learning interventions, evaluation methods, and sharing of findings.

A final point that I have made a note of was that we need to think about how theory can relate to and drive our research.  This left me with a question: which theories are important and relevant?  This, of course, connects back to the importance of being aware of current debates, issues and, of course, the literature that relates to a particular area of research.

Workshop: what do you mean by tuition?

The university is introducing something called the Group Tuition Policy which is to affect both on-line and face to face tuition.  The aim of this workshop (which was one of many different events I could have chosen) was to facilitate discussions about how we might begin to plan and implement the policy (which is something that I’ll have to do as a part of my day job).

The workshop was split into two different activities and related to two different perspectives.  The first was to discuss what is meant by the term tuition, from the tutor’s perspective.  The second activity was all about what students should expect from tuition.  For this second activity we were encouraged to draw a ‘rich picture’.

At the end of each section, we shared different perspectives.  Points that I noted down were, ‘we need to up our game when it comes to on-line [tuition]’, ‘you can’t describe on-line as tutorials’ (which was an interesting perspective), and that there is ‘no difference between watching a recording and being on-line (or, participating in an on-line tutorial)’.  It was obvious there were a number of interesting, slightly conflicting, views.

How students learn in Massive Open Online Courses

The third session that I went to was all about MOOCs, or Massive Open Online Courses.  Allison Littlejohn, from the Centre for Learning and Teaching (and the Institute of Educational Technology) began by asking everyone how many had taught or learnt through a MOOC.  A good number of members of the audience put up their hands.

Allison spoke about a topology of learning.  This included dimensions of formal/informal, intentional/unintentional and recognised/unacknowledged.  She then went onto mention a study at Duke University which analysed 75 different MOOCs in terms of whether they adhered to good instructional design.  If I remember correctly, the results were not very positive.

 A key research question that was asked was: how do students learn in MOOCs?  A related question is: do people who are highly motivated behave differently?  To answer his question, a researcher called Barry Zimmermann was mentioned (with regards to his work on self-directed learning), and three case studies.

The first case study was about a ‘connectivist MOOC’ called SRL-MOOC (Glasgow Caledonian University) (I’m not sure what connectivist in this context means – I think I’ve made a note of the term correctly!)

The second case study was an introduction to the data sciences, and was from the University of Washington.  It ran using the Coursera platform, and had forty thousand learners.  We were introduced to an instrument called SQLMQ which was used to analyse learner behaviour, and could connect with factors such as student motivation.  (There was a lot of detail here that didn’t make a note of since this was all new to me!)

After this second case study there was an opportunity to discuss a question: how would we create a MOOC that could help self-regulated learners?  This was an interesting question that led onto quite a bit of debate, about the business models of MOOCs, how you might engage learners that were not ‘self-regulated’, and worries about their terrible completion rates.

 Allison found something interesting about self-regulated learners.  Low self-regulated learners sometimes engaged with MOOCs with the objective of getting a certificate, whereas high self-regulated learners took a more strategic approach, choosing to carry out learning that relates to a job, role or task.  Simplistically put, some high regulated learners tended to dip in and out of a MOOC, gain what they need, and then move on.

I can relate this finding with my own experience.  I have signed up to three different MOOCs, but I haven’t finished any of them.  The first one was about the history of the internet.  I completed the assessment, but then became a bit grumpy about the comments that were coming back from my ‘peer’.  Plus, I was finding there was a bit more reading to do than I expected (so I dropped out!)  My reasons to take the two other MOOCs were all about ‘checking to see what other institutions were up to’, and finding out whether I was missing anything in my teaching.  I dropped out of the first interaction design MOOC when I realised that the content was solid, and offered me some reassurance that my teaching was ‘on target’ with the overall aims of the discipline.  I dropped out of the final MOOC when I realised that the course was pretty baffling and didn’t seem to be teaching the subject in a very satisfactory way.  This relates, in part, to Allison’s opening comment about the importance of effective learning design.

The third case study was a module about clinical trials, and was hosted in the Edx platform.  I didn’t take any notes of this third case study, since I was probably still thinking about the distinction between ‘high self-directed learners’ and ‘low self-directed learners’.

A final activity of the day was to think about some form of recommendations about either MOOC design, or learning design.  Our table chose, instead, to discuss other issues, including the role and importance of face to face tuition.

Short paper session

The next session contained three short ‘paper’ presentations. 

The first was by Clem Herman, and her presentation was entitled ‘putting gender on the agenda: why gender should be a threshold concept for STEM educators’.  Clem spoke about the university’s involvement with an initiative called Athena Swan (Equality Challenge Unit).  

Two of the key objectives of the initiative is to ‘address gender inequalities requires commitment and action from everyone, at all levels of the organisation’ and ‘to tackle the unequal representation of women in science requires changing cultures and attitudes across the organisation’.  To be recognised by the initiative, institutions have to go through an audit process, enabling the university to gain an understanding of the state of gender representation in individual departments. 

It was interesting (and alarming) to hear that the number of women enrolling in the first level undergraduate computing module has been dropping (in comparison to Maths and Statistics, which was reported as being okay). Postgraduate registrations, apparently, have always been low.

During the question and answer session, questions were asked about engagement with external organisations (which have similar objectives), and there was a discussion about unconscious bias and the ‘stereotype threat’.  I think what is means being aware of gender related expectations when it comes to subject specific performance.

The next presentation of the day was by ‘yours truly’.  I briefly spoke about a university funded project that has been carrying out some research into the tutor experiences of teaching on a second level computing module called TT284 Web Technologies (Open University).  I won’t go into the fine detail, but a description of the project is available on the eSTEeM website, with an accompanying project poster (PDF).

The final talk of the day was from Martin Reynolds, who gave a talk entitled, ‘Designing a learning system for postgraduate recruitment and retention based on systemic enquiry’ (I may or may not have made a proper note of his title).  During his talk I remembered him telling us something about a university LinkedIn ‘systems thinking’ alumni forum, where students are continuing to share knowledge and experience beyond the boundaries of the postgraduate modules that they have been studying.

Closing keynote

 The closing keynote, entitled ‘getting data into your eye: live in the field, life in the lab, and augmented reality’ was by Peter Scott, who was from The Open University Knowledge Media Institute (KMI). 

Peter talked us through a series of EU funded projects that KMI had been involved with; I recognised the name of some projects, but not all, such as WeSpot (EU project website), The Open Science Laboratory (Open University website) and Engaging Science (EU project website) which might have been mentioned into an associate lecturer development event that I went to at the University of Sussex.  Another project was called the Field Network System (Open University website), which was about creating a portable network infrastructure for scientific fieldwork.

A big part of Peter’s talk was about applications of something called ‘augmented reality’; a topic that is featured in a module that I tutor called M364 Fundamentals of Interaction Design (OU website).  Augmented reality is where digital technologies can add additional information to a digital scene.  An interesting point was made is that AR can become really useful if we use it in combination with people, which leads us to the term ‘socio-technical augmentation’.

An interesting example of this can be found in a project called TellMe (EU project), an abbreviation for Technology Enhanced Learning Living Lab for Manufacturing Environments.  We were shown a demo where a computer tool offered engineers visual guidance about how to assemble and work with components.   Another perspective is that you could potentially be guided by another engineer who is working at a distance.  During these demonstrations I thought about my own interests in teaching computer programming, and wondered about how these tools might be used in this somewhat different context.

Towards the end of his talk, we were shown a demonstration of a virtual volcano (that was spewing lava) that popped out of a text book.  We could only see the ‘virtual volcano’ is we viewed it through the screen of a smartphone, which hinted at the wide variety of different ways that technology can be used when it comes to teaching and learning.

Final thoughts

There was a lot going on during the day, and I felt that I missed out on quite a few things.  I like days like these, since they force you to sit down, listen and learn.  They are also opportunities to help you to understand what is going on, and to gather up gently clues as to how the teaching and learning of science and technology may be changing.  A connected challenge is to try to find the time to investigate what happened in the other sessions and continue to keep up with the various developments that you are introduced to.

During conference I became involved in a couple of conversations about research about introductory programming, and there was even some talk about organising what might become a mini conference.  The bulk of the talk was an objective for a couple of us (who were interested in similar topics) to try to get our heads together; to try to understand more about where the ‘state of the art’ was heading.  In some respects, this was an outcome that was as just as useful as learning about new projects.  The reason for this is that these new connections and discussions have given me a bit of much needed and welcome motivation.

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

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

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: 2273206