Ghana curriculum lesson note
SHS 1 Computing 1st Semester Week 10 Lesson Plan
Need the editable version?
Generate, personalize and download the complete lesson plan on Sirbus.
Create Lesson Plan| Weekly Learning Plan | |||
| Subject | Computing | Week | 10 |
| Duration | 60 minutes | Form | SHS 1 |
| Strand | COMPUTER ARCHITECTURE AND ORGANISATION | Sub-Strand | DATA STORAGE AND MANIPULATION |
| Learning Outcome(s) | 1.1.1.LO.1 - Apply Computer Architecture concepts related to the design of modern processors, memories, Input and Output to manipulate data | ||
| Content Standard | 1.1.1.CS.1 | ||
| Learning Indicator(s) | 1.1.1.LI.4 - Understand and explain the control bus, address bus, data bus and the internal clock, Machine Cycle, Von Neumann architecture (Fetch–Decode–Execute-Store Cycle), instruction set for a CPU, Harvard architecture and embedded systems Group Activity: • In groups, let learners collaborate and brainstorm on the following components and concepts of Computer Architecture: Control Bus, Address Bus, Data Bus, Internal Clock, Machine Cycle, Von Neumann architecture (Fetch-Decode-Execute-Store Cycle), and Instruction set for CPU. • Guide the group discussions by providing prompts and questions that encourage in-depth exploration of each component or concept. • Assess learners based on their ability to articulate the purpose, functioning, and interconnections among these components and concepts, as well as their ability to relate them to data manipulation | ||
| Lesson Focus | Understand and explain the control bus, address bus, data bus and the internal clock, Machine Cycle, Von Neumann architecture (Fetch–Decode–Execute-Store Cycle), instruction set for a CPU, Harvard architecture and embedded systems Group. | ||
| Previous Knowledge | Learners recall related ideas, vocabulary or experiences from earlier lessons and everyday contexts. | ||
| Lesson Objective(s) | Describe the key idea in: Understand and explain the control bus, address bus, data bus and the internal clock, Machine Cycle, Von Neumann architecture (Fetch–Decode–Execute-Store Cycle), instruction set for a CPU, Harvard architecture and embedded systems Group. Apply the idea through guided and independent learning activities. Demonstrate understanding through oral responses, written work or practical performance. | ||
| Essential Question(s) | What computing concept, system, algorithm or technology is central to Understand and explain the control bus, address bus, data bus and the internal clock, Machine Cycle, Von Neumann architecture (Fetch–Decode–Execute-Store Cycle), instruction set for a CPU, Harvard architecture and embedded systems Group Activity: • In groups, let learners collaborate and brainstorm on the following components and concepts of Computer Architecture: Control Bus, Address Bus, Data Bus, Internal Clock, Machine Cycle, Von Neumann architecture (Fetch-Decode-Execute-Store Cycle), and Instruction set for CPU. • Guide the group discussions by providing prompts and questions that encourage in-depth exploration of each component or concept. • Assess learners based on their ability to articulate the purpose, functioning, and interconnections among these components and concepts, as well as their ability to relate them to data manipulation? How can we model, test or build the concept using hardware, software, code, diagrams or simulation? How can this knowledge be applied to solve a new real-life computing problem? | ||
| Pedagogical Strategies | Problem-Based Learning Collaborative Learning Pair Programming/Peer Review where appropriate Demonstration and Guided Practice Project-Based Learning Digital/Simulation-Based Learning | ||
| Teaching & Learning Resources | Computer(s) where available Projector/TV where available Computing textbook/reference materials Whiteboard/markers Learners' notebooks Notepad or exercise book Pen Smartphones Laptops Desktop computers Tablets TV and Radio Open Educational Resources (including YouTube, MOOCs - Udemy/Coursera, Khan Academy, and TESSA) The iBox/iCampus (CENDLOS) Productivity tools ix. Subject-based application software Instructional Laboratories (with multimedia equipment and smartboards) Computer hardware components or labelled diagrams System-unit/component images Code editor/IDE or visual programming environment Sample code files | ||
| Key Notes on Differentiation | |||
| Content | Use labelled diagrams, step-by-step worked examples, starter code, partially completed flowcharts or guided configuration sheets for learners who need support. Extend advanced learners with optimisation, debugging, system-design trade-offs, additional features or more complex test cases. | ||
| Process | Use mixed-ability grouping and pair work, rotating roles such as driver, navigator, tester, documenter or presenter. Where devices or internet access are limited, use offline simulators, printed code/diagrams, unplugged activities and shared-device rotations without changing the learning objective. | ||
| Product | Allow appropriate evidence such as annotated diagrams, algorithms, pseudocode, code, app screens, webpages, network designs, troubleshooting reports or presentations. Assess correctness, computational reasoning, functionality, testing/debugging, documentation, responsible digital practice and ability to justify design decisions. | ||
| Success Criteria | Learners use correct subject vocabulary. Learners complete the main task with reasonable accuracy. Learners explain or demonstrate how the concept applies in a new situation. | ||
| Homework | Complete a short application task connected to the week's learning indicator. | ||
| Lesson Activities | |||
| Stage | Teacher Activity | Learner Activity | Assessment / DoK |
| Starter10 minutes | Show a simple digital example involving data storage and manipulation and ask learners to predict what is happening. | Share prior knowledge, listen to peers and record the lesson question in their notebooks. | Not provided. |
| Activity 115 minutes | Demonstrate data storage and manipulation using a board sketch, device setting, code snippet, data table or simulation. | Observe the demonstration, identify the key parts and explain their functions. | Ask learners to define the key term and identify it in the demonstration. |
| Activity 220 minutes | Guide learners through a hands-on task where they apply data storage and manipulation and record the result. | Complete the practical task, test the result and note any errors or fixes. | Check the task output for correct procedure, testing and explanation. |
| Activity 310 minutes | Present a different digital scenario and ask learners to use data storage and manipulation to solve or explain the result. | Apply the idea to the new scenario and present the result or explanation. | Use a short exit task requiring learners to apply the idea in another digital context. |
| Lesson Closure | Summarise data storage and manipulation and correct one common misconception using learner examples. State one thing learned and complete the exit response. | ||
Need the editable version?
Generate, personalize and download the complete lesson plan on Sirbus.
Create Lesson PlanMore SHS 1 Computing 1st Semester Lessons
Week 1Sub-strand: DATA STORAGE AND MANIPULATIONWeek 2Sub-strand: DATA STORAGE AND MANIPULATIONWeek 3Sub-strand: DATA STORAGE AND MANIPULATIONWeek 4Sub-strand: DATA STORAGE AND MANIPULATIONWeek 5Sub-strand: DATA STORAGE AND MANIPULATIONWeek 6Sub-strand: DATA STORAGE AND MANIPULATIONWeek 7Sub-strand: DATA STORAGE AND MANIPULATIONWeek 8Sub-strand: DATA STORAGE AND MANIPULATIONWeek 9Sub-strand: DATA STORAGE AND MANIPULATIONWeek 10 (current)Week 11Sub-strand: COMPUTER HARDWARE AND SOFTWAREWeek 12Sub-strand: COMPUTER HARDWARE AND SOFTWAREWeek 13Sub-strand: COMPUTER HARDWARE AND SOFTWAREWeek 14Sub-strand: COMPUTER HARDWARE AND SOFTWAREWeek 15Sub-strand: COMPUTER HARDWARE AND SOFTWAREWeek 16Sub-strand: COMPUTER HARDWARE AND SOFTWARE