51ºÚÁÏ

This is a 6 week SOW which introduces learners to the concept of abstraction, pseudocode writing, and then flowcharting, with examples, and easy to follow PowerPoints with activities to deepen learning. Abstraction, pseudocode, flowchart, create, debug, improve is given as a cycle for learning programming. Lessons 4 5 and 6 are about creating a step by step Fifa football game with challenges at the end. There are differentiation tasks throughout the sow.

This is a whole half term of work relating to the questions appearing in the second Computer Science paper. The lessons are on input, processing, output selection statements boundary testing recognising constructs trace tables a test The lessons guide the learner from easy to understand exercises, to GCSE level exercises. There is a learning question focus for each lesson, but in some cases the bronze silver and gold outcomes have been left blank for you to tailor to your classes. There is enough work here for a half term.

Building on from knowledge of flat file databases, tables, fields, records, this lesson guides the learners on a journey into foreign keys, relationship types (one to many, many to many, one to one) They are given fields names at first to rearrange into two tables for one to many, learning the concept of how we decide upon the relationship to use. This builds further into recognising where to use a foreign key. The knowledge is expanded upon with the introduction of many to many relationships, and the concept of link, or junction tables. Learners then have the opportunity to test their knowledge. Answer slides are given. This was observed and judged to be engaging, and showed excellent progress. Everybody needs a bit of that!

This resource is mainly PPT for three lesson, a double history, and single people. All LO and outcomes are included. There are links to other resources. There is a worksheet for learners to fill in and learn the influential people. Finally there is a end of unit test with mark scheme graded on the 9-1 scale. Although I have aimed this at middle to lower ability year 7, it can be adapted to year 6-9 with a few tweaks. My year 7 were completely engaged, and loved learning about something that they believed began in 2000!!!

Is a PowerPoint with revision notes on networks and network protocols. It contains link to a Kahoot. It is meant to be used in conjunction with the exam paper, mark scheme made purely of communication and network questions from past papers. I've deliberately left it image free, and just the content needed for the past papers.

An engaging resource which develops an understanding of manipulating lists in Python. There are two lessons here, first to introduce the topic and the second to consolidate learning. The answers are included as are extended learning tasks.

This PPT with exercises takes the learner through all of the concepts in the Programming Subset List 1. Data types. Input / Output. Maths operators, including modulus, exponent, Boolean, integer division. There are coding tasks, and enough work for around 3 or 4 hours of GCSE in preparation for the coding part of the exam. See also PLS2 if you like this resource!

This resource takes the learner through everything in the Programming Language Subset 2. Coding structures IF statements Loops Sub programs Input and output File handling With examples and tasks. This is around 3-4 hours work and covers the whole of PLS2, and can be worked on individually / at home, or set as a whole term HWK task. If you like this, PLS1 is also available to buy.

A lesson which was described as ‘outstanding’ for it’s engagement of the youngsters. It covers personal data, legislation, big data, and breaches, surveillance issues, and the benefits of surveillance. There are two PPTS, one is teachers (with answers) and one for the learners. There are opportunities for discussion, research, short answer question, long answer question, and recall from previous T5 lessons. It has it all!

This is one of a series of lessons teaching about the issues of computing. This one focusses on what we use technology for, and the effect of those who either cannot, or will not use technology. The impact of technological exclusion is discussed. There is an opportunity to do a little research into the downside of technological inclusion, with gaming addiction (to balance the argument). There is also the opportunity to complete a six mark question with AO1, AO2, AO3 guidance. There is also a model six mark answer showing how the marks for each section are awarded, and the opportunity to peer mark. Student PPT does not contain the answers, whereas the teacher one does. I tend to put student copy on Google Classroom, and have teacher copy on the board for them to check answers after the task is finished. Then at the end of the lesson I remove the student copy, and put the teacher copy up, for isolators, or for revision purposes.

It can be difficult to think up new ideas for coding, and embedding skills. Have the benefit of my 10 years teaching coding with this resource. After you have taught the content of PLS 1 and 2, give the learners these 11 challenges to get their teeth into. I have included a teacher file with suitable answers for each. You could add to the learner file with more hints, or take away the hints I have given. Skills tested that will prepare them for the coding examination: IF, concatenation, iteration, tuples, constants, variables, write to file, sub routines, functions, global variables and much more.

I put together this pack aimed mainly at KS3, and as the Esafety Officer at my Academy. The pack includes lessons on hoaxes, keeping personal data safe, live streaming and reputation, gaming addiction, and bullies/ trolls. All have been made with regard to the new KCSIE recommendations. There is a powerpoint for each lesson, chance for discussion, and different tasks each lesson to embed the knowledge. These lessons have been delivered as a half term full unit, and have also been delivered in the PSHEE last year, as the last lesson before a half term, thereby lasting for one year.

Excellent resource that is very popular with GCSE students in Computer Science. Students are arranged into guild teams, then given 6 challenges (1 per lesson) They earn points for their team, and can choose from a simple, intermediate, or expert level of coding for the given task. Loops, random, subroutines, turtle, adding scores, and finally a TKInter project are all included. The students have so much fun, but be aware, they get very competitive! It is useful to mix high level with low level coders, as the high level will prompt low level on how to achieve the higher marks. This will last around 6 lessons.

This unit of work will easily fill a half term with teaching of: inputs and outputs Variables IF statements Delays Sub routines Iteration Lists All in the form of a memory game ‘you enter a cave, do you turn left or right?’ This is best suited to students who have a little knowledge of inputs outputs and IF, and can be used to expand upon that knowledge. I cannot upload Py files, but if you email me annemariebradshaw@hotmail.com I will send teacher files to you (there are screen shots of the coding in the unit though)

This resource will last around three lessons. It ties in error types such as syntax, and logic and relates them to what the learner will find in Python. It covers how to spot errors, what the common pop ups are, variable name errors, and the most common ones- casting errors, and the terrible indents. I have clearly gone through ‘belonging’ with indentation, and how to get a fix. Trace tables get a mention with one exam paper showing a for loop and a print statement outside of the loop. Many learners lost 6 marks for not understanding ‘belonging to the loop’. Well not anymore! There are a bank of Python files to go with this resource, but I cannot upload them here. If you email me annemariebradshaw@hotmail.com I can send those to you to. This is a fresh way of teaching errors, and also a good way of embedding Python coding skills, meaning that in the assessment they will be able to help themselves debug their own code. There is