OCR Computing A-Level Revision

Interface Design

Good Interface Design (2.1.a)

It is important to design user interfaces well, so that the software is simple and intuitive to use. When designing the user interface, 4 factors should be considered:

Analysing User Interfaces - Examples (2.1.b)

Facebook for Android - Menu Based

Facebook for Android User Interface

Google Accounts - Form Based

The google account sign-up screen

Types of Data

Data Capture Form, Screen, and Report Layouts (2.1.b)

These questions are often very mark heavy (8-12 marks), and there is lots of low-hanging fruit - for example, there will be marks awarded for giving the form a title, and making sure there are submit and reset buttons. The question also often contains a checklist of the fields which should be in the solution - make sure the type of input is suitable for the data the user will be filling in - by using dropdowns, checkboxes, and radio buttons, and explaining why they're appropriate.

It's also important to use all the space on the screen as efficiently as possible - there's often a mark for use of space. Finally, make sure all the form fields are big enough - it's a good idea to give an extreme example, for example "Super Chocolate Cake with Sauce" for a recipe form.

Data Requirements (2.1.c)

n.b. - this is effectively a summery of 2.3.*, and is not about the data a program requires (but about the types of data - for example strings and integers). For revision, see 2.3.3 Records & Files.