Key term
CCEA A-Level Software Systems Development CL4
Software and the Development Environment
Topic overviewSystems software and application softwareThe operating system and file managementSource code filesBinary, object and executable filesCompilers, interpreters and the build processXML files and structured dataUtility software and managing files on diskThe integrated development environmentObject oriented development platformsOpen source software and licensing
Defining Data: Types, Variables and Classes
Topic overviewPrimitive types and their storageReference types, objects and nullDeclaring variables, scope and lifetimeType casting and conversionArithmetic operators and expressionsRelational and logical operatorsOperator precedence and evaluation orderObjects as occurrences of a classAbstract, base and inherited classesAttributes and the properties of a classStatic variables in a classInterfaces and class reusability
Program Control Structures
Topic overviewSequence and the order of executionMethods and passing control between themSelection with IF and IF ELSENested IF and multi-way selectionThe switch statementCount-controlled repetition with FORConditional repetition with WHILE and DO WHILENested loops and tracing iterationsBreaking out of loops and avoiding infinite loopsChoosing and evaluating control structures
Objects, Classes and Data Structures
Topic overviewConstructors and creating objectsMethods, parameters and return valuesEncapsulation and access modifiersGetters, setters and validating an object's stateInheritance and the base classOverriding methods and run-time polymorphismOverloading methodsChoosing and organising data structuresStrings and string handlingStatic arrays of simple typesArrays of objects
Exception Handling and Managing Input and Output
Topic overviewWhy errors have to be trappedTypes of error and how an exception is raisedThe try and catch blockCatching more than one kind of exceptionThe finally block and releasing resourcesThrowing exceptions and writing an exception classChecked and unchecked exceptionsReading and validating input from the command lineControlling screen outputText filesBinary filesObject files and serialisation
Testing an Object Oriented Application
Topic overviewWhy an object oriented application must be testedChoosing test data: normal, boundary and erroneousWriting a test plan for a classTesting a class method by methodTesting constructors and object stateTesting inheritance and overridden methodsTesting error handling pathsDry runs and trace tablesTest harnesses, drivers and stubsRecording and interpreting test resultsEvaluating a test plan and re-testing
Graphical User Interface Objects and Events
Topic overviewGraphical user interfaces and console programsForms and their common propertiesLabels, text boxes and text areasButtons, check boxes and radio buttonsLists, combo boxes and other selection controlsProperties, methods and events of a GUI objectContainers, panels and laying out a formThe event loop and the event queueEvent handlers and registering a listenerThe event object and reading it inside a handlerButton, mouse and keyboard triggers
Multiple Forms and Linking to Files
Topic overviewWhy an application needs more than one formCreating, showing, hiding and closing a formModal and modeless formsPassing data between formsMenus, menu items and shortcutsToolbars and navigation buttonsDesigning navigation for a multi form applicationReading and writing text filesBinary files and streamsObject serialisation and object filesChoosing between text, binary and object files
Designing, Testing and Evaluating an Event Driven Application
Topic overviewStoryboards and what they showBuilding a storyboard from user requirementsPrototyping and refining a designError trapping in an event driven applicationUsing try and catch inside an event handlerValidating what a user types into a controlDesigning a test strategy for an event driven applicationTest plans and choosing test dataTesting the paths a user takes through an interfaceDocumenting and interpreting test resultsEvaluating an application against its requirementsEvaluating features, functionality and usability
Reasons for Systems Development and Systems Methodologies
Topic overviewWhy organisations initiate systems developmentAnalysis and design principles for business solutionsRoles in development and the place of the userThe purpose of a methodology and how methodologies evolvedThe waterfall modelIterative, incremental and spiral developmentRapid application developmentThe dynamic systems development methodScrumExtreme programmingPrototyping in the development processUML modelling and simple diagrams
Managing Projects
Topic overviewThe purpose of project managementProject management concepts and the project life cycleRoles and responsibilities in project managementResources needed to develop a projectEstimating effort, duration and costGantt charts and the scheduleMilestones and checkpointsNetwork diagrams and PERTFinding the critical pathFloat and how it is usedMonitoring and controlling progressManaging risk and change
Testing Strategies
Topic overviewWhy testing matters throughout the development cycleTesting at the design stageProgram and unit testingIntegration testingSystem testingWhite box testingBlack box testingNormal, boundary and erroneous test dataUser acceptance, alpha and beta testingThe personnel involved in testingWhat a test plan containsBuilding a test plan for a scenario
Database Concepts and Entity Relationship Modelling
Topic overviewWhat a database is and why one is usedDatabase terminology: fields, records and keysThe relational modelThe hierarchical modelThe network modelEntities and attributes in an ER modelRelationships and their degreeBuilding an ER model for a problemFrom ER model to a working designComparing the three database models
Normalisation and Structured Query Language
Topic overviewWhy data is normalisedUn-normalised data and repeating groupsFirst normal formSecond normal formThird normal formWorking a full normalisation throughThe advantages and limits of normalisationThe principles of SQLSQL commands for defining and changing dataSQL statements for retrieving dataJoining tables and grouping results
Project Management and the Systems Approach in Practice
Topic overviewBreaking a development into tasks and deliverablesEstimating durations, effort and dependenciesDocumenting the plan as a Gantt chartWorking out the critical path and floatMilestones, reviews and user sign-off pointsPlanning people, resources and skillsBuilding a plan capable of reflecting changeRecording progress against the planUpdating the plan to reflect slippageRecording change requests and versions of the planEvaluating different approaches to a business problemSelecting and justifying a specific approach
Defining Requirements and Documenting the Design
Topic overviewEliciting requirements from the userWriting functional requirementsWriting non-functional requirementsSpecifying the software and hardware the solution needsProducing and agreeing the user requirements specificationDesigning the data model and the tablesDesigning the inputs, the screens and the navigationDesigning the outputs and the reportsDocumenting the processes and the logic of the solutionTesting the design against the desired user outcomesPresenting the design and the solution using appropriate media
Building a Desktop Solution with a Database
Topic overviewApplying relational techniques to a real solutionChoosing the database and the development toolConnecting the application to the databaseData adaptorsData setsData commands and parameterised queriesBinding the database to the interfaceMultiple forms and navigationSaving changes and protecting the dataTesting and documenting the built solution
Testing and Evaluating the Solution
Topic overviewPlanning the testing of the finished solutionChoosing test data: normal, boundary and erroneousTesting validation and error handlingTesting the database and its queriesTesting the user interface and the navigationTesting the whole solution and testing with the userDocumenting test outcomes as evidenceDiagnosing failures and retestingEvaluating the test proceduresEvaluating the solution against the user requirementsEvaluating delivery against the project planEvaluating your own performance on the development
Normalisation and Structured Query Language
- 11 subtopics
- 33 things to know
- A2 Unit 1
What Normalisation and Structured Query Language covers
Normalisation and Structured Query Language is examined in Unit A2 1, Systems Approaches and Database Concepts — a written examination on a pre-release case study. It covers why data is normalised, un-normalised data and repeating groups, first normal form, second normal form, third normal form, working a full normalisation through, the advantages and limits of normalisation, the principles of SQL, SQL commands for defining and changing data, SQL statements for retrieving data and joining tables and grouping results.
Where it is assessed
A2 Unit 1
Systems Approaches and Database Concepts, examined on a pre-release case study.
Check the CCEA specification ↗The 11 subtopics
Each one has its own page.
- Why data is normalisedUpdate anomaly, insertion anomaly and deletion anomaly.Open →
- Un-normalised data and repeating groupsUn-normalised form and repeating group.Open →
- First normal formAtomic value and process of reaching first normal form.Open →
- Second normal formPartial dependency and table in first but not second normal form.Open →
- Third normal formTransitive dependency, mnemonic for third normal form and relationship between third normal form and the ER model.Open →
- Working a full normalisation throughComplete worked examples taken from a business document to third normal form, showing the key at each stage and naming the dependency removed, with the common mistakes made when normalising by eye.Open →
- The advantages and limits of normalisationFour advantages of normalisation, three disadvantages of normalisation and effect of normalisation on storage.Open →
- The principles of SQLStructured Query Language, two main divisions of SQL and SQL being a standard.Open →
- SQL commands for defining and changing dataCreating a table with its constraints, declaring a foreign key, inserting, updating and deleting rows, altering a table, the difference between dropping and emptying one, and committing or rolling back a transaction.Open →
- SQL statements for retrieving dataSelecting columns and filtering rows, ordering the result, pattern matching, combining conditions, ranges and lists, the aggregate functions, and removing duplicates.Open →
- Joining tables and grouping resultsDifference between an inner join and a left outer join, difference between WHERE and HAVING and query that needs both a join and a grouping.Open →
What you need to know
Answer each one before you reveal it.
Your recallNot started
Key term
How do you choose the key for un-normalised data?
Process
What is the process of reaching first normal form?
Key term
Take an order document holding OrderNo, OrderDate, CustomerNo, CustomerName and repeating lines of ProductCode, Description, UnitPrice and Quantity to first normal form
Key term
Why does the order line table need a composite key?
Key term
Is UnitPrice always dependent on the product alone?
Key term
State the mnemonic for third normal form.
Key term
What anomaly does a transitive dependency cause?
Key term
Why is third normal form usually treated as far enough?
Key term
Normalise to third normal form a hospital appointment card holding appointment number, patient number, patient name, consultant code, consultant name and clinic.
Key term
Normalise to third normal form a training record holding course code, course title, and for each attendee a staff number, staff name and department.
Key term
Why does the same source document sometimes normalise differently in two businesses?
Evaluation
State three disadvantages of normalisation.
Key term
How does normalisation improve data quality?
Key term
Why can a normalised design be slower to query?
Evaluation
Why is it an advantage that an SQL query states what is wanted rather than the method of retrieving it?
Key term
What is a null in SQL, and how does it differ from zero?
Key term
What are privileges in SQL?
Key term
Why is naming the columns preferred to using an asterisk in an application?
Key term
What is the difference between an inner join and a left outer join?
Key term
What is the difference between WHERE and HAVING?
Key term
What is an insertion anomaly?
Key term
What does a CHECK constraint do?
Key term
What is a deletion anomaly?
Key term
Why does second normal form only matter for a composite key?
Numbers
Write the SQL to add a new member.
Key term
Write the SQL to list every column of every row in the Member table.
Key term
What is functional dependence?
Key term
What does un-normalised form mean?
Key term
How is a partial dependency removed?
Numbers
Write the SQL to change a member's surname.
Numbers
Write the SQL to list the surnames of members who joined after the first of January 2026.
Key term
Write the SQL to list each loan with the borrower's surname.
Take Normalisation and Structured Query Language further
The same content, four other ways.
Commonly confused
Pairs that lose marks when they are blurred together.
Normalisation vs Denormalisation
Normalisation: removing duplication so that each fact is held once. Denormalisation: deliberately reintroducing duplication for a measured gain in speed.
A view vs A table
A view: a stored query that produces its rows when it is read. A table: a structure that physically holds its rows.
Questions from this topic
Each one with the model answer underneath.
- 1
What is normalisation?
Model answer
Normalisation is a step-by-step process of arranging attributes into tables so that each fact is stored once and every non-key attribute depends on the whole primary key and on nothing else.
- 2
What problem is normalisation solving?
Model answer
Normalisation removes the duplication that arises when related facts are held in one flat structure, because duplication lets copies of the same fact disagree once one of them is updated and the others are not.
- 3
What is an update anomaly?
Model answer
An update anomaly occurs when a single fact is stored in many rows, so changing it means changing every one. A supplier's address held on each of that supplier's product rows must be corrected in all of them or the data contradicts itself.
- 4
What is an insertion anomaly?
Model answer
An insertion anomaly occurs when a fact cannot be recorded because unrelated data is missing. If product details are held only inside order lines, a new product cannot be recorded until somebody orders it.
- 5
What is a deletion anomaly?
Model answer
A deletion anomaly occurs when removing a record destroys unrelated information. If a product exists only inside order lines, deleting the last order for it removes every record of the product.
- 6
What is functional dependence?
Model answer
An attribute is functionally dependent on another when the value of the second determines the value of the first. A product description is functionally dependent on the product code, because one code always gives the same description.
What is inside Levo
Six ways to work the same material.
Normalisation and Structured Query Language revision questions
- What does Normalisation and Structured Query Language cover in CCEA A-Level Software Systems Development?
- 11 subtopics: why data is normalised, un-normalised data and repeating groups, first normal form, second normal form, third normal form, working a full normalisation through, the advantages and limits of normalisation, the principles of sql, sql commands for defining and changing data, sql statements for retrieving data and joining tables and grouping results. Each one has its own page with questions and model answers.
- How is Normalisation and Structured Query Language organised?
- By the CCEA CL4 specification, subtopic by subtopic, so it matches the order you are taught it in.
Every question in Normalisation and Structured Query Language, on a schedule.
Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.
Or £46 a year, about £3.83 a month. Cancel anytime.