Unit 7: System Development & Programming Concepts – GCE A/L Exam NOTES | DFD Context Diagram Focus | A/L Computing | Questions and Answers

📘 GCE A/L ICT – UNIT 7

System Development & Programming Concepts

🎯 Exam Level | Complete Notes | Blogger Ready

📋 Quick Navigation:

• 7.1 Introduction to System Development
• 7.2 SDLC (System Development Life Cycle)
• 7.3 Feasibility Study
• 7.4-7.5 Data Flow Diagrams (DFD)
• 7.6 Algorithms
• 7.7 Flowcharts
• 7.8 Programming Concepts
• 7.9 Testing & Debugging
• 7.10 Implementation
• 📄 Pass Paper Questions

🔷 7.1 INTRODUCTION TO SYSTEM DEVELOPMENT

🔹 What is a System?

A system is a collection of interrelated components working together to achieve a common goal.

📌 Example: School Management System

Component	Description
Inputs	Student data, attendance, marks
Processes	Attendance tracking, marks calculation, report generation
Outputs	Reports, results, certificates

🔹 Types of Systems

Type	Characteristics	Example
Manual Systems	• Paper-based • Human-operated • Slower processing	Attendance register, paper files
Computer-Based Systems	• Automated • Software-driven • Faster & accurate	School ERP, Library Management System

🔹 What is System Development?

The process of creating or modifying a system to meet user requirements and solve problems.

💡 Key Point: System development follows a structured approach called SDLC to ensure quality and efficiency.

🔷 7.2 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

🔹 Definition

SDLC is a structured, phased process followed to plan, create, test, and deploy an information system.

🔹 The 7 Phases of SDLC

Planning → Analysis → Design → Development → Testing → Implementation → Maintenance

1. Planning
   • Identify the problem/need
   • Conduct feasibility study
   • Define project scope & resources
2. Analysis
   • Study current system
   • Gather user requirements
   • Create Requirement Specification Document (RSD)
3. Design
   • System architecture
   • Database design (ERD)
   • UI/UX mockups & DFDs
4. Development
   • Actual coding/programming
   • Database implementation
   • Module integration
5. Testing
   • Find & fix bugs
   • Unit testing, system testing
   • User acceptance testing (UAT)
6. Implementation
   • Install & deploy system
   • Train users
   • Data migration
7. Maintenance
   • Fix post-launch issues
   • Apply updates & patches
   • Add new features

🔹 SDLC Example: Library System

Phase	Activity
Planning	Identify need to manage books digitally
Analysis	Interview librarians, list requirements
Design	Create database schema + UI wireframes
Development	Code the system in chosen language
Testing	Test borrowing, returning, fine calculation
Implementation	Install in library, train staff
Maintenance	Fix bugs, add e-book feature later

🔹 SDLC Deliverables (Exam Important)

Phase	Key Deliverables
Analysis	• Requirement Specification Doc • DFDs (Level 0, 1) • Use Case Diagrams
Design	• ER Diagrams • Database Schema • UI Design Mockups • System Architecture

🔷 7.3 FEASIBILITY STUDY

🔹 Purpose

❓ Key Question: "Is this system worth developing?"
Feasibility study evaluates if the project is practical, affordable, and achievable.

🔹 Types of Feasibility (TEOS)

Type	Key Question	Example
Technical 🔧	Do we have the technology & skills?	Need mobile app developers, cloud server
Economic 💰	Do benefits > costs?	Cost: Rs.500k | Benefit: Rs.1M → ✅ Feasible
Operational 👥	Will users accept & use it?	Can teachers learn the new system easily?
Schedule 📅	Can it be done on time?	Can we finish before next academic year?

🔹 Economic Feasibility Formula (Concept)

Feasible if:
Expected Benefits > Development + Operational Costs

Example Calculation:

• 💸 Development Cost: Rs. 500,000
• 📈 Annual Benefit: Rs. 300,000 × 4 years = Rs. 1,200,000
• ✅ Net Gain: Rs. 700,000 → Project is feasible!

🔹 Real-World Example: School Mobile App

🔧 Technical: Need Android/iOS devs 💰 Economic: Budget Rs.800k available? 👥 Operational: Teachers tech-savvy? 📅 Schedule: 6-month deadline?

🔷 7.4-7.5 DATA FLOW DIAGRAMS (DFD)

🔹 What is a DFD?

A Data Flow Diagram is a graphical representation showing how data moves through a system – from input, through processes, to output.

🔹 DFD Symbols (MEMORIZE FOR EXAMS)

Symbol	Name	Meaning	Example
○ Circle	Process	Transforms input to output	"Calculate Marks"
➜ Arrow	Data Flow	Movement of data	"Student Details"
▭ Rectangle	External Entity	Source/destination outside system	Student, Admin, Bank
▭▭ Open Rectangle	Data Store	Where data is stored	Database, File

🔹 Levels of DFD

🎯 Exam Focus: You MUST know Context Diagram (Level 0) in detail!

• Level 0 (Context Diagram): Entire system as ONE process + external entities
• Level 1 DFD: Breaks system into major sub-processes
• Level 2+ DFD: Further decomposition of processes

🔷 🔹 Context Diagram (Level 0 DFD) – EXAM CRITICAL

✅ What it Shows:

• The whole system as a single process
• All external entities interacting with it
• Data flows between entities and system

🔹 Why Context Diagrams Matter

• ✓ Clear system overview for stakeholders
• ✓ Defines system boundaries (what's in/out)
• ✓ Identifies all users & external systems
• ✓ Clarifies inputs & outputs early
• ✓ Improves developer-client communication

🔹 How to Draw: 4 Simple Steps

1. Identify the System
   Example: [ Student Registration System ]
2. Identify External Entities
   Example: [Student] [Admin] [Examination Dept]
3. Map Inputs & Outputs

   Entity	Input to System	Output from System
   Student	Registration details	Confirmation SMS
   Admin	Course data	Enrollment reports

4. Draw Labeled Arrows
   [Student] → Registration Details → [System] [System] → Confirmation → [Student]

🔹 Full Text-Based Example

Registration Details [Student] ------------------------> | | [Student Registration System] | | [Student] <------------------------ Confirmation [Admin] ------------------------> Course Data | | [System] | | [Admin] <------------------------ Enrollment Reports

🔹 Critical Rules (MCQ Gold)

✔ MUST DO:

• Only ONE process box (the whole system)
• NO internal processes or data stores
• ALL external entities must be shown
• EVERY arrow must have a clear label
• Arrows show direction of data flow

❌ AVOID THESE MISTAKES:

• Drawing multiple process circles ❌
• Adding database symbols ❌
• Unlabeled arrows ❌
• Missing key entities (e.g., forgot "Bank") ❌

🔷 7.6 ALGORITHMS

🔹 Definition

An algorithm is a finite, step-by-step procedure written in simple language to solve a specific problem.

🔹 Characteristics of a Good Algorithm

Characteristic	Meaning
Finite	Must have a definite end point
Clear	Each step must be unambiguous
Logical	Steps must follow correct order
Effective	Must solve the problem correctly
Input/Output	Must have defined inputs & outputs

🔹 Algorithm Writing Rules (Exam)

• ✓ Use numbered steps (1, 2, 3...)
• ✓ Use simple, plain English (no code syntax)
• ✓ Start with INPUT and end with STOP/END
• ✓ Use IF-THEN-ELSE for decisions
• ✓ Keep each step atomic (one action per step)

🔹 Example: Find Largest of 3 Numbers (Exam Level)

1. INPUT A, B, C 2. IF A > B AND A > C THEN 3. PRINT "Largest is", A 4. ELSE IF B > C THEN 5. PRINT "Largest is", B 6. ELSE 7. PRINT "Largest is", C 8. END IF 9. STOP

🔹 Example: Check Pass/Fail

1. INPUT marks 2. IF marks >= 50 THEN 3. PRINT "PASS" 4. ELSE 5. PRINT "FAIL" 6. END IF 7. STOP

🔷 7.7 FLOWCHARTS

🔹 Definition

A flowchart is a graphical representation of an algorithm using standardized symbols to show the flow of control.

🔹 Essential Flowchart Symbols

Symbol	Name	Purpose
⬭ Oval	Terminal	Start/End points
▭ Rectangle	Process	Calculation/action step
◇ Diamond	Decision	Yes/No condition check
➜ Arrow	Flow Line	Direction of execution
▱ Parallelogram	Input/Output	Read data / Display result

🔹 Example: Check Even/Odd Number

┌─────────┐ │ START │ └────┬────┘ ▼ ┌─────────┐ │ INPUT N │ └────┬────┘ ▼ ┌─────────────┐ │ N % 2 == 0 ?│ └────┬─┬─────┘ │ │ Yes │ │ No ▼ ▼ ┌────────┐ ┌────────┐ │PRINT "EVEN"│ │PRINT "ODD"│ └────┬───┘ └────┬───┘ │ │ ▼ ▼ ┌─────────────────┐ │ END │ └─────────────────┘

🔹 Loop Structure Concept

For repetition (e.g., FOR or WHILE loops), draw an arrow returning to the decision diamond to show iteration.

💡 Exam Tip: Always label decision branches with "Yes/No" or "True/False"!

🔷 7.8 PROGRAMMING CONCEPTS

🔹 Variables

Named storage locations that hold data values.

Example:
int age = 20;
String name = "Yew";
boolean isActive = true;

🔹 Basic Data Types

Data Type	Stores	Example
Integer	Whole numbers	25, -10, 0
Float/Double	Decimal numbers	3.14, -0.5
String	Text characters	"Hello", "A/L 2026"
Boolean	True/False values	true, false

🔹 Operators

🔢 Arithmetic: + - * / % ⚖️ Comparison: == != > < >= <= 🔗 Logical: AND(&&), OR(||), NOT(!) 📝 Assignment: = += -=

🔹 Control Structures (CORE CONCEPT)

1️⃣ Sequence

Statements executed in order, one after another.

INPUT name PRINT "Hello", name CALCULATE total PRINT total

2️⃣ Selection (Decision)

Execute different code based on a condition.

IF-ELSE Example:
IF marks >= 50 THEN PRINT "PASS" ELSE PRINT "FAIL" END IF

3️⃣ Iteration (Loop)

Repeat a block of code multiple times.

FOR Loop Example:
FOR i = 1 TO 10 STEP 1 PRINT i NEXT i

🔷 7.9 TESTING & DEBUGGING

🔹 Testing vs Debugging

Testing	Debugging
• Finding errors/bugs • Done BEFORE release • Uses test data	• Fixing identified errors • Done AFTER testing • Requires code analysis

🔹 Types of Testing

Type	Purpose	Example
Unit Testing	Test individual modules/functions	Test "calculateTotal()" function alone
System Testing	Test complete integrated system	Test full library borrowing workflow
Acceptance Testing	User validates system meets needs	Librarian tests before going live

🔹 Test Data Types (EXAM FAVORITE)

Type	Example (for marks 0-100)	Purpose
Normal Data ✅	50, 75, 90	Verify expected valid inputs work
Boundary Data 🎯	0, 100	Test edge limits of valid range
Invalid Data ❌	-10, 150, "abc"	Check error handling & validation

🔹 Input Validation Techniques

📏 Range Check: 0 ≤ marks ≤ 100 ✉️ Format Check: email@domain.com 🔢 Type Check: isNumeric(phone) ✅ Presence Check: name != empty 🔐 Length Check: password ≥ 8 chars

🔷 7.10 IMPLEMENTATION METHODS

🔹 When to Use Each Method

Method	Best For	Pros	Cons
Direct (Big Bang)	Small, low-risk systems	• Fast • Low cost	• High risk • No fallback
Parallel	Critical systems (Banks, Hospitals)	• Safe • Easy rollback	• Expensive • Double work
Pilot	Large organizations (Test in one branch)	• Low risk • Real-world feedback	• Slow rollout • Branch comparison issues
Phased (Modular)	Complex modular systems	• Manageable • Early benefits	• Integration challenges • Longer timeline

🎯 Exam Answer Template:
"For a banking system, I would recommend Parallel Implementation because:
✓ Critical data must not be lost
✓ Old system can run as backup
✓ Users can be trained gradually
✓ Errors can be fixed without stopping service"

📄 PASS PAPER QUESTIONS & MODEL ANSWERS

🔹 Question 1 (2 Marks)

Define SDLC.

✅ Model Answer:
SDLC (System Development Life Cycle) is a structured, phased process used to plan, create, test, deploy, and maintain information systems through stages such as planning, analysis, design, development, testing, implementation, and maintenance.

🔹 Question 2 (4 Marks)

List 4 phases of SDLC.

✅ Model Answer:
Planning Analysis Design Implementation
(Also accept: Development, Testing, Maintenance)

🔹 Question 3 (2 Marks)

What is a feasibility study?

✅ Model Answer:
A feasibility study is the process of evaluating whether a proposed system is practical, affordable, technically achievable, and worth developing before committing resources to the project.

🔹 Question 4 (2 Marks)

Name two types of feasibility.

✅ Model Answer:
Technical Feasibility Economic Feasibility
(Also accept: Operational, Schedule)

🔹 Question 5 (2 Marks)

What is an algorithm?

✅ Model Answer:
An algorithm is a finite, step-by-step procedure written in clear, unambiguous language to solve a specific problem or perform a task.

🔹 Question 6 (6 Marks)

Draw a flowchart to find the largest of two numbers.

✅ Model Answer Structure:

1. Start (Oval)
2. Input A, B (Parallelogram)
3. Decision: A > B? (Diamond)
4. Yes branch → Print A (Rectangle)
5. No branch → Print B (Rectangle)
6. End (Oval)

✨ Award marks for: correct symbols, labels, flow direction, and logic

🔹 Question 7 (2 Marks)

What is a DFD?

✅ Model Answer:
A Data Flow Diagram (DFD) is a graphical representation that shows how data moves through a system, including processes, data stores, external entities, and the flows between them.

🔹 Question 8 (2 Marks)

State two programming control structures.

✅ Model Answer:
Selection (IF-ELSE) Iteration (FOR/WHILE loops)
(Also accept: Sequence)

🔹 Question 9 (2 Marks)

What is debugging?

✅ Model Answer:
Debugging is the process of identifying, analyzing, and correcting errors (bugs) in a program's code to ensure it functions as intended.

🔹 Question 10 (6 Marks) – Context Diagram

Draw a context diagram for a Library Management System.

✅ Model Answer Structure:

1. Center: [ Library Management System ]
2. External Entities: Member Librarian Supplier
3. Data Flows:
   • Member → Book Request → System
   • System → Borrow Confirmation → Member
   • Librarian → Update Catalog → System
   • System → Overdue Report → Librarian
   • Supplier → New Books List → System

✨ Must have: 1 process, labeled arrows, all entities, no data stores

🧠 FINAL MASTER TIP – A/L ICT EXAM

👉 For DFD/Context Diagram Questions:
✓ Draw neatly with pencil & ruler
✓ Label EVERY arrow with data name
✓ Use correct symbols ONLY (no databases in Level 0!)
✓ Show ALL external entities mentioned in question
✓ Keep system as ONE process box

👉 For Algorithm/Flowchart Questions:
✓ Start with INPUT, end with STOP
✓ Use numbered steps for algorithms
✓ Label decision branches "Yes/No" in flowcharts
✓ Test your logic with sample values!

✨ Practice drawing 3 different context diagrams before exam day! ✨

🌟 UNIT 7 – SUPER SIMPLE EXPLANATIONS

👉 Perfect if you're learning this for the FIRST time!

🌟 1. What is an Information System?

👉 Simple Definition:
An Information System is a system that:

• 📥 Collects data (Input)
• ⚙️ Processes data (Process)
• 💾 Stores data (Storage)
• 📤 Outputs information (Output)

💡 The Golden Rule: Input → Process → Output

📥 INPUT → ⚙️ PROCESS → 📤 OUTPUT

📌 Real-Life Example: Student Result System

Stage	What Happens	Example
📥 Input	User enters data	Teacher types marks: 75, 80, 90
⚙️ Process	System calculates/works	System adds marks & divides by 3
📤 Output	System shows result	Displays: "Average = 81.67 – Grade: A"

🎯 Exam Tip: If asked "What is an information system?", always mention: Input → Process → Output

🌟 2. Types of Systems – Very Easy!

Think of a school or business — different people need different systems.

🟢 OAS – Office Automation System

👉 Used by: Office workers, clerks, admin staff
💡 Purpose: Helps with documents & communication
🎯 Easy Memory: OAS = Office work tools

Examples:

📝 Typing letters (Word) ✉️ Sending emails 📊 Making presentations

Real-life: School office typing student admission letters

🟢 TPS – Transaction Processing System

👉 Used by: Cashiers, bank tellers, shop staff
💡 Purpose: Handles daily small events (transactions)
🎯 Easy Memory: TPS = Daily work system

What is a transaction? A small event like buying, paying, withdrawing

Examples:

🏧 ATM withdrawal 🛒 Supermarket billing 🎫 Online ticket booking

Real-life: You buy a biscuit → system records sale → updates stock

🟢 MIS – Management Information System

👉 Used by: Middle managers, department heads
💡 Purpose: Takes TPS data & makes reports for decisions
🎯 Easy Memory: MIS = Reports for managers

Examples:

📈 Monthly sales report 👥 Student attendance summary 💰 Expense analysis

Real-life: Principal checks "Which subject has lowest pass rate?"

🟢 DSS – Decision Support System

👉 Used by: Top managers, CEOs, directors
💡 Purpose: Helps make big strategic decisions
🎯 Easy Memory: DSS = Smart decision helper

Examples:

🏢 "Should we open a new branch?" 📊 "Will profits increase next year?" 🎯 "Which product to launch?"

Real-life: CEO uses sales trends + market data to decide expansion

📊 Quick Comparison Table (MEMORIZE!)

System	Used By	Purpose	Keyword
OAS	Office staff	Documents & communication	📝 Office work
TPS	Front-line staff	Daily transactions	💰 Daily events
MIS	Managers	Reports from TPS data	📊 Reports
DSS	Top managers	Big decisions	🎯 Strategy

🌟 3. System Development Models (How Systems Are Built)

👉 Different ways to build a system — like different recipes for cooking!

🟡 Waterfall Model – Step by Step

👉 Simple Idea: Like climbing stairs — one step at a time, no going back
🎯 Easy Memory: Waterfall = Straight line

Steps (Must Know Order!):

1. Requirements – What does the user want?
2. Design – Plan how it will look & work
3. Coding – Write the actual program
4. Testing – Find & fix bugs
5. Deployment – Launch for real use

❌ Disadvantage: Cannot easily go back to fix earlier steps
✅ Best for: Small projects with clear, fixed requirements

🟡 Spiral Model – Loop with Risk Check

👉 Simple Idea: Like drawing a spiral — repeat steps, check risks each loop
🎯 Easy Memory: Spiral = Circle + checking risks

How it works:

• 🔄 Plan → Design → Build → Evaluate → Repeat
• ⚠️ Each loop checks: "What could go wrong?"

✅ Best for: Large, risky projects (e.g., banking systems)

🟡 Agile Model – Flexible & Fast

👉 Simple Idea: Build in small parts, show user, improve as you go
🎯 Easy Memory: Agile = Flexible & fast

How it works:

• 🧩 Break project into small "sprints" (2-4 weeks each)
• 👥 Show working part to user → get feedback → improve
• 🔁 Repeat until complete

✅ Best for: Projects where requirements may change (e.g., mobile apps)

🟡 RAD – Rapid Application Development

👉 Simple Idea: Build system very fast using ready-made tools
🎯 Easy Memory: RAD = Fast development

How it works:

• 🧰 Use pre-built components & templates
• ⚡ Create quick prototypes → test → refine
• 👥 Involve users heavily from start

✅ Best for: Projects with tight deadlines & clear requirements

📊 Model Comparison (Exam Favorite!)

Model	Key Idea	Best For	Keyword
Waterfall	Step-by-step, no going back	Small, clear projects	🪜 Straight line
Spiral	Loop + risk checking	Large, risky projects	🌀 Circle + risk
Agile	Small parts + user feedback	Changing requirements	🤸 Flexible
RAD	Fast build with tools	Tight deadlines	⚡ Speed

🌟 4. Tools Used in System Development

🔵 DFD – Data Flow Diagram

👉 Simple Idea: Shows how data moves through a system
🎯 Easy Memory: DFD = Data movement diagram

💡 Example: Student Registration

[Student] → Registration Form → [System] → Confirmation → [Student]

🔑 3 Basic Symbols (Context Diagram Level):

Symbol	Name	Meaning
▭ Rectangle	External Entity	Person/organization outside system
○ Circle	Process	Something that transforms data
➜ Arrow	Data Flow	Direction data moves

🔵 ER Diagram – Database Design

👉 Simple Idea: Shows how data is organized in a database
🎯 Easy Memory: ER = Data relationships

💡 Example: Student & Course

[Student] ────── [Course] │ │ name, ID code, title

🔑 3 Key Parts:

Part	Meaning	Example
Entity	Object/thing we store data about	Student, Course, Teacher
Attribute	Details about an entity	name, ID, email, phone
Relationship	How entities connect	Student enrolls in Course

🔵 Process Description

👉 Simple Idea: Explains how a process works in simple steps
🎯 Easy Memory: Process description = step explanation

Two Common Methods:

Method	What It Is	Example
Flowchart	Graphical steps with symbols	Diamond for decision, rectangle for action
Structured English	Simple English steps (like algorithm)	1. Input marks 2. If marks≥50 → Pass

🌟 5. SDLC – Super Simple 4-Step View

👉 Forget complex phases — just remember these 4 big steps:

🎨 DESIGN → 🔍 TESTING → 🚀 DEPLOYMENT → 🔧 MAINTENANCE

🟣 Step 1: DESIGN – Plan It

👉 What we do: Plan how the system will look & work

Key Tasks:

• 📝 Design input forms (What data will users enter?)
• 📊 Design output reports (What will system show?)
• 🗄️ Design database (How to store data?)
• 🎨 Design user interface (What will screens look like?)

🟣 Step 2: TESTING – Check It

👉 What we do: Find & fix errors before real use

Two Main Types:

Type	What It Tests	Example
Unit Testing	One small part/function	Test "calculateAverage()" alone
System Testing	Whole system together	Test full registration → result → report flow

🟣 Step 3: DEPLOYMENT – Launch It

👉 What we do: Put system into real use

4 Deployment Methods (Know These!):

Method	Simple Explanation	Best For
Direct	Switch off old → switch on new (one day)	Small, low-risk systems
Parallel	Run old + new together for a while	Critical systems (banks, hospitals)
Pilot	Test in ONE place first (e.g., one branch)	Large organizations
Phased	Launch module by module (e.g., registration first, then results)	Complex systems

🟣 Step 4: MAINTENANCE – Fix & Improve

👉 What we do: Keep system working well after launch

Two Main Types:

🔧 Corrective: Fix bugs/errors ✨ Adaptive: Add new features/improvements

🌟 SUPER SIMPLE SUMMARY – MUST REMEMBER 💯

📌 COPY THIS 1-LINER FOR QUICK REVISION:

Term	Super Simple Meaning	Memory Trick
OAS	Office work tools	📝 Office = OAS
TPS	Daily transactions	💰 Transaction = TPS
MIS	Reports for managers	📊 Manager = MIS
DSS	Big decision helper	🎯 Decision = DSS
Waterfall	Step-by-step, no going back	🪜 Stairs
Agile	Flexible, small parts	🤸 Jump & change
RAD	Build very fast	⚡ Lightning
Spiral	Loop + check risks	🌀 Spiral + ⚠️
DFD	How data moves	➜ Arrow diagram
ERD	How data connects	🔗 Relationship map
SDLC	Build → Test → Use → Maintain	🔄 4-step cycle

🎯 EXAM TRICKS – VERY IMPORTANT!

🔥 If the question says... → Write this answer:

🔍 Question Keyword	✅ Write This System	💡 Why?
"daily transactions", "buying", "billing", "ATM"	TPS	TPS handles small daily events
"reports", "summary", "monthly analysis"	MIS	MIS makes reports from TPS data
"decision", "strategy", "should we...?", "future plan"	DSS	DSS helps with big decisions
"typing letters", "emails", "documents"	OAS	OAS is for office document work
"step by step", "cannot go back", "sequential"	Waterfall	Waterfall is linear, no iteration
"flexible", "user feedback", "changing requirements"	Agile	Agile adapts to changes
"fast", "prototype", "ready-made tools"	RAD	RAD focuses on speed
"risk", "large project", "check each phase"	Spiral	Spiral checks risks in loops

✨ Bonus Trick for DFD Questions:
If asked to draw a Context Diagram:
1️⃣ Draw ONE rectangle in center = [System Name]
2️⃣ Draw rectangles around it = External Entities
3️⃣ Draw arrows between them = Data Flows
4️⃣ LABEL EVERY ARROW!
5️⃣ NO circles, NO databases, NO internal processes!

✅ Beginner Section Complete!

📌 Tip: Review the "Super Simple Summary" table 3x before exam!
🔄 Next: Ask for 1-page revision sheet or model exam answers

📚 GCE A/L ICT – UNIT 7 COMPLETE NOTES

System Development • DFD • Algorithms • Programming • Exam Ready

✅ 0729622034 Online Classes 📱 Mobile Responsive 🖨️ Print Friendly

💡 Pro Tip: Save this post as PDF for offline revision! Use Ctrl+P → "Save as PDF"