IT systems

Welcome to the World of IT Systems!

In this chapter, we are going to explore what an IT system actually is. Many people think it’s just a computer on a desk, but it’s actually much bigger than that! We will look at how systems are designed, how data moves through them, and how to decide if a system is actually doing its job properly. Don't worry if some of the diagrams look like a maze at first—once you know the "map," they are very easy to read!

4.1 Systems Design: The "Big Picture"

An IT system isn't just a piece of metal and plastic. To work correctly, it needs four specific ingredients working together.

The Four Pillars of an IT System

1. Hardware: These are the physical parts you can touch (like a keyboard, a server, or a tablet).
2. Software: These are the programs and instructions that tell the hardware what to do (like an App or an Operating System).
3. Processes: These are the rules or steps followed to achieve a goal (for example, the steps a shop takes to scan an item and take your payment).
4. People: The most important part! These are the users who interact with the system or the technicians who keep it running.

The Baking Analogy: Imagine you are baking a cake. The Hardware is the oven and the bowls. The Software is the recipe book. The Process is the actual mixing and baking steps. The People are the bakers (you!). If any one of these is missing or broken, you don't get a cake!

Decomposition: Breaking it Down

Complex systems can be overwhelming. To understand them, we use Decomposition. This simply means breaking a large system down into smaller, more manageable sub-systems.
Example: A "School IT System" can be decomposed into a "Registration Sub-system," a "Grading Sub-system," and a "Library Sub-system."

Fitness for Purpose

When we evaluate a system, we ask: is it fit for purpose? This means: does it actually do what the user needs it to do efficiently? A supercomputer is amazing, but it isn't "fit for purpose" if you just need to send a simple text message!

Quick Review: An IT system = Hardware + Software + Processes + People. To understand it, break it into sub-systems (Decomposition) and check if it does its job (Fitness for Purpose).

4.2 Dataflow: Tracking the Information

Information in a system is like water in pipes; it needs to flow from one place to another. We use Dataflow Diagrams (DFDs) to map this out.

Why do we need DFDs?

DFDs help us see where data comes from, where it goes, and where it is stored. It doesn't show when things happen, just what happens to the data.

Common DFD Symbols to Know:

• External Entity (Square/Rectangle): Where data comes from or goes to (e.g., a Customer).
• Process (Circle or Rounded Box): An action performed on the data (e.g., "Calculate Total Price").
• Data Store (Two parallel lines): Where data sits while not being used (e.g., a Database).
• Data Flow (Arrow): The path the data takes.

Common Mistake to Avoid: Never draw a data flow arrow directly between two Data Stores or two External Entities. Data must always go through a Process first!

Key Takeaway: DFDs are the "roadmaps" for information. They show the journey data takes through a system.

4.3 Flowcharts: The Logic of the System

While a DFD shows where data goes, a Flowchart shows the steps and decisions in a process. It’s like a set of instructions.

Flowchart Symbols:

• Terminator (Oval): Marks the "Start" or "End" of the process.
• Input/Output (Parallelogram): Represents data being put in or shown out (e.g., "Enter Password").
• Process (Rectangle): A specific action or instruction (e.g., "Add 1 to Score").
• Decision (Diamond): A "Yes/No" or "True/False" question that changes the path.

Mnemonic Aid: Remember "Diamonds are for Decisions"—whenever the system has to make a choice, use the diamond shape!

Key Takeaway: Flowcharts are the "instruction manuals." They explain the logic and the order of steps in a system.

4.4 Evaluating IT Systems

Why do organizations spend millions on IT systems? Because when they work, they provide massive benefits, but they also come with risks.

Advantages vs. Disadvantages

Advantages:
- Speed: Processing millions of transactions in seconds.
- Accuracy: Computers don't get tired or make "human" typos.
- Storage: Huge amounts of data can be kept in a tiny physical space.

Disadvantages:
- Cost: Setting them up and maintaining them is expensive.
- Security: Systems can be hacked or infected by malware.
- Reliance: If the system goes down, the whole business might stop!

Selecting the Right Components

When building a system for a specific person or business, you must choose the right hardware and memory. Example: A professional video editor needs a high-performance processor and lots of storage, while a delivery driver needs a portable device with GPS and long battery life.

Did you know? The "best" system isn't the most expensive one; it's the one that most closely matches the user's specific requirements.

Quick Review Box:
1. IT Systems include people and processes, not just tech.
2. Use DFDs for data movement and Flowcharts for step-by-step logic.
3. Always evaluate a system based on its fitness for purpose.

Encouragement: You've just covered the core of IT Systems! Understanding how these parts fit together is the foundation for everything else in Unit 1. Keep practicing those flowchart symbols, and you'll be an expert in no time!