Hell No, No More Quals For Us!

I'd like to tell you about one of my students. We shall call her Mel (not her real name). I can't remember how Mel came to me, though I do know it was through her father who we shall call Bob (again, not his real name).

Bob and Mel lived, with the rest of their family (and a number of furry friends) in Spain, though they were British by origin. They'd been living there for some time, Mel was I believe somewhere between 19 and 21, and wanted to study A-level Computer Sciene with me. Oh, and there was a small hiccup: Mel was almost entirely non-verbal and communicated primarily from off-camera through Bob. The reasons for this I was never entirely sure about, but I think a large part of it came from moving first to a Welsh-speaking school and then a local Spanish speaking school and losing confidence with her use of words. A terrible shame, and I know Bob felt guilty about this - he shouldn't: we do our best for our children and he certainly showed nothing but love every time I met with them.

So we worked through the A-level specification, and I was pleasantly pleased. Bob led the conversations, Mel contributed from the side, and achieved very well. Understanding was strong. Time passed, Mel flew to the UK and sat her AS exams. Well - she sat part of one of them: she froze. The environment, the formality, the pressure all too much.

We thought that was it.

Thankfully it wasn't. Bob contacted me and we came up with a plan. Mel has no set plan for her life. University wasn't on the cards. She may or may not want to work in IT but it wasn't a real desire. She wanted to continue studying, but didn't want to study towards the A-level exams as he knew she woudln't be able to actually engage with them. What to do, what to do...

With their agreement, I set up a bespoke course. It will be signed off by my educational company in the same way as any other training course can be, but be designed as an A-level plus. It doesn't carry any UCAS points, but other than getting into University, why would that matter? The academic intent of the course is to cover A-level material as relevant, but somewhat more. All the things that are removed or reduced from A-levels due to guided learning hours, Ofqual scrutiny, and the need to examine are back on the table. The assessment strategy is simple: it will work around the student. Recall is minimally assessed - skills and ability much more so. Automated assessment where feasible. I've got to know Mel and Bob really well over the last few years, if Bob tells me Mel did the assignment on her own, then I've got no reason to doubt him. Would I trust every student, and every parent? Hell no, but I'm able to apply a professional judgement here. Assessment objectives, and in particular their weightings, are able to be flexible based on learner need, but are generally:

AO1 Demonstrate knowledge and understanding of the principles and concepts of computer science

AO2 Apply knowledge and understanding to analyse problems and construct solutions

AO3 Design, program, and evaluate computational solutions using reasoned judgement

Not a million miles away from a "normal" A-level. Seventeen units were designed, with unit 17 being quadruple weighted to give an effective twenty unit course.

Unit 1: Python Fundamentals. Like every other introductory programming module, although I decided not to shy away from using Python. Out of the back end of this module, learners can put together a decent enough program.

Unit 2: Data Structures I. This expands Unit 1 to include the data structures built into Python; lists, tuples, sets, dictionaries, nested structures. Again because we're up-front about learning Python, we can focus on Python and assess through code.

Unit 3: Algorithms I. This covers the usual standard algorithms, but also covers the complexity of algorithms. This is not normally introduced until the full A-level - but why bounce back and forth?

Unit 4: Logic and Boolean Algebra. Some A-levels rely on K-maps, some on simplification. There simply isn't time for both. Well, that's not a problem we have so we can look at both approaches and go in to as much depth as we want.

Unit 5: Mathematical Structures for CS. Some of this is in all A-levels: bases, for example. But CS is a highly mathematical subject - and due to the siloism of the education system much mathematics is left out - this is wrong. So we cover sets, relations, mappings, induction and proof techniques. We learn to model data and operations formally.

Unit 6: Data Representation. Thisis our standard binary, hex, etc, plus text, image and sound manipulation. It doesn't go much further than normal A-levels, though the flexibility to talk about things beyond the specification is lovely.

Unit 7: Introduction to AI & Machine Learning. This is where things become interesting. A-level specifications are generally quite "behind the times" at best. Learning about AI takes time and effort and the amount of content even in the newest specs is horrendously low. We have the option to actually train and test simple models and critically reflect on the limitations and risks of AI systems. Joy.

Unit 8: Algorithms II. While we covered the "standard" algorithms in Unit 3, now we can focus on the interesting ones: recursion is introduced, as is backtracking, graph searches, Dijkstras, A* if we want it, heuristics, divide and conquer. There is flexibility to go as far as we need and learn why these algorithms are used rather than the standard learn to do it.

Unit 9: Data Structures II. This takes us beyond the built-in structures of Unit 2 and introduces abstract data structures as a concept, looking at stacks, queues, linked lists, trees, graphs, hash tables and the like.

Unit 10: Computer Architecture. Here we focus on the CPU, the von Neumann model, and are clear and open about the abstractions that are made. Some assembly code programming is also learnt. This is a module that I'd like to expand at some point because (a) the history of architecture is largely ignored, (b) it's evolving all the time although the abstractions taught have not changed in 20+ years and (c) it's real Computer Science stuff.

Unit 11: Communication and Networks. In the specification I've got the OSI model, though really the TCP model needs to be taught explicitly as well. A note to change (which, given the way this is designed, I can do!). We also look at the usual protocols, transmissions modes, network devices etc. Not my favourite topic (and not something I'm ashamed of!) but important all the same.

Unit 12: Databases. Again there's nothing "new" about this compared to A-levels, although we don't have to cut out bits for time saving. I always focus databases on computers and teach both in MySQL and using Python with SQLite.

Unit 13: Software Engineering. Most A-levels, if they touch on this, are fairly vague and give it a nod. I don't pretend a single unit can match a degree, or any of the many books on the subject, but we will cover modern agile methods, project design, the importance of testing and documentation, debugging, and one of the most sought after employability needs, version control.

Unit 14: Formal Methods and Computability. Often overlooked, this used to be one of the most fun parts of AQA for me. Finite state machines, regex, Turing machines, the halting problem, and similar.

Unit 15: Cybersecurity and Ethics. Covered in many A-levels... ish. A good overview of frameworks and at least touching on modern cybersec principles, the critical bit is the ethics. A good ethical argument is great fun and learners need to both be supported and be able to navigate their way through ethical dilemmas.

Unit 16: Object-Oriented Programming. While the content doesn't differ from most A-levels, this unit should be used to really use OOP in anger, to really learn the skills neded.

Unit 17: Final programming project. An NEA. Counting four times, but focussing on the project and the write-up, looking for a fair average between the focus on GUI and write-up in OCR and the focus on complexity in AQA.

Each unit is graded Pass, Merit and Distinction. We don't need to set hard percentages for each grade at this point, but accept that a pass demonstrates basic competence of the core concepts. A merit shows a good grasp of the material with thoughtful application. A distinction reflects exceptional understanding, clarity and execution. To pass, you must pass all units. A merit requires 15 at merit or above. A distinction means 15 at distinction or above. 15 distinctions and 5 pass means a distinction.

What really makes this approach different, and probably unsustainable for a significant number of students, is the format can vary for the student. For Boolean simplification, I set up a website for Mel where she could do the simplifications online. Other students may find something hand-written more appropriate. The ethics module she mis-read the question which was to identify and discuss two news articles, but the level of detail she went into regarding a single story, with full-on academic references, demonstrated the outstanding understanding that I really want to recognie. We also accept resits. As many as the student needs - because it's all about the student and their learning.

Mel has made good progress, great progress in fact: sadly we've parted ways in terms of regular sessions, as Bob and family have moved back to the UK with all the challenges and costs involved, but Mel is still working through the material and assignments. We've had some great successe on the way. Some days when Bob hasn't been around Mel and I had 1:1 sessions where she was happy talking to me. Every assignment she's done she's aced - straight in at a distinction. I'm not surprised - it's harder than the AS assessment she had to walk away from, but it's done on her terms.

So maybe Mel won't get UCAS points and A-level qualifications. What the hell, she's going to get a piece of paper that shows she has amazing knowledge, understanding and skills. And by hell she's going to know she earned it.