Welcome to the World of IT Systems!
In this chapter, we are going to look "under the hood" of the technology we use every day. Whether you are ordering a pizza on an app, checking your grades online, or a business is tracking its stock, an IT system is at work. We will learn how these systems are designed, how data flows through them, and why some systems are better than others. Don't worry if it sounds technical—we'll break it down step-by-step!
4.1 Systems Design: The Building Blocks
An IT system isn't just a computer. It is a combination of different parts working together to solve a problem or perform a task. Think of it like a professional kitchen: you need the appliances, the recipes, the chefs, and a plan for how to cook the meal.
4.1.1 What makes up an IT system?
There are four main "pillars" you need to remember:
- Hardware: The physical parts you can touch (like a barcode scanner in a shop or a server in an office).
- Software: The programs and instructions (like the database that stores prices or the operating system).
- Processes: The "rules" or steps followed to get the job done (for example, "If an item is scanned, subtract 1 from the stock count").
- People: The most important part! These are the users who enter data or the managers who use the information to make decisions.
Memory Aid: Just remember H-S-P-P (Hot Soup Pleases People) — Hardware, Software, Processes, People.
4.1.2 Breaking it down (Decomposition)
Big IT systems can be scary and complicated. To make them easier to design, we use decomposition. This simply means breaking a large system down into smaller, more manageable sub-systems.
Example: A "School Management System" can be decomposed into a "Registration Sub-system," a "Grading Sub-system," and a "Library Sub-system."
4.1.3 Designing to Meet Requirements
When designers build a system, they must choose the right components to meet a specific need. For example, a system for a delivery driver needs portable hardware (like a tablet) and GPS software, whereas a system for a video editor needs a high-performance processor and large storage.
4.1.4 Fitness for Purpose
When we evaluate an IT system, we ask: is it fit for purpose? This means: does it actually do what the user needs it to do?
Example: If a supermarket's checkout system is very secure but takes 10 minutes to scan one item, it is NOT fit for purpose because it fails to meet the need for speed.
Quick Review: An IT system is a mix of Hardware, Software, Processes, and People. We break big systems into sub-systems to make them easier to handle.
4.2 Dataflow: Tracking the Information
Data is the "fuel" of an IT system. We need to know where it comes from, where it goes, and where it is stored. We use Dataflow Diagrams (DFDs) to show this visually.
4.2.1 Why do we need DFDs?
Dataflow diagrams help us see how data moves through a system. They are useful because:
- They show where data enters the system (Input).
- They show how data is changed (Process).
- They show where data is kept (Data Store).
- They show the final result (Output).
4.2.2 Interpreting DFDs
When looking at a DFD, follow the arrows! The arrows show the path the data takes. If you are asked to create one for a scenario, like a pizza order, think: The customer (Source) sends an order (Data Flow) to the "Process Order" step, which checks the "Menu" (Data Store).
Common Mistake to Avoid: Don't confuse Dataflow with Flowcharts. DFDs show what data is moving; Flowcharts show the order of steps and decisions.
4.3 Flowcharts: The Logic of the System
A flowchart is a diagram that shows the step-by-step logic of a process. It’s like a map for a computer's "brain."
4.3.1 The Need for Flowcharts
Flowcharts are vital because they help designers spot logic errors before the software is actually written. They use standard symbols to show starting points, actions, and decisions (usually "Yes/No" questions).
4.3.2 Creating Flowcharts
When creating a flowchart for a scenario, always start with a "Start" bubble and follow the sequence.
Example: For a login system: Input Password -> Is password correct? -> If Yes, Grant Access -> If No, Show Error.
Key Takeaway: Flowcharts show the logic and decisions in a system. If there is a "Yes/No" choice to be made, you need a flowchart!
4.4 Using IT Systems in Organisations
Why do businesses spend millions on these systems? Let's look at the balance sheet.
4.4.1 Advantages and Disadvantages
Advantages for Organisations:
- Speed: Processing thousands of transactions in seconds.
- Accuracy: Computers don't get tired or make "human" typos (if the data entered is correct!).
- Storage: Huge amounts of data can be kept in a tiny space (Cloud or Hard Drives).
Disadvantages for Organisations:
- Cost: Buying hardware and software is expensive.
- Training: People need to be taught how to use new systems.
- Security: Systems can be hacked or infected by malware.
4.4.2 Selecting the Right Tools
To make an organisation successful, you must select the right digital devices, peripherals, storage, and memory.
- Memory (RAM): Needed for systems that run many tasks at once.
- Storage: Needed for keeping long-term records (like customer history).
- Peripherals: Choosing the right "extra" tools, like a biometric scanner for a high-security office or a barcode reader for a warehouse.
Did you know? Many organisations now use embedded systems. These are small, specialized IT systems inside larger devices, like the computer system inside a modern washing machine or a car's engine!
Final Summary: IT systems combine hardware, software, people, and processes to solve real-world problems. We use DFDs to track data and Flowcharts to map logic. A good system must be "fit for purpose," balancing speed and accuracy against cost and security risks.