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
Multiple Forms and Linking to Files
- 11 subtopics
- 33 things to know
- AS Unit 2
What Multiple Forms and Linking to Files covers
Multiple Forms and Linking to Files is examined in Unit AS 2, Event Driven Programming — an internally assessed portfolio. It covers why an application needs more than one form, creating, showing, hiding and closing a form, modal and modeless forms, passing data between forms, menus, menu items and shortcuts, Toolbars and navigation buttons, designing navigation for a multi form application, reading and writing text files, binary files and streams, object serialisation and object files and choosing between text, binary and object files.
Where it is assessed
AS Unit 2
Event Driven Programming — an internally assessed portfolio.
Check the CCEA specification ↗The 11 subtopics
Each one has its own page.
- Why an application needs more than one formSplash screen, main form or parent form and dialog box.Open →
- Creating, showing, hiding and closing a formCreating an instance and showing it, the difference between hiding a form and disposing of it, what happens to the values in its controls either way, and why a secondary window must not close the whole application.Open →
- Modal and modeless formsModal form, modeless form and one danger of overusing modal dialogs.Open →
- Passing data between formsShared data class, one disadvantage of holding data in public global variables and callback used for between forms.Open →
- Menus, menu items and shortcutsMenu bar, drop-down menu and context menu.Open →
- Toolbars and navigation buttonsNavigation button and breadcrumb trail.Open →
- Designing navigation for a multi form applicationNavigation map, dead end screen and progressive disclosure in a multi form design.Open →
- Reading and writing text filesText file and three steps that surround reading a file.Open →
- Binary files and streamsBinary file, difference between an input stream and an output stream and serial or sequential access.Open →
- Object serialisation and object filesObject serialisation, object file and written out when a serialised object refers to another object.Open →
- Choosing between text, binary and object filesTwo questions to ask before choosing an appropriate file format, portability advantage of a text file and file format specification.Open →
What you need to know
Answer each one before you reveal it.
Your recallNot started
Key term
What is a stream, and how does an input stream differ from an output stream?
Key term
Give two reasons an application is built from several forms rather than one.
Key term
What is a modal form?
Evaluation
What is the advantage of passing a value through the constructor of the second form?
Key term
What is a menu bar?
Key term
What is a toolbar?
Key term
What is a navigation map?
Key term
What is a text file?
Key term
What is object serialisation?
Key term
Which file type suits data that must be opened in a spreadsheet, and why?
Key term
What is a splash screen?
Process
What two steps are needed to implement a second form on the screen in code?
Key term
What is a modeless form?
Process
How does a modal dialog return a value to the form that opened it?
Key term
What is a drop-down menu?
Key term
Why does a toolbar button usually show an icon rather than a caption?
Key term
What is a dead end screen?
Evaluation
Give two advantages of storing data in a text file.
Key term
What is a binary file?
Key term
What is deserialisation?
Key term
Which file type suits a large table of numbers read repeatedly, and why?
Key term
Explain why a login screen is usually a separate form from the main window.
Key term
The Java code FrmReport f = new FrmReport(); f.setVisible(true); runs in a handler and the button is clicked twice. How many report windows appear?
Key term
What happens to the calling code when a modal form is shown?
Key term
Why can the calling form not read a modeless form's fields immediately after showing it?
Key term
What is a submenu?
Key term
What must a toolbar button provide because its icon may not be understood?
Key term
How is the number of clicks needed to reach a feature a measure of design quality?
Evaluation
Give two disadvantages of a text file for numeric data.
Key term
Why is a whole number stored in fewer bytes in a binary file than in a text file?
Key term
What is an object file?
Key term
Why is a text file the easiest format to debug?
Take Multiple Forms and Linking to Files further
The same content, four other ways.
Commonly confused
Pairs that lose marks when they are blurred together.
Serial access vs Direct access
Serial access: reaching a record by passing every earlier one in turn. Direct access: jumping straight to a calculated position.
Questions from this topic
Each one with the model answer underneath.
- 1
Give two reasons an application is built from several forms rather than one.
Model answer
Several forms keep each screen focused on one task, and the user is not shown fields belonging to a job they are not doing.
- 2
What is a splash screen?
Model answer
A splash screen is a short-lived form shown while an application starts, and a splash screen displays the product name and a progress message.
- 3
What is a main form or parent form?
Model answer
A main form is the window opened at startup that stays for the life of the application and from which the other forms are reached.
- 4
Explain why a login screen is usually a separate form from the main window.
Model answer
A login screen is separate so the main window is only built once the credentials are accepted, and the login form is then closed and cannot be returned to.
- 5
What is a dialog box?
Model answer
A dialog box is a small form that asks for one decision or one piece of information and then closes.
- 6
Give an example of a task that suits its own form and one that does not.
Model answer
Editing a customer record suits its own form, while a single confirmation question does not and is better served by a small pre-built message box.
What is inside Levo
Six ways to work the same material.
Multiple Forms and Linking to Files revision questions
- What does Multiple Forms and Linking to Files cover in CCEA A-Level Software Systems Development?
- 11 subtopics: why an application needs more than one form, creating, showing, hiding and closing a form, modal and modeless forms, passing data between forms, menus, menu items and shortcuts, toolbars and navigation buttons, designing navigation for a multi form application, reading and writing text files, binary files and streams, object serialisation and object files and choosing between text, binary and object files. Each one has its own page with questions and model answers.
- How is Multiple Forms and Linking to Files organised?
- By the CCEA CL4 specification, subtopic by subtopic, so it matches the order you are taught it in.
Every question in Multiple Forms and Linking to Files, 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.