OU blog

Personal Blogs

Christopher Douce

A233 Journal - September 2023

Visible to anyone in the world
Edited by Christopher Douce, Sunday, 31 Mar 2024, 09:49

I’ve read four of the set texts over the summer: Hardy’s Far from the Madding Crowd (which maddened me a bit), Wharton’s The Custom of the Country (which I loved), Carter’s The Bloody Chamber (which I was a bit ambivalent about), and a collection of stories from Anderson (which I quite enjoyed).

9 September 2023

I’ve been reading Ali Smith’s Hotel World. I have three sections to go.

10 September 2023

I finished Smith’s Hotel World. Whilst I really liked the opening chapter, I found the stream of consciousness chapter annoying and difficult. Whilst it might have been thoroughly rewarding to write from the author’s perspective, it makes the reader really work, and I just didn’t have the patience. I know we’ll get into looking at this, but it felt indulgent. I have mixed feelings, but we’ll see what is said in the module materials.

Talking of module materials, I open the first book and start reading the introduction, and the first chapter about Hardy and characterisation. I really like how the introduction is written. I must start to have a look around the module website, and to find if there is any on demand printing service for the study guides.

I keep looking at buying another second hand e-reader; one that has a bigger screen, so I can read the block PDFs more easily whilst I’m travelling; whilst my current e-reader does the job, I’m getting older – bigger screens are better screens!

22 September 2023

I realised that there were some books that I didn’t have, and I might need to read, so I went on eBay to look for a few. I was particularly intrigued by the science fiction book that was on the reading list. I used to be a huge sci-fi fan when I was a teen.

Yesterday I started to book onto tutorials for the entire year, guessing what direction I would like to go in terms of the book club choices. Over the summer I really enjoyed the Wharton text, so I’m really looking forward to The Age of Innocence.

Another thing that has happened: I’ve exchanged messages with my tutor! I’m not sure, but I think I recognise her name from A230.

Next step: to pick up reading of the block materials, and to try to get printouts of the study guides. The only thing: I don’t have access to a printer at the moment!

Looking back over this blog: I wasn’t keen on Hotel World. I really liked the start, but it didn’t do it for me. I look forward to learning more about how the module guides us through the text.

23 September 2023

It’s back on the module block again, and a bit of directed reading from Far form the Madding Crowd. I’m stuck by how closely we have to do the close reading! I have one more chapter to go (I shall revisit those two that I have read) before getting to the chapter about Wharton.

27 September 2023

My new books have arrived! I’ve put them in a pile. I think I’m going the read the science fiction one first, and The God of Small things last, if I don’t get distracted.

Talking of being distracted, I have again been looking at large screen e-readers so I can put all of the texts (module materials, and the books) on a single device. I need to stop procrastinating and get on with some reading.

30 September 2023

I did a bit of reading of the block, skim reading the final chapter of the last Hardy chapter. I liked the section that discussed the serialisation. This was giving me another perspective on the text. I also liked the question about whether the text had any subplots. 

After doing a bit more reading in a local café (and then bailing out when a group of noisy cyclists came in), I started to go through the module website properly, ticking off all the resources I looked at. So far I have: read the welcome letter, read the letter from the lead cluster manager, module guide and the audio clip that can be found in the studying literature page. I also had a look through the two bits of the English Literature Toolkit: how to study English Literature, and how to write an English Literature essay.

One thing I learnt about was the time planner. When I was a social science OU student, my tutor ran exactly the same activity, which I found really helpful. Reflecting on this, I need to do an hour (or so) of study in the morning, after breakfast, before doing my day job, just so I can keep on top of everything. 

Two other sections look helpful: the ‘being critical’ section, and the ‘practising headings for notes’ which suggests a number of handy headings to keep in mind whilst you are reading a text. I also hadn’t heard of the study diamond approach, which is completely new to me. The headings being: effects, meaning, techniques and context. (I think I forgot to write about context, when it came to my A230 emTMA).

The section on essay writing was useful, which highlights the following keywords and phrases: analyse, assess, compare, contrast, describe, discuss, examine, explain, how far … ?, synthesise, and to what extent … ? I also remember the PEAL approach to writing essays: point, evidence, analysis and evaluation, and linking sentence back to the question. Another suggestion (in the materials) is to have a three part structure: an argument, an opposing argument, then a compromise solution.

Here's some tips about close reading: what is the passage doing?, how is it doing it?, for what reasons?, and how does the bit of text relate to the wider text?

I’ve also noticed that all the TMA questions are available. When I get home, I’m going to print them all out. I’ve noted that TMA 5 is an emTMA which accounts for 40% of the overall module score, with all the other TMAs accounting for 15%. There is a threshold of 30% on the final TMA. I’ve also noticed that we have to make some forum posts. One thing I must remember is that the assessment guide also says how the module materials can be referenced.

I had a look at the module forum, and they appear to be pretty busy (one thread has over 100 posts), so I don’t subscribe to them. I’ll subscribe to the tutor group forum when it opens.

The final bits: a very brief study of the week 1 reading guidance (noting what I need to return to), and a quick look at the careers page and the learning journal document; it looks so long! Last of all, after checking off all the bits of the block I had read, was to eyeball the OU subjects and qualifications website https://learn2.open.ac.uk/blocks/subjectlist/ which I have never seen before.

Now that I’ve got into the module website, and I’ve seen what some of the key resources are, I need to start to go through everything properly, and a bit more slowly.

Permalink Add your comment
Share post
Christopher Douce

Working with the SST

Visible to anyone in the world

On Friday 14 July 23, I spoke with colleagues who work within one of the OU’s student support teams (SSTs) with the intention of learning more about what the SST does. I also wanted to learn about what messages or words of advice they would like to share with tutors.

The aim of this post is to highlight some of the great work the SST does, and to share some practical advice to tutors. This post is intended to be one of a series of posts that aim to offer tutors some practical guidance.

Introducing the SST

Tutors are the academic face of the university. You represent the collective views of module teams, and help students to find their way through the materials they have prepared. Whilst you are expected to answer academic questions, you’re not expected to respond to questions that go beyond the boundaries of the module that you are helping to deliver.

In you are ever asked questions about the next module a student should study, what to do if a student find themselves struggling with changing personal circumstances, of have concerns about student fees, there is another group of colleagues who can help: members of the student support teams who work within what is called the Student Recruitment and Support Centres (SRSC).

It is helpful to think of us all members of an SST: tutors are a member, as are staff tutors and module team members. The SST colleagues located within the SRSC carry out a number of different roles: they may be educational advisors, senior advisors, or enrol students to modules. 

One of the roles and responsibilities of a tutor is to proactively refer students to the student support team if it looks like they need help.

At the time of writing, an article on TutorHome describes the SST as “provid[ing] specialist support such as module choice, transferring credit, regulations, disability and can make referrals for careers guidance.” It goes on to say that tutors “can refer students to the SST for detailed advice and guidance. Support teams may occasionally approach Associate Lecturers to undertake Individual Student Support Sessions (ISSSs) with students.  Referrals are made using the electronic Student Referral Form (eSRF).”

What does the SST do?

The SST provides non-academic support and information to students. The SST provides information about different modules, how study takes place, and what the various options might be for student fees. After a student has enrolled, the SST may help a student to think about how to approach their study, and even their study workload. 

The SST uses a model known as Information Advice and Guidance, or IAG, for short. IAG is a model that is applied across higher education, and in situations where learners need information and guidance about learning choices. 

Consider IAG to be a funnel, or an inverted pyramid. Students may begin by asking for information. In turn, they might have further questions about different curriculum choices, and may end up speaking with a senior advisor or an educational advisor who will be specialised in providing different types of advice and guidance.

Seventy percent of queries that the SST handles relates to study intentions. These can include changes to registered qualifications, or increasing or decreasing of study intensity, which refers to the number of modules a student might be studying at the same time. 

Other queries that the SST respond to might be about offering information about assessment and examinations, helping student to navigate university policies, and to offer guidance about reasonable adjustments for disabled students. Advisors will also help with study postponements and fee credits (after postponements), and signpost additional resources such as the student assistance fund.

SST roles

To learn more about how the SST works, it is useful to know a little more about roles of colleagues who work in a SRSC, and how these roles relate to the IAG model.

Advisors (I)

The main role of the advisors is to provide information. An advisor can be thought of as being “a bit like a GP; we need to know a bit about everything – there are specialists we can refer students to”. The advisor acts like the first stage of a filter, passing student queries onto other teams if more detailed responses are needed.

There are often a lot of queries close to, and after a TMA cut-off date. In many cases students are referred back to their tutor and sometimes queries as passed onto the faculty, which will find their way to the staff tutor. If students ask about TMA questions, these will, of course, be referred back to the tutor, and possibly the faculty.

In this first stage of the IAG model, advisors are not meant to offer advice, or guidance or discuss in depth issues that relate to student finance, but they can direct students to information that they may find helpful.

Senior advisors (A)

After the information (I) stage, an advisor might pass a query onto a senior advisor, for the advice (A) stage. It is always worth remembering that senior advisors can only provide advice about study. They can only make students aware of different options that are available to them, perhaps signposting them to different resources to help them to make decision. What they cannot do, of course, is to provide solutions or answers to students: they can only provide them with tools that help them to make decision.

Senior advisors can do a number of things: they can share information about what modules might potentially be useful to study, they might also help students to understand whether any there are any pre-requisites that need to be completed before students choose a particular path of study or module combination, and they can also say something about what is involved with OU study.

Senior advisors also make telephone calls to students if there are any concerns about their progress that may have been raised by tutors with an aim to find out if there is anything they might be able to help with. They often follow up with an email, if necessary, making records to the university student-relationship management system.

Educational Advisors (G)

Education advisors get involved with more complex issues. For example, if there are potential or persistent barriers to learning. If a barrier relates to a disability, they will work with other teams, such as the Disability Support Team. They may also refer students to specialist mental health advisors, or even to a safeguarding team.

It is worth noting that there are some differences in what happens in England, and what happens in the other UK nations. In England, the Disability Support Team works with students to write a support profile, which is available to tutors through TutorHome. They may also help students to begin to claim for the Disability Support Allowance (DSA), to help students to get their right support for their studies. In the other UK nations this support is provided by educational advisors.

Educational advisors may also gently challenge students if there is a sense that someone is taking on too much. They may also offer practical advice about how to catch up with their studies. They may also speak with students if they are finding it difficult to decide whether to continue with their study, and will offer advice about options. They can also help to manage student expectations in terms of the form and extent of support that they are likely to receive, either from tutors or, more broadly, from the university. In this sense, educational advisors can proactively help students to develop the academic relationship they have with their tutor.

The SST always aims to work in the best interests of the students. They are there to make sure students have the right information to enable them to make the right decision, that matches their needs and circumstances.

When should I refer students to the SST?

There is a simple rule: tutors respond to academic queries, and non-academic queries should be referred to the SST. An academic query can be thought of anything that relates to the study of a module. 

There are also grey areas between academic and non-academic support that tutors can proactively help with. For example, if a student is considering stopping studying of a module due to the difficulty of the module materials or the scores they are getting, a tutor should try to speak with a student to find out whether there is anything they can do to help. Sometimes an additional support session might be enough to get a student back on track. On other occasions, a discussion about their TMA feedback might help them to put their work and progress into perspective.

Tutors can also help if a student queries their marks, or asks for study advice within the context of a module. Whilst the SST is able to offer general advice about student, a tutor is best placed to offer detailed practical study advice about what a student might be able to do to maintain steady progress during a module. In a computing module, for example, this might be making sure a student is aware of the importance of getting better through practice. If you are asked some academic questions that you can’t immediately answer, consider seeking advice from the tutor’s module forum, or your staff tutor.

If a student is experiencing difficulties, and feel their personal circumstances may affect either their TMA or exam performance, tutors can and should refer students to the special circumstances form, which can be accessed through the university help centre.

You should refer a student to the SST if there is any non-academic problem that you cannot solve, or a student is asking questions that are not related to the academic elements of the module that you are teaching, or you are unable to get in contact with your student. The earlier you refer the student to the SST, the better.

You should also refer students to the SST if a student has disclosed a disability. The act of a student telling a tutor they have a disability means that they have told the university they have a disability, and tutors are obliged to pass this information on to the SST.

The SST will “usually try to respond within 2 working days, and then 5 working days during very busy periods. That is the same across the I, A and G”. When a referral or request for information or support is passed between different teams, the respond time begins whenever a new service request has been created.

How should I refer students?

Referrals can be made to the SST in a number of ways. There are two main ways that tutors need to be aware of.

TutorHome

The primary way tutors can refer students to the SST is through their student list, which is available through TutorHome. From your student group summary, click on the name of the student you wish to refer. Under the heading ‘referrals’ you should see a link that has the title: Refer to Student Support team. This will open a form which gives you a number of different options. Always ensure that you provide as much detailed information as you can, also saying what you expect to be done with the referral. If you wish to be contacted by the SST, if you have further information to share, please mention this.

Responses to a referral will either be sent by email, or you can see if there are any updates if a ‘C’ (contact history available) flag is displayed next to the student’s name in the student group summary. You can view any updates by clicking on the student’s name, and then clicking on the ‘Show contact history’ link, which provides a summary of the most recent interactions between the university and our student.

If you wish to share some additional information with the SST after a referral has been made, you can use the ‘Update record’ link, which can be found on the right of the student group summary. 

Staff tutors

Whilst working with a student, you might contact your staff tutor for support. In some situations, your staff tutor might ask you to refer a student through TutorHome, or they might get in contact with the SST to ask them for help, by sending a referral through the university systems.

Other approaches

If an issue is really urgent, tutors can also directly call the SST, but it is advised that on some occasions, the extent of actions that might be possible might be limited, due to data protection limitations. The SST finds it easier to handle written requests, since it enables them to make decisions about priority, identify who should be attending to an issue, and gives the SST time to formulate a response.

What do tutors need to know?

The most important point to reiterate is: if a query from a student is considered to be an academic query, tutors should take the initiative and respond to it as best as they can. Although colleagues within the SST know about modules, they don’t know the details of modules, or know the details of what is contained with their assessments. They do, however, know about when assessments take place and the policies that relate to assessments.

When there is a query that may sit within a grey area, such as whether a student wishes to continue with a module, tutors should feel confident enough to ask some probing questions about the extent to which an issue is one that is academic, or needs SST support. If you are unsure about where the boundaries between tutor support and SST support lie, the best thing you can to is to contact your staff tutor for guidance.

Early referrals to the SST are important, since there are dates known as fee liability points. This means that in some situations, if students defer early, they will be eligible have a percentage of their overall student fee returned. If a student is paying for their studies through a series of student loans, this will reduce the amount a student is liable for had they deferred later. From the student’s perspective, if you are unsure whether a student is engaging, it is always better to send in a referral than to hope they will return to their studies.

If a tutor has referred a student to the SST since they are having difficulty getting in touch with a student, this may mean that the SST may also have the same problem. If a “no contact” referral is made, the SST will always try to contact our student. Attempts will be always recorded, and these should be visible through the contact history part of TutorHome.

If students require advice about module choice, whilst tutors can refer students to the SST, one practical suggestion is to refer students to the OU’s subject sites. Subject sites are available for all students who are registered, and offer useful summaries, and pointers to other resources and events. SST advisors direct students to explore the subject sites.

A frequent request that will come to tutors through the SST are requests for TMA extensions, since TMA extensions are an academic and faculty issue. If there is a request for a particularly long extension which is to be approved from the faculty by your staff tutor, tutors are encouraged to speak with their students. In these cases, tutors should work with their students to establish an informal plan to ensure that they submit their TMA by the date of their new next extension, but also catch up with their study.

The following very practical point is important: since such a lot of the communication between the SST, tutors and students take place through email, it is important to remember to ensure that your Out of Office reply is turned on when you are unavailable.

Acknowledgements 

Many thanks are extended to Felicity Howe, Jamie Ireland, Anthony Short, Matthew Protz and Alexis Lansbury.

Permalink Add your comment
Share post
Christopher Douce

Book review: Two novels about DevOps

Visible to anyone in the world

When I started to do some background reading into how TM354 Software Engineering might need to be updated, I was guided towards two curious novels. 

From October 23 I start to study A233 Telling stories: the novel and beyond, as a part of my gradual journey through a literature degree. For quite a while, I have been thinking there have been very little to connect novels and software engineering, other than obvious: the development of Word processing tools that can be used to write novels, and the Amazon cloud infrastructure used to distribute eBooks.

What follows is a very short (and not very through) review of two books that are all about DevOps: The Phoenix Project, by Gene Kim (and others), and The Unicorn Project, which is also by Kim. 

The Phoenix Project

I shall begin by sharing an honest perspective: the idea of a novel about software development did not excite me in the least. The text has a subheading that seemed to strengthen my prejudices: “a novel about IT, DevOps, and Helping Your Business win”. This is no crime drama or historical novel. The closest genre that one could attribute to The Phoenix Project is: thriller. I feel it occupies a genre all of its own, which could be labelled: IT business thriller.

The main protagonist is Bill Palmer, who has the unenviable job title of “Director of Midrange Technology Operations”. Bill works for a mysterious American company called Parts Unlimited. A lot happens in the early chapters: Bill is invited in to have a chat with a manager, who gives him a promotion. He is then asked to take a lead in getting the Phoenix Project, a new mission critical software system to work. Failure means the business would lose any potential competitive advantage, and the IT infrastructure might be outsourced, which means that people would lose their jobs.

Before Bill can get settled, he is hit by a payroll outage, which means the employees and unions are angry. He also quickly realises that the whole IT setup is in a complete state. Kim and his co-writers do a good job at attempting to convey a sense of paralysis and panic. The reason for this is expressed through the notion of ‘technical debt’, which means that existing IT infrastructure has become increasing complicated over time. Quick fixes now can, of course, lead to further problems down the line. Parts Unlimited has not been ‘paying down’ their technical debt.

An important element of the novel is the division between the Ops (operations) bit of IT, and the development division. There are other competing teams, which also play a role: there is the QA (quality assurance), and the security team. Security is important, since if an organisation doesn’t keep its auditors happy, the directors may face legal consequences.

I think I would be mean to describe the characters as one dimensional, since plot clearly takes precedence over characterisation. The main protagonist Bill is the most richly described. His organisational skills and sense of calm in the face of chaos is explained through his military background. 

Ubergeek Brent plays an important role, but I really wanted to know what made him tick. Erik Reid, an unofficial mentor to Bill plays the role of a Yoda-like mystic who provides insightful advice, who draws on his extensive knowledge of lean manufacturing. A notable character is Sarah Moulton, the Senior Vice President of Retail Operations, who takes on the unenviable role of the villain.

What struck me was the amount of technical detail that exists within the text. There are references to services, languages, and source code management. There is also the important notion of the ‘release’, which is a persistent problem, which pervades both this text, and its follow-up. Whilst I enjoyed the detail, I’m unsure about the extent to which the lay reader would grasp the main point that the book was making: to gain efficient business value from IT, it is best to combine together operations and development. Doing this enables the creation of tighter feedback loops, and reduces operational risk. Along the journey, there are these moments which raise an eyebrow. An example of this is where there is unambiguous contrition from a security manager once he sees an error in his thinking.

Bill identifies barriers and instigates change. After a “challenging” release of Phoenix, he ultimately prevails. During the updates, there is the emergence of a ‘side project’, which makes use of new fangled cloud technology to deliver value to the business. In turn, this generates income that makes shareholders happy. Political battles ensue, and Bill then gets on a fast track to a further promotion.

Apparently, The Phoenix project was popular amongst developers when it first came out, but I’ve been peripherally distant from the domain of software engineering, which means I’ve been a bit late to the party. Before providing further comment, I’ll move onto the sequel: The Unicorn Project.

The Unicorn Project

When I read The Phoenix Project, one of my criticisms was about the identity of the main protagonist. Novelists can not only use their craft to share a particular reality, but they can also have the potential to effect change. Whilst I liked Bill and the positive role that he took within the novel, given the clear and persistent gender disparities in the sector, I did feel that a female protagonist would have been more welcome. This unarticulated request was answered through The Unicorn Project in the form of Maxine Chambers, the lead protagonist in Kim’s follow up novel. 

Maxine is collateral damage from the payroll failure. Despite being hugely talented, she is side-lined; temporarily reassigned to The Phoenix Project. Her starting point was to try to get a build of all the software that was being developed, but faced persistent complexity, not just in terms of software, but in terms of finding out who to speak with to get things done.

Whilst the main project was saturated with bureaucratic burden, Maxine gradually found “her people”; smart like minded people who were also frustrated by the status quo. She also spoke with the business mystic and mentor, Erik Reid, who was very happy to share his words of wisdom. Ubergeek Brent also makes an appearance, but his backstory continued to remain opaque.

A really interesting part of the text is where Maxine ‘goes into the field’ to learn what happens in the Parts Unlimited stores. Drawing on the notion of ethnographic observations, she learns first-hand of the difficulties experienced by the store workers. Another interesting element which occurs towards the end of the novel is the movement towards embedding institutional learning, and drawing upon the creativity that exists within the workforce. In comparison to The Phoenix Project, there is more emphasis about culture, specifically, developing a no blame culture.

A key theme of The Unicorn Project is shared with The Phoenix Project: it is important to combine development and operations together, and it is helpful to perform continually integration since users can gain access to the new features more readily. A notable section highlighted the challenge of carrying out code merges during marathon meetings. If code is continually integrated, then there isn’t the need for all those uncomfortable meetings. Significantly, the Unicorn project also goes further than The Phoenix Project, since it is also about the power of teamwork, collaboration and the potential of smaller projects positively affecting and influencing others. Like Bill, the formidable Maxine is successful. 

Reflections

My initial scepticism of these novels comes from my view that novels are made from story and character, not technology. What is very clear is that although technology plays an important role, people are, by far, the most important. The novels foreground the role of teams and their organisation, the importance of sharing knowledge, and the importance of collaboration and leadership. It is clear that soft skills matter for the simple reason that software is something that is invisible; developers must be able to talk about it, and to each other. This is also why organisational culture is so important.

An important reflection is that both Bill and Maxine have difficult and very stressful jobs. They are both shown to work ridiculously long hours, often over the weekend. In the novels, IT is depicted as a difficult occupation, and one that is far from being family friendly. The families of both protagonists are featured, and they both suffer.

Although both of these novels are stories about the success of heroes battling against impossible odds, the hyperreality of the chaos within Parts Unlimited makes their success difficult to believe. Conversely, the hyperreality that is expressed through the impossible administrative burdens of the ticketing systems offers a warning to those who have to work with these systems on a daily basis.

The mystical mentor Erik is, of course, difficult to believe. He is a device use to share the pragmatic business and manufacturing theories that are central to the themes that are common to both books. I didn’t mind Erik. Like with Brent, I wanted to know more of his backstory, but with a limited work count and a lot of themes to work through, I understand why creative trade-offs were made to foreground more pressing technical topics.

Whilst I found the broader context, automotive spares, mildly interesting, I found myself becoming bored by the theme of IT being used to gain ever increasing amounts of money through the persistent and relentless pursuit of the customer. Although I accept that IT can be thought of a product of capitalism, there are more interesting ways that IT can be used and applied. Technology can be used to reflect humanity, just as humanity is reflected in technology. Whilst capital is important, there are other subjects that are more interesting. I think I would like to read an IT business thriller about cyber security, as opposed to one about a business that has found a new way to sell engine monitoring apps.

To conclude, these two novels were fun. They were also informative without being overly didactic. Although IT business thriller books is not my favourite genre, I can say that I enjoyed reading them. I’m more a fan of Victorian romances.

Epilogue

In 2004, I was working as a Software Engineer in a small company that designed and manufactured educational equipment used to teach the principles of electrical engineering and computing. 

One day in April, the manager director bounded into the office where I worked.

“We’re selling our e-learning division! This means that we won’t be able to sell our flagship learning management system anymore. We need to find a solution. We had been working on an earlier project, but that didn’t work out. So, we need you to head up the development of a new learning management system”.

That new learning management system was given an internal codename. It wasn’t very original. 

We called it Project Phoenix.

References

Kim, G. et al. (2014) The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win. 1st edition. Place of publication not identified: IT Revolution Press.

Kim, G. (2019) The Unicorn Project. IT Revolution Press.

Permalink Add your comment
Share post
Christopher Douce

Digital Technology Solutions Professional 1.2 briefing (England)

Visible to anyone in the world

In addition to being a staff tutor, I am also a degree apprenticeship practice tutor for the OU DTS scheme, which is an abbreviation for Digital Technology Solutions. This is a standard which has a number of pathways, which takes apprentices 56 months to complete.

On 17 July 23, went to a briefing which aimed to summarise updates to the DTS programme, which has now moved to version 1.2. What follows is a summary of that briefing. An important point to note that is that all these notes only applies to England, since Scotland and Wales have their own schemes (there is no equivalent scheme in Northern Ireland).

What follows is information about the new DTS apprenticeship standard, followed by a summary of changes and a recap of the OU modules that contribute to the DTS scheme. More details are then provided about the end point assessment which ties everything together.

Where possible, to make this blog as useful as possible, I have also provided links to module descriptions. Within the OU apprenticeship scheme, module codes that contain the letters XY are used to identify which modules contribute to a degree apprenticeship programme. For practical and study purposes, there are no differences between apprenticeship and non-apprenticeship modules, other than apprenticeship modules being supported by both a practice tutor and an associate lecturer (who is an academic tutor).

It should be noted that this blog only relates to a programme that is run from the School of Computing and Communications, and is not relevant to other apprenticeship schemes run by other schools. 

The apprenticeship standard

The DTS apprenticeships are defined in terms of the duties that apprentices carry out in their workplace role, and the Knowledge, Skills, and Behaviours (KSBs) that they require to fulfil those duties. The OU provides teaching to apprentices to enable them to gain the necessary KSBs needed to fulfil the DTS standard. 

During the course of the apprenticeship each apprentice is expected to demonstrate during their normal work that they are competent in each of the KSBs. This will be recorded in an ePortfolio system, known as My Knowledge Map, and assessed through an End Point Assessment (EPA).

Apprentices, practice tutors, and employer representatives working with apprentices should be familiar with the current apprenticeship standard. One of the roles of the practice tutor is to signpost these standards to these stakeholders.

Another key role of the PT is to make sure that the apprentice and the employer (and other people who may well be supporting an apprentice) are aware of the KSBs, the learning outcomes of the different modules. They are also to facilitate the discussion of opportunities to make sure the apprentices gains sufficient learning experiences to enable them to fulfil the requirements of the KSBs. In some cases, the employer will be responsible for providing the apprentice with additional training and mentoring in the specific KSBs that apply in their workplace.

The PTs will be responsible running regular review meeting, working with employers to make sure that the apprentice has sufficient work-based opportunities to enable them to demonstrate their KSBs, and ensure that their ePorfolio is regularly updated. Regarding the ePortfolio, there are two important elements that need to be remembered: the recording of off-the-job time (to demonstrate engagement with the academic content), and the saving of assessments and materials which relate to the KSBs. The practice tutor also has a responsibility for ‘marking’ that materials have been submitted.

Main changes

The following points highlight the key changes:

  • All the KSBs have changed from the previous version of the standard. The new KSBs, however, cover the same ground.
  • Cyber specialism improved, with a module change (TMXY352 Web, mobile and cloud technologies, replaced by TMXY256 Cyber Security)
  • EPA project report is shorter, but the ePortfolio is now assessed.
  • Employers will need to ensure apprentices have the right opportunity to demonstrate KSBs in the workplace.
  • EPA date and results moved a month later to allow for modules results.
  • Rewording and enhancing of KSBs in the standard, but delivery is very similar (improved content on mobile communications added to networking specialism, new module for cyber)

Compulsory modules

What follows is a list of all the compulsory modules that an apprentice will work through, summarised in terms of the aim of each module:

During TMXY476 the apprentice should work on a substantial project (during their on the job time) which makes a positive impact on the operation of the business. This project should be substantial enough to allow the apprentice to illustrate their competency in the KSBs assessed within the project.

The programme has three modules that are intended to relate to work-based learning that takes place: TXY122, TXY227 and TMXY350, which are studied in parallel with the other modules. For TXY122 apprentices need to prepare a CPD plan which should be related to their pathway. Working with their employer and practice tutor, apprentices should aim to secure work experience that adds depth and relevance to the academic modules.

Apprenticeship pathways

The DTS scheme has four pathways. Apprentices study the following modules, depending on the pathway:

Practice tutors need to have some knowledge of all these pathways. If further information is needed, practice tutors can gain support from other colleagues who know more about specific areas.

End Point Assessment (EPA) requirements

The End Point Assessment (EPA) has become a more formal requirement. Apprentices are expected to demonstrate competence through applying the KSBs in the workplace, where their manager or a mentor confirms they are working at the expected level. Evidence is collated and stored in their portfolio. The practice tutor will help apprentices to prepare, collate and submit their best evidence through the MKM ePortfolio.

To complete the EPA, apprentices must:

  • Submit a record of six workplace experiences related to the apprenticeship to demonstrate what has been achieved. These can be examples from TMAs produced from the work-based learning modules.
  • Complete a 6000 word project report and deliver a 20 minute presentation. This is accompanied by a 40 minute question and answers session, and 60 minute professional discussion supported by the portfolio. The grading criteria for the project module will be tightly aligned to the apprenticeship grading criteria.
  • Provide a portfolio of completed assignments for all modules that have been studied, which have been approved as ‘marked’ by the practice tutor.
  • To have a clear record of off-the-job time, which is the equivalent of one day a week dedicated to study that complements the work-based element of the apprenticeship.

My knowledge map: the ePorfolio

All new apprentices will be enrolled to the MKM ePorfolio. PTs should take both the employers and the apprentices through MKM and emphasise its use. 

MKM will contain the following information:

  • Background information and documentation, such as the chosen pathway and the apprentice's skills scan document, which is a knowledge assessment of skills possessed by an apprentice at the start of the programme.
  • Details of four progress reviews that are scheduled throughout the year. A practical suggestion for practice tutors is to set them all up at the start of the year with an expectation that they might be change if necessary. One of these meetings will be face-to-face; the rest are virtual.
  • Records: of off-the job study time, which is to be recorded by the apprentice. Records of successfully completing the assignments for the academic elements.

New PTs are able to view screen share recordings to become familiar with the tool, and how it works. All PTs should have access to the tool when they are assigned a group of apprentice students.

Acknowledgements

Acknowledgements are given to Chris Thomson who prepared and delivered this briefing. Much of this summary has been drawn from the PowerPoint resource that he prepared, and many of his words have been edited into a form that is more easily presented through this blog. Any errors or misunderstandings are likely to be mine, rather than Chris’s.

Permalink
Share post
Christopher Douce

Inclusive Student Engagement in Level 1 modules

Visible to anyone in the world
Edited by Christopher Douce, Monday, 31 Jul 2023, 15:31

On 20 July 23 I attended a short one hour seminar that was all about inclusive student engagement in level 1 modules. The seminar had the subtitle: “a supportive framework designed by current/recent students”. The session was prepared and presented by Catriona Bergman, Olivia Brennan, Norain Imtiaz and Owen Lucas, who were also OU student virtual interns.

The seminar had a bit which shared their framework, followed by a discussion activity. I’ll begin by sharing an abridged version of the framework, and then I’ll go on to sharing a couple of points from the discussion, then concluding with a set of reflections.

Engagement framework

If I understood this correctly, their framework shared a number of themes that relate to the student/tutor relationship. There are six key points, each of which was complemented by a suggestion, or a prompt. For brevity, I’ve edited these into a form that works with my own practice.

  1. Addressing the power dynamic: address the difference in status between tutors and students. What do you do to encourage students to reach out to gain support?
  2. Consistency of communication: regular support and timely responses. How often do you communicate with your students?
  3. Proactive communication: tutors taking the initiative to interact with students. Do you contact students before their assignments are submitted?
  4. Humanising tutors: providing an opportunity to build a relationship. Do you feel comfortable in sharing your own personal experiences?
  5. Assessing communication and support needs: in the opening letter encourage disclosure. What opportunities are there for you to discuss individualised study needs with students?

Tutor and students are unknown to each other: a two-way relationship is important. What opportunities are there for icebreaking activities for students and tutors to get to know one another?

The Hidden Curriculum

There was another useful slide during the first section which was all about the notion of the hidden curriculum. I have come across the idea through the notion of academic literacies. Put another way, this is all about knowing the hidden conventions that relate to study, a discipline, and academic communication.

  • Students might not have necessary skills from their earlier education experience. Tutors can direct students to resources that can be used to develop skills (e.g. numeracy, academic writing skills, critical thinking, IT literacy, etc.).
  • Encourage students to reflect on the skills they may need to develop, and provide (or signpost students to) appropriate resources.
  • Encourage development of TMA writing skills and inform students about the importance of good academic conduct.
  • Encourage students to develop their own study habits to support their learning, and embed this within tutorial and one-to-one sessions. Consider the environment in which study takes place.
  • For the module that you are tutoring, highlight, discuss and critique ideas and practices that can contribute to the hidden curriculum.
  • Ensure students are aware of the different avenues that could be followed to gain support (from the tutor, from the module forums, or from the student support team).

Breakout rooms: what do you share, what don’t you tell them?

It was onto a breakout room discussion, where we were asked what we share with our students, and whether we share any of our own vulnerabilities. The intent behind this was to think about the extent to we may disclose something about ourselves, to engender trust and to demonstrate empathy.

Rather than focussing on sharing of vulnerabilities, the group I was assigned to primarily discussed what information we might disclose to students when we contact them for the very first time. Some key points to share include: our qualifications, whether we have been a tutor on the module before, and something about where we are based in the country. There was also some discussion about the importance of tone, and the phrase ‘professional informality’ was shared.

Reflections

I felt this session offered me some reassurance that I have been doing (roughly) the right thing. One way to formalise some of the points mentioned in the framework would be to devise some form of communication plan. This might mean a summary of what is sent to students and when. It is, of course, important to be aware of what module teams are doing, since they may well have their own communication plan, and sets of reminders and messages scheduled.

I was drawn to the session due to the mention of inclusive engagement, since I didn’t really know what this was, or how to describe it. I found it interesting that the focus lies on facilitating inclusive engagement through sharing, and putting oneself, and sharing aspects of one’s identity to others. The aim of doing this is, of course, to attempt to remove potentially perceived barriers, such as power differences between tutors and students.

Reflecting on this further, I have certainly disclosed more personal information. When tutoring on a module about accessible online learning, I have, for example, disclosed a hidden disability. My view is that context is always really important, whether context relates to the subject, or the tutor-student relationship.

Acknowledgements

Many thanks to the AP student virtual interns who facilitated the session and shared their framework. I hope that the version that appears in this blog matches with its original aims and intentions.

Permalink 1 comment (latest comment by Paul Leo Antoine Piwek, Monday, 31 Jul 2023, 15:36)
Share post
Christopher Douce

TM470 Project Report as a journey

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 25 Jul 2023, 08:55

The main output from the TM470 project module is a project report. 

The report shares what has been done and what has been learnt. The ‘things done’ bit relates to the planning, the reading (and any research that has been done), and the actual work that has been carried out. The ‘things learnt’ bit is shared in a section which is used to share reflections, or thoughts about all the work that has been carried out.

One of the bits of advice I offer students is: think of the TM470 project report as a “technical story”. When sharing this view with fellow tutors, another tutor, Kawal Banga, shared another metaphor: the TM470 project as a journey. 

Kawal shared a list of 13 really useful points which relate to actions that take place on the journey of completing TM470. The links to the module learning outcomes are, of course, associated with each of these points:

  1. You identified a real business/social problem that could be solved through an ICT solution (LO2), engaging with sponsors/users who needed a solution to the problem. 
  2. You project managed (keeping evidence of records, plans, outcomes) the delivery using a suitable project/process lifecycle (LO9). 
  3. You identified and managed risks (LO3) on the way and identified and utilised skills, resources and people you needed (LO3). 
  4. You made use of technical concepts and principles (LO1) from your Level 3 modules. 
  5. You analysed, designed and developed an ICT solution building on and extending skills from your Level 3 and other modules (or equivalent professional skills), and using any additional skills you needed (LO11). 
  6. You took into consideration any LSEPIs (Legal, Social, Ethical, Professional issues) and EDI (Equality, Diversity and Inclusion) issues and modified your project and your behaviour to deal with such issues (LO10).  
  7. You carried out a literature review using quality, credible and relevant sources in which to ground your work, and supporting your decisions (LO4, LO6). 
  8. You worked independently as much as possible and learned new skills and knowledge that you applied to your project (LO8). 
  9. You reflected on things (processes, tools, resources, studying, etc) that worked or things that didn’t work (LO5), and lessons and skills (technical, professional, academic, organisational, project management) that you learned through the project.  
  10. You replanned and rescheduled your work when things went wrong (LO9, LO3, LO5, LO8). 
  11. You communicated effectively through TMAs/EMA, reports, emails etc with your tutor and other project stakeholders (LO7).  
  12. You engaged the sponsors and/or users throughout the project journey, where appropriate, seeking feedback on interim deliverables and they evaluated your final artefact. 
  13. You can prove all of the above with solid evidence that you collected over the project journey, and can communicate this effectively to your tutor and other stakeholders.

It's really helpful to reflect on his list. 

Another thought is that the notion of stories and journeys are compatible with each other. In some respects, my advice for the TM470 Project Report Structure reflect both perspectives. This structure intends to take the EMA examiner on a journey from the start of the project to the final summary, which should clearly highlight the learning that has taken place.

Acknowledgements

Many thanks to Kawal for giving permission to share his list. Thanks also to fellow tutors who responded to my post about the notion of the project report being a story.

Permalink Add your comment
Share post
Christopher Douce

SEAD/LERO Research Conference ‘23

Visible to anyone in the world
Edited by Christopher Douce, Thursday, 20 Jul 2023, 09:56

I attended my first joint OU SEAD/LERO research conference, which took place between 4 July and 6 July 23. SEAD is an abbreviation for Software Engineering and Design Research Group a research group hosted within the OU’s School of Computing and Communications. The conference was joined by members of LERO, the Science Foundation Ireland Research Centre for Software, which based in Limerick.

What follows is a summary of the two days I attended. There was a third day that I didn’t attend, which was all about further developing some of the research ideas that were identified during the conference, and researcher professional development

The summary is intended for the delegates of the conference, and for anyone else who might be interested in what happens within the SEAD research group. All the impressions (and any accompanying mistakes in my note taking) are completely my own. What is summarised here isn’t an official summary. Think of it as a rough set of notes intended to capture some of the themes that were highlighted. It is also used to share some potential research directions and areas that intend to be further developed and explored.

Day 1: Introductions and research discussions

Bashar Nuseibeh kicked off the day by highlighting the broad focus of the conference: to consider the role of software in society. Although I missed the first minutes of his opening address due to traffic, there was a clear emphasis on considering important related themes, such as social justice.

The first session was an ice breaker session. This was welcome, since I was an incomer to the group, and there were many delegates who I had not met before. We were asked to prepare the answers for three questions: (1) Who you are, including where you are based and your role? (2) What is your main research area/interest?, and (3) Something you love about your research and something you dislike. (Not bureaucracy!)

Having a go to answer these myself, I work as a staff tutor. My research interests have moved and changed, depending on what role I’ve been doing. Most recently, it has been about the pedagogy of online teaching and learning. When I was a researcher on an EU funded project, I was looking at the accessibility of online learning environments and supporting students who have additional requirements. Historically, my research has been situated firmly in the area of software engineering; specifically, the psychology of computer programming, maintenance of object-oriented software, and software metrics (informed by research about human memory). I have, however, returned to the domain of software engineering, moving from the individual to communities of developers by starting to consider the role of storytelling in software engineering, working with colleagues Tamara Lopez and Georgia Losasso.

What I like about the research is that it is really interesting to discover how different disciplines can be applied to create new insights. What can be difficult is that different disciplines can sometimes use different languages.

Invited talk: navigating the divided city

Next up was an invited talk by Prof. John Dixon from the OU’s Social Psychology research group. John’s presentation was about “intergroup contact, conflict, desegregation, and re-segregation in historically divided societies”. John described how technology was used to explore human mobility preferences. Drawing on research carried out as a part of the Belfast Mobility Project. The project studies, broadly speaking, where people go when they navigate their way through spaces, and can be said to sit within an intersection between social science and geography. Technology was used by researchers to study activity space segregation and patterns of informal segregation, which can shed light on social processes. 

John also highlighted tensions that a researcher must navigate, such as the tension between open science (where data ca be made available to other researchers) and the extent to which it is ethical to share detailed information about the movement of people across a city.

There was a clear link between the talk and the theme: the connection between software and society. This talk also resonated with me personally: as a regular user of an activity tracker called Strava, I was already familiar with some of the ethical concerns that were shared. After becoming a user of Strava, I changed a couple of settings to ensure that my identity is disguised. Also, a year ago I noticed that the activity tracker has started to hide the start point and the end point of any activity that I was publicly sharing. A final point from the part of the day is that both technology and software can lead to the development of new methods and approaches.

Fishbowl: Discussing society and software

Talking of new methods and approaches, John’s talk (and a lunch break) was followed by an event that was known as the ‘fishbowl session’, which introduce a ‘conference method’ that I had never heard of before.

In some respect, the ‘fishbowl’ session was a discussion with rules. Delegates sat on one of ten chairs in the middle of the room, and have a conversation with each other, whilst trying to connect together either the main theme of the discussion (software and society) or some of the topics that emerge from the discussions.  We were encouraged to discuss “anything where software has a role to play”.

The fishbowl discussed consequences of technology, collective education, critical thinking (of users), power of automation, concentration of power (in corporations), the use of AI (such as large language models), trade-offs, and complex systems. On the subject of AI, one view I noted down was that perhaps the use of AI ought to be limited to low risk domains, and leave people to the critical thinking (but this presupposes that we understand all the risks). There was also a call to ensure that AI tools to explain their “reasoning”, but this also implicitly links back to points about skills and knowledge of users. This is linked to the question: how do we empower people to make decisions about the systems that they use?

Choices were also discussed. Choices by consumers, and by developers, especially in terms of what is developed, and what is good to develop. Also, when uncovering and specifying requirements, it is important to consider what the negatives might be (an observation which reminds me of the concept of ‘negative use cases’ which is highlighted in the OU’s interaction design module).

I noted down some questions that were highlighted: how do we present our discipline? Do we research how to “do software” and leave it up to industry? Should we focus on the evaluation of the impact of software on communities and society? An interesting quote was shared by Bashar, which was: “working in software research is working for society”.

A final reflection I noted was that societal problems (such as climate change) can be thought as wicked problems, where there is no right answer. Instead, there might be solutions that are not very right or wrong, or solutions that are better or worse than others.

It was difficult to distil everything down to a group of neat topics, but here are some headings that captured some of points that were discussed during the fishbowl session: resilience, care, sustainability, education, safety and security, and responsibility.

At the end of the session, all delegates were encouraged to join a group that reflected their research interests. I joined the sustainability group.

Group Work 1 - Expansion of themes from the fishbowl

After a coffee break it was time to do some work. The guidance from the agenda was to “to develop some proposals for future research (problem; research objectives; research questions; methods; impact)”. 

The sustainability group comprised of four members: three from SEAD, one from LERO.

After broadly discussing the link between sustainability and software engineering, we produced a sketch of a poster that shared the following points:

  • How can we make connections and causal links between different (sub)systems explicit.
  • How can we engineer software to be holistically ‘resource aware’?
  • What is the meta-language for sustainable software systems?
  • What are the heuristics for sustainable software systems?

On the surface of it, all these points are pretty difficult to understand. 

The first point relates to the link between software, economics, and society. Put another way, what needs to be done to make sure that software systems can make a positive contribution to the various dimensions of our lives. By way of further context, the notion of Doughnut Economics was shared and discussed.

The second point relates to the practice of developing software. Engineers don’t only need to consider how to develop software systems that use resources in an efficient way, they also need to consider how software teams use and consume resources.

The third point sounds confusing, but it isn’t. Put another way: how do we talk about, or describe, or even rate the efficiency, or sustainability of software systems. Going even further, could it be possible to define an ISO standard that describes what elements a sustainable software system could or should contain?

The final point also sounds arcane, but when unpacked, begins to make a bit of sense. In other words: are there rules that software engineers could or should apply when evaluating the energy use, or overall sustainability of software systems? There are, of course, some links from this topic to the topic of algorithms and data structures (which is explored in modules such as M269 Algorithms, data structures and computability) which considers efficiency in terms of time and memory. A simple practical rule might be, for example: “rather than continually polling for a check in status of something, use signals between software elements”. There is also a link to the notion of software patterns and architecture (with patterns being taught on TM354 Software Engineering).

Day 2: Ideate and prototype

The second day kicked off with summaries from the various groups. The responsibility team spoke about the role of individuals, values, and organisations. The care group highlighted motivation, engagement, older users and how to help people to develop their technical skills. The education had been discussing computing at schools, education for informed choices, critical thinking, and making sure that the right problem is addressed. The resilience group discussed support through communities, and the safety and security group asked whether safety related to people, or to process.

A paraphrased point from Bashar: “look to the literature to make sure that the questions that are being considered haven’t been answered before” also, reflecting on the earlier keynote, “consider radical methods or approaches, and consider the context when trying to understand socio-economic systems”.

Group Work 2 - ideate and prototype

Back in our groups, our task was to try to operationalise (or to translate) some of our earlier points into clearer research questions with a view to coming up with a research agenda.

Discussing each of the points, we returned to the meaning of the term sustainability, along with what is meant by resource utilisation by code, also drawing upon the UN sustainable development goals https://sdgs.un.org/goals .

We eventually arrived at a rough agenda, which I have taken the liberty of describing in a bit more detail. The first point begins from a high level. Each subsequent points moves down into deeper levels of analysis, and concludes with a point about how to proactively influence change:

  1. What types of software systems or products consume the most energy?
  2. After identifying a high energy consuming product or system, use a case study approach to holistically understand how energy used, also taking into account software development practices and processes.
  3. What are the current software engineering practices of developers who design, implement and build low energy computing devices, and to what extent can sharing knowledge about practice inform sustainable computing?
  4. What are the current attitudes, perceptions and motivations about the current generation of software engineers and developers, and how might these be systematically assessed?
  5. After uncovering practices and assessing attitudes, how might the university sector go about influencing organisations to enact change?

Relating to the earlier call to “draw on the literature”, a member of our team knew of some references that could be added to the reference section of our emerging research poster:

Lago, P. et al. (2015) Framing sustainability as a property of software quality. Communications of the ACM, Volume 58, Issue 10, pp.70–78. https://doi.org/10.1145/2714560

Lago, P. (2019) Architecture Design Decision Maps for Software Sustainability. 2019 IEEE/ACM 41st International Conference on Software Engineering: Software Engineering in Society (ICSE-SEIS), 25-31 May 2019, IEEE. https://doi.org/10.1109/ICSE-SEIS.2019.00015

Lago, P. et al. (2021). Designing for Sustainability: Lessons Learned from Four Industrial Projects. In: Kamilaris, A., Wohlgemuth, V., Karatzas, K., Athanasiadis, I.N. (eds) Advances and New Trends in Environmental Informatics. Progress in IS. Springer, Cham. https://doi.org/10.1007/978-3-030-61969-5_1 

Manotas, I. et al. (2018) An Empirical Study of Practitioners' Perspectives on Green Software Engineering. 2016 IEEE/ACM 38th International Conference on Software Engineering (ICSE). 14-22 May 2016. https://doi.org/10.1145/2884781.2884810

Wolfram, N. et al. (2018) Sustainability in software engineering. 2017 Sustainable Internet and ICT for Sustainability (SustainIT). 06-07 December 2017. https://doi.org/10.23919/SustainIT.2017.8379798

(A confession: I added the Manotas reference when I was writing up this blog, since it looked like a pretty interesting recommendation, especially have previously been interested in the empirical studies of programmers).

Conference visit: Bletchley Park

The second day concluded with a visit to Bletchley Park, which isn’t too far from the campus. It seemed appropriate to visit a place where socio-technical systems played such an important role. I had visited Bletchley Park a few times before (I also recommend the computing museum, which is situated on the same site), so I sloped off early to try to avoid the rush hour to London.

Day 3: Consolidate and plan next steps

This final day contained a workshop that had the title “consolidate and plan next steps” and also had a session about professional development. Unfortunately, due to my schedule, I wasn't able to attend these sessions.

Reflections

I really liked the overarching theme of the event: the connection between software and society. Whilst listening to the opening comments it struck me that there were some clear points of crossover between research carried out within the SEAD group, and the research aims of the OU Critical Information Studies research group.

It was great working with others in the sustainability group to try to develop a very rough and ready research agenda. It was also interesting to begin to discover how fellow researchers in other institutions had been thinking along similar lines and have already taken some of our ideas further. 

One of my next steps is to continue with reading and exploring with an aim of developing a more thorough understanding of the research domain.

It was interesting that I was the only staff tutor at the event. It is hard for us to do research, since our time split in three different ways: academic leadership and management (of part time associate lecturers), teaching, and whatever time remains can be dedicated to research. For the next few years, my teaching ‘bit’ of time will be put towards doing my best to support TM354 Software Engineering.

Looking forward, what I’m going to try to do is to integrate different aspects of my work together: integrate the teaching bit with the research bit, with the tutor management bit. I’m also hoping (if everything goes to plan) to tutor software engineering for the first time.

As well as integrating everything together, another action is to begin to work with SEAD colleagues to attempt to put together a PhD project that relates to sustainable computing.

Update 20 July 23: After doing a couple of internet searches to find more about DevOps, I discovered a new book entitled Building Green Software (O'Reilly), which is due to be published in July 24. I also found an interview with the lead author (YouTube), and learnt about something called the Green Software Foundation. I feel really encouraged by these discoveries.

Permalink
Share post
Christopher Douce

Preparing for the summer: A233 reading list

Visible to anyone in the world

At the start of October 2023 I will be studying A233 Telling stories: the novel and beyond. I usually take a few books on holiday with me. To give myself a bit of a head start, I’m going to get through some of the books that feature on A233 reading list.

What follows are list of books that will be discussed within A233, in the order that I understand they are studied. Where possible, I’ve provided a link to a version from Project Guttenberg which can be downloaded to an eReader.

If you do make use of the Guttenberg version, do note that there may well be significant differences between the text that is officially recommended by the module team, and the downloaded version. The editorial that the officially recommended text may well be useful.

Hardy, T.: Falck-Yi, S.B. (ed) Far from the Madding Crowd, Oxford World's Classics, ISBN 9780199537013

Wharton, E.: Orgel, S. (ed) The Custom of the Country, Oxford World's Classics, ISBN 9780199555123

Smith, A. Hotel World, Penguin, ISBN 9780140296792

Blunden, E. Undertones of War, Penguin, ISBN 9780141184364

Roy, A. The God of Small Things, 4th Estate, ISBN 9780006550686

Perrault, C.: Betts, C. (trans.) The Complete Fairy Tales, Oxford World's Classics, ISBN 9780199585809

A direct equivalent to this text isn’t available through Project Guttenberg, but there is a collection that has the title: The Fairy Tales of Charles Perrault by Charles Perrault

Grimm, J. & Grimm, W.: Crick, J. (trans.) Selected Tales, Oxford World's Classics, ISBN 9780199555581

I’m assuming that Grimm is read at the same time as the other texts that relate to fairy tales. A direct equivalent isn’t available through Project Guttenberg, but there is a different collection that is available: Grimms' Fairy Tales by Jacob Grimm and Wilhelm Grimm

Andersen, H.C. Hans Andersen's Fairy Tales: A Selection, Oxford World's Classics, ISBN 9780199555857

Like with both Grimm and Perrault, there isn’t a direct equivalent in Project Guttenberg, but there is a broader collection which can be downloaded: Andersen's Fairy Tales by H. C. Andersen

Carter, A. The Bloody Chamber, Vintage, ISBN 9780099588115

Armitage, S. Sir Gawain and the Green Knight, Faber and Faber, ISBN 9780571223282

Gaiman, N. & Vess, C. Stardust, DC Comics (Vertigo), ISBN 9781401287849

Le Guin, U. The Dispossessed, Gollancz, ISBN 9781857988826

Shakespeare, W.: Orgel, S. (ed) The Tempest, Oxford World's Classics, ISBN 9780199535903

Although the raw text of The Tempest is readily available for download, it is worth nothing that the introduction and the editorial comments from these Oxford World’s classics versions are really useful in terms of figuring out what is going on.

A233 has a ‘book club’ section, where students will choose one book from the following:

Smith, A. Girl Meets Boy, Canongate Books, ISBN 9781786892478 

Sassoon, S. Memoirs of an Infantry Officer, Faber and Faber, ISBN 9780571064106 

Hardy, T. Wessex Tales, Wordsworth Editions, ISBN 9781853262692 

Anand, M.R. Untouchable, Penguin, ISBN 9780141393605

Wharton, E.: Orgel, S. (ed) The Age of Innocence, Oxford World's Classics, ISBN 9780199540013 

A disclaimer. I’m going on what I understand was covered during the previous presentation of A233. Future presentations may well present things differently, and use different texts.

Looking forward: when I get started with A233 properly, I’ll be using this blog to share my study log. I’m sharing this, so I can hold myself to account.

Acknowledgements: this reading list has been directly liberated from the A233 module website. 

Permalink
Share post
Christopher Douce

Sharing source code in a TM470 project report

Visible to anyone in the world
Edited by Christopher Douce, Saturday, 15 Jul 2023, 11:38

TM470 projects can take many different forms. 

Some might be design projects, some might be research projects, and some might be development projects. One of the most important points that all students should bear in mind is that there is a need to share evidence of project activity and learning that takes place.

Evidence is shared only through the project report. If your project is all about software development, you are not required to upload software to a GitHub repository, or to provide examiners with a working version of anything you may have designed. You should, however, provide evidence of software development having been carried out, and must provide evidence of critical thinking you have applied. In other words, you should write a technical story that describes how your software was created. Although every project is different, your report should share the story of requirements discovery or specification, design, development, evaluation, and testing. The number of times you carry out an evaluation cycle is, of course, completely up to you.

I am sometimes asked a question, which is: how should I share code through my EMA report?

A case study approach

You don’t need to share all your code. 

You should share your code in two ways: in the body of the report, and in an appendix.

For the body of your report, choose bits of code that best demonstrates your technical skills and help to demonstrate a technical story of what you have done, and how you have done it. You should also show how you have drawn upon modules you have previously studied.

Think about the body of your report as a showcase, where you share a series of mini case studies which demonstrate your skills, abilities, and learning. Providing snippets of code in the body of your report that highlight show the important and difficult problems that you have had to resolve during the course of your project. In the body, you can then provide a pointer to one or more appendices, where you can provide more code, which the examiner can look at.

A simple rule of thumb is: provide snippets that show your work and your learning in the body of your report, and provide bigger sections of code as a section in an appendix.

Some projects might require the development of an algorithm, so showcasing its development will be a really important part of the technical story of your project. In this example, you might want to refer to M269 Algorithms, data structures and computability, or another module.

If your project has user interfaces that is coded up in a language, such as HTML, you might want to include fragments of these, and refer to modules such as TM352 Web, mobile and cloud technologies and TM356 Interaction design and the user experience.

You should also refer to texts, such as set texts, module materials, or any other resources that you have mentioned in your literature review section.

Presentation

In the body of your report, a practical approach is to share small sections of your code using tables. By using this approach, you can refer to your code using a table number, when you discuss how you created your software.

A suggestion is to present your code a font, such as Courier New, to clearly distinguish between what is code, and what is discussion. To make sure you don’t use too many pages in your project report, it is okay to make your code a bit smaller. From my tutor perspective, 8 point Courier New is a good choice. 

A fellow tutor shared a particular opinion about code presentation that has stuck with me, which was: try to avoid presenting code on a black background. The reason for this is pretty simple: if bits of your report are printed (which I don't think is likely to happen), it would use black ink or toner than is necessary. Another argument is that it might make the code harder to read on some devices.

For bigger chunks of code, you should use one or more appendices. A practical suggestion is to use one appendix for the code, dividing it up into subsections if you need to, since this way everything is in one place. You might want to use an appendix to share an entire file, or perhaps show how all your earlier code fragments look when they are combined together. You should use a font like Courier New to present your code, but you don’t need to present your code in a table, since you can refer to it with an appendix or a reference number.

Pro-tips: cross referencing and Word headings

The bigger a Word document becomes, the harder it becomes to maintain, especially if you’re starting to add in a lot of sections. To make things easier, I have the following recommendations:

  • Make use of the Word in built headings; this enables you to easily create a table of contents using a feature of Word. Also, get Word to number each section for you, since this way you don’t have to renumber everything is you need to add a new section.
  • Use the Word document navigator view to get an overview of your document.
  • Have up to 3 levels of headings, i.e. 1.2.2; too many levels will make things confusing.
  • If you add tables and figures, get Word to number them for you.
  • If you refer to a table or a figure, do so using the Word cross reference feature, since that way if you add more tables, you won’t need to mess with editing table numbers.

The final point is: if all this is a bit much, do what you need to do to get your report written. Sometimes it is best to decide to get things done. TM470 is all about OU study and running a project, rather than making a perfect Word document.

Edited 15/7/23, adding a further bit guidance about the formatting of code.

Permalink Add your comment
Share post
Christopher Douce

Considering LSEPI

Visible to anyone in the world
Edited by Christopher Douce, Wednesday, 28 Jun 2023, 09:02

In TM470 LSEPI is an abbreviation for Legal Social Ethical and Professional Issues. A good TM470 project report should clearly address these issues to show the examiner that you have thought about how these issues have impacted on your project, and what you have done to take these into account.

LSEP issues are increasingly important in computing due to the increasing impact that computing and IT has within society. When speaking with students I often a recent example: the Volkswagen emissions scandal. In this case, there are clear environmental impacts and legal implications. It is also clear that both the engineers and leaders have to make ethical decisions.

In TM470, LSEP issues are assessed through the following learning outcome: “LO10. Identify and address the legal, social, ethical and professional issues (LSEPIs) and the equality, diversity and inclusion (EDI) concerns that may arise during the development and use of computing and IT systems.” In the marking of the EMA, this learning outcome is assessed with LO2, which is all about the aims and goals of your project.  When just looking at the number of learning outcomes, and the marks available, the LSEPI section could account for 10 marks.

To gain a top score for this learning outcome a student: “has comprehensively identified the relevant LSEPIs and EDI concerns arising during development and use and modified their project work to take these into account and behaved professionally in all aspects of their project work”. EDI being an abbreviation for equality, diversity and inclusion.

Given the importance of both LSEP and EDI, a suggestion is to include it as a top level section in your report, just before the literature review section. The justification for this is that if you identify some issues that need to be explored in greater depth, you can then go onto provide evidence of your reading.

Module materials

At the time of writing, it takes a bit of digging to find two documents that relate to both LSEP and EDI issues. From the module website, click on the Resources heading, and then click on the Study materials section.

The LSEP document contains the following key headings: working with stakeholders, working with human participants, and asking the right questions. Do review the materials that are presented under these headings and review Appendix A Guidelines for conducting research with human participants. Related to these are two template documents: a sample consent form, and a participant information sheet.

Informed consent is the process through which researchers share the aims and purpose of their research with participants, and gain their approval that they are happy to participate in a study. The accompanying information sheet is designed to offer further information under a set of familiar headings.

When working with participants, I always remember two points. The first is that participants are at liberty to leave a study at any point. The second point is related: the participants are always more important than the research that is being carried out.

The equality, diversity and inclusion section addresses “why equality, diversity and inclusion are relevant to computing and IT professionals”, introduces the concept of protected characteristics, and “unconscious bias is and how it might affect your practice as a computing and IT professional” and what mitigations might be adopted (TM470 module materials).

EDI relates to people, and differences between people, irrespective of whether they are perceived or due to physical, cognitive or sensory impairments. Since Computing and IT products are, ultimately, used by people, it is necessary to consider EDI issues. If you design an app or a website, your product should be accessible to the widest possible group of users. The motivations for doing this are twofold: firstly, there is a legal obligation to ensure that products and systems are accessible under the Equality Act, and secondly, all users are potential customers. If a product isn’t accessible or perceived negatively, a consumer might choose another service that has a more accessible, usable, or appealing interface.

Looking at this issue from a slightly different perspective, if your project uses artificial intelligence or machine learning, it is necessary to question the extent to which biases might exist within either data that informs your project, and the extent to which bias might be potentially reinforced, or even magnified.

Questions to ask

As highlighted earlier, the LSEP materials contains a section that has the title: asking the right questions. 

Go through each of these questions in turn. 

When working through these questions, do think about the stakeholders who are involved with your project. A stakeholder can be thought of anyone who is affected by your project, either directly or indirectly. Ask yourself questions about what data might need to be held and collected, and what bits of legislation might play and impact if you were ever to deploy your project. The Equality Act was mentioned above. You might want to also consider data protection and computer misuse legislation.

If your project is a research report it is important to ask: what might be the impact of my report? If something is discovered by the report, what might be the impact of disclosing the results, or not disclosing the results? The point here is that it is important to go further than just the immediate project, but also to consider wider and broader impacts.

Differences between student projects and university projects

Before university staff can carry out research that involved human participants, they must submit project proposals through a formal ethics panel. The aim of this panel is to make sure that researchers have carefully considered everything, and any potential risks to all participants (and to the university) have been mitigated.

Unlike official university projects, undergraduate and postgraduate projects are not required to go through such a rigorous process. Rather than having an ethics panel and a lot of electronic paperwork to complete, students should think of their tutor or project supervisor as a mini ethics panel.

Interacting with your tutor whilst considering your LSEP and EDI issues should be thought of as a useful and necessary part of your project. Your tutor will be able to offer some thoughts about what needs to be considered. Plus, interactions with your tutor or supervisor can be documented in an appendix of your final reports.

Further resources

A lot of good resources about ethics are available, and some of these resources are mentioned in the module materials. Here are a collection of links that might be useful:

For those that find this subject really interesting, there is a whole suggested curriculum about Society, Ethics and Professionalism on the ACM website.

Going through the ethics bit of TM470 gives you a taste of what university researchers have to go through when they plan and design studies that involve human participants. More information about what goes on behind the scenes at the OU is presented through Ethics support for projects: Which studies need review, by whom and why? (OU blog)

Reflections

I find ethics a fascinating subject. In computing it comes into play more than you might initially expect since computing touches on so many different areas of human activity. Rather than being a subject that was once on the periphery of the discipline, I now see it as a topic that has moved to the centre. It is an important and necessary part of becoming a computing professional.

It is also interesting to reflect on how ethics has developed since I was a graduate student. There is now a lot more that has to be done, but this isn’t a bad thing. Additional scrutiny along the way helps researchers to carry out better research. For TM470 students, my key bit of advice is: speak with your tutor; they are your own personal ethics panel.

Permalink Add your comment
Share post
Christopher Douce

Planning and evaluating impact of a scholarship project

Visible to anyone in the world

On 23 June 23, I attended an online seminar about impact and scholarship, which was facilitated by Shailey Minocha and Trevor Collins. Shailey is the School of Computing and Communications scholarship lead, and Trever used to be a director of the university’s STEM scholarship centre, eSTEeM.

The event is summarised as follows: “we will take you through the toolkit for impact of SoTL and introduce you to various resources of the impact evaluation initiative. By the end of the event, we hope that you will feel prepared to use the resources/toolkit to plan, evaluate, and report the impact of your (past, present and future) SoTL projects and interventions.” Early on in the seminar, there was a reference to a page about impact, which can be found on the eSTEeM website.

Stories of impact

One of the most notable parts of this seminar was the amount of articles and resources that were shared. One of the first articles mentioned was: Impact of Scholarship of Teaching and Learning: A compendium of case studies. In this publication, 16 Scholarship of Teaching and Learning (SoTL) projects were analysed by something called the Impact Evaluation Framework (IEF).

Two other articles were: 

Defining impact

The UK Research Excellent Framework (REF) defines impact as “an effect on, change or benefit to the economy of society”. There is a connection here with the school research fiesta which took place earlier this year: REF impact case studies are important. In terms of SoTL, impact implies demonstrative benefits to learning and teaching that are directly attributable to a specific project.

I noted a question: what has changed (as a result of a project)? What new insights have gained (from the project)? Also, how can the institution put the outcomes into use? What are the current debates that this scholarship relates to?

Impact evaluation framework

The impact evaluation framework was mentioned, but what exactly is it? It is said to contain 12 facets (or aspects) of impact, which are spread over 4 categories. During the session, I attempted to briefly summarise what they are:

  • Learning and teaching: impact on student experience; student retention; evidence of excellence?
  • Transfer to others: an influence on discipline based teaching, research, or practice; dissemination of outcomes; extent of adoption by others?
  • Stakeholder benefits: enhanced mutual understanding; facilitated personal or professional development; recognition of project team members and other stakeholders.
  • Cultural and economic benefits: has it fostered scholarship culture; financial implications (saving of money); funding opportunities.

Relating to this framework, Shailey shared a link to her blog, Impact of scholarship of teaching and learning

This article provides links to related resources, such as an executive summary, case studies, guide for educators, and two workbooks: one about impact evaluation, and another about planning for impact

Six principles (or values) of SoTL

A particularly useful resource which relates to scholarship is a free badged open course from Open Learn: Scholarship of Teaching and Learning in STEM.

This short course has 6 sections, which emphasises what contributes to an effective study:

  1. Grounded in student learning and engagement
  2. Grounded in one or more context
  3. Rigorous and methodological sound research design
  4. Conducted in partnership with students
  5. Appropriately public for evaluation and uptake by peers
  6. Reflection, critical reflection and reflexivity.

Strategies for planning and generating impact

This section of the seminar shared some useful practical tips for anyone who was considering setting up a scholarship project, or thinking about impact. These have been paraphrased as follows:

  • Align scholarship with strategic priorities of institution, school and discipline.
  • Use social media to create community and connection; make use of YouTube channels, and other social media platforms.
  • Make sure you keep a clear record of evidence of impact.

Another thought I did have was: consider developing a scholarship team which has complementary skills.

Impact resources

Building on the section which introduced the impact evaluation framework, this section aimed to highlight resources and ideas that could be useful. A key element of this was the Theory of Change methodology (ToC). This was highlighted as a dominant image methodology which is used by the Office for Students https://www.officeforstudents.org.uk/ . Apparently, the Theory of Change helps scholars plan a project for impact, helping them to consider pathways to impact from the start of project.

Some resources that were highlighted included a ToC visual tool, a SoTL impact evaluation workbook, and the Planning for SoTL impact evaluation workbook. There was also a question driven template, which was considered to be a project management tool.

A key point highlighted in this section: know who your stakeholders are. Without stakeholders, and without influence across stakeholder communities, there is no impact.

Reflections

A question that I always return to is: what is the difference between scholarship and research?

In some respects, the answer to this question is directly linked to the notion of impact. The way that I understand it is that scholarship relates to impact on teaching practice and activities. In turn, scholarship can have a direct impact on the student experience. Research, on the other hand, has impact on an academic discipline, or field of study. There is, of course, cross over between scholarship and research, especially within the domain of education and education studies. 

Another thought I always come back to is that both scholarship and research are important, and that academics should do both: research relates to what we teach, whereas scholarship relates to how we teach. I can’t get away from the perception that due to the Research Excellence Framework (REF) that research activity is valued higher than scholarship activity. This said, there are other metrics and league tables that relate to the student experience: the student satisfaction survey, and the Teaching Excellence Framework (TEF).

This seminar was timely. I’ve just finished setting up what is called my annual Academic Workload Plan. In the forthcoming year, I’m hoping to set up a scholarship project (subject to approval, of course). An important point from this session was: build in dissemination and impact right from the start.

I thought that the tools shared during this session were potentially useful, especially the articles. The session clearly highlighted that there are challenges in planning for and generating impact: projects can often take longer than expected, and project members can become tired at the end of the project. An excellent point was made; sometimes impact could occur years after the completion of a project. This point emphasises the importance of importance of collating impact after a scholarship project has officially finished.

I once heard it said that it is very difficult to change the world by writing an academic article. I understand impact being all about what you do with either your practice or research findings. A lot of academic effort goes into finding things out and getting articles published in prestigious journals. Impact, in my eyes, is all about enabling findings to facilitate positive and constructive change.

Permalink Add your comment
Share post
Christopher Douce

Working with the tutor website

Visible to anyone in the world

Every module has a student facing website which is likely to slightly change for every module presentation, and an accompanying tutor facing website. The ‘tutor website’, as I’ll call it, is a really important resource for any tutor who is tutoring a module.

This short blog post highlights some of the most important elements of a tutor website. Every version of a tutor website is slightly different, but is likely to contain a few common elements: one or more forum spaces, a space to access resources (which may, or may not, be also the forum areas), and a space to have online meetings (although the module team and you line managers might choose to use different rooms in some circumstances).

Tutor websites are ‘go to’ places if you have any questions about any element of the module that you’re tutoring. If you have been asked a question by a student, and you’re not sure how to answer it, you should feel free to ask for help on the tutor forum. Also, if you’re unsure how to interpret, or to mark an element of an assignment, you should also ask on the forum. Tutor websites are monitored by curriculum managers, which means they are able to quickly highlight issues to module team members, or even the module team chair.

You usually gain access to the tutor’s website through a link on the student’s version of the module website. Alternatively, your curriculum manager might send you a link, which you should then keep in a safe place. Two recommendations about how to do this are: save the email in a folder that relates your module, and save the link to the ‘your links’ section on TutorHome or to your dashboard.

Forums

Different modules will have different forums. One module might have one main forum, where all tutors exchange perspectives and experiences. Another module might have dedicated forum spaces for each of the TMAs. A recommendation is to have a look at each of these forum areas, and subscribe to each of them.

Subscribing to a forum means that you are sent an email message whenever anyone makes a post. The advantage of subscribing, and receiving an email notification is that your email account can give you an overview of what is happening and what questions are being asked. If you have a high level of email traffic, a practical suggestion is to set up an email filter, so forum messages are all sent to dedicated folders. Do refer to one of the other blogs here about effectively managing your IT. On the subject of forums, do also refer to another article that is about student facing tutor group forums.

Some modules will apply a single component assessment strategy, where module performance is assessed purely through TMA scores. If your module adopts this approach, you might have to carry out what is known as a coordination exercise, which may take place either within a dedicated forum, or on a dedicated forum thread. The aim of the coordination exercise is to ensure that all tutors are marking to the same standards. If you are unsure whether this applies to your module, do speak with your line manager.

Activity

Find an equivalent of a tutor’s café forum. A café forum can be thought of as an informal space where views, opinions and experiences can be shared. If you can’t find a café forum, go to the main module forum area. Look for a thread where tutors introduce themselves. If you can’t find one, start one by posting anew message. When you have made the post, make sure you subscribe to the forum area to you can see everyone’s reply.

On some tutor websites, there might be a forum that is used by tutors to share tutorial resources, such as PowerPoint files, and accompanying resources, such as handouts, which might be in the form of Word documents. Sometimes, tutorial resources might be shared within the resources section, or through another tool, which is known as a Wiki.

Activity

Find out whether your tutor website has a forum where tutorial resources area shared. Identify a couple of discussion threads where sharing takes place, downloading some PowerPoint resources. Open these resources, and consider how a tutor might use this PowerPoint resource within a tutorial.

Resources

As well as being a space to get help and support, the tutor’s website is also a space for the module team to share some essential resources for tutors. For every TMA there will be a set of accompanying tutor notes. These notes, which typically take the form of a Word document, offers exacting guidance about how each student’s TMA should be marked. As well as offering a summary of the marks that should be allocated, they also offer guidance about what answers are acceptable, and what kind of feedback should be offered. The tutor notes represents the offical ‘line’ from the module team about what is acceptable and what isn’t. The role of the tutor is to interpret the student’s submission, the module team’s tutor notes, and to provide constructive comments to help to facilitate learning.

Activity

Find the tutor notes for the next TMA. Download a copy of it, and then get a printout of them if you feel this is an approach that might works for you. Read through the notes, highlighting sections that you feel you need to pay close attention to. You might want to consider highlighting important parts of the marking scheme. 

When I start marking, I always begin with a new printout of the tutor notes. I usually print them double sided, with two pages on a side, just to save a bit of paper, and staple them all together. I also get a printed copy of the TMA questions, so I have them side-by-side. I highlight key sections, but sometimes add my own handwritten notes. By the time I have finished marking, my own set of tutor notes look to be a bit torn and ragged.

Some module teams use the Resources section of the tutor websites share additional resources, such as a link to a set of frequently asked questions, or FAQs, or a set of links to any other documents that may offer further background materials that might help with the marking and the provision of feedback.

Activity

Look for a discussion about one of the TMA questions a forum area. What issues are being discussed? Has the issue been resolved? Have there been any contributions by the module chair or the curriculum manager?

Tutor rooms

Since tutor websites are editable VLE websites, sometimes the module team will add an online room, which can be used to hold module wide meetings. When a module is presented for the first time, the module chair, curriculum manager and other members of the module team will run what is known as a module briefing. This is where the module team highlights some of the key elements of a module design, summarising its structure and assessment strategy.  Module wide meetings may also be sometimes. used to prepare for exam and EMA marking.

Activity

Find out if your tutor website has a module meeting room. If one is available, click on a link that allows you to view a summary of previous recordings. What recordings can you see? Do you notice a recording of any module briefing?

A note about Netiquette

The tutor websites forums are incredibly helpful. If you have a question, no matter how difficult, invariably there will be some tutors who will be able to offer some practical advice to help you out. The tutor forums only work when everyone is willing to share experiences with each other. If you post a question to the tutor forums, do be prepared to answer other questions that are posted. The effectiveness of these spaces relies on everyone being willing to contribute.

Also, if you download a tutorial resource that has been shared by a fellow tutor and wish to modify it, and make use of it in your own tutorial, do acknowledge whoever it was who created the original version. If you do make improvements or enhancements to a resource, do also consider sharing your updated version with your fellow tutors.

Reflections

The tutor website is one of my ‘go to’ places.

I access it before the start of a new presentation and find myself accessing it regularly throughout the academic year, mostly to access, review and respond to posts that are made on the tutor’s forum. I might, of course, access the site to download updates to the tutor notes. 

A tutor website is used as a repository for resources. If you need inspiration for an upcoming tutorial, the Tutor website is likely to contain presentations that have been prepared by the module team and fellow tutors.

It is a place to visit to ask questions and to highlight issues. If you notice an issue with some module materials, or marking guide, to make a post to one of the forums. Similarly, if you have a student asking questions about the module materials, or the module, that you don’t entirely know how to respond to: ask a question. There will always be a response, often within hours of sharing your point or posting your question.

Permalink Add your comment
Share post
Christopher Douce

Curriculum continued

Visible to anyone in the world

A recent blog post I wrote about curriculum highlighted the concepts of programmes and qualifications. This blog post is a continuation of that earlier article, but introduces the various components that makes up a module. 

This article has been written for tutors who might be new to the university, but also might be useful for students too. For those of us who are experienced with OU teaching and learning, much that is presented here will be familiar.

After beginning by introducing some key concepts, I’ll talk through the ‘unboxing’ of four different modules. What is important to remember is that every OU module is slightly different, due to the role it plays with a programme or qualification.

Module components

Every module has an accompanying module website. Some modules will be presented entirely online, which means that all the module materials will need to be accessed through a computer, or a mobile device, such as tablet computer.

Other modules have a module mailing, which means there will be a package of materials that are delivered to students in the post. In some cases, a module mailing will include a number of printed books. These books might include module blocks (I’ll introduce the concept of a block in a moment) and a set of materials that must be read or studied. Sometimes, there might be other resources, such as audio CDs or DVDs, but increasingly audio and visual materials are available through the module website.

Guides

Every module contains three really important guide documents that you should read, and guide students towards:

  • A module guide offer a module specific summary of its most important elements and resources a module contains. 
  • An assessment guide offers a summary of what is assessed, and how it takes place. This can typically be found in the assessment section of the module website, but it can also be sent to you as a separate mailing.
  • An accessibility guide offers guidance for students who might need to access the resources, assessments and resources of the module in different ways.

Module calendar

A really important element of a module is the module calendar which defines the study tempo of the module, highlighting what needs to be studied and when. The module calendar also highlights when the key points of assessments are to take place. The calendar lies at the heart of the module website, and students are also typically sent a copy if it in their module mailings.

Using the module website, students are encouraged to tick off each of their study weeks. In return, they will see how much of a module they have studied, and how much further they have to go. Tutors should, of course, encourage students to regularly refer to their module calendar to make sure they are on track. You could also refer the calendar during tutorials, and within assessment feedback. 

Module books, blocks, and units

Modules are typically divided into blocks. Blocks can be thought of as a significant section of study that addresses a set of related subjects. Blocks contains numbered units, which can be thought of as topics for study.

An OU published book might be an entire OU block, or it might collate a number of related subjects together. For some modules, a block can be thought of approximately 10 points of study, but in other modules, a different structure may be used where chapters (or units) are the dominant component.

Units and chapters contains a number of important elements that tutors need to be aware of. They are typically studied at a particular time, as defined within the module calendar, and typically begin by highlighting a set of learning outcomes. These unit or chapter learning outcomes can, of course, be traced back to module level learning outcomes. It is a good idea to highlight these unit and chapter learning outcomes to students, since they are directly related to assessments.

Units and chapters also contain numbered learning activities. Although these can be easily skipped over by students, these activities are linked to the learning outcomes, and are also implicitly linked to any forthcoming assessments. The aim of the activities is simple: to give students some practice in developing the skills and knowledge that they will need to apply when they get to completing their assessment. Tutors should highlight these activities to students. They may also be useful to mention, and to draw upon, when preparing for tutorials.

Assessments

There are two main assessment components that OU tutors need to be aware of: continual assessment, which takes place during a module presentation, and the examinable component, which takes place towards the end of a module presentation.

Continually assessment takes the form of tutor marked assignments (TMAs) and interactive computer marked assignments (iCMAs). Tutors mark and to provide feedback on student TMAs, and offer help to students who might be stuck on any iCMA questions. Each TMA must be submitted by a student on a fixed date, which is known as a cut-off date. There will be other blogs about what it means to mark TMAs and to provide teaching comments.

The examinable component is either an equivalent of a written exam, or it is something called an End of Module Assessment (EMA). Think of the EMA as an extended assignment, or essay. It differs from a TMA in a few ways: it is longer, it usually accounts for a larger part of the overall module results, and it marked to higher standards than the TMAs. An EMA is typically marked by two tutors.

An OU exam used to be a written exam that took place in a physical examination hall. Due to advances in technology and changes in examination policies, an OU exam is sometimes an assessment you can complete remotely, at a set time, over a set duration.

The key differences between the continually assessed component and the examinable component is that the TMAs are sometimes though as formative assessments (where the assessment is used to facilitate student learning), and the exam bit is a summative assessment (where the assessment is used to determine what has been learnt). 

In the OU, TMAs can be both formative and summative, in the sense that although they are primarily about learning, the results that students gain from completing them also contributes to their overall score.

To pass a module, students need to technically pass both the continually assessed component and the examinable component. Just to add to the richness of this picture, there is also something called the single component assessment (SCA) module, where TMA results and exam results all combine together to form one score at the end. If single component assessment isn’t use, the student’s results is limited to whatever their highest score is across each of those two main components. Typically, the exam scores are slightly lower than the TMA score.

When it comes to module materials, tutors need to be aware of two key documents or resources that are usually found within the module website: the assignment booklet (which is a version of what tutors can see under the assessment bit of the module website), and the assessment handbook. The assignment booklet summarises the TMA, and the assessment handbook tells everyone what the assessment strategy for a module is. 

It is important that tutors know what the assessment approach for their module is, and how it works, since this is something that students will ask about, and this is something that you can mention during an introductory tutorial.

Module website

A module website is accessed through a student’s StudentHome page. The module website presents the module calendar. In turn, this provides clickable links to materials that should be studied and activities that need to be completed. 

The module website is designed to be used alongside any printed materials a student has received. Sometimes there are extra materials on the website that are not in the module materials. The exact balance of what is available online, and what is provided through printed material depends on the module. Typically, the module team uses the module website to share learning materials that are likely to change regularly.

The module website presents five clickable headings: assessment, tutorials, forums, resources and news. There is also a useful search tool which enables students (and tutors) to search for texts and terms that are used, defined and referred to in the module materials. 

Assessment

This takes students (and tutors) to pages where the TMAs and iCMAs are presented. This section also shares any additional supporting materials which students might need to complete the assessment, the module assessment strategy which students need to be aware of, and accompanying academic conduct policies. There is also information about the exam and associated revision materials. Do encourage students to look through this section, paying particular attention to deadlines.

Tutorials

This section is about online tutorials. It serves a couple of purposes. It is the route through which students access online rooms to attend online tutorials. There are different online rooms for different purposes, which will be explained a bit later on. The tutorial section also allows students to watch tutorial recordings. Tutors should encourage students to this page to attend online tutorial, and also to listen to past recordings. There is also a link between this section and the tutorial dates section of a student’s StudentHome page through something called the university Learning Event Management system.

Forums

Forums can be through of an online noticeboard where discussions can take place. The university provided online forums before the emergence of discussion and sharing spaces that are now available on social media platforms. A number of different forums can be found on a module website: there are tutor group forums, module wide forums, and even assessment specific forums. There also may be forums used to facilitate online group work. 

The exact choice and use of the forums will depend on the module team. Tutors should make use of their own forums, and encourage students to subscribe to updates. More about forums will be covered in a later section. 

Resources

The resources section enables students to access the materials that are shared through the module calendar. In addition to module materials, the resources section shares the following:

  • Guides: module guides, accessibility guides and any software guides.
  • For level 1 modules, there might be ‘getting started’ guides. These couple of pages highlight how to login to Student Home, the importance of the module website, and the study calendar.
  • Links to subject or discipline websites.
  • Useful module resources, such as indices and glossaries.
  • Links to online software tools that might be needed as a part of module study.
  • If appropriate to a module, information about how to download software and tools that students might need during their study.

At the time of writing, the module resources page offered two buttons: a download button, and a library resources button. 

The Downloads button takes students to a page where they are able to download learning resources in a number of different formats. There are typically Microsoft Word versions, different types of ePub files (which are used on e-readers), and PDF files. The reason for these formats is simple: in some circumstances, and for some students, some formats work better than others. Word versions, for example, can work well with different types of assistive technologies used by students with disabilities. Tutors should encourage students to use the different formats that are available to them, to find a study approach that meets their needs.

The Library resources page shares a set of articles that have been curated by both the module team and the library. This might include additional reading, such as academic articles, which complements the module materials.

It is worth nothing that glossaries serve a very practical purpose: they share official definitions of concepts and ideas from the module team. If an exam question asks for a definition of a term, the module team is invariably asking a student for a definition which is similar to the one that is defined in the module glossary. 

News

It is important to occasionally review the news section, and also encourage students to do so. It offers mix of helpful announcements from the university, which might be pointers towards university wide study events, and module specific announcements. A module chair and curriculum manager might use the news section to remind students about module wide lectures or tutorials, or to let students know about any issues, such as TMA or module material corrections.

Activity 1

Look through the resources section of your module website. Take a few moments to familiarise yourself with all the resources that can be accessed through the page. Click on the Downloads button. What different filetypes can you identify? How do you think you might make use of these resources with your own teaching? What might you tell students about the different types of resources that are contained within the downloads section? 

Exploring module resources

Each module uses a unique combination of resources and materials. This section takes you through a non-exhaustive list of some of the different types of resources that may be introduced to students through the module guide.

Software

Sometimes students are required to download, install, and use bits of software. For computing modules, this might include programming tools and network simulators. Design students might need to download mind mapping tools which are used to express their design thinking. Students studying electronics might need to download circuit simulation software. There is, of course, an expectation that students will be able to write their assignments using a Microsoft Word compatible word processor and submit them electronically through the eTMA submission system.

Online tools

In many cases the software that students need is available entirely online. Design and Computing students are likely to use something called Open Design Studio, which enables students to share their work with other students as a part of group projects. Computing students may use programming notebooks and reserve time to remotely configure physical networking equipment that is located on campus. Science students will be directed towards online laboratories which are made available through the Open STEM Labs. Depending on what they study, science students may also have access to virtual microscopes.

Library resources

The university library, which is accessed entirely online, is an amazing resource. Through the Library resources link, module teams may direct students to articles that are made available through the library. For arts modules, for instance, students can be directed to video archives, such as Drama Online, where they may access plays and films. Students in computing modules might be directed towards online versions of popular computing textbooks. Through the library, students can also access well known external resources, such as the Oxford English Dictionary. The library also provides access to digital versions of textbooks. If students are encouraged to carry out wider reading, do direct them towards the library.

Readers and other books

Sometimes module teams might collate resources together into a book or booklet, which may be included within a module mailing. The module materials will refer to sections in the reader, and may be used as source materials for assessments. In some cases, a published textbook will play an important role within a module. If this is the case, these textbooks will be sent as a part of the module mailing. It is likely that only certain parts of these textbooks will be used; always be directed by what guidance is offered in the module materials.

Set texts

Some modules need students to buy some additional books. This is typically the case for literature modules, where there is a reading list. Some good advice for students is: don’t buy everything in one go, since the module materials might use some books for one presentation, and a different set of books for another.

Print on demand materials

Different students have different study preferences. In the case where a lots of study materials are provided through a module website some students might be content access material directly through the module website. Other students, however, may much prefer to work with printed versions.

If a printed copy of some module materials is required, students can easily get a printable version of learning materials by clicking on a ‘view as single page’ link, and print out what they need. If someone hasn’t got access to a printer, and would prefer to get a printout of the study materials that are available through the module website, the university provides a ‘print on demand service’ where students can pay an additional fee to get a neatly printed version of the materials that are available through the module website.

Module accessibility

Accessibility is a term that can be understood in different ways; it can be understood in either a practical sense, or a technical sense. 

For a module to be accessible, students must be able to attain the learning aims that are expressed through its learning outcomes. In some cases, students might need additional support or technology to access, participate in, and contribute to learning activities.

Accessibility is a topic all of its own, and will be addressed in another section. Before this is explored in greater depth, it is important to highlight that each module has an accessibility guide. This offers practical (and technical) advice to students. To help students, tutors should also take the time to review the module accessibility guide.

Activity 2

Find the accessibility guide for your module by going to your module website. Is there anything specific to your module? If your module uses software or online tools, what does it say about them, and what elements might you have to help students with? Does the guide highlight different formats of module materials?

Examples

In this section, we look at some modules. Although these modules may be unfamiliar to you, there should be similarities with the modules that you are tutoring.

Example 1: A111 Discovering the arts and humanities

Using a university fee waiver, I studied A111 Discovering the arts and humanities, which has been produced by the Faculty of the Arts and Social Sciences. For students who are studying the humanities, this will be their every first OU module.

A111 is a 60 point module. The point scheme is explained later, but essentially 60 points means that it is worth half a year of full time study, when compared to a face-to-face university. A111 starts once a year, in October.

When opening the module mailing, I found the following items:

  • Quick start guide 
  • Welcome Letter
  • Book 1: Reputations
  • Book 2: Traditions 
  • Book 3: Crossing Boundaries  

The quick start guide is four sides of A4, which has the bold title: Read me first. It mentions the student’s university login code, provides an address to the Student Home website, and highlights the module website. It then goes onto mention many of the elements highlighted in this guide: the module calendar (which is known as a study planner), forums, the assessment guide, learning events (tutorials) and, of course, the role of the tutor.

Rather than being organised in terms of blocks, this module is divided into three sections, each of which relate to each of the published books that have been sent to students. The study is divided into weeks, where students are directed to carry out reading and complete activities to help them to prepare for the tutor marked assessments. During their study, they need to refer to chapters within the book, and the material that accompanies each study week.

Depending on their path through this module, students may need to buy up to three set texts, of which, only a relatively small element of each of the books are needed. During the module, students will be also directed to listen to some audio recordings, and watch some recordings of some plays through a service called Drama Online, which is provided by the university library.

Students need to complete 6 TMAs, which is typical for 60 point modules. Rather than having an end of module assessment (EMA), A111 has something called an emTMA; an end of module tutor marked assessmens. Each TMA, including the emTMA, contributes between 10 and 20% of the overall module result. There are also a series of iCMAs, interactive computer marked assessments. To pass A111 students need to gain a combined score of 40% or over across all the TMAs and must get an overall score of over 50% on the iCMAs.

Students can gain one of three different results from level 1 modules: distinction, pass, or fail. Students are awarded distinctions if they gain an overall score of 85%, but this exact score can vary slightly, depending on whether any statistical adjustments are made to ensure consistency between student groups. Since level 1 modules are all about the development of skills, all a student needs to do to progress to the second level, is to pass A111.

Example 2: TM112 Introduction to Computing & IT 2

TM112 Introduction to computing IT 2 has been produced by the School of Computing and Communication, which is based in the Faculty of Science, Technology, Engineering, and Mathematics (STEM). Unlike A111, TM112 is a 30 point module. Students typically study TM112 after having studied TM111 Introduction to Computing and IT 1, which is also a 30 point module.

Like A111, TM112 students are sent three books. These are imaginatively titled: Block 1, Block 2 and Block 3. These blocks are not named, since this module structured around three repeated themes: essential information technologies, problem solving with Python, and information technologies in the wild, which are featured within each of the block.

The module website is split into weeks. Each week has a summary of online activities. These may involve reading some materials, completing quizzes, or watching video materials. Students may also be directed toward programming tasks and exercises.

Since one of the aims of this module is to introduce students to computer programming, students are provided with some quick start guides to help to get them started. There are also some additional materials to help students who might struggle with numeracy. TM112 tutors should be able to direct students towards these different resources.

Since TM112 is a 30 point module, students need to complete 3 TMAs; one for each block. To pass the module, like A111, students need to get an overall score of at least 40%. The first TMA accounts for 15% of the overall score. TMA 2 accounts for 35% of the overall score, and the final TMA accounts for 50%. An additional complication is that students do need to gain a score of at least 30% in TMA 3 to demonstrate they have met all the module learning outcomes.

Like A111, TM112 uses interactive questions, but uses them in a slightly different way. Unlike the A111 iCMA question results, which feed directly into the module results, students are asked to provide evidence of answering some of the questions in their TMA answers. Also like A111, students can gain the overall results of distinction, pass or fail, from studying TM112.

Example 3: M250 Object-Oriented Java Programming

M250 Objects First with Java is a 30 point second level Computing module. Some students who find their way to M250 have previously studied TM112. Since M250 is a second level module, module results directly contribute to a student’s degree classification. In other words, the scores they gain in this module begin to matter.

M250 students are sent a textbook: Objects First with Java. This book is well known by Java educators and is used in many other universities. Rather than having any OU published books, all the module materials that students need are presented through the module website.

Like the other modules, M250 has a clear study calendar. What differs from other modules is that students are directed to carry out reading and activities from the set text using materials which are known as chapter companions. The companion documents can be through of as an equivalent of an OU lecturer taking students through the bits of the text that they need to be familiar with.

The module and set text makes use of a bit of software called BlueJ, an integrated development environment (IDE) that has been designed for students who are learning the concepts of Java and object-oriented programming. During the course of the module, students will need to spend a lot of time using BlueJ, where they will get to solve programming puzzles and, of course, make mistakes.

The set text makes use of external resources, such as YouTube screen sharing videos, where students are shown how BlueJ and the Java programming language works. The idea is that students should be able to copy what is done in the videos to help them to develop knowledge, skills and understanding. In addition to each of the chapter companions, are required to complete a number of iCMAs. These iCMAs test understanding of key terms, and understanding of concepts that are introduced by the set text chapter, and accompanying chapter companions.

A difference between M250 and other modules is that students can submit bits of programming code to be evaluated by the module website before they officially submit section of their work through a tutor marked TMA. Students can, in turn, get an indication about whether fragments of code are likely to be correct, allowing students to build up their confidence. There are also some resources and guides that are not found in other modules, such as a software guide, and a Java language guide.

Like other modules, M250 applies a single component assessment strategy, which is summarised an M250 Assessment Strategy document which can be found under the assessment bit of the module webiste. The TMAs account for 50% of the overall module result, and the exam accounts for the other 50%. TMA 1 accounts for 15% of the whole module result, TMA 2 accounts for 15%, and TMA 3 accounts for 30%. Students must submit an exam and gain at least 30%, and an average score of 40% overall to pass the module. Curiously, at the time of writing, TMAs are marked out of a score of 150, which is converted to a percentage. The module iCMAs are formative and do not contribute to an overall module result.

Example 4: TM354 Software Engineering

As the module code suggests, TM354 Software Engineering is a level 3 module, which means that it is equivalent to final year study at a brick university. Like other computing modules, TM354 is a 30 point module.

The module is divided into three blocks, which are also printed books. Version of these printed books are also available through the resources section on the module website. The module blocks are organised into sequential themes. The first block is entitled ‘from domain to requirements’, the second ‘from analysis to design’, and the third is called ‘from architecture to product’. Each block is divided neatly into 4 units, or sections.

This module requires students to make use of a programming tool, but one that is different to the one that is used with M250. It also asks students to use something called a ShareSpace, an online tool where students are to share some of their software designs with other students, and comment on the work of others.

Like all the other modules, TM354 has a very clear study calendar, which is divided into weeks. For every week, there is a study guide, which refers students to sections of the printed text, but also guides students towards readings which have been made available by the module team and the library. All the units that are provided within the printed module materials are also available through the module website.

Students need to complete three TMAs, one for each block, and sit an end of module exam. Unlike the other modules mentioned here, TM354 does not use single component assessments. Students need to gain an average of 40% in both the continually assessed components (the TMAs) and the examinable component (the exam). The overall score is limited by the lowest score of these components.

Activity 3

What have you received in your module mailing? Open up your view of the module website and look at the module calendar. Can you see how the different components you find relate to the module calendar? Click on the resources link on the module website, and identify where you can find electronic versions of the module materials.

Activity 4

Find the assessment guide. What are the main assessment components for your module? What contributions do each of these components make? What would you say is the largest component? What does a student have to do to pass the module? Does your module apply a single component assessment strategy? Do your students need to submit their final assessment?

Reflections

This blog is one of a short series that introduces curriculum. Before this one, there was a blog about qualifications, and what these are. I do expect to be writing another one at some point. Eventually I’ll collate all these together into a bigger resource.

I’m always struck by how many resources there are on a module website.

When beginning to teach on a new module, I’m often very strategic in terms of what I look at. I make sure I know what the key dates on the module calendar are. I would then have a good read of the module guide, read through the accessibility guide, and then have a read through the assessments. This will, of course, primes my reading for when I get to the module materials. I also get printouts of these guides so I can scribble on them. A lever arch file is my friend.

As well as there being a module website, which is student facing, every module has a tutor website which is for tutors and the module team. They key elements of the tutor’s website will be the focus of another blog.

Permalink Add your comment
Share post
Christopher Douce

Generative AI and the future of the OU

Visible to anyone in the world
Edited by Christopher Douce, Tuesday, 20 Jun 2023, 10:24

On 15 June 2023 I attended a computing seminar about generative AI, presented by Michel Wermelinger.

In some ways the title of his seminar is quite provocative. I did feel that his presentation relates to the exploration of a very specific theme, namely, how generative AI can play a role in the future of programming education; a topic which is, of course, being explored by academics and students within the school.

What follows is a brief summary of Michel's talk. As well as sharing a number of really interesting points and accompanying resources, Michel did a lot of screensharing, where he demonstrated what I could only describe as witchcraft.

Generative AI tools

Michel showed us Copilot, which draws on code submitted through GitHub. Copilot is said to use something called OpenAI Codex. The witchcraft bit I mentioned was this: Michel provided a couple of comments in a development environment, which were parsed by the Copilot, which generated readable and understandable Python code. There was no messing about with internet searches or looking through instruction books to figure out how to do something. Copilot offered immediate and direct suggestions.

Copilot isn’t, of course, the only tool that is out there. There are now a bunch of different types of AI tools, or a taxonomy of tools, which are emerging. There are tools where you pay for access. There are tools that are connected with integrated development environments (IDEs) that are available on the cloud, and there are tools where the AI becomes a pair programmer chatbot. There are other tools, such as learning environments that offer both documentation and the automated assessment of programming assignments.

The big tech companies are getting involved. Amazon has something called CodeWhisperer. Apparently Google has something called AlphaCode, which has participated in competitive programming competitions, leading to a paper in Nature which questions whether ChatGPT and AlphaCode going to replace programmers? There’s also something called StarCoder, which has also been trained on GitHub sources.  

AI can, of course, be used in other ways. It could be used to offer help and support to students who have additional requirements. AI could be used to transcribe lectures, and help student navigate across and through learning materials. The potential of AI being a useful learning companion has been a long held dream, and one that I can certainly remember from my undergraduate days, which were in the last century.

Implications

An important reflection is that Copilot and all these other AI tools are here to stay. It wouldn’t be appropriate to try to ban them from the classroom since they are already being used, and they already have a purpose. Michel also mentioned there is already a textbook which draws on Generative AI: Learn AI-assisted Python programming

Irrespective of what these tools are and what they do, everyone still needs to know the fundamentals. Copilot does not replace the need to understand language syntax and semantics and know the principles of algorithmic thinking. Developers and engineers need to know what is meant by thorough testing, how to debug software, and to write helpful documentation. They need to know how to set breakpoints, use command prompts, and also know things about version and configuration management.

An important question to ask is: how do we assess understanding? One approach is an increasing use of technical interviews, which can be used to assess understanding of technical concepts. This won’t mean an academic viva, but instead might mean some practical discussions which both help to assess student’s knowledge, and help them to prepare for the inevitable technical interviews which take place in industry.

New AI tools may have a real impact on not only what is taught but how teaching is carried out, particularly when it comes to higher levels of study. This might mean the reformulation of assignments, perhaps developing less explicit requirements to expose learners to the challenge of working with ambiguity, which students must then intelligently resolve.

Since these tools have the potential to give programmers a performative boost, assignments may become more bigger and more substantial. Irrespective of how assignments might change there is an imperative that students must learn how to critically assess and evaluate whatever code these tools might suggest. It isn’t enough to accept what is suggested; it is important to ask the question: “does the code that I see here make sense of offer any risks, given what I’m trying to do?”

A term that is new to me is: prompt engineering. This need to communicate in a succinct and precise way to an AI to get results that are practical and useful within a particular context. To get useful results, you need to be clear about what you want. 

What is the university doing?

To respond to the emergence of these tools the university has set up something called the Generative AI task and finish group. It will be producing some interim guidance for students and will be offering some guidance to staff, which will include the necessity to be clear about ethical and transparent use about AI. It is also said to highlight capabilities and limitations.  There will also be guidance for award boards and module results panels. The point here is that Generative AI is being looked at. 

Michel suggested the need for a working group within the school; a group to look at what papers coming out, what the new tools are, and what is happening across the sector at other institutions. A thought that it might be useful to widen it out to other schools, such as the School of Physical Sciences, and any others which make use of any aspect of coding and software development.

Reflections

Michel’s presentation was a very quick overview of a set of tools that I knew very little about. It is now pretty clear that I need to know a lot more about them, since there are direct implications for the practice of teaching and learning, implications for the school, and implications for the university. There is a fundamental imperative that must be emphasised: students must be helped to understand that a critical perspective about the use of AI is a necessity.

Although I described Michel’s demonstration of Copilot as witchcraft all he did was demonstrate a new technology.

When I was a postgraduate student, a lecturer once told me that one of the most fundamental and important concepts in computing was abstraction. When developers are faced with a problem that becomes difficult, they can be said to ‘abstract up’ a level, to get themselves out of trouble, and towards another way of solving a problem. In some senses, AI tools represent a higher level of abstraction; it is another way of viewing things. This doesn’t, of course, solve the problem that code still needs to be written.

I have also heard that one of the fundamental characteristics of a good software developer or engineer is laziness. When a programmer finds a problem that requires solving time and time again, they invariably develop tools to do their work for them. In other words, why write more code than you need to, when you can develop a tool that solves the problem for you?

My view is that both abstraction and laziness are principles that are connected together.

Generative AI tools have the potential to make programmers lazy, but programmers must gain an appreciation about how and why things work. They also need to know how to make decisions about what bits of code to use, and when. 

It takes a lot of effort to become someone who is effective at being lazy.

Permalink Add your comment
Share post
Christopher Douce

Ethics support for projects: Which studies need review, by whom and why?

Visible to anyone in the world

On 15 June 2023, I went to another academic professional event. This one was all about ethics and ethical approval. In some respects, it directly follows on from the previous blog, which was all about how to write a 4* research paper.

The session was facilitated by Alison Fox, Chair of Human Research Ethics Committee, and Bart Gamber who is a Student Research Manager for the student research project panel (SRPP). Alison is based in ECYS, the school of Education Childhood Youth and Sport.

The aim of the session was to present an overview of ethics mechanisms for researchers who make use of human participants, and to share something about who, how and why things work. Another aim was to share something about the types of studies that may require ethical approval.

Introducing HREC

HREC is an abbreviation for the Human Research Ethics Committee. We were shown something called the Research Ethics Landing Page, which offered a whole set of links which relate to the different parts of the university which support both ethics and research. An important element of this was a flowchart which highlights what needs ethical review.

Different types of research were mentioned: evaluation research (of services, procedures and policies).; audit research; market research; research. Each of these might necessitate ethical consideration. If OU students are involved with any type of study, this necessitates a referral to the SRPP team. Also, if a study involves more than more than 30 members of staff, researchers must consult the Staff Survey Project Panel (SSPP).

An important point was made about the use of data. Audio recordings that are collected during a study is considered to be personal data, which means that it must be manged carefully. This leads us to consider the different places of support that we may need to draw upon. 

The teams we might consult, include:

  • Data projection team; to gain advice about how to record information assets.
  • Information security team; if wanted to use particular platforms.
  • Library research support team; to consult about how data is stored, how it can be retrieved.

A tip: apply to each of these in parallel.

Two ways to apply to HREC were highlighted. The first was a checklist, which is submitted to the committee. This has a 7 day turnaround time. If your project is a high risk application, a full HREC application can be submitted, then there is a longer 3 week turnaround since it is submitted to two reviewers.

Introducing SRPP

Next up was a summary of the SRPP, which is an abbreviation of the Student Research Project Panel. SRPP is the mechanism used by researchers to gather names and identifies of students you might wish to invite as participants to different kinds of studies. SRPP is important. It is a gatekeeper; you have to go through it to access any of the OU’s students. The reason why it exists is simple: it presents the same students from being approached time and time again. It’s function is pretty simple too: you give it a criteria, and it gives you back identities of those you are allowed to contact.

We were introduced to the SRPP internal website, and shown an online application form. This form contains section where you describe the methodology of your study, a description of the sample of students you wish to involve, a confirmation that you have engaged with HREC, and have taken into account information security, and data protection. 

As the site SRPP site develops, there is the intention of providing examples of previous submissions.

Tip tips

Towards the end of the session, we were given a number of top tips. What follows is an abridged (and edited) version:

  • Start early and expect a dialogue with the teams, and build this into any timescales and plans.
  • Contact teams before submitting applications to get advice.
  • If collecting personal information, you need an asset register.
  • Consider everything from a participants’ perspective; think about their concerns.
  • Consider what data is being collected, how it will be held, destroyed and how consent might be withdrawn.

If you are getting started with a design, visit the research journey landing page for help and guidance.

Undergraduate and postgraduate projects

During this session, then following important point was made: everything described earlier relates to research that is carried out either by doctoral students, or academic staff. 

Students who are carrying out projects that are a part of taught undergraduate and postgraduate qualifications do not need to make HREC submissions or interact with any of the organisational units that were mentioned earlier. This is all to do with insurance.

Students who are completing undergraduate projects, or are writing dissertations that may necessitate carrying out a small study must follow the ethical guidance that is presented within the modules that they are studying. 

Reflections

It’s been a while since I’ve been to a session about research ethics. It is interesting to see how things have developed. Notably, there is a lot more emphasis on securing and holding of data. This is, of course, a very welcome development. The advice “make sure you speak with each unit” early on in the research journey is good sound advice.

One the topic of a theoretical research journal, we were also introduced to a resource that was called “Research Journey”. This resource, a web page, was all about educational research with students, which is where SRPP comes in.

An interesting point that I have noted was: most scholarship projects won’t need to go down the road of HREC, but some academic publishers do require evidence of engagement with ethics panels before research is published. As a reviewer, I certainly look to see the extent to which ethics is mentioned within the articles that are submitted.

The themes and issues that have been mentioned have wider relevance. It was mentioned that both undergraduate and postgraduate students don’t need to submit anything to HREC. Being a tutor on an undergraduate module, where students are asked to consider ethics from a number of different perspectives has made me reflect that perhaps I ought to be sharing a bit more about the kinds of ethical issues they should consider. I feel another blog about TM470 might be needed.

Permalink Add your comment
Share post
Christopher Douce

Writing a 4* paper for the REF

Visible to anyone in the world
Edited by Christopher Douce, Friday, 30 Jun 2023, 08:26

On 14 June 2023, I attended a professional development event that was all about the previous REF, the next REF, and the sharing of tips about how to prepare what is called a 4* paper. The event was facilitated by Rachael Luck, who is a lead for a design qualification, and Toni Gladding.

The REF is the UK Research Excellence Framework, which is a controversial system that ranks UK universities in terms of the quality of the research that they carry out. It was interesting to hear that both Rachael and Toni were both on review panels for the previous REF.

The most recent REF happened in 2021, and the next one is due in 2028. The broad aim of this session was to begin to think about preparation for the 2028 REF, to begin to consider what a 4* paper looks like, and to have a discussion with colleagues.

What is a 4* paper looks like is, of course, a highly debated and contested question.  A point was: to try to increase quality for next REF, need to be thinking about it, and talking about it early.

The REF score matters. The higher the overall score, the more Quality Related (QR) income (UKRI website) an institution gains from the government. During this session, I learnt there is a multiplier effect, which means that 4* paper attracts 4 times the funding of 3* activity. A small improvement in the number of 4* papers that are published could have a large impact in QR funding. This funding is important since it is used to fund school doctoral studentships and university facilities. This, in turn, can increase the development of the university’s research capacity.

What follows is an edited set of notes I made during the session.

What happened in REF 2021?

University has a code of practice. If someone has a certain amount of research time, has to submit at least one output to REF 2021. There is a long tail of “other colleagues” who were also included. It is the quality of the output from those colleagues who might benefit from additional support. Since the rules for the 2028 REF have not yet been defined (but will be available in January 2024), there is a possibility that a wider group of staff might be included.

In the 2021 REF, 157 universities were assessed. In the OU context (if I’ve noted this down properly), 44% of staff only had 1 output, 10% produced 5 outputs.

What is a 4* output?

Each category of quality assessment has an accompanying “quality descriptor”. A three star paper is considered to be research that “is internationally excellent in terms of originality, significant and rigour but which falls short of the highest standards of excellence”. A 4* bit of research is “beyond internationally excellent”, but I’m not exactly sure what this means.

The university strategy is to maximise QR income, to increase its overall score, to aim to gain higher QR income. A strategy for an individual unit, such as a school, may be to try to gain the highest possible score with a specific assessment area.

An output could be chapters in books, design, exhibitions, journal articles, monographs, performance. This said, the largest and most significant output across universities and all units of assessment (UOA) are journal articles.

Key components of a high quality paper

This section of the session asked the question: what does a 4* paper look like? 

One way to answer this question is to consider what the characteristics of a good journal article might be. A paper should have an eye catching title that has a broad appeal, and a clear abstract which highlights clear research questions, summarises methods, and offers a clear summary of the novel contribution made to knowledge. 

Turning to the body of the article, a paper should clear clearly state research questions, clearly describe the methods that are applied (and share clear citations that offer more detail about them), explain how the research relates to theory, describe research instruments and ethical approach taken, provide details about the data samples, and conclude with acknowledgements. Not having dealt with ethical issues will limit the journals that you can submit to.

An important tip I noted down was: “know about the journal that you’re writing for”. See whether your research or research article is an argument that fits with the aims of the journal. A phrase I noted down was: “papers are not written in the abstract, they’re written with a journal in mind”.

This section of the presentation reminded me of a blog article that I wrote some years back, which had the title Getting published in Open Learning. Open Learning is, of course, a journal that I co-edit with two other colleagues. The points that were made about the clarity of papers is really important. A suggestion for anyone who is interested in writing papers, is to get involved with the peer review process in some capacity. This way you can learn more about how everything works.

During the session, the notion journal impact factors were mentioned, which are known as bibliometrics which highlight how influential a publication is within an area of research. When it comes to the REF, it isn’t just the impact factor of the journal that matters; the assessment of quality of paper is independent of the quality (or impact factor) of the journal. This is linked to something called DORA, which is an abbreviation of: Declaration On Research Assessment (DORA website), which the OU has signed up to, along with other higher education institutions (HEIs). 

What can we change?

Research can be thought of in different ways. Research is, of course, carried out by individual researchers and academics, but since much research (especially within STEM require collaboration, a wider perspective is necessary. Individual academics should develop their own research strategies (which could be shared with others), but also strategies should be defined by units, such as schools, which then should be linked to REF units of assessment. This also links to the importance of developing a research culture.

An interesting question was: what practical things could be done?  Some suggestions include working with others to ensure thar articles are thoroughly proofread before submitting to journals, perhaps setting up internal peer review processes within research groups, writing articles with co-authors, and setting up mentoring schemes with colleagues who are new to research.

The discussion of papers led onto a discussion about the challenges that accompany getting articles published in open access journals. Open access publishing means that the readers do not pay for access to research articles. Instead, researchers and writers pay. This means that authors may be asked to pay what can amount to a substantial publishing fee. This can limit the extent to which researchers are able to publish unfunded research, such as personal projects.

A suggestion is to always consider the cost of publishing fees when writing and preparing research bids, to make sure that they are considered during the budgeting. Also, if research is funded by a UK research funding council, the university library has an agreement that they will cover publication fees. 

By way of contrast, Open Learning offers a hybrid scheme. The editors of Open Learning chooses to ‘open access’ one article per issue. Individual authors can also secure open access by submitting what amounts to a publication fee, but it is typically less than journals that adopt a completely open access funding model. The advantage of this approach is that it enables institutions that do not have extensive research budgets to disseminate their research. An important point here is: pay attention to the terms and conditions that relate to the journal that you’re hoping to publish through.

One of the final comments I noted was: there are tensions between helping those currently work on 3* papers, to help them to submit 4* paper, and helping those with little research time to start publishing. A big win for the university might be to enable a wider group of staff to be included in the REF. This also links to the tension between supporting the individual researcher, and supporting the institution as a whole to gain an overall higher rating.

Reflections

I don’t like the REF for the simple reason that terms such as quality and excellence are dangerously slippery terms. Also, research is something that takes place over an extended period of time, and certainly not across a neatly defined seven year cycle. I’m also grumpy after learning that 4* papers have a multiplier effect on research income for the simple reason that universities, schools and individuals who are already doing excellent research are likely to gain even more income to do even better research, with more resources. This multiplication factor is not progressive, and it feels far from equitable. Institutions with a lower research ranking will, of course, struggle more to make an impact in comparison to, say, Russell Group universities.

I come to this topic having struggled to build a research strategy and profile. As a staff tutor, half of my time is dedicated to academic leadership and management, and the other half is dedicated to ‘academic stuff’, which means either working on module teams or working on research. If I have module team (teaching) responsibilities, this means that less of my time is available to research, and what really helps with research is building those close collaboration with colleagues, and all this takes time.

Over the last few years, and to this day, a lot of my time has been spent dealing with internal institutional changes (mainly, the new AL contract), of which a lot still remains to be figured out and understood. Whilst this does sound a little grumpy, dealing with the practicalities of my staff tutor day job leaves very little practical time to carry out disciplinary research. Whilst I’m not contractually obliged to make a REF submission, the idea of leading a submission of an article feels current unattainable, never mind the notion of producing an article that is “beyond internationally excellent”.

What are the answers? One of the obvious answers is to work on research culture. This requires the involvement of multiple stakeholders, at multiple levels. It means facilitating conversations, and learning about the interests of others. It means getting involved and encouraging others to get involved. It means joining research groups, and being patient when listening to the perspectives, challenges, and experiences of others. This is also, of course, made harder when everyone is working at a distance.

Two thoughts that I return to regularly are as follows. The first thought come from the words of a former head of school who said: “if you have two reasons to do something, there is a greater likelihood that you’ll get that thing done”. Following this though, the accompanying thought is: “try to align everything together, into a personal strategy”. It is this alignment that I’m trying to do, and this may well mean saying “no” to some things.

Permalink Add your comment
Share post
Christopher Douce

Critical thinking and writing (Intermediate)

Visible to anyone in the world
Edited by Christopher Douce, Wednesday, 14 Jun 2023, 08:32

On the evening of 13 June 2023, I attended a university wide session about critical thinking and writing, which was delivered as a part of the Student Hub Live programme. The event was facilitated by Margaret Greenhall, study skills specialist, and OU tutor in Science, and was supported by another tutor, Nicky Mee. An edited recording to this session is available through the Student Hub Live website.

Margaret presented what could be described as a “a buffet of ideas” to help students to work through ideas and concepts they are presented with during their studies. Whilst it is intended to be a starting point, the buffet presents some really useful tools that could be used by anyone who is approaching the study of a new subject. It may also be useful for anyone who needs to do a review of a topic, or to carry out a literature review.

We were given a lot of notes to download, which shared some of the key concepts which I hope to summarise through this short blog.

What follows is my own notes from the session, which are presented, of course, from my own perspective, complete with my own understandings (and misunderstandings!)

What does critical thinking mean to you?

We were asked a question, and invited to respond by giving answers in a text box. We were then led towards a suggestion, that perhaps critical thinking could be thought of a pyramid, or hierarchy, which has a number of levels, such as:

  1. Content
  2. Validity
  3. Relevance
  4. Criteria
  5. Evaluation

These concepts could be unpacked further, by asking accompanying questions, such as:

  1. What? What is the content?
  2. Who? Who wrote it?
  3. Why? Why is it relevant to you and the problem?
  4. What? What is important with what you have found?
  5. How? How does it connect to other things and how is it useful?

In the following sections, I summarise how each of these key points were broken down.

Content: What?

A question I noted down during the presentation as: is this all about reading the information? We were also asked a question during the session: what do you do before you read the course materials? This question led to a short activity, where we were shown sections of text.

There was an important point which was made here, which is: critical thinking starts before you read the assessments; you’re gathering criteria before you start. Critical thinking before reading helps to prime oneself with respect to what things we will be looking at.

I made a note of some tips: read the TMA first, write down your own questions, look at big picture and detail, leave things overnight before reading in detail, and then go back to review the material. I might have imagined this, but I’m pretty sure that spider diagrams were mentioned too.

Validity: Who?

In other words, where did the information come from? This connects to the source of the material. Who wrote it? Did it come from a reputable source.

The tool that we were introduced to help us think about validity was PROMPT: Provenance, Relevance, Objectivity, Method, Presentation, Timeliness. There is some accompanying OU materials about PROMPT on the OU website.

Another tool, which was gently rephrased as being ‘CAARP’ serves a similar purpose: CRAAP: Current, Relevance, Authority, Accuracy and Purpose (University of the West of Scotland)

Relevance: Why?

Simply put, why is something important? It is very well looking at an article and thinking you know something is important, but why is it really important? 

One tool is to keep continuing the ‘why’ question 5 times over. When you get an answer to the first ‘why’ rephrase it, and ask another ‘why’ question, until you create a chain of five of them. This might be the real reason why something is studied or examined. By rephrasing question, you dig deeper into the issue.

Criteria: What?

What is important? In other words, how do you make an evaluation about whether a particular article or source (or topic) is important in the context of the problem? A meta question (questions about questions) is: what questions would you ask what is important?

An interesting tool that was shared was something called the CIA Phoenix list (Wikiversity).

Three of the first questions from this list are: Why is it necessary to solve the problem?, what benefits will you receive by solving the problem?, and what is the unknown? The idea is to use this list to try to dig deeper to evaluate a problem. There is also a list of questions that relate to evaluating a plan.

One further question was asked, which was: which question (on the Phoenix list) is your favourite?

Evaluation: How?

How does everything all connect with each other. In other words, if you have found something out, how can you use it? When it comes to being a student, an evaluation is often expressed through a tutor marked assessment, which is often in the form of an essay.

One of the tools that might be useful for essay writing is something called PEEL, which is an abbreviation for: Point, Evidence, Explain, Link. In other words, you make a point, you evidence that point (with a reference), explain to the reader what it is (and why it is important in the context of an argument), and then add some words which link to the next paragraph. There could well be one PEEL per paragraph.

Another tool was introduced was PESELS, which is an abbreviation for: Point, Explain, Support with evidence, Evaluate (for or against), Link, Signpost to the next paragraph.

Reflections

I haven’t ever come across this particular pyramid before, but I do know of another (and arguably similar) pyramid, Bloom’s taxonomy (Wikipedia) which is likely to be more useful in terms of thinking about our own understanding and learning of a topic, as opposed to surveying, and reading. 

I had heard of the PEEL approach to essay writing, but I had not heard of the PESELS abbreviation; this just goes to show that there are always things to learn! Another tool that was unfamiliar to me was the Phoenix list, which looks quite useful in terms helping to reflect on what has been found about a subject. A lot was covered in a short time, and I will certainly have come round for another pass of this buffet.

The closing points were helpful, which included: critical thinking starts before reading, it takes time, and you need to spread it out over an extended period of time; it is something that can take days, since you need time to let things sink in.

It was also a quite a busy session, with up to 120 students attending. The session is, of course, one of a series on Student Hub Live. A later section will focus on the evaluation stage of the pyramid model. It was also interesting to learn about what general study skill support is available for students. There are, of course, recordings of other sessions that are available.

A final point: please don’t use Wikipedia in formal pieces of writing; always consider the validity of your sources. Formal references from the university library presented using the Harvard format, as described in CiteThemRight is always the way to go. 

Acknowledgements

Many thanks to Student Hub Live, and to Margaret Greenhall who was the presenter and facilitator of this session. The structure of this blog completely mirrors what she presented. I also have quoted from her directly when preparing these notes. I did try to find references for each of the tools that are mentioned in this blog, but I haven’t managed to track these down.

Permalink Add your comment
Share post
Christopher Douce

Preparing to chair TM354 Software Engineering

Visible to anyone in the world

Over the years I’ve had a connection with a number of Computing modules. I started as a tutor on M364, which then became TM356. When I became a staff tutor, I joined the TM352 for a short period of time, where I made a couple of very minor contributions, and TT284, where I offered some suggestions about web development frameworks. Most recently, I’ve been helping behind the scenes on TM112.

In the coming months, I’m going to be taking over the chairing TM354 Software Engineering. This module closely aligns with some of my long standing research interests. When I was a doctoral student, I studied the maintenance of object-oriented software, during which I looked at the subject of software metrics, where I made a very tiny contribution to the area. After completing all my studies, I worked in industry for a number of years, before returning to the university sector.

In September 2014, I attended a TM354 module briefing, where I wrote a quick summary of all the main components of the module. Since the briefing, I understand that the module has gradually changed and evolved over time.

From time to time, I shall be writing blog posts as an incoming module chair.

Figuring everything out

After a handover meeting, I have the following questions and the following tasks. 

I should add that I have mostly answered some of these questions:

  • Who do I need to speak to, to get things done? I know our curriculum manager, and fellow members of the module team, but there might well be other people who I need to know about.
  • What are the key dates and times by which things need to be done? I think I’ve seen a seen a document that contains the title ‘schedule’.
  • What are the biggest issues and challenges that immediately need to be dealt with? There is a lot going on at the moment in the university; I need to know what to prioritise.
  • What bits of software do I need to know about, and where should I go to find everything out?

Here are my immediate tasks. I have started some of them, but I need to work on others:

  • Acquaint myself with the module guide, assessment guide and accessibility guide.
  • Read all the module materials carefully (there is module mailing that is likely to be coming to me over the next couple of days)
  • Go through all the software engineering textbooks the outgoing module chair has left me.
  • Review all the assessment materials; the exams, the TMAs and and iCMAs.
  • Look at how the module makes use of Open Design Studio.
  • Listen to or watch any podcasts or videos that are used within the module.
  • Identify the file store or file areas that everyone uses to carry out assessment authoring.
  • Learn how much time every module team member has allocated to the module.

Reflections

I view TM354 as a really important level 3 module.

It is also a really interesting subject, since it links many different subjects together. On one hand, software engineering is quite a technical subject. On the other, it is about people and organisations; creating software is an intrinsically human activity. Software engineering processes and tools help to guide, manage and often magnify the creative contributions that people make to the development of software.

I would like to publicly acknowledge the contribution and efforts of our outgoing module chair, Leonor Barroca, who has worked on the module since the first presentation.

Permalink Add your comment
Share post
Christopher Douce

ChatGPT school seminar

Visible to anyone in the world
Edited by Christopher Douce, Sunday, 21 May 2023, 09:49

On 19 April 2023, I arrived slightly late for an online seminar about ChatGPT and generative AI. This blog post share some of the notes that I made during the session. It might be useful to read this post in conjunction with an earlier blog that was written on the same topic that summarises a workshop organised by the OU Knowledge Media Institute (KMI). These notes are pretty rough-and-ready, since they were edited together a month after the event took place.

Seeking opinions

Mike Richards, from the School of Computing and Communications, began by summarising some research that he had carried out with a number of colleagues. Five tutors were interviewed. When it comes to reviewing and marking assignments, it was noted that tutors are sensitive to changes in formatting style, voice and vocabulary.

Tutors rely on module teams and central systems for plagiarism detection, but they can and do pick up on things themselves. ALs don’t like referring students to disciplinary processes. They are cautious; they usually have a very high level of suspicion before they contact staff tutors and invoke the academic conduct processes. In the cases where the identify issues, they take opportunities to make a teaching point to students.

Tutors wish to maintain positive relationships with students, but they are worried about the implications of raising academic conduct referrals and potential professional consequences if they raised unwarranted academic conduct concerns. Of course, there are no consequences for tutors. It is, of course, the academic conduct officers who make the decisions.

Key points

During the session, I captured the following important points. The first point was that assessment is vulnerable to ChatGPT. Specifically, highly structured essays are vulnerable, but these type of essays are used to develop student skills.

ChatGPT perform less well with anything to do with reflections about learning, since anything that is produced will not sound genuine.

There is a role for ChatGPT (or generative AI) detection software, but there are issues with detection tools, since they present a high rate of false positives. Detectors only gives you a probability that something is synthetic, but doesn’t provide evidence like TurnItIn.

Tutors are very important. They are able to spot synthetic solutions; they can identify bland, superficial, repetitive and irrelevant materials in a way that automated tools cannot. To assist with this, and to help our tutors, the university needs to provide better plagiarism training.

A recognised issue is that ChatGPT will generate superficially compelling references that are completely fake. Asking ALs to scrutinise the referencing would go some way to determine whether a chunk of text has been automatically generated. ChatGPT doesn’t currently do referencing at the moment, but there is a possibility this might change if it is connected with public databases.

The next step of this project is to write up findings and to have conversations with other faculties. There is also a university working group which aims to generate an assessment authoring guide to mitigate against generative AI. There is, of course, the need to do more studies. There might also be the need to adopt subject or discipline specific approaches. 

The closing thoughts shared during the seminar are important: we need to teach all students about the consequences of AI. Perhaps there needs to be some Open Educational Resources on the topic, perhaps something on OpenLearn that offers a sketch of what it can and cannot do. A closing point was that there are no ‘no-cost’ options. The university needs to carefully consider the role and purpose of assessments. Doing nothing is not an option.

During the discussion session, I noted down a couple of interesting questions: what question types would cause large language modules to perform sufficiently bad from caring to not caring? Also, what limits its abilities? ChatGPT writes in generalities. Its responses comes from how questions are worded. There is also the issue of concreteness. Assessment tasks are often related to specifics, in terms of activities texts, module materials, and forum posts. If generative AI cannot access the texts that students need to access and critically evaluate to develop their skills, its uses are, of course, limited.

Reflections

One of the key points that was emphasised was the importance of the tutor. They have such an important role to play in not only identifying instances of potential academic misconduct, but also in educating students about generative AI, and the risks these tools present.

It is also useful to reflect on the point that tutors can spot changes in writing style. There is the possibility that the stylistic quality of generated text is a characteristic that could be used to respond to not only ChatGPT, but also contract cheating. At the time of writing, anti-plagiarism detection tools such as TurnItIn only evaluate individual assignments. In the arms race to ensure academic integrity, the next generation of tools might analyse text across a number of submissions whilst taking into account the characteristics or structure of individual assessments.

I expect there will be a multi-faceted institutional response to generative AI. There will be education: of students, tutors, and module teams. Students will be informed about the ethical risks of using generative AI, and the practical consequences of academic misconduct. Tutors will be provided with more information about what generative AI is, and offered more development to facilitate sessions to help students. Module teams will have an increasing responsibility to develop assessment approaches that proactively mitigate against the development of generative AI. Also, technology will play a role in detecting academic misconduct, and new procedures will be developed to assist academic conduct officers.

Acknowledgements

An acknowledgement is due to Mike Richards and everyone who took part in aspects of research which is summarised here. A thank you goes to Daniel Gooch, who facilitated the event.

Permalink Add your comment
Share post
Christopher Douce

A230 Journal - April 2023

Visible to anyone in the world

1 April 2023

A serious post for April Fool’s Day!

I’m going through the block materials about Sam Selvon, and I’m quite enjoying it. I think I might go this direction in the EMA, but I have to read Lonely Londoner’s again.

2 April 2023

Just finishing up reading the chapter about Selvon, and then I move onto the chapter about Elizabeth Bishop, which is proving to be slow going. I find the readings and work through a couple of them, and find them to be quite difficult. As a bit of side reading, I have a quick read of a summary of Bishop’s biography.

10 April 2023

I’m pulling together a set of notes before pulling everything together for the EMA. Today I’ve been focussing on one of the set texts: The Lonely Londoners by Sam Selvon. Despite its obvious issues, I’m starting to really like this book.

11 April 2023

I’m moved on from Selvon and onto one of Joyce’s short stories. I read it again, underline some passages, read a review of the story, and then transcribe some quotes into my notes document. My next task is to make some notes from the module materials.

15 April 2023

I get a couple of hours to work through all my notes whilst on a short break. I move different notes into group of categories, set up a few subheadings, and a structure emerges: introduction, text 1, text 2, compare and contrast, conclusions. I manage to work on the introduction and the beginning to the text 1 section.

19 April 2023

I find a bit of time in my day job to do some writing. I cut a few notes and quotes that I feel I don’t need, and work on text that flows between the different sections.

20 April 2023

Another couple of hours for writing. I return to reading one of the texts, identify a couple of elements, and comment on these within the EMA document, and then completely change the conclusion, editing up a new version. It’s time to cut out all the temporary headings, see what my current word count is (I think I’m roughly on target), and get a printout ready for editing. I think I’m two days away from submission. Even if I need to make some further changes, I can go ahead and submit revisions before the cut-off date.

When I take out my structural headings and exclude my references, Word tells me that I’m slightly below the word count. I do some editing on my printed document using a pack of coloured pens: one colour that is an edit, and another colour that confirm that the edit has been actioned in the submission. After the edits, I’m a touch over, but only by a tiny amount.

I submit my EMA, ridiculously early.

Being a swot, I still hope to attend the EMA prep session that my tutor runs, just to make sure that I haven’t completely got the wrong end of any sticks.

Permalink
Share post
Christopher Douce

Curriculum

Visible to anyone in the world
Edited by Christopher Douce, Sunday, 14 May 2023, 12:08

On 9 May 23, I attended a staff development event that had the title “Our STEM curriculum” which was presented by David Morse, Associate Dean for Curriculum, Faculty of Science Technology Engineering and Mathematics. 

I must admit that I was expecting a very different session to the one that I attended. I was expecting something about curriculum accessibility. Instead, I had stumbled into what appeared to a briefing about the STEM curriculum.

What follows is a set of notes that I’ve taken from this session which I’ve moulded into a summary about different types of curricula that the university offers. Although the focus on this blog is, of course, STEM curricula, there will, of course, be similarities and differences between what happens in other faculties and institutions. Hopefully what follows will be a useful summary for anyone who is trying to understand what curriculum is all about.

How everything works

There are quite a few terms to understand: modules, qualifications, and credits. You gain credits by studying modules, and modules contribute towards qualifications. A degree is a qualification, as is a certificate and diploma. There are undergraduate and postgraduate qualifications.

The most familiar qualification is the undergraduate degree. To really understand what is meant by curriculum it is worth spending a couple of minutes to unpick what it comprises:

A full-time three year undergraduate degree is 360 academic credits.

Every year, a full time student will be studying 120 worth of modules.

Students studying at half time study intensity will, of course, study modules worth 60 credits.

In the OU, modules are either 30 or 60 credits depending on the faculty, and the module. In the Faculty of Arts and Social Sciences, the modules are typically 60 credits. In STEM, they are often 30 credits. In some cases, students can study one 30 credit module after another.

Other institutions might have different sizes of modules. I’ve seen modules that are 15 credits, 20 credits or 45 credits. Some really bit postgraduate modules might be even 90 credits.

One credit is typically considered to be 10 hours of study. The term ‘study’ can refer to a whole set of different activities: it can refer to attending tutorials, reading learning materials, completing study tasks, interacting with fellow students, and completing assessments. The exact make-up of that time will depend on the module.

With 10 hours of study per credit, this means that a 60 credit module means 600 hours’ worth of study. If we assume a typical working day is 7.5 hours, this can be translated to 80 days of study time.

A traditional academic term lasts 9 months from October until June, but within this period there are the Christmas and Easter holidays, which means a break of4 weeks. This means there are 8 months of study time for full time students.

120 credits of full time study means, of course, 1,200 hours. Dividing this by 7.5 hours per day gives us 160 days of study time. Dividing this by 5 gives us 32 week of study time per year. Dividing this by 4 weeks in a month gives us exactly 8 months, which means that everything fits.

Modules are broadly categorised in terms of level, which corresponds to the year of study at a face-to-face university. A module that has the number 2 as the second number is a second year module. I’ll cover more about this a bit later.

Now that we’ve figured out undergraduate degrees, let’s turn our attention to postgraduate master’s degrees. A one year master’s degree at a face-to-face university typically takes 12 months rather than 9 months, usually running between September to September. This means there is more to study. MSc and MA degrees typically require 180 credits. When studying part time, OU students typically study for them over a three year period.

All this is enough to make our head hurt. When we look into the particulars of individual degrees and qualifications, we find a whole lot more detail.

What follows is an edited set of STEM specific notes that I made from the session. I’ve taken the liberty of adding a number of sections which shares a bit more context.

Access modules

The first elements of curricula which some students may encounter are the university’s access modules. These modules are presented as an introduction to distance learning and aim to offer students a broad overview of a subject. There are four modules, one for each faculty, each taking up to 30 weeks.

The STEM access module is split into three sections (or blocks) which have the subjects: life, water and home. The first block addresses biology and ecology, the second adopts a practical perspective, and the third begins to address design, engineering and computing.

These access modules don’t attract academic credit. They do, however, help students to gain an understanding of what is involved with university level study. Students will gain experience of writing and submitting assignments, and will receive significant help and guidance from a tutor.

Undergraduate qualifications

The faculty offers a number of qualifications: foundation degrees, undergraduate certificates, undergraduate diplomas, first degrees, postgraduate certificates and diplomas and taught higher degrees. The most popular is the first degree.

The most popular qualification in STEM is the Computing and IT BSc (Q62), followed by Natural Sciences degree (Q64), and then the Certificate in HE in Computing and IT (T12). The popularity of the certificate in Computing and IT might be explained that certificates in HE (CertHE) and diplomas (DipHE) are known as milestone qualifications, which means that students can gain these qualifications as they accumulate credit for an undergraduate degree.

The faculty also offers a number of foundation degrees, such as the Foundation Degree in Computing and IT Practice (X15). Rather than being 360 credits, these qualifications are 240 credits and cover stages 1 and 2, an contains a compulsory work-based learning element.

Students can also use something called credit transfer. There is an increasing number of students who have studied at another university and convert their foundation degree to an OU BA or BSc by using the credit transfer service. This is sometimes called a top up degree.

Most of the degrees and qualifications that the university has are what are called named degrees, which means a degree that is specifically linked to a particular subject or discipline. Named degrees are relatively new to the OU. They were introduced in their current form to enable students to apply for student loans which are available for part time study. Loans are only available to students who are studying a named degree.

Each school within a faculty ‘owns’ the qualifications that are aligned to their subject area. There are, of course, some qualifications which cross schools and faculties. A popular choice is a joint honours qualification. An example of this is the Computing and IT degree with a second subject. With this qualification, students can study Computing with Business, Design, Mathematics, Psychology, Statistics and Electrical Engineering. 

It is also worth mentioning an undergraduate qualification called the Open Degree. The Open Degree predates the introduction of the named degree. It enables students to create their own degree from any undergraduate module. It is described as follows: the Open degree “allows you to bring together different areas of study in a completely flexible way to develop knowledge and skills. … Choose from over 250 modules across 16 subject areas, to create a bespoke qualification to match your interests”. Returning to the topic of credits, students must study 360 worth of academic credit, in three groups of 120 credits, which correspond to each of the levels.

A variation of the Open degree in the STEM faculty is the Combined STEM degree where students can create their own STEM degree from the different STEM modules that the university offers. Within this qualification, there are corresponding diplomas and certificates.

Undergraduate degree classifications

In keeping with all other higher education institutions (HEIs), when a student gains their OU degree, it is assigned a classification which reflects their performance. The highest category is a first, followed by an upper second (2:1) or a lower second (2:2), or third class.

Also in keeping with other HEIs, the first level of study is all about skills development. Although the first level modules do not officially contribute to a degree classification, level 1 modules can have two overall scores: distinction, or pass. To get a distinction, students must gain an overall score of 85%, as defined by a module’s tuition strategy. This said, the exact boundary for a distinction can be slightly adjusted by a module results panel to ensure that results are awarded in a way that is consistent between different module presentations. More information about what is meant by assignment scores, module results and overall grades is available through the university help centre. 

Results from level 2 and level 3 modules (modules that have the numbers 2 and 3 as the first numbers in the module code) do contribute to a degree classification. Module results are presented in terms of grades, ranging from grade 1 (which is a distinction) through to grade 4 (which is a bare pass). The module result grades are then combined with each other to calculate a student’s degree classification. More information about the algorithm used to calculate a degree classification is also available through the university help centre.

Postgraduate qualifications

Like the undergraduate qualification, the postgraduate master’s qualifications also contain milestone qualifications which are, of course, qualifications in their own right. As mentioned earlier, a master’s degree is gained through 180 credits of study. Along with way, students can gain a postgraduate certificate, PGCert through 60 credits of study, or a postgraduate diploma, a PGDip through 120 credits of study.

The classification scheme for postgraduate qualifications are different to undergraduate qualifications. There are three different results for master’s degrees: distinction, merit, and pass. In keeping with postgraduate qualifications in other institutions, the pass mark for modules is 50%. For undergraduate modules, the pass mark is 40%.

Higher degrees, such as doctorates and MPhil qualifications are not discussed here. Further information about these qualifications are available in another blog about doctoral study.

Apprenticeships

The OU also offers a number of degree apprenticeshipsThe degree apprenticeships share a similarity with foundation degrees. Both have a compulsory-work based learning element, but with an important difference: an apprenticeship is essentially a job role, with an aspect of study attached to it. The study is aligned with the job role. Apprentices have access to module tutors, and to practice tutors. The role of the practice tutor is to help the apprentices relates their formal academic study with their work-based learning, and carry out regular reviews to evidence their learning.

The funding for apprenticeship study comes from the apprenticeship levy, which all employers of a certain size have to pay from their salary bill. Employers can gain back the value of the levy by encouraging some of their employees to participate in a degree apprenticeship scheme.

Unlike many of the other qualifications, the degree apprenticeship standards are defined by external organisation in conjunction with employers rather than the qualifications being owned by an academic school. Apprenticeship schemes are nation specific. In England, degree apprentices are defined by the Institute for Apprenticeships and Technical Education with other bodies for Scotland, Wales and Northern Ireland.

In STEM, there are two degree apprenticeships; a Digital and Technology solutions (DTS) qualification, and a postgraduate Systems Thinking Practitioner qualification.

Higher Technical Qualifications

Higher Technical Qualifications follow the roughly the same standard as the apprenticeship qualifications. Unlike the degree apprenticeships, these qualifications do not have the compulsory work-based learning component or have the requirement for students to be connected with an employer.

In STEM, there are two Higher Technical Qualifications, which are available in England only: one that relates to Network Engineering (W19) and another about Software Development (W20). Students studying these qualification also have the potential to use their credit from the constituent OU modules on different qualifications, if they wish to further their studies.

Microcredentials

In the OU, typical modules are either 30 or 60 credits. OU microcredentials, however, can be thought as short courses (or modules) which run between 10 and 12 weeks which attract either 10 or 15 of academic credits. In some cases, these bits of academic credit can be ‘boxed’ together into a larger unit, and can be brought into a larger qualification through credit transfer, if the learning outcomes of the microcredentials are compatible.

Microcredentials aim to appeal to a different group of students: those who are interested in upskilling, or developing an evidenced continuing professional development (CPD) portfolio. This emphasis on CPD can be seen through the computing microcredentials, which currently draw on materials from industrial providers, such as Cisco.

Microcredentials differ from other modules in the sense that students are not provided a tutor. Instead, students have to carry out self-directed learning. Technology also plays an important role in the learning experience. At the time of writing OU microcredentials are delivered through FutureLearn, a MOOC provider, which offers a social learning approach. 

Time will tell whether microcredentials will become a bigger element of the university’s portfolio of curriculum. A personal view is that they are useful for some disciplines and for some groups of students, but may not work for others. It is interesting to note that are international initiatives that support the development of microcredentials (Microcredentials.EU) and accompanying policies.

Other types of curricula

As well as formal qualifications and modules, there is also a site called OpenLearn which shares free online courses. Some of the courses delivered through OpenLearni are known as Badged Open Courses (BOCs). This means when a student completes an OpenLearn course, they are eligible to get a digital badge, and download a certificate of completion. Learners can highlight the completion of these BOCs by mentioning them on CVs and job applications. If OpenLearn learners are also OU students, completion of OpenLearn modules will also appear on their student record, which are visible to students.

The OpenLearn resources that are summarised within this section can also be called Open Educational Resources (OERs), which is a category of freely available resources which can be used and shared by educators.

There are quite a few OpenLearn courses and resources which can be useful to tutors. There are courses that enable students to gain an understanding about what is involved with online and OU study. Since a percentage of OU modules are shared through OpenLearn, there are also courses that enable students to get a flavour about what they will be studying if they are to formally enrol. Also, there are courses which can be taken as continuing professional development modules for tutors.

What follows is a sample of some of the materials that are available.

Courses about learning to study

Here are some courses that might be useful to share with students who are considering OU study, or are new to OU study:

The following courses would be helpful for students considering postgraduate study:

Courses that offer introductions to formal study

Here are some notable courses from other disciplines:

Courses that help with tutoring and teaching

The following courses can offer CPD for tutors, and help learners to gain more of an understanding of what is involved with OU teaching and learning:

STEM facts and figures

During this session, David shared some facts and figures about the STEM faculty. For 2021 and 2022, there were 47k students registered on STEM modules. Out of these, 3.5k students completed a qualification, which represents roughly 19% of all OU students graduating. Although there are three faculties, approximately a third of students graduate with an Open degree.

Out of these students, 76% of students work either part-time or full time. 69% of undergraduate students had no previous HE qualifications. This highlights that the transfer of academic credit is playing an important role in the journey for some students.

As mentioned earlier, the Q62 computing qualification is the most popular undergraduate programme offered by the faculty. In recent years there has been a decline in students registering for Q62, but there has been an increase in the number of students registering for the cyber security qualification. In terms of postgraduate study, the Mathematics MSc is the largest MSc within the faculty.

Reflections

I was initially a bit grumpy when I realised that this continuing professional development session was offering a sketch about curriculum, rather than being about accessibility. A key learning point here is: make sure you read the event description carefully.

Sometimes it’s useful to stick with things. In this case, the summary of all the different qualifications that are provided by the faculty was a helpful reminder. I also took the opportunity to really figure out the notion of academic credit, and how it relates to modules, qualifications and the academic year. 

I’ve taken the opportunity to add two complementary sections: a bit about access modules (which wasn’t really covered during the session), and a section about degree classifications. Everything is, of course, linked to each other: qualifications are linked to modules, which are linked to schools, which are liked to disciplines.

There are, of course, bits of curriculum that I haven’t mentioned. Some years ago, there used to be a number of short courses, some of which were credit bearing, but there is only one short course is run by the faculty: a digital photography course. There is also something called ‘open box’ modules, where bits of external academic credit can used to contribute to an OU qualification.

Curriculum is subject to continual change. Its structure is affected by a number of variables: academic and cultural trends, innovations in pedagogy and technology, and wider political changes, such as changes to funding. It is interesting to see the extent to which freely available materials complement formal credit bearing materials. Knowing about what free resources are available has the potential to make a real difference to the student experience.

Acknowledgements

Thanks are extended to David Morse for running such a thorough session.

Permalink Add your comment
Share post
Christopher Douce

Supervisory Professionalism and Recognition workshops

Visible to anyone in the world

On 3 and 4 May 2023 I attended a couple of workshops that introduced a professional recognition scheme for doctoral supervisors, which is run by the UK Council of Graduate Education, which is abbreviated to UKCGE. I attended these workshops since the OU is running an accreditation pilot scheme through the OU graduate school. It’s aim is to help to guide a cohort of participants through the accreditation process through workshops, sharing of resources, and providing mutual support, with an intention of making a submission in October 2023.

This blog post summarises what I considered to be some of the key points or highlights from the workshops. Very many of the words shared in this post come from points made by the presenter, and are also reflected within the UKCGE recognition scheme which is clearly referenced. Towards the end of the blog, I have offered some reflections and have shared some accompanying resources.

A further note is that the terms ‘student’ and ‘candidate’ are used interchangeably.

Introduction

The pilot was opened by Lindsey O’Dell, Director of the OU Graduate School. She offered a summary of the pilot scheme, and emphasised that doctoral supervision is an important part of the academic role, and it is important to both recognise and celebrate it.

Both workshops were facilitated by Stan Taylor who is an Honorary Professor from the School of Education, University of Durham. Stan said that he originally learnt ‘on the job’ as a supervisor, and later moved to the area of professional academic development. He is the author of UKCGE Framework for Good Supervisory Practice and led the development of supervisor’s recognition scheme. 

Stan also mentioned some books he has had an involvement with: a handbook for doctoral supervisors, a book that referred to the making of doctoral supervisors, and publications that examines the ways in which doctoral examinations take place and how supervisors are supported in different countries.

The changing landscape of doctoral education

The first day of the workshop began with a bit of history.

Historically, doctoral supervision was “an adjunct of the research function of academics” and underpinned by the master-apprentice model. Constant change within the higher education sector has, of course, led to changes to doctoral supervision. Key changes has included increasing formalisation and diversification of doctoral programmes, the commodification of higher education and increasing movement towards competition between institutions, and an increased emphasis on the welfare of candidates.

This perspective on welfare is important. Historically, if things went wrong, it was the fault of the student rather than the supervisor or the university. The movement towards thinking of a student as a consumer has, arguably, led to a change of power balance between student and supervisor. If students are not provided with effective supervision, there has been a precedent of students seeking compensation. It is now clear that institutions and individual supervisors have more direct responsibilities towards their students.

There was a historical perspective which can be phrased as: if students paid their fees “no one worried too much about how long they took” (Taylor, citing Simpson, 2009, p.458). A review of completion rates led to the introduction of tougher measures: candidates are now typically required to complete within a 4 year period, but there are exceptions to this, such as if they are carrying out research part-time.

A term that was introduced which I was unfamiliar with was: structuration. I understand this term to refer to the extent to which structures have been created to support doctoral students and supervision. This has partly arisen due to an increase in regulation. In the UK, there is the QAA, the Quality Assurance Agency for Higher Education. Countries now typically have their own national quality assurance systems for higher education and external monitoring. In response, universities have developed their own internal systems to ensure the quality of doctoral education, which can take place within supervision teams. This has necessarily led to the creation of graduate schools and accompanying units and roles. Doctoral supervisors need to understand what these units are within their own institutions and what services and support they offer. Graduate schools may also play a part in setting up of doctoral training and development alliances.

Diversity was emphasised from two different perspectives. Firstly, there has been increase in diversity of different types of doctoral programmes. In addition to a full time PhD, there are now different types of EdD programmes. There is also the possibility of a doctorate through submission, or carrying out research with an industrial partner.

The second perspective relates to the diversity of doctoral candidates. Historically, candidates were young, white, male, middle class, and studied full time. The demographics of candidates have changed: 48% of doctoral students are now women, but there has been less progress for candidates with other protected characteristics. Significantly, there is a significant underrepresentation of black candidates, which needs to be addressed.

There has been a change of perspective when it comes to the obligations that institutions and supervisors have to doctoral students. Historically, students were perceived as being responsible for their own mental health, which can present significant and ongoing challenges to students. There many be a number of issues for this, such as financial challenges, the limited number of opportunities in the higher education sector post-completion, and loneliness. Institutions are now seen as having a duty of care for students. This means that supervisors have a responsibility, but they may often lack confidence in terms of how to provide support.

Other changes include digitalisation and increasing interdisciplinarity. Whilst digital technologies can enable candidates to carry out their research at a distance, they also can present challenges too; candidates need to learn and work with digital tools and systems.

Interdisciplinarity can also lead to the emergence of barriers. Supervisors from different disciplines can communicate using different academic languages. This leads to the important question of: how do examiners from different disciplines understand what is meant by an effective contribution to a field?

Given that there are more doctoral students than full time academic posts, supervisors and graduate schools have a responsibility to offer help and guidance to candidates, to make them aware of what opportunities might be available to them after they finish their research.

This leads us to a wider question, which is: what is doctoral research for if its purpose isn’t to train academics? One answer be connected to the word capitalisation. In other words, doctoral research can have economic value as well as academic value. There is a link here to the notions of human capital and knowledge economies, and this can be linked to whatever is meant by economic growth. It could more directly argued the doctoral research helps to develop the skills and abilities of researchers. This release to the Vitae researcher development framework https://www.vitae.ac.uk/   which describes skills that researchers should acquire and develop over the course of their studies.

The UKCGE framework

Supervision has changed from an adjunct activity that takes place within a private space to a more demanding complex set of roles which are carried out and supported by supervisors and organisational units. 

What follows is a summary of the UKCGE framework. Stan was Invited in 2019 invited by UKCGE to define good supervision practice. These were combined into a draft framework which was then streamlined into 10 domains which aimed to describe the core elements of good practice. To become a recognised supervisor, applicants to the UKCGE scheme must provide evidence under each element.

What follows is a summary that has been made following the workshop presentation. The official description of these criteria can be found by through the Good Supervisor Practice Framework summary

1. Recruitment and selection

This element relates to the very start of the doctoral journey. Recruitment involves reaching out to diverse candidate populations, developing a research proposal with a potential candidate, and offering feedback to candidates.

Supervisors should publicise the areas of research that they can offer. They should also participate in campaigns to recruit from underrepresented groups, assess whether applications from candidates that are likely to make the transition to independent researchers, and assess whether a research project is realisable, and candidates have the knowledge and skills. Key tasks will include interviewing applicants, making a final decision and giving useful feedback. An important question to ask is: how do you make the decision about whether someone has the skills for independent research, and what is the evidence for this?

2. Relationships with candidates

This criterion relates to having an awareness of diversity of candidates, negotiating expectations between student and supervisor, monitoring of activities, and understanding of issues. Supervisors should be conscious of different supervisory styles and their relationship to student needs and be aware of how student needs change over time.

3. Relationships with co-supervisors

Supervision now typically takes place within teams. Supervisors need to be aware of the benefits of team supervision and issues that may arise whilst working within a team. It is important to clarify the roles of co-supervisors, important to set expectations of the project, and regularly review relationship with co-supervisors and candidates. This criterion relates to the importance and necessity of working well with others.

4. Supporting candidates’ research projects

This relates to “inducting candidates into research, advising them about how to go about it, advising on skills and issues”. In other words, helping them to become familiar with what research entails within a field of study. The involves “discussing conceptions and misconception of research, looking at threshold concepts”, discussing issues of academic integrity, choosing topics, advising on notions of theory, methodology and methods. Other aspects of support includes helping candidates to navigate through the necessity of gaining ethical approval (if appropriate to their project), and developing research skills.

5. Encouraging candidates to write and giving appropriate feedback

Encourage candidates to write “throughout their studies, not at the end of research, giving effective feedback”. Writing is something that can be practised. Although a lot of writing is typically done towards the end of a doctoral project, it is helpful to encourage candidates to write from the start of their studies to assisting their development of academic writing skills. Key points includes: create opportunities for writing, give timely, constructive and actionable feedback, and consider the suggestion and use of research diaries and writing of blogs. A point I noted down from the discussions were: ask students what they understand by the feedback they have received. Supervisors can benefit from getting feedback from their students.

6. Supporting candidates’ personal, professional and career development

This criterion links back to the earlier point that there are more doctoral candidates than there are academic posts. To help candidates with their personal and professional development, it may be helpful to offer advice and guidance about possibilities within the domain in which they are carrying out research. It is also important to be a good role model in terms of work-life balance, it would be useful to introduce candidates into disciplinary networks and activities, and supporting their development as teachers. Where possible, advice about academic careers and post-doctoral work (and challenges that accompany these roles) is helpful.

7. Supporting progress and monitoring progression

A point that was highlighted earlier was: candidates have to complete within a 3 or 4 year period. A question is: what might a supervisor do to motivate their students during this time? Also, how might a supervisor or supervision team actively monitor progress? Two suggestions could be: encouraging students to attend conferences (which can also help them to develop their writing skills and contribute to departmental seminars. From a pragmatic and administrative perspective, supervisors must help students to participate in formal progression events (in the OU context, this is called upgrade reports). This might mean the reviewing of documents before sent onto graduate schools.

8. Supporting candidate through completion and final examination

This point strikes me as being very practical. Supervisors should offer advice on submissions and examinations, and should work closely with a candidate to finalise their submissions. Some direct advice was shared at this point: encourage students to look at exemplar submission so students understand what is meant by, and what should go into a thesis. A thesis should, of course, present an argument, with accompanying evidence. Supervisors can offer some really practical help: they can help students to prepare for the viva by describing the procedures, and running a mock viva. Different supervisors from a supervision team can take on different roles. It doesn’t end with the exam: supervisors also have a responsibility to support candidates after the viva, especially if some corrections have to be made.

9. Supporting candidates to disseminate their research

This point links to some of the earlier points, which related to encouraging students to attend conferences and workshops, and thus help to develop their writing skills. Essentially, this point is all about “making work available within the community” and sharing findings with a wider audience. A useful point was: “set expectations at the start of the candidacy” about what is expected, role model the process of publication to show how its down, encourage candidates to publish as they go, and explain what is meant by co-publishing or co-authoring, and set up a post-doctoral publication plan. In some cases, it might also be helpful to consider dissemination and publication alongside the concept of research impact, which is something that postdoctoral researchers need to include into research bids and plans.

10. Reflecting upon and enhancing practice

Reflection is a cornerstone of education, and it feels right that those involved in providing supervision should not only reflect on their practice, but regularly “undertake appropriate professional development and disseminate”. A bit of advice to accompany this point was: use an appropriate mix of methods for evaluating supervision, undertake initial and continuing professional development, and contribute to the professional development of other supervisors. A further point was: professional development isn’t just about workshops; it can also be keeping up to date with reading. There is, of course, also a considerable literature about supervision. Finally, professional development opportunities may be provided by your university’s graduate school, or equivalent unit.

Writing an application

During the workshops we were offered some advice and guidance about the application procedure and the process of writing an application.

A submission is a reflective account of your supervisory practice which addresses each of the 10 headings. Applications should be 5k words in length, with a permitted 10% leeway. Two referees are required, one of which should be from a former doctoral candidate. The second referee should be a colleague who knows about your practice, but need not necessarily be someone who is involved with supervision.

Applications are read by two reviewers who are recognised supervisors themselves; all applicants receive constructive feedback. The reviewers are recognised supervisors who have completed a training programme about how to evaluate submissions. If recommendation is acceptance, you become a UKCGE recognised supervisor.

Preparing a submission

To help to prepare a submission, the UKCGE have prepared a workbook, in the form of a detailed Word document. The workbook is a template, which offers some guidance and spaces to allow candidate to comment on each of the criteria of the framework. A practical suggestion is to provide two examples to evidence your understanding and experience.

Begin with an introduction

A useful bit of advice was to begin with an introduction. Do describe your educational background, summarise the number of research students supervised and in what capacity including the number of students who have completed. Also provide other relevant information, such as whether you have experience of an examiner of research degrees, and whether you have been an internal or external examiner.

Evidence of scholarship

A question that was asked was: “are we expected to use academic references in our application, like we did for an Advance HE SFHEA submission?” The answer is: yes. Evidence of scholarship, and awareness of scholarship that relates to supervision is necessary. A practical suggestion is to provide between 8 and 12 references. A good place to look is the bibliography documents which are provided by the UKCGE. A couple of links have been provided in the resources section of this blog.

Points to bear in mind

Do include evidence that relates to all the criteria. If this is not possible, offer an explanation why not. Examples should be drawn from recent practice.

Application should relate to you, and should have a reflective quality. Write about why you did something.

As suggested above, you should show engagement with research, scholarship and professional practice, and links with professional bodies and wider communities.

You must demonstrate real and practical commitment to reflection about supervision practice.

Making a submission

In this pilot, the OU will be making what is called a group submission. The UKCGE does, of course, accepts individual submissions, which must be accompanied by a processing fee.

Reflections

Things have changed since I was a doctoral candidate. There is more structure and formality than there used to be. 

Reflecting on the framework, I’ve come to the conclusion that I had a pretty good doctoral experience. My supervisor gently introduced me to many of the principles and ideas that are embedded within Stan’s framework. There were regular meetings, I was encouraged to write and publish early, to join academic communities, and there were discussions about the role of theory in research, and what is meant by co-authoring. There was also some discussion about post-doctoral planning too, but it was done in quite an informal way.

Thinking back, it took me quite a few years to publish the final article from my doctoral research. Curiously, it wasn’t the main research that had the biggest impact. A small paper that I wrote along the way grabbed the attention of fellow software engineering researchers. This goes to show the importance of “getting things out there”. 

Two noticeable differences come to mind: I don’t remember there being a graduate school when I was a doctoral student, and there wasn’t a supervision team. 

I also remember struggling too. At the time, I was trying to do too much: I was working part time whilst I was studying full time. I should have made more time to have more fun, and to relax; that could have potentially helped me to be a bit more creative.

I’m currently a supervisor on two different doctoral programmes; a doctorate in Education programme, and a disciplinary doctorate. I’m also something called a third-party monitor for candidates on both programmes.

I like the framework since I feel that it solidifies and clarifies many of the important responsibilities of supervisors. It also implicitly connect with another (optional) aspect of my day job, which is supporting undergraduate students. With all these different perspectives, I’m definitely going to make a submission.

Resources

I have written some other blogs about doctoral study and supervision, as well as summarising some of the continuing professional development that I have participated in:

The following resources from the UKCHE are likely to be useful when it comes to making a submission:

For supervisors making submissions, the following two resources may be especially useful, depending on the context:

Supervisors should, of course, be aware of the following framework:

During these workshops, the QAA, the UK Quality Assurance Agency for Higher Education was mentioned. The following link offers a summary of the characteristics of doctoral degrees:

Acknowledgements

A substantial acknowledgement goes to Stan Taylor who designed, delivered and facilitated the workshops, with help from Soraya Tate from the OU graduate school. Acknowledgements are also given to Linsdey O’Dell, director of the graduate school, and fellow workshop delegates.

Permalink Add your comment
Share post
Christopher Douce

Individual support sessions

Visible to anyone in the world

This blog post is about individual support sessions. It has been written from the perspective of a tutor, with the intention of sharing practice with other tutors.

If you discover that one of your students is struggling with their studies, a tutor can ask a student whether they would like to have an individual support session (ISS) to help them to get them back on track. An ISS isn’t a 15 to 20 minute telephone call in response to a student’s question, or a quick talk through different parts of some module materials. An ISS is a structured and dedicated one-to-one session to help a student to progress with their studies.

A request for an ISS can come from either from yourself, or from a student or via the student support team. A request may also come from one of your line managers. To request an ISS, you can send a request to the student support team (SST) via your TutorHome page, or you can contact your line manager, who will do this for you. It is important that ISS requests are recorded since individual support sessions are not technically a part of your module teaching time. Instead, every session needs to be accounted for since they will come from your FTE.

From the student’s perspective, an ISS typically lasts for one hour, but from the tutor’s perspective, two hours of their time is accounted for; one hour for the actual session, and one hour for the preparation time. More will be said about what it means to deliver and prepare a session in a moment.

An important point to note is that different modules differ in terms of their tuition models. A first year module may have a different model to a final year project module. In a dissertation module, where you may have a fewer number of students than typical module, an element of one-to-one tuition is likely to be built into its tuition module. For example, at the time of writing, the computing undergraduate project module has for hours of one-to-one time for every student. It is up to the individual tutor (and their students) to device how to best make use of that time.

What follows is a short summary of what might happen within an individual support session. Every session is likely to be different, since ever student and every module is different.

Identifying a need

In my distance teaching practice, I try to tie everything together. In my script comments, I refer students to my eTMA feedback summary page. In my feedback summary page, I may refer to other tutorials, earlier feedback, or module resources. In some cases, I may also suggest to students in their eTMA summary that it might be useful to have an additional support session by encouraging them to contact either myself, or the student support team. In some cases, I might even give them a ring to ask this question. 

Booking in a time

The next step is to book in a date and time that works for a student. I always ask what their communication preferences might: whether they prefer to use the phone, or use Adobe Connect, or MS Teams. At the time of writing, I prefer MS teams, since I can use my web cam, and it enables me to do some screensharing, which is especially helpful when working with a technical subject, such as computing. It can also be useful to guide students through important parts of module materials. When arranging a date and time, I also ask the important question: what would you like to get out of the session? In addition to confirming a date and time by phone or by email, I also send a digital calendar meeting invite, which would also contain a link to either a MS Teams room, or an Adobe Connect room.

Preparing

I have one hour to prepare. To keep things fresh in my mind, I tend to prepare close to the time of when the session is scheduled. Some important questions to ask include: how well has our student being doing in their studies? I answer this by looking at current progress and their study history. I also ask: where are they, or where should they be in the study of their module? To make sure I know where they are, I review the module calendar and identify which bits of module materials they should be studying. Another question is: what assessments are coming up? Is there an exam, or is there an important TMA coming up?

Since students are likely to want to become more familiar with any forthcoming assessments, a really good idea to thoroughly review the assessments, and any accompanying tutor notes. If the focus is likely to be on a TMA, I get a printout of the current TMA and any accompanying tutor notes, and go through these documents with a highlighter and pencil. I highlight which sections are important, and if there are any reference to module materials sections which are important, such as chapter number or page numbers within block materials or set texts.

Running the session

This is a summary of how I run my session; different tutors have different styles and approaches. Since the session is all about our student, I begin with the question: “what would you like to get out of this session?”, and ask any clarifying questions. Whilst I take their lead, I’m also led by another question of my own, which is: “where is our student at?” Or, put another way, where do they need to get to so they are able to reach the learning outcomes to enable them to complete their forthcoming assessments? To understand their own understanding, I ask them about their understanding of some of the module concepts, by asking questions like “how would you describe…”; I aim to establish a dialogue where they teach me what they know, which would enable me to pick up on any gaps of understanding.

If appropriate, I would use screen sharing. In my own world of computing, I would share a software environment, but I also might share an empty Word document, where we can collaborate together on a set of notes, where each of the main points are being suggested by the tutor. In some cases, this document might contain headings which reflect the themes that may for a part of any forthcoming assessment.

Asking questions is important. During the session, I would regularly check for understanding. For example, I might ask “remind me again how you would go about…” or “remind me again about how you would define…”. 

Conveying a positive perspective, which reflects a growth mindset, is important too. I would never say that an expression of an understanding is “wrong”. An expression of an idea or a principle in terms that is different to the expectation of the module team is an opportunity to further develop a student’s understanding. If an idea is expressed that has some elements that reflect learning, I would praise those elements, and add to their explanations whilst trying to lead them on a path to develop their own enhanced explanations.

Towards the end of the session, I would ask whether they have any more questions they would like to go through. I would also offer a quick summary to recap some of the points that have been discussed during the session. I would close by saying that they should feel free to contact me if they have any follow up questions, and that it would be possible to request a further one-to-one session if necessary; maintain a line of communication is important.

After the session

If any notes were made, code written, or documents shared during the session, do email them to your student after the event. 

To confirm completion of the session to the university, I send an update to the student’s record, which can be seen by the student support team. To do this, I go to the “update record” link that is next to the student’s name on TutorHome, recording the date of the session, specifying support on current module, individual support session, regular AL/student contact, and whether the event took place in an online room or over the phone. In the comments section, I write: “This is to note completion of an ISS for student” also noting the time when it took place, and highlighting that no SST action is required.

Recording the completion of sessions is especially important if students are given sessions to help them develop an awareness of study skills and good academic practice. Evidence of pro-active interventions are really important for academic conduct officers.

Reflections

An interesting question to ask is: what is the difference between providing student support during a module presentation and an individual support session? The answer depends on the tuition support model that is adopted by a module. This said, on a typical module, tutors are usually expected to respond to questions send to the tutor by their tutors. As aspect of my own practice is to regularly ‘check in’ with students between assessment points, to ask them how everyone is. Running ISSs is also one of those elements of tuition which requires collaboration with the student support team, and line manager. A final point to note is that ISSs are not typically performed by practice tutors.

Permalink Add your comment
Share post
Christopher Douce

A230 Journal - March 2023

Visible to anyone in the world

9 March 2023

Has it really been so long since I last got my head down and did a bit of proper study? The answer is yes; there have been a few things going on, including a lot of TMA marking for the modules that I’m teaching, and also helping out my mum and dad with a few things.

Anyway, today was TMA results day! I’m very happy, and dare I say it, surprised with my results. My tutor offered some helpful comments, which suggests that I should consider the wider themes within a text when writing a thematic essay. I need to re-read his comments to really take them on board.

10 March 2023

I have a day of leave, so I’m going to do a bit of study.

There was a bit of chat in the WhatApp group about an audio book of Dubliners. Not having a subscription to Audible, and not really wanting to go through the fuss of setting up and account, and then cancelling, I’ve discovered a site called LibriVox, which has the subtitle: Acoustical liberation of books in the public domain.

It turns out there’s a version of Dubliners which can be downloaded. I’m going to give this a go.

Onto the block about The Twentieth Century. Before I go there, I’m going to have a rummage around the module website, to see how far behind I am.

11 March 2023

A day of catching up. I’ve noted the date of the next TMA. I’ve realised I don’t have much time. I briefly read the TMA question, which will help me with my reading of Dubliners.

After reading first two chapters of the blocks, I start re-reading Dubliners (which I had read over the summer), with help from LibriVox. It is going in this time; I’m making sense of it.

I also listen to a documentary about the publication of Dubliners that I found on BBC Sounds. This was both interesting and helpful. One expert claimed that Joyce uses the word ‘confused’, only once, within each of his short stories. So far, this seems to be the case, except ‘confused’ doesn’t feature within the first story, The Sisters.

12 March 2023

It’s back to re-reading Dubliners. I begin with the story, Two Gallants.

13 March 2023

It’s tutorial day! I start the day with another story from Dubliners.

15 March 2023

It’s strike day, which means I’m in a position to do a bit of uninterrupted study.

I’m now up to the final short story, which is actually quite a long story. When I’m done, I’ll then make a choice about which story to choose for the TMA.

I went on a slight study diversion, and found a web page that shares what is described as James Joyce reading from Ulysses https://lithub.com/listen-to-the-first-ever-recording-of-james-joyce-reading-from-ulysses/

I’m heading away tomorrow for a short break. I am, however, going to take my study block, and also the reading supplement. I need to get things together quite quickly, since TMA 5 is coming up quite rapidly.

18 March 2023

I spent a quite a bit of quality time with my books. I think probably four or five hours in total. I finished rereading The Dead. I read through the last chapter of the block I needed for TMA 5, and then had a good read of the poems in the reading supplement, getting through most of them. 

I really liked the New York texts; they really spoke to me. Whilst I appreciated the structure of the sonnets, I really liked the poems by Langston Hughes.

19 March 2023

A few more readings to get through, which didn’t take too long. I think I’ve chosen my texts for TMA 5.

20 March 2023

I had a quick read through chapters 1 and 2. I ask my tutor a question, who immediately responds; he offers me a helpful steer, which I am really grateful about. My next step was to create two notes files, filled with notes I’ve pulled together from all the text. There’s one for the final TMA, and another one for the EMA.

My next step: tomorrow, I’ll dig into the text of the text I’ve chosen, relating words back to the words of TMA question. I’ll begin with Dubliners in the morning, and then I’ll have another look at the texts I think I have chosen for the second part of the question. I should then have a set of ideas that I can start to mould into my TMA 5 submission.

26 March 2023

TMA writing day. A couple of days earlier I had collated a whole bunch of notes into my Word file; I have section headings, quotes from the module materials, quotes from the Joyce story, quotes from the poems, and all the references sorted out.

I begin the day with a printout of all my notes. I re-read a short story for a final time, and discovered a couple of elements that I had missed. Letting things sit with me had helped: I’m starting to get an idea what modernism is all about. Although the ambiguity that some elements are presented can be frustrating, it also become fascinating too.

I move paragraphs about, delete a whole set of quotes, write some linking text, added a couple of new bits, and write a short conclusion. I’m nearly done. I edit up the introduction, and get the word count down. I’m slightly over, but it’s okay. It’s good to go.

I go back to the website, to see what next: Sam Selvon and Lonely Londoners. I work through the video materials, which I really enjoyed.

Permalink Add your comment
Share post
Christopher Douce

Object-oriented programming: seven tips

Visible to anyone in the world
Edited by Christopher Douce, Friday, 16 Feb 2024, 16:01

Over the last few years, I’ve been tutoring M250 Object-oriented Java programming. During some of the tutorials that I facilitate, I share set of tips with students. What follows is a brief summary of the tips, and some accompanying notes. I hope these might be helpful to anyone studying M250, or any other OU module that involves a bit of programming.

1. You can't learn programming by reading the course books. You need to do it. You need to spend serious time playing.

It’s important to spend some quality time with the language that you’re using and the integrated development environment that you’re using to manipulate that language. You can only properly learn to get a feel for both object-oriented programming, and programming constructs by using them. Get a feel for the words and the punctuation that you’re using. Also, instrument your code with print statements, and consider using a debugger to really see what is happening. Play and mess about. Getting yourself in a tangle is all a part of the process. There is another related tip is: do one thing at a time.

2. Use the examples as a starting point; then go further.

Start to play, and then to play a bit more, and see where this will take you. Invariably, you’ll end up writing more and more code. This means that you’ll get to a point where you need to think about how to make things a bit easier again. If you’ve found a problem in a textbook, think about how might alter that problem to solve a slightly different problem, or a more general problem.

3. Accept that things are going to be uncomfortable sometimes: it’s impossible to understand everything at once, things will only make sense after you've spent the hours playing and learning.

There’s a lot going on with object-oriented programming. 

There’s the key ideas of types (or classes), objects, attributes and member functions. Not to mention, of course, how objects might work with each other to solve problems. Plus, there’s constructors, libraries and iterators.

It’s all a lot of take in, and it isn’t a surprise if you start to feel a bit overwhelmed. If you see difficult things and struggle to understand what is going on, accept certain things at face value for the time being; full understanding will come a bit later.

4. Always make a backup copy.

This relates to the first tip: playing.

When you play with code, you can also mess things up and get yourself in a tangle, especially if you follow tip 2 where you build on earlier things you have earlier done. As you figure everything out, make sure you take a backup copy of your code. If you’re making lots of changes, you might want to create different versions of your code. You might create a copy, save all your files in a new directory and call it ‘version 1’, ‘version 2’ etc. 

Also, do make sure you save your files in a location that is different your computer, just in case your computer goes wrong. A bit later on, you might start to use something called GitHub.

5. Try to explain your code to someone else. (Or, get a plant, and call it Dijkstra)

Sometimes coding presents some real puzzles; sometimes there’s something that isn’t quite understood, or something doesn’t quite work as expected. As a developer, I’ve sometimes had bugs which have been both weird and persistent. When this happens, I would “have a chat with Dijkstra”.

Let me explain. I once heard that in a computer lab in Cambridge, there was a houseplant, which was named called Dijkstra, named after a famous Dutch computer scientist called Edsger Dijkstra. If a student was struggling with some code, and asked themselves the question “why doesn’t this work?” they were told to explain their code to Dijkstra. The very act of explaining your code, a step at a time, has the potential to help you to understand what is happening, and what the problem is. 

If you have a partner, sibling, or pet, they can all become Dijkstra.

6. If you keep going over the same things time and time again, don’t be afraid to step away from it. Sleep on it, and come back to it with fresh eyes.

In computing, there’s a term called thrashing, which is sometimes used to describe a phenomenon that occurs with computer operating systems. This needs a bit of explanation, so please do bear with me.

Your computer has two types of memory: random access memory, and backing store memory. Random access memory is fast and expensive, but your computer doesn’t have very much of it. In contrast, there is typically a lot backing store memory in your computer (which used to be held on a magnetic disk), which is pretty inexpensive in compared to random access memory. Your computer operating system provides programmers with a lot more memory than is actually available through random access memory. It does this by moving data between different types of memory.

Thrashing is what happens when your computer operating system causes your computer to spend all its time trying to get things done by moving data between different types of memory, rather than doing the work that needs to be done.

If you find yourself ‘thrashing’, you need to reboot. You need to step away from your code and come back to it after a break.

I remember once having an idea about how to solve a coding problem when I was having a shower. A break can do you the world of good. This point leads me to my final point.

7. Have fun, and be gentle with yourself.

Everyone learns at different speeds; learning isn’t a race, so do be gentle with yourself. It’s important to have fun too. I remember that one of my first object-oriented programs was a simulated card game that was based on a television gameshow. It was fun to write, and it was fun to play. This point about playing takes us back to the first point: you can't learn programming by reading the course books; you need to find the time to play.

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