Process
CCEA A-Level Digital Technology 2650
Systems Analysis and Development Approaches
Topic overviewThe software crisis and the need for systems developmentUser needs, time and costRoles in a systems development teamThe purpose of analysisFact-finding techniquesFunctional and non-functional requirementsData flow diagramsThe waterfall modelRapid application development and AgileResources, constraints and risks in a software projectProject management, Gantt charts and critical path analysisVersion management
Design, Development and Testing
Topic overviewThe purpose of systems designStoryboarding the user interfacePrototyping the interface and the data modelThe development stage: turning a design into working codeWhy testing runs throughout developmentLevels of testing: unit and integrationSystem testingAcceptance testingAlpha and beta testingThe purpose and components of a test planTypes of test data
Implementation and System Security
Topic overviewThe purpose of system implementationDirect and parallel changeoverPilot and phased changeoverUser documentationTechnical documentationData conversionThe purpose of system maintenanceCorrective, adaptive and perfective maintenanceArchiving dataBackup and recoveryFull, differential and incremental backupsDisaster recovery plans
Programming
Topic overviewThe purpose of a computer programThe integrated development environmentTranslation: compilers, interpreters and assemblersThe stages of compilation and linkingAlgorithms, pseudocode and syntaxVariables, constants and data typesSequence and selectionIteration: count-controlled and condition-controlled loopsFlowcharts and algorithm representationObjects, classes and methodsInheritance and evaluating the object-oriented approach
Data, Information and Data Representation
Topic overviewBits, bytes and units of storageHow many values a given number of bits can holdConverting decimal to binaryConverting binary to decimalTwo's complement and negative numbersCharacter sets: ASCII and UnicodeData, information and knowledgeFactors affecting the quality of informationValidation: range, type, length and presence checksValidation: format checks and lookup checksCheck digits and the Modulus 11 methodBatch totals, verification and the limits of checking
Computer Architecture and Processing Systems
Topic overviewThe processor, the clock and the registersThe fetch-execute cycleBuses, input and output controllers and portsMain memory: RAM, ROM and addressingCache memory and the memory hierarchyFactors that affect processing speedThe need for secondary storageMagnetic, optical and flash storage mediaChoosing secondary storage for common applicationsBatch, real-time and transaction processingAutomatic teller machines and point of sale terminalsSmartphones: input, output and processing
System Software, Application Software and the User Interface
Topic overviewUser interfaces: WIMP, command line and forms dialogueChoosing and evaluating a user interfaceInputting text, sound and videoThe purpose of an operating systemHow an operating system manages memory and processesTypes of operating systemUtility programsThe need for data compression, lossless and lossyZipping and archive filesCommon data file formatsApplication software: generic and special purposeObtaining and delivering software
Web Technology and Multimedia
Topic overviewThe internet, the World Wide Web and web standardsURLs, HTTP and the request-response cycleDomain names, DNS and IP addressesWeb browsers, search engines, cache and cookiesWeb servers, hosting, ISPs and file transferIntranets and how an organisation uses oneCreating web pages with HTMLHTML tags for text, lists, images and linksStyling pages with CSSMultimedia assets in a web pageClient-side and server-side processingSecurity over the internet: encryption, HTTPS and certificates
Networks
Topic overviewNetwork scope: LAN, MAN and WANNetwork hardware and connection devicesIP addresses and MAC addressesPeer-to-peer and server-based networksBus, star and ring topologiesThe need for communication protocolsThe OSI seven-layer modelTCP/IP, Ethernet and media access methodsWi-Fi, Bluetooth, VoIP and RFIDBandwidth and broadbandTransmission media: metal cable, fibre optic and wirelessDetecting and correcting transmission errors
Databases
Topic overviewThe relational database and its main featuresLogical and physical data modelsEntities, attributes and keysEntity-relationship modellingNormalisation to third normal formThe data dictionaryStructured Query Language: creating and changing dataStructured Query Language: retrieving dataQuery By Example and alternatives to SQLDatabase security, integrity and recovery
Artificial Intelligence, Expert Systems and Robotics
Topic overviewWhat artificial intelligence meansThe Turing test and machine intelligenceNeural network modellingThe structure of an expert systemThe knowledge base and the inference engineShells, heuristics, fuzzy logic and the knowledge engineerExpert systems in medicine, fault diagnosis and insuranceNatural language processingVoice recognition technologyEvaluating natural language and voice recognition systemsThe technology of roboticsRobotics in commercial situations
Mobile Technology, Data Mining and Cloud Computing
Topic overviewCells, masts and frequency reuseHandoff between cellsThe base station controller, the mobile switching centre and the PSTNWhat data mining isGathering and storing data for miningProcessing and analysing large volumes of dataBig data in health, finance and retailData mining and the privacy of the individualWhat cloud computing isVirtualisation, hosted instances, hosted solutions and clusteringCloud services: storage, email, software and backupEvaluating cloud computing for business
Individual, Social and Legal Considerations
Topic overviewThe Data Protection Act 2018 and the UK GDPRThe data protection principles and the rights of the data subjectThe Copyright, Designs and Patents Act 1988The Computer Misuse Act 1990Data protection duties of an organisationHow the legislation affects employees and the publicThe ethics of automated decision makingOnline censorshipMonitoring of personal behaviourThe ethics of artificial intelligence and of personal information
The Development Project: Analysis and Design
Topic overviewScheduling the project with a Gantt chartInternal and external constraints on the solutionDetailing user requirements as inputs, processes and outputsPrioritising requirements as essential and non-essentialData flow diagrams at level 0 and level 1Specifying hardware and software requirementsThe overall system designProcess descriptions and algorithmsUser interface design and validationData modelling and normalisation for the solutionDesigning the queries and reportsDeveloping a comprehensive test plan
The Development Project: Build, Testing and Evaluation
Topic overviewChoosing software to develop the solutionBuilding the solutionTest data and the types of testingCarrying out and recording the testingDocumenting a strategy for system implementationEvaluating the solution against the user requirementsIdentifying extensions to the systemThe electronic user guideBringing the system into use and supporting itDocumentation for the completed system
The Development Project: Analysis and Design
Data modelling and normalisation for the solution
- 3 things to know
- A2 Unit 2
Overview
Identifying the entities from the client's own documents, showing the working from un-normalised data to third normal form, drawing the entity-relationship diagram for the design, and documenting every attribute, key and integrity rule.
What you need to know
Answer each one before you reveal it.
Your recallNot started
Key term
What should be documented for each table in the design?
Key term
How is the data model checked against the requirements?
Questions from this subtopic
Each one with the model answer underneath.
- 1
What must the design document show about the data model for the solution?
Model answer
The design must show the entity-relationship diagram for the fully relational database, the attributes and keys of every table, and the working that takes the client's data from its original form to third normal form.
- 2
How are the entities for a solution identified from the requirements?
Model answer
The things the client keeps records about become the entities, and they usually appear as the nouns that recur in the requirements and on the existing documents, such as member, loan, book and copy in a library.
- 3
Why must the normalisation be shown in detail rather than only the final tables?
Model answer
Showing the working demonstrates that the final structure was derived rather than guessed, and it lets a reviewer find the step where a dependency was missed instead of only seeing that the answer looks wrong.
- 4
What should be presented at each stage of the normalisation?
Model answer
Each stage should present the attributes as they stand at that point, the key of each group, and a statement of what was removed and why — the repeating group, the partial dependency or the transitive dependency.
- 5
Where should the source data for the normalisation come from?
Model answer
The source is the client's own documents — the order form, the invoice, the enrolment sheet — because normalising the real document guarantees that everything the client actually records has a place in the design.
- 6
How does the entity-relationship diagram relate to the normalised tables?
Model answer
They must describe the same structure: each entity on the diagram is a table, each relationship is a foreign key, and any many-to-many relationship on the diagram must appear in the tables as a link table.
Other ways to work this
The same content, four other ways.
What is inside Levo
Six ways to work the same material.
Every question in The Development Project: Analysis and Design, 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.