Systems approach to designing

Welcome to the Systems Approach!

Hello there! Today, we are going to look at one of the most important "Core Technical Principles" in Design and Technology: the Systems Approach to Designing.

Don't let the word "system" intimidate you. In simple terms, a system is just a group of parts working together to do a job. Think of a bicycle, a toaster, or even your own body—they are all systems! In this chapter, we focus specifically on electronic systems and how they make products smarter and more useful.

What is a Systems Approach?

When designers use a systems approach, they don't just look at a product as one big chunk. Instead, they break it down into three main stages. We call this the Input-Process-Output model (or IPO for short).

Memory Aid: Just remember "I Play Outside" to keep Input, Process, and Output in the right order!

1. The Input

The input is how the system "senses" the world around it. It gathers information from the environment and turns it into an electrical signal.

Analogy: Think of inputs as the "senses" of a product, like your eyes, ears, or skin.

According to your syllabus, you need to know these specific input components:

• Light Sensors (LDRs): These detect how bright or dark it is. Example: A street light that turns on automatically when it gets dark.
• Temperature Sensors (Thermistors): These detect heat. Example: A digital thermometer or a central heating system.
• Pressure Sensors: These detect physical force or weight. Example: An alarm that goes off when someone steps on a hidden mat.
• Switches: These are the simplest inputs. They are either "on" or "off" based on a person pressing them. Example: A doorbell button.

2. The Process

The process is the "brain" of the system. It takes the information from the input, thinks about it, and decides what to do next. In modern products, this is usually done by a programmable microcontroller.

Analogy: This is like your brain deciding to pull your hand away if you touch something hot.

The microcontroller can be programmed to perform specific tasks:

• Counters: Keeping track of how many times something has happened. Example: A turnstile counting people entering a stadium.
• Timers: Waiting for a specific amount of time to pass. Example: A microwave waiting 30 seconds before stopping.
• Decision Making: Using "If... Then..." logic. Example: IF the light sensor detects darkness, THEN turn on the lamp.

3. The Output

The output is the "action" part of the system. It is what the product actually does to react to the information it received.

Analogy: This is like your voice speaking or your legs walking.

Your syllabus focuses on these three outputs:

• Buzzers: Create a buzzing sound. Example: The "beep" at the end of a washing machine cycle.
• Speakers: Create more complex sounds or voices. Example: The voice in a GPS Sat-Nav.
• Lamps: Create light. Example: An LED indicator on a phone showing it is charging.

Quick Review:
Input: Senses (Light, Temp, Pressure, Switches)
Process: Brains (Microcontrollers doing counting, timing, and decisions)
Output: Action (Buzzers, Speakers, Lamps)

Why Use Microcontrollers?

In the past, electronic circuits were "hard-wired," meaning if you wanted to change how a product worked, you had to rebuild the whole circuit!

Today, we use programmable components (microcontrollers) because they allow us to enhance and customise how a product operates just by changing the software code.

Did you know? Using a microcontroller often makes a product smaller and cheaper to build because one tiny "chip" can replace dozens of older, bulkier components!

Step-by-Step: How a System Works

Let's look at a Night Light as a real-world example:

Step 1 (Input): An LDR (Light Sensor) detects that the sun has gone down and the room is dark.
Step 2 (Process): The Microcontroller receives the signal from the sensor. It checks its "decision logic": "Is it dark enough to turn the light on?" If the answer is yes, it sends a signal to the next part.
Step 3 (Output): The Lamp turns on, lighting up the room.

Common Mistakes to Avoid

1. Mixing up Inputs and Outputs: Students often think a switch is an output because it "makes things happen." Remember: if a human or the environment provides the information, it's an Input. If the machine does the action, it's an Output.

2. Forgetting the Process: A sensor cannot talk directly to a buzzer without a "brain" in the middle to tell it when and how to buzz!

Summary: Key Takeaways

• A systems approach breaks a design into Input, Process, and Output.
• Inputs (sensors/switches) triggered by the environment.
• Processes (microcontrollers) handle logic, timing, and counting.
• Outputs (buzzers/lamps/speakers) provide the physical result.
• Programmable components allow designers to customise products easily without changing the hardware.

Don't worry if this seems a bit technical at first! Just keep thinking about the "IPO" flow for every electronic gadget you see today, and it will soon become second nature.