Creating a complex software system requires more than just coding; it requires a deep understanding of organizational needs and a structured design process. Lesson 7 of the GCE A/L ICT syllabus introduces Systems Analysis and Design, focusing on the System Development Life Cycle (SDLC) and the graphical tools used to model data.

By combining our LMS theory with the SchoolICT.net Systems Analysis Learning Tool, you can practice building logical models that are essential for any successful ICT project.

1. The System Development Life Cycle (SDLC)

The SDLC is a conceptual model used in project management that describes the stages involved in an information system development project.

Key Phases of SDLC:

1. Identification of Requirements: Recognizing the need for a new system.
2. Feasibility Study: Assessing technical, economic, and operational viability.
3. System Analysis: Gathering detailed requirements through interviews, questionnaires, and observations.
4. System Design: Creating logical and physical designs (DFDs, ERDs, UI design).
5. Software Development: The actual coding and database creation.
6. Testing: Finding and fixing bugs (Unit, Integration, and System testing).
7. Implementation: Deploying the system (Direct, Parallel, Phased, or Pilot).
8. Maintenance: Ongoing support and updates.

2. SDLC Models

A/L students must understand different approaches to the life cycle:

• Waterfall Model: Linear and sequential; each phase must finish before the next begins.
• Iterative/Spiral Model: Focuses on risk assessment and building the system in repeated cycles.
• Agile Model: Focuses on flexible, rapid delivery and continuous user feedback.

3. Data Flow Diagrams (DFD)

A DFD is a graphical representation of the “flow” of data through an information system. It models the processes, data stores, and external entities.

DFD Symbols (Gane-Sarson or Yourdon):

• Process: An activity that transforms data (Circle or Rounded Rectangle).
• Data Store: Where data is kept (Open-ended rectangle).
• External Entity: Sources or destinations of data outside the system (Square).
• Data Flow: The path data takes (Arrows).

DFD Levels:

1. Context Diagram (Level 0): Shows the entire system as a single process and its interactions with external entities.
2. Level 1 DFD: Breaks the system down into its major sub-processes.

4. Entity Relationship Diagrams (ERD)

ERDs are used to model the logical structure of databases. They show the relationships between different “Entities.”

• Entity: A real-world object (e.g., Student, Teacher).
• Attribute: Properties of an entity (e.g., Name, Age).
• Relationship: How entities interact (e.g., Student enrolled in Course).

5. System Deployment (Implementation) Methods

How do we transition from the old system to the new one?

• Direct: Stop the old, start the new immediately.
• Parallel: Run both systems simultaneously to ensure the new one is stable.
• Phased: Introduce parts of the new system in stages.
• Pilot: Implement the full system in one department before a full rollout.

6. Interactive Learning: Systems Analysis Tool

Drawing diagrams on paper can be messy. The SchoolICT.net Systems Analysis Learning Tool provides a digital canvas to master these modeling skills.

Features of the Tool:

• DFD Builder: Drag and drop entities and processes to create a Context Diagram. The tool checks for “Black Holes” (processes with no output) or “Miracles” (processes with no input).
• SDLC Phase Matcher: Match real-world tasks (like “calculating the ROI” or “writing a user manual”) to their correct SDLC stage.
• ERD Workshop: Practice defining primary keys and foreign keys while building relationships between entity blocks.
• Feasibility Simulator: Input budget and resource data to determine if a mock project is “Feasible” or “Not Feasible.”

7. Exam Success Tips for A/L Students

1. DFD Rules: Never connect an External Entity directly to a Data Store. There must always be a Process in between.
2. Context Diagrams: Remember that a Context Diagram should never show a Data Store; stores are only shown in Level 1 and below.
3. Feasibility Types: Be ready to explain TELOS (Technical, Economic, Legal, Operational, Scheduling).
4. Testing Types: Understand the difference between White Box Testing (internal logic) and Black Box Testing (functionality based on inputs).

Conclusion: Engineering Better Systems

Systems Analysis and Design is the bridge between a business problem and a technical solution. Mastering Lesson 7 ensures you can lead a project from a simple idea to a complex, reliable system. Use our LMS notes to study the SDLC and the interactive tool to perfect your diagramming skills.

Ready to design your system?

• 📖 Read the Full GCE A/L Systems Analysis Notes
• 💻 Try the Interactive Systems Analysis Tool