Why is a graphical interface described as user driven rather than program driven?

A graphical interface is user driven because the user chooses which control to operate next, and the program fixes no order for those choices.

Give two features of a graphical interface that make it easier for an inexperienced user than a command line.

A graphical interface shows the available options on screen so nothing has to be memorised, and selection is made by pointing rather than by typing exact commands.

State one advantage a command line interface keeps over a graphical interface.

A command line interface can be scripted, so a long sequence of operations is repeated exactly without a user clicking through it.

CCEA A-Level Software Systems Development CL4

Software and the Development Environment

Topic overview Systems software and application software The operating system and file management Source code files Binary, object and executable files Compilers, interpreters and the build process XML files and structured data Utility software and managing files on disk The integrated development environment Object oriented development platforms Open source software and licensing

Defining Data: Types, Variables and Classes

Topic overview Primitive types and their storage Reference types, objects and null Declaring variables, scope and lifetime Type casting and conversion Arithmetic operators and expressions Relational and logical operators Operator precedence and evaluation order Objects as occurrences of a class Abstract, base and inherited classes Attributes and the properties of a class Static variables in a class Interfaces and class reusability

Program Control Structures

Topic overview Sequence and the order of execution Methods and passing control between them Selection with IF and IF ELSE Nested IF and multi-way selection The switch statement Count-controlled repetition with FOR Conditional repetition with WHILE and DO WHILE Nested loops and tracing iterations Breaking out of loops and avoiding infinite loops Choosing and evaluating control structures

Objects, Classes and Data Structures

Topic overview Constructors and creating objects Methods, parameters and return values Encapsulation and access modifiers Getters, setters and validating an object's state Inheritance and the base class Overriding methods and run-time polymorphism Overloading methods Choosing and organising data structures Strings and string handling Static arrays of simple types Arrays of objects

Exception Handling and Managing Input and Output

Topic overview Why errors have to be trapped Types of error and how an exception is raised The try and catch block Catching more than one kind of exception The finally block and releasing resources Throwing exceptions and writing an exception class Checked and unchecked exceptions Reading and validating input from the command line Controlling screen output Text files Binary files Object files and serialisation

Testing an Object Oriented Application

Topic overview Why an object oriented application must be tested Choosing test data: normal, boundary and erroneous Writing a test plan for a class Testing a class method by method Testing constructors and object state Testing inheritance and overridden methods Testing error handling paths Dry runs and trace tables Test harnesses, drivers and stubs Recording and interpreting test results Evaluating a test plan and re-testing

Graphical User Interface Objects and Events

Topic overview Graphical user interfaces and console programs Forms and their common properties Labels, text boxes and text areas Buttons, check boxes and radio buttons Lists, combo boxes and other selection controls Properties, methods and events of a GUI object Containers, panels and laying out a form The event loop and the event queue Event handlers and registering a listener The event object and reading it inside a handler Button, mouse and keyboard triggers

Multiple Forms and Linking to Files

Topic overview 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 Choosing between text, binary and object files

Designing, Testing and Evaluating an Event Driven Application

Topic overview Storyboards and what they show Building a storyboard from user requirements Prototyping and refining a design Error trapping in an event driven application Using try and catch inside an event handler Validating what a user types into a control Designing a test strategy for an event driven application Test plans and choosing test data Testing the paths a user takes through an interface Documenting and interpreting test results Evaluating an application against its requirements Evaluating features, functionality and usability

Reasons for Systems Development and Systems Methodologies

Topic overview Why organisations initiate systems development Analysis and design principles for business solutions Roles in development and the place of the user The purpose of a methodology and how methodologies evolved The waterfall model Iterative, incremental and spiral development Rapid application development The dynamic systems development method Scrum Extreme programming Prototyping in the development process UML modelling and simple diagrams

Managing Projects

Topic overview The purpose of project management Project management concepts and the project life cycle Roles and responsibilities in project management Resources needed to develop a project Estimating effort, duration and cost Gantt charts and the schedule Milestones and checkpoints Network diagrams and PERT Finding the critical path Float and how it is used Monitoring and controlling progress Managing risk and change

Testing Strategies

Topic overview Why testing matters throughout the development cycle Testing at the design stage Program and unit testing Integration testing System testing White box testing Black box testing Normal, boundary and erroneous test data User acceptance, alpha and beta testing The personnel involved in testing What a test plan contains Building a test plan for a scenario

Database Concepts and Entity Relationship Modelling

Topic overview What a database is and why one is used Database terminology: fields, records and keys The relational model The hierarchical model The network model Entities and attributes in an ER model Relationships and their degree Building an ER model for a problem From ER model to a working design Comparing the three database models

Normalisation and Structured Query Language

Topic overview 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 Joining tables and grouping results

Project Management and the Systems Approach in Practice

Topic overview Breaking a development into tasks and deliverables Estimating durations, effort and dependencies Documenting the plan as a Gantt chart Working out the critical path and float Milestones, reviews and user sign-off points Planning people, resources and skills Building a plan capable of reflecting change Recording progress against the plan Updating the plan to reflect slippage Recording change requests and versions of the plan Evaluating different approaches to a business problem Selecting and justifying a specific approach

Defining Requirements and Documenting the Design

Topic overview Eliciting requirements from the user Writing functional requirements Writing non-functional requirements Specifying the software and hardware the solution needs Producing and agreeing the user requirements specification Designing the data model and the tables Designing the inputs, the screens and the navigation Designing the outputs and the reports Documenting the processes and the logic of the solution Testing the design against the desired user outcomes Presenting the design and the solution using appropriate media

Building a Desktop Solution with a Database

Topic overview Applying relational techniques to a real solution Choosing the database and the development tool Connecting the application to the database Data adaptors Data sets Data commands and parameterised queries Binding the database to the interface Multiple forms and navigation Saving changes and protecting the data Testing and documenting the built solution

Testing and Evaluating the Solution

Topic overview Planning the testing of the finished solution Choosing test data: normal, boundary and erroneous Testing validation and error handling Testing the database and its queries Testing the user interface and the navigation Testing the whole solution and testing with the user Documenting test outcomes as evidence Diagnosing failures and retesting Evaluating the test procedures Evaluating the solution against the user requirements Evaluating delivery against the project plan Evaluating your own performance on the development

Graphical User Interface Objects and Events

11 subtopics
33 things to know
AS Unit 2

What Graphical User Interface Objects and Events covers

Graphical User Interface Objects and Events is examined in Unit AS 2, Event Driven Programming — an internally assessed portfolio. It covers graphical user interfaces and console programs, forms and their common properties, labels, text boxes and text areas, buttons, check boxes and radio buttons, lists, combo boxes and other selection controls, properties, methods and events of a GUI object, containers, panels and laying out a form, the event loop and the event queue, event handlers and registering a listener, the event object and reading it inside a handler and button, mouse and keyboard triggers.

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.

What you need to know

Answer each one before you reveal it.

Your recallNot started

Key term

A list box is empty and the code asks for the selected index. State the value returned and why the program must check it.

Key term

A mouse handler contains if (e.getClickCount() == 2) { lblOut.setText("Opened"); } and the user double clicks. Explain what the label shows and why.

Process

Describe the sequence of mouse events raised by one complete click on a button.

Key term

What is a graphical user interface?

Key term

What is a form in an event driven application?

Key term

What is a label used for on a form?

Key term

The Java code JButton btn = new JButton("Save"); btn.setEnabled(false); runs when the form loads. What does the user see, and what happens on a click?

Key term

What is a property of a GUI object?

Key term

What is a container in a graphical interface?

Key term

What is the event queue?

Key term

What is an event handler?

Key term

How does the flow of control in an event driven program differ from that of a console program?

Key term

Name five properties a form typically has.

Key term

What kind of data does a text box always give back to the program?

Key term

Why disable a Submit button until a form is complete rather than showing an error after the click?

Key term

What is a list box?

Key term

What is a method of a GUI object?

Key term

Give two examples of a container.

Key term

Describe the event loop.

Key term

The Java line btnSave.addActionListener(handler); appears twice in the same setup code. How many times does the handler run for one click?

Key term

Name three pieces of information an event object can carry.

Key term

Name three kinds of user action that commonly act as triggers.

Key term

Name four visual objects a user expects to find on a typical desktop window.

Key term

What is the difference between a form's title and its name?

Key term

The Java line int age = Integer.parseInt(txtAge.getText()); runs while txtAge contains the word seventeen. What happens?

Key term

What is a check box used for?

Key term

How does a combo box differ from a list box?

Key term

Give the key difference between setting a property and calling a method.

Key term

Why group related controls onto a panel?

Key term

Where do events come from before they reach the queue?

Key term

What is meant by the source of an event?

Key term

How does a handler find out which control raised the event?

Key term

Give two examples of a trigger that does not come from the user.

Take Graphical User Interface Objects and Events further

The same content, four other ways.

Commonly confused

Pairs that lose marks when they are blurred together.

Read only text box vs Disabled text box
Read only text box: a control that still lets the user highlight and copy what is shown. Disabled text box: a control that is greyed out and cannot even take the focus.

Questions from this topic

Each one with the model answer underneath.

1
What is a graphical user interface?
Model answer
A graphical user interface is a screen of visual objects such as windows, buttons and text boxes that a user operates with a mouse, a touch screen or a keyboard.
2
How does the flow of control in an event driven program differ from that of a console program?
Model answer
A console program runs its statements in a fixed order from start to finish, while an event driven program waits and runs a block of code only when the user acts.
3
Name four visual objects a user expects to find on a typical desktop window.
Model answer
A typical desktop window offers buttons, text boxes, labels and menus.
4
Why is a graphical interface described as user driven rather than program driven?
Model answer
A graphical interface is user driven because the user chooses which control to operate next, and the program fixes no order for those choices.
5
Give two features of a graphical interface that make it easier for an inexperienced user than a command line.
Model answer
A graphical interface shows the available options on screen so nothing has to be memorised, and selection is made by pointing rather than by typing exact commands.
6
State one advantage a command line interface keeps over a graphical interface.
Model answer
A command line interface can be scripted, so a long sequence of operations is repeated exactly without a user clicking through it.

See the rest and revise

What is inside Levo

Six ways to work the same material.

1Closed book

2Open book

3Closed book

The 3-step method, run for you

Answer cold, learn it, then prove it stuck. Levo tracks the jump between your first attempt and your last.

Software and the Development Environment

Defining Data: Types, Variables and Classes

Program Control Structures

Objects, Classes and Data Structures

Cram a whole paper in one sitting

Sort every topic into what you know and what you do not, then drill only the weak ones.

A null is the of one.

absencepresencetype

Blank Blitz makes facts automatic

Rapid timed gap-fills on the terms and numbers you need to recall without thinking.

AA null means no value has been recorded.

BZero and an empty string are values.

CA null is the absence of a value.

Build It gets the exam shape right

Assemble a full-mark answer from its marking points, in the order an examiner wants them.

An error is the mistake a person made.

TrueFalse

Test It catches misconceptions

Spot the fault in a statement. The traps are the mistakes students actually make.

721941163128510

Brain Breaks between sessions

Short focus games to reset attention, so the next set lands better than the last.

Graphical User Interface Objects and Events revision questions

What does Graphical User Interface Objects and Events cover in CCEA A-Level Software Systems Development?: 11 subtopics: graphical user interfaces and console programs, forms and their common properties, labels, text boxes and text areas, buttons, check boxes and radio buttons, lists, combo boxes and other selection controls, properties, methods and events of a gui object, containers, panels and laying out a form, the event loop and the event queue, event handlers and registering a listener, the event object and reading it inside a handler and button, mouse and keyboard triggers. Each one has its own page with questions and model answers.
How is Graphical User Interface Objects and Events organised?: By the CCEA CL4 specification, subtopic by subtopic, so it matches the order you are taught it in.

Every question in Graphical User Interface Objects and Events, 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.

Start revising, £5 a month See how the method works

Or £46 a year, about £3.83 a month. Cancel anytime.