OU blog

Personal Blogs

Christopher Douce

Academic conduct review briefing

Visible to anyone in the world

On 29 February 2024 I attended an academic conduct review briefing for module teams. The aim of this blog is to share some highlights that may be useful for colleagues (and to also try to remember what was covered, since there’s always a lot going on).

During the introduction, it was highlighted that the number of academic referrals have increased over the last 5 years. Two thirds of these typically relate to study skills and poor academic practice. In other words, this relates to what could be called inadvertent misconduct.

There are some specific challenges. Investigations take time, there is an obvious need for consistency with decision making, a need for transparency, and continually emerging threats, such as essay mills and the arrival of generative AI. To respond to this changing landscape, there is a new VLE page for staff, a new academic conduct tariff, new guidance on StudentHome, a new referral form, and new processes and study skills arrangements.

Academic integrity principles for assessment design

Assessment design is important. Good assessment design should ‘reduce the motivation and opportunities for plagarism’ and focus should be on how learning takes place, as well as what is learnt.

An important point that I noted was that module teams should look at patterns of academic conduct referrals. One way to respond to repeated issues is, of course, to consider the assessment design. To help with this, there some useful principles of assessment which I share below.

A key theme of these principles is authenticity. This is connected with need for to assessments that focus on problem solving, perhaps solving problem that might have an open ended answer.

Here are the ten principles that were shared during the session.

Principle 1: Reward academic integrity

Make sure students reflect on their skills and capabilities that demonstrate academic integrity.

Principle 2: Assess higher skills

Assess metacognitive skills where students actively create an answer, with an emphasis on construction and their own thinking. This point is, of course, linked to the principle of refletion.

Principle 3: Open-ended solutions

This principle is related to authenticity. It’s possible to see authenticity within the undergraduate computing project module.

Principle 4: Diversify assessment formats

This is linked to how students might relate assessment to their own interests and preferences. Providing a variety of different assessment formats also speaks to the importance of accessibility and diversity.

Principle 5: Authentic assessment

Making an assessment real by sharing an exciting concept can enhance motivation. Make an assessment authentic by drawing on their own experience.

Principle 6: New assignment questions

To limit the risk of academic conduct, prepare new assignment questions every year. Design the assignments in such a way that students cannot re-use a previous answer. In other words, make it difficult for students to directly benefit if the questions were to be shared.

Principle 7: Process besides product

Ask students to submit interim versions of assignments or ask them to provide a demonstration. In the computing project module, students are asked to submit a draft EMA as an assessment.

Principle 8: Making quality criteria transparent

Make rubrics transparent; share with students how assessments are made so everyone knows what the module team (and the university) is looking for. 

Principle 9: Generating and acting on feedback

Encourage students to generate their own feedback, which helps to develop critical thinking. This relates to a principle of peer assessment. This is used, to a limited extent in a software engineering module, where students comment on interim designs. 

Principle 10: Authentication methods

Are students who they say they are? There used to be a time when students had carry out written exams by attending exam centres at a specific date and time. As a part of this, students needed to show a form of ID, such as a passport or a driving licence. An alternative approach would be for a student to have a conversation with a tutor about their assignment.

TurnitIn

A recent development has been the increased availability of TurnItIn to students. Module teams and staff tutors always used to receive TurnItIn reports. These reports indicated whether a submission contained words found in other online resources. A typical TurnItIn report might highlight legitimate quotes that a student used to evidence an argument, as well as uncited text.

On many modules students can now submit an earlier version of an assignment into TurnItIn. In turn, they can review a ‘similarity report’ to gain confidence that their assignment is adhering to sound principles of good academic practice. More information about TurnItIn can be typically found within a module’s assessment handbook.

Resources

A whole host of useful resources are available to students. The blog post Study Skills Resources: what is available? offers a handy summary of some of the most useful.

Reflections

I’m not sure where these assessment principles come from. I really like them. I can bring these ten points into module team meetings. Their focus on authenticity strikes me as being really important. It is important in terms of problem solving, skill development and the application of knowledge.

Putting the assessment design principles to one side for a moment, tutors are really important. If appropriate, students can refer students for additional support sessions, and can also refer students to study advisors who work within the student support team.

Students can then be referred to additional support needs, and referral to a study advisor. In my experience tutors may sometimes get a sense when a student may have used Generative AI.

Acknowledgements

Acknowledgements are duly given to the academic conduct review team who facilitated this session. The principles shared in this blog post are their own, and I take no credit for them. I hope I’ve summarised them effectively.

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

XTXY112 Practice Tutor Briefing

Visible to anyone in the world

On 24th in September I attended a new module briefing at the University headquarters in Milton Keynes. Rather than being the usual ‘academic’ module briefing, this was a briefing for new practice tutors (PTs). 

Practice tutors support degree apprenticeship (DA) students. DA students are funded by employers. They have one day a week, or 20% of their time allocated to degree level study. 

Practice tutors are a part of a 3 way relationship between the employer, the student and the university. Their role is to support the student, and to facilitate the students progress though the pathway by working with employer and university representatives. On the employer side, there is also someone called the APDM, who is known as the Apprenticeship Programme Delivery Manager, who work with all employers who have apprentices at the OU. 

One of the most significant differences between a practice tutor and a module tutor is that rather than getting a new set of students every year, a practice tutor supports a group of students over a number of years. 

What follows is a quick summary of some of the things that practice tutors have to do, along with some more general notes and facts about degree apprenticeships. One thing that I should note is that whilst the roles are clearly defined, some aspects to the degree apprenticeship scheme may change. What this means is that if you’re reading this a couple of years after its publication, it’s entirely possible that things might have moved on from what was described here.

The code XTXY112 relates to the activity of supporting Digital Technology Solutions (DTS) apprentices who are based in England.

Key components

A degree apprenticeship consists of a number of different components. 

Qualification: the result of studying a combination of academic modules and completing work based learning-modules (where a student has an opportunity to apply academic ideas and practice new skills in a real work environment).

English and Maths functional Skills: although there are no entrance requirements to begin a degree apprenticeship, there is an exit requirement. If a student hasn’t gained a certain level of English and Maths skills, they must achieve a certain level by the end of the programme.

Portfolio and work based projects: students need to complete an agreed work based project which something that relates to a business need, and create a valued body of work, which is represented by regular contributions to an e-portfolio system.

End point assessment (EPA): students need to get to this stage, which represents an assessment of the knowledge, skills, and behaviours learnt from the apprenticeship programme.

All this leads to: a recognised apprenticeship that was designed with input from industry, a recognised degree, and an opportunity (if applicable) to register with a professional body.

There are a number of different people involved: there are the academic/module tutors who deliver academic modules who assess progress and moderate forum discussions. There are also the practice tutors who check and evidence the e-portfolios, reviews progress, carry out assessment of work-based learning (if applicable), and help with the end point assessment preparation. There are also apprenticeship programme delivery managers who handle the registration, employer liaison and the EPA processes.

Introductions

Since a PT is going to be important in the life of the degree apprentice student and represent a key point of contact with the university, a positive introduction is really important. 

A face-to-face meeting is expected to take place between the beginning of the module and 6 weeks with the apprentice, the practice tutor, and the apprentice’s line manager. To arrange a meeting, the PT will (like other OU tutors) send a welcome message by email. Following the introductory email, different bits of information are shared, such as contact details, confirmation of work addresses, and telephone numbers.

The first meeting

The first meeting is all about getting to know the apprentice and their line manager. It’s also about information sharing. It’s an opportunity to introduce the apprentice to the various OU systems and ways of working. A suggestion is to bring along a laptop, or ask to have access to a computer, as that way you can use it to talk the apprentice through some various bits of the OU system, such as: the StudenHome website, the module website, where to find information about the module tutor, where to find the assessment resources, what the study calendar is, what a TMA is, what cut-off dates are, and how to submit an assessment. It’s also important to ask whether they have been through the OU study materials (studying at the OU).

Another key issue to explore or address is the importance of time and planning. Since the apprentices will be working full time and will have dedicated study time, it’s important to find out whether they are aware of the time commitment that is necessary to study, and that time is carefully accounted for.

Another important topic that must be spoken about is something called the Individual Learning Plan (ILP), which is a progress report that is also used to record at least three objectives. The ILP will be completed and signed off by both the practice tutor and their line manager. During the meeting, the practice tutor must make the apprentice aware of the ILP, what it is and highlight that it must be completed, and it will be returned to during future meetings.

An important question to ask is: what pathway are they taking? The English degree apprenticeship has a number of different pathways through it. This discussion will help everyone have an early understanding of what the different options are. (More will be covered about the pathways later).

Record keeping

An e-portfolio system called OneFile is used to keep records of the work that an apprentice does. It can be thought of a document store that can be used to confidentially store evidence of progress that can be reviewed by other people. It can also be used as a personal journal too; evidence of learning can be selectively made available by an apprentice to their line manager, or to the practice tutor. 

It is used to store copies of the module TMAs that a student submits, and also keeps a copy of the ILP. I understand that it can also be used to gather evidence to support the completion of the ‘apprentice’ part of the degree apprenticeship. 

Quarterly and end of year reviews

An important role of the practice tutor is to keep a gentle eye on the apprentice; to make sure that they’re on track with their studies. The practice tutor may also check with the apprentice’s TMA results, and also send a quick note to a module tutor to ask whether everything is going okay.

Before a visit or meeting, an apprentice needs to update their ILP. The practice tutor might also send a note to the module tutor to ask how things are going, and if there have been any problems. A key question that might be asked is: has anything changed with respect to any study plans?

Towards the end of the first year, there will be what is called an end of year review about how things have gone. Also, towards the end of the second year, the PT will have a discussion with the apprentice about the different pathway options that exist through the apprenticeship programme.

It will be important to review ILP, and to discuss the objectives that can be set on the plan. A suggestion is to use SMART targets; targets that are Specific Measurable Achievable Relevant and Timebound. Discussions may include points about progression, training opportunities, and whether it is necessary to gain exposure to different parts of the organisation. Essentially, it will be about what has happened, and what may happen. 

Functional skills and prerequisites

There are no prerequisites to start on a degree apprenticeship programme, but they need to have functional maths, English and ICT skills by the time they finish. If apprentices don’t have at least a GCSE grade 4 in English and Maths (if I understand this correctly) they can complete what is known as function skills test, a two hour exam, run by an organisation called BKSB (website). 

It is recommended that apprentices complete them within their first 18 months of study. Records of gaining the functional skills in these areas will be stored within the student’s e-portfolio.  An important role of the practice tutor will be to make sure that students do complete these exams as early as they can, so as to make room in their study schedule for everything else that they have to do.

Modules that DA students will study

In the first year, students will study the following three modules:

TMXY130 Introduction to computing technologies: this module has a bit of networking, cybersecurity and bits of mathematics that are specific to computing. Students will complete formative interactive computer marked assessments (iCMAs), complete tasks using Cisco packet tracer, and complete 3 tutor marked assessments. The final EMA covers all three components of the module.

TMXY112 Computing and IT 2: three different themes are interlaced; hardware, problem solving and computing in the wild. During the module, students are introduced to the Python language. All the topics are connected to the development of skills. There are 3 summative TMAs, each contributing an increasing percentage to the overall score. Students must also complete various block quizzes.

TMXY122 Work based learning: students must design a study planner, and consider their study skills, and write a reflective piece. There are 3 x TMAs and an EMA. TMA 2 is skills based, where students must identify an IT related issue, and consider a hypothetical research project. They must also develop a research proposal to collect data. TMA 3 is about reflection, and asks students to relate their role to a national occupations database. Finally, the EMA relates to a professional (or personal) development plan. 

Looking towards the second level, student will study MXY250 Object-oriented Java, TMXY254 Managing IT: the why, the what and the how (which is about service management, and has a bit about relational databases), and TTXY284 Web Technologies

DA pathways

There are Four pathways through the English degree apprenticeship programme (things are different for Wales and Scotland). 

Students can opt for a Data Analyst pathway, where they may study OU modules such as M269 Algorithms, Data Structures and Computability (a computer science module) and TM351 Data Management and Analysis (where students get to write programs to analyse data).

Another pathway is the software engineering route, where students may study TM352 Web, Mobile and Cloud Technologies  and TM354 Software Engineering.

The third pathway is about cybersecurity. Here students will study TM352 Web, Mobile and Cloud Technologies which has a small amount of penetration testing, and TMXY311 which is about information and security management.

The fourth pathway is all about becoming a network engineer. Here the students will study some industrial Cisco material that also enables them to gain university credit. The modules are TM257 Cisco networking (CCNA) part 1 and TM357 Cisco networking (CCNA) part 2

Tips for the Practice tutors

What follows is a summary of tips that I’ve picked up from the briefing:

  • Emphasise that they need to do programming. This makes up an important aspect of the whole programme. They need to develop their skills in level 1, since it gets a whole lot more harder in the later levels.
  • Check to make sure that they have completed their OU induction.
  • Encourage the apprentices to speak to their module tutors as soon as they need to. Emphasise the point that they are there to help. Also, a practice tutor can ask a module tutor how their apprentice is getting along.
  • Make sure that they’re using the 20% of the time that they have available and emphasise the importance of time management. Also highlight that it’s important to get a work, life and study balance right. 
  • Record keeping is important, and this means that the individual learning plan needs to be filled in for each meeting. This needs to be signed by practice tutor, the apprentice, and the line manager.
  • Suggest that the OneFile e-portfolio tool could be used as a way to gather reflections (since reflections will be important in the work based learning modules).
  • The work based project is important. If they’re not in a position to do this easily, given their current role and responsibilities, find out whether there is a way that they can be temporarily seconded to an appropriate project. 
  • When considering the quarterly review, ask the question: has anything changed such as the study plan?

Acknowledgements

This blog was prepared from notes made during a briefing day that was organised by Chris Thomson, Computing and Communications Staff Tutor who also kindly copy edited (and corrected) an earlier version of this blog. During the day, presentations were given by Christine Gardner, David McDade, Claire Blanchard, and Caroline Stephens. Contributions were also made by XTXY122 staff tutors, Nigel Gibson and Ann Walshe. I also acknowledge the important role of the three Apprenticeship Programme Delivery Managers who helped us to further understand the role of the practice tutor. 

Permalink Add your comment
Share post
Christopher Douce

TM356 new tutor briefing 2018

Visible to anyone in the world

On 8 October 2018 I helped to deliver an online briefing to introduce new tutors to TM356 Interaction Design and the user experience, with a number of module team and staff tutor colleagues. What follows is a really brief summary of what was covered during this session.

I’m posting this blog for a couple of reasons: (1) so I can effectively share notes with everyone who attended, (2) so I can look back to see what I did when I helped to run a briefing, and (3) so I can easily remember what I’ve done when I get to that part of the year when I have my annual appraisal!

Agenda

The structure of the briefing was as follows: begin with some introductions and an ice breaker (so the new tutors can meet each other), present an overview and background of the module, and then present a summary of the module materials. The next part was to say more about the role of the tutor and the way that the module applies something called the Group Tuition Policy, including a description of all the key learning events. At the end there was a Q&A session.

The main ‘presentation’ part of the session was recorded, but the icebreaker session and the Q&A wrap-up session was not.

Tools

One of the slides mentioned the key tools and technologies that could be used for learning. These were: Open Studio (for the sharing of designs), discussion forums (module, cluster, tutor group), Adobe Connect for online tutorials (with the tutor, cluster forums, and module wide events), and prototyping tools (such as Balsalmiq).

Module materials and philosophy

A significant part of TM356 is based around a project; students are asked to think about an interactive product, which can be the focus of their investigations. There is also an emphasis on ubiquitous computing, iteration and prototyping.

The module consists of four blocks: an introductory block, a requirements block, a design block and an evaluation block.

Block 1, the introductory block has 4 units. These have the titles: Unit 1 - What is interaction design? Unit 2 - Goals and principles of user-centred design, Unit 3 - The ‘who, what and where’ of the design context, and Unit 4: Interaction design activities and methods. 

Block 2, requirements for interaction, also has 4 units: Unit 1 - Knowing the Users, Unit 2 - Exploring activities and contexts, Unit 3 – Data gathering for Requirements, and Unit 4 - Establishing Requirements.

Block 3, design and prototyping: Unit 1 - Understanding and Conceptualising Interaction. Unit 2 - Interface Types. Unit 3 - Design becoming concrete through prototyping, and Unit 4 - Conceptual design: Moving from requirements to first design.

Finally, Block 4, evaluation, has the following units: Unit 1 – Introduction to evaluation, Unit 2 - From data to information, Unit 3 - Planning and conducting an evaluation, and Unit 4 - Module reflection.

Tutorials

The module has three clusters (groups of tutors) which are broadly split across the UK. This module does have face to face tutorials; there is one towards the start of the module, and one towards the end. Here is a summary of the current group tuition plan:

  • Interaction Design - getting you started
  • Project choice workshop (module team)
  • Preparing for TMA 2: practising skills - data gathering for requirements
  • Prototyping and the development of concepts
  • Design Hackathon (module team and some tutors)
  • Prepare for TMA 3
  • Preparing for TMA 4: practising skills for evaluating your design
  • Preparing for exam: revision sessions (one block per cluster, and shared)

The design Hackathon is an event that is organised by the module team that is intended to expose students to collaborative design work. Suitable materials and electronics will be provided, and a topic for design activity will be agreed by the team beforehand.

At the event, tutors will help facilitate the students' work and reflections, in preparation for TMA03. For the 2018 presentation, the Hackathon will take place in Milton Keynes and Edinburgh at the same time, and students who were not able to attend physically will be able to connect to an online room and view presentations from both face-to-face groups to get some idea about what happened during the event.

Q&A and wrap up discussion

I didn’t make notes during the Q&A session, but I do remember a few things. I remember using the screen sharing tool in Adobe Connect to show tutors different parts of the TutorHome page and the module website. I also remember mentioning the importance of the tutor’s forum, highlighting a resources area, and a discussion about the introductory letter.

I’m also pretty sure that I emphasised that every tutor should make good use of their staff tutor (their line manager): their job is to answer questions about anything, and address any worries that they may have.

Permalink Add your comment
Share post
Christopher Douce

TM354 Software Engineering: briefing

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

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

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

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

Module structure

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

Block 1 : from domain to requirements

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

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

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

Block 2: from analysis to design

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

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

Block 3: from architecture to product

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

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

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

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

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

Software

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

Assessment

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

Tutorials

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

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

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

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

Permalink Add your comment
Share post
Christopher Douce

T217/8 module briefing

Visible to anyone in the world

Even though I’m based in the Computing and Communications department, I have to confess that I do a bit of moonlighting in the Engineering and Innovation department.  I don’t feel too guilty about doing this since there is a lot of cross over between some of the subjects.  One of the cross over subjects is design: computer systems need effective and efficient interfaces, and software systems need (obviously) to be designed (or engineered).  An important question is how we might set about creating different designs.  There are, of course, strong connections between the subjects of design and engineering too.

This blog post is from a set of notes that I made during a module briefing that I attended on 28 September.  Module briefings are events that happen whenever a new Open University module starts.  It’s an opportunity for the module team to meet all the associate lecturers who have been recruited and an opportunity for them to ask questions about how things are going to run.

The event on the 12 September introduced two new design modules: T217 Design Essentials and T218 Design for Engineers.   These two second level modules follow on from a first level introductory module, U101 Design Thinking.  Whereas U101 (as far as I understand things) helps students to start to think like a designer though engendering a playful and reflective approach, T217 and T218 begin to focus on more practical and detailed issues that relate to products and how they might be manufactured.  The forthcoming T317 module, Innovation: Designing for Change, will move things along a bit further by considering wider issues, such as how design connects with and interacts with society.  (I’ve only heard snippets about this new module, so I had better not go on and say something that patently isn’t true!)

The briefing wasn’t held in the university but in a nearby conference centre.  Without having done a head count, I estimate that there were about thirty people in total.  This includes T217 and T218 tutors and their line managers (staff tutors) who will be helping within things behind the scenes.  We were, of course, joined by members of the T217/8 module team (Theo Zamenopoulos, Georgy Holden and Jeff Johnson) and our curriculum manager (Hannah Juma).

Module structure

Much of the following information is available on the module description, but I’m also including it here too (since it was explicitly covered during the briefing).  T217 comprises of five blocks.  These are: exploring designs and designing, designing for people, creative designs, embodying designs and design for making.  The module comprises of a set of printed books as well as a modelling workbook, which helps students to get to grips with sketching (an invaluable skill for communicating the designs of products).

There is, of course, a module website which leads everyone through the module materials a week at a time.  During the module, there are a set of skills development activities.  There are three types: design activities, assessment activities (which help to prepare students for the assignments), and workbook activities (which are all about building skills and confidence).

T217 is assessed by four tutor marked assignments and an end of module exam.  T218, on the other hand, is slightly different – it has three tutor marked assignments and is examined by a substantial piece of work, which is known as an end of module assessment.

Block summary

The first block is all about big ideas in design and how it relates to engineering, human and cultural perspectives.  It contains some ideas from the history of design and tries to get students sketching.  (The design of chairs features heavily in this first block, since they permit different aspects or perspectives on design to be exposed).  The message for the second block is that it is essential to consider the end user.  This second block also takes some first steps towards thinking about environmental issues.  

The third block is a bit different.  This block addresses theories of creativity and invention and how these are reflected in the practices of creative designers and engineers.  It exposes students to different techniques about how to help designers to become more creative.

Block four is about how to move from a broad concept design into a more detailed design that could be eventually manufactured.  It also continues to help students to think spatially and visually.  In this block there is also an emphasis on style and branding and how it relates to design.

The final block moves into even more detail.  It covers issues such as the choice of materials for prototyping and manufacturing, encouraging students to analyse existing artefacts.  I made a note of the terms, ‘materials, methods and emotions’ during the briefing.  The block also makes connections with open source projects and introduces students to maker and hacker communities.

Software

Although you might argue that the designer’s most powerful tool is a pencil, developments in information technology has led to the emergence of new and exciting design and illustration tools.  Software and information technology can also take us towards new ways of working.  One of the challenges with learning design at a distance is that students don’t have the opportunity to work within a studio space (where students might have an opportunity to wander around to look at the work that other designers are working on, allowing students to gain not only motivation but also inspiration).  Building on the experience gained in U101, the T217 module team are using some on-line social software called OpenDesignStudio.  This is a web application that allows students to share aspects of their work to other students.  Sharing is done through the use of images.  Students might take photographs of sketches or rough physical models.

Students are also encouraged to use of 3D drawing software, such as SketchUp (Wikipedia).  They can also use other (but different) 3D drawing software, allowing students to gain an appreciation of the differences between tools.  Other software includes a database about different materials and manufacturing methods (which students can used to inform their assignments), and a tool that can be used to create mind maps.  (Students who studied U101 will remember a software package called Compendium).

On-line and face to face tutorials

A part of the day was also spent discussing on-line and face to face tutorials.  Although most of the teaching (and learning) is performed through the module materials and the guidance that associate lecturers offer in response to tutor marked assignments, students can also attend a number of interactive tutorials.

The face to face tutorials (or day schools) are arranged by the regional centre that a tutor is affiliated with.  The on-line tutorials, on the other hand, are held in an ‘on-line OU live’ room.  This is a virtual space where tutors can speak to students through their computer.  During the briefing, tutors were briefly shown how to use and access these on-line rooms.  Towards the end of the day, there was an activity where different groups of tutors got together to plan a day school (which is OU parlance for a bigger multi-group event that is held usually on a Saturday) to help students become familiar with a module.

Reflections

I always enjoy going along to module briefings; they’re always fun and useful events, and this was no exception.  A couple of weeks after this event both T217 and T218 began their first presentations.  For me, three things stood out during this day.  The first is the extent to which the design team are building on the work that they carried out in the earlier first level module: U101 Design Thinking.  The second is that the T217 module (as well as T218) has a very clear and compelling structure which relate to very explicit themes within design.  The third is the way that software and technology has been embedded within the module.

A final thought was that I was easily able to connect aspects of T217 and T218 to the module that I’ve been a tutor on for a number of years: M364 Fundamentals of Interaction Design.  I could clearly see links between areas such as user centred design, accessibility and the importance of skills such as sketching (as a way to rapidly communicate aspects of a design to others).  This, to me, underlined the importance and the need for connections between different subjects and disciplines.

Although I started this blog post by confessing that I have been moonlighting in another department, this term shouldn’t be used in a derogatory or negative sense.  When it comes to sharing perspectives and gaining insight into what happens in a slightly different (but connected) subject, moonlighting should be positively encouraged.

Acknowledgements

Many thanks to Theo Zamenopoulos (T217 module chair), Georgy Holden, Jeff Johnson (T218 module chair) and Hannah Juma (curriculum manager for T217 and T218) for running the briefing.

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