Digital Skills & IT Revision — CCEA A-Level
Complete CCEA A-Level Digital Skills & IT specification revision resources. Tailored syllabus coverage with topic breakdowns, quizzes, and practice questions.
Specification Topics
- Approaches to Systems Development
- Data Modelling
- Database Systems
- Web Application Development
- Digital Technology and Society
Top Exam Board Tips
- 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.
- 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.
- Practice drawing ER diagrams from scenarios.
- Label all relationships clearly.
- Check for many-to-many relationships and resolve them.
- When normalising, show step-by-step transformations: list the original table, identify anomalies, decompose to 1NF, then 2NF, then 3NF, clearly indicating keys and functional dependencies at each stage.
Common Mistakes to Avoid
- 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.
- 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 entities with attributes.
- Omitting primary keys or foreign keys.
Key Terminology & Definitions
- Waterfall model
- Agile methods
- Iterative development
- Structured methods
- Rapid application development
- CASE tools
- Entities
- Relationships
- Cardinality and modality
- 1NF, 2NF, 3NF
- Functional dependencies
- SELECT, INSERT, UPDATE, DELETE
- JOINs, subqueries
- Relational databases
- Data integrity