Approaches to Systems Development — CCEA A-Level Digital Skills & IT Revision
This subtopic focuses on structured and rapid methodologies for systems development, comparing the formal, sequential SSADM with the iterative, user-centri
Topic Synopsis
This subtopic focuses on structured and rapid methodologies for systems development, comparing the formal, sequential SSADM with the iterative, user-centric RAD. It also covers essential modelling tools—Data Flow Diagrams (DFDs) to represent information movement, and Entity Relationship Diagrams (ERDs) to design database structures—providing learners with practical skills for analysing and designing system components in real-world projects.
Key Concepts & Core Principles
- Waterfall model: a linear, sequential approach where each phase (e.g., requirements, design, implementation) must be completed before the next begins. Best for projects with clear, stable requirements.
- Agile methodologies (e.g., Scrum): iterative and incremental development with frequent feedback loops. Emphasises flexibility, collaboration, and responding to change. Suitable for projects with evolving requirements.
- Prototyping: building a working model of the system early to gather user feedback. Can be throwaway (for clarifying requirements) or evolutionary (refined into the final system). Reduces risk of misunderstanding.
- The Systems Development Lifecycle (SDLC): a framework comprising stages like feasibility study, analysis, design, implementation, testing, and maintenance. Different approaches follow the SDLC in different ways.
- User involvement: a key factor in choosing an approach. Agile and prototyping involve users continuously; Waterfall involves users mainly at the start and end. High user involvement can improve satisfaction but may increase cost and time.
Exam Tips & Revision Strategies
- When comparing methodologies, always relate them to scenario constraints—e.g., RAD for urgent, evolving requirements; SSADM for stable, large-scale systems.
- Practice DFDs by consistently numbering processes and ensuring all data flows start/end at a process; avoid crossing lines for clarity.
- For ERDs, double-check that each entity has a primary key and that many-to-many relationships are resolved into associative entities before implementation.
- Use clear diagrams or flowcharts to illustrate lifecycle stages when appropriate, ensuring they are labelled and referenced in your written answer.
- For comparison questions, structure your response using direct contrasts (e.g., 'Unlike Waterfall, Agile allows...') to demonstrate analytical depth.
- Integrate industry terminology (e.g., sprints, prototyping, V-model) to show breadth of understanding beyond the basic theory.
Common Misconceptions & Mistakes to Avoid
- Confusing RAD with a lack of planning or documentation, failing to recognise that RAD still requires initial requirements gathering and produces focused prototypes.
- Misplacing data flows in DFDs, such as directing flows between external entities or data stores without an intervening process.
- Forgetting to specify relationship cardinalities in ERDs or mixing up crow's foot notation, leading to incorrect database designs.
- Confusing the stages of the lifecycle with the activities within each stage, e.g., listing 'coding' as a separate lifecycle stage rather than an activity within implementation.
- Assuming that a single lifecycle model is universally superior without considering project constraints like scale, clarity of requirements, and team structure.
- Omitting post-implementation activities such as maintenance and review, viewing development as a finite process.
Examiner Marking Points
- Award credit for accurately contrasting SSADM and RAD, highlighting key differences such as linear vs. iterative processes, documentation emphasis, and suitable project contexts.
- Expect evidence of correctly drawing DFDs with proper notation (processes, data stores, external entities, data flows) at context and level 1 detail.
- Look for clear ERDs that correctly identify entities, attributes, primary keys, and relationships with cardinality and optionality notations.
- Award credit for correctly identifying and sequencing at least five distinct lifecycle stages, e.g., feasibility study, analysis, design, implementation, testing, maintenance.
- Credit comparison of models by evaluating their advantages and disadvantages in relation to project requirements, e.g., risk management, flexibility, and stakeholder involvement.
- Look for application of SDLC concepts to real-world scenarios, demonstrating understanding of when each model is most appropriate.