Lesson Plan

• Describe the key characteristics that differentiate embedded systems from general‑purpose computers.
• Identify common hardware components of an embedded system and their roles.
• Explain the step‑by‑step design process for developing embedded firmware.
• Compare real‑time constraints and reliability requirements of embedded devices.

• Projector and screen
• Whiteboard and markers
• Printed handout with component table and design steps
• Arduino (or similar) development board and USB cable
• Laptop with Arduino IDE installed
• Sample code for a simple LED blink (real‑time timing demo)
• Exit‑ticket slips

Begin with a quick show‑of‑hands: “Who has used a digital thermostat or a car’s ECU?” Connect this to prior knowledge of how computers work, then state that today students will discover why those devices are special. Explain that by the end of the lesson they will be able to list embedded components, compare them to PCs, and outline a design workflow.

1. Do‑now (5'): short quiz on differences between PCs and embedded devices; collect responses.
2. Mini‑lecture (10'): present key characteristics and typical components using the block diagram.
3. Case‑study activity (15'): groups analyse a smart thermostat scenario, identify components, constraints, and required reliability.
4. Design process walkthrough (10'): step‑by‑step explanation of functional definition, hardware selection, firmware development, integration, and validation.
5. Hands‑on demo (15'): program the Arduino to blink an LED with a fixed period, discuss deterministic timing and WCET.
6. Check for understanding (5'): exit‑ticket question – “Name one hardware constraint that influences an embedded design.”

Summarise the main points: embedded systems are purpose‑built, resource‑constrained, and often real‑time. Collect exit tickets, then preview the next lesson on IoT integration. For homework, ask students to choose an everyday device, research its embedded components, and write a brief paragraph describing its design constraints.