28
Revision Lesson 1 3.3.2: DESIGNING COMPUTER-BASED INFORMATION SYSTEMS

3.3.2 Revision

Embed Size (px)

DESCRIPTION

3.3.2: DESIGNING COMPUTER-BASED INFORMATION SYSTEMS Revision Lesson 1 THIS PRESENTATION COVERS: • Processing Systems • Designing the user interface • Mode of operation (Discuss processing, response time and user interface) • Batch, Interactive and Real-Time processing systems. • Operating systems (Describe characteristics) • Single user, Multi-user, Multi-tasking, Interactive, Real-time, Batch processing and Distributed processing. • For the exam you need to know about: MODE OF OPERATION BATCH PROCESSING

Citation preview

Page 1: 3.3.2 Revision

Revision Lesson 1

3.3.2: DESIGNING COMPUTER-BASED INFORMATION SYSTEMS

Page 2: 3.3.2 Revision

THIS PRESENTATION COVERS:• Processing Systems

• Designing the user interface

Page 3: 3.3.2 Revision

PROCESSING SYSTEMS• For the exam you need to know about:

• Mode of operation (Discuss processing, response time and user interface)

• Batch, Interactive and Real-Time processing systems.

• Operating systems (Describe characteristics)

• Single user, Multi-user, Multi-tasking, Interactive, Real-time, Batch processing and Distributed processing.

Page 4: 3.3.2 Revision

MODE OF OPERATION

Page 5: 3.3.2 Revision

BATCH PROCESSING

Page 6: 3.3.2 Revision

INTERACTIVE PROCESSING

Page 7: 3.3.2 Revision

REAL-TIME PROCESSING

Page 8: 3.3.2 Revision

OPERATING SYSTEMS• Single-user

• One user at a time

• Users must log off before another can use it

• Multi-user

• Allows more than one user at a time

• Usually runs over a network

• OS manages each user to ensure conflicts do no occur

Page 9: 3.3.2 Revision

OPERATING SYSTEMS• Multi-tasking

• Allows the processor to ‘apparently’ deal with multiple processes at the same time.

• Actually allocates chunks of time to different processing requires and flicks between them.

• Interactive• Requires direct user interaction whilst running.

• Real-time• Usually embedded in another application and can run on their own with no user

interaction, but might react to a stimulus caused by the user.

• For example, the ECU of a car.

Page 10: 3.3.2 Revision

OPERATING SYSTEMS• Batch processing

• Given a set of tasks to complete without user interaction.

• Processes jobs when system is not in use or just before the processed data is required.

• Distributed processing

• Computers connected together sharing the work load.

• Each computer processes parts of the job.

• Results are later combined.

Page 11: 3.3.2 Revision

USER INTERFACES (BASICS)• For the exam you need to know about:

• Design Principles (Discuss design principles)

• Colour, layout, quantity of information, complexity of language and type of controls.

• Method of controls (Discuss methods for communication techniques)

• Computer to person, Person to computer and computer to computer.

Page 12: 3.3.2 Revision

Quantity of information

Font

DESIGN PRINCIPLES

Page 13: 3.3.2 Revision

COLOUR• Things to think about:

• Do end users have any disabilities?

• Colour blindness

• Dyslexia

• Colours can trigger reactions (Green is ok, Red is bad) and grab attention.

• Limit the number of colours (4 per screen, 7 per sequence).

• Colours can be used to code information.

Page 14: 3.3.2 Revision

LAYOUT• Things to think about:

• Consistent layout (between screens and applications).

• Layout of information and data entry should be logical.

• Important information and action points need to be in a prominent position.

• Designing for easy learning and efficient use.

Page 15: 3.3.2 Revision

FONT• Things to think about:

• Easy to read.

• Who are the end users and what are their needs.

• What equipment will be used and possible ergonomics should be considered.

• PC, Laptop and hand-held devices are all placed at different distances from the end user.

• Styles should be applied appropriately for easy transfer of information.

Page 16: 3.3.2 Revision

COMPLEXITY OF LANGUAGE• Things to think about:

• Who are the end-users?

• Complexity kept as low as possible.

• All errors should be in the simplest of forms.

• Help should be useful, not condescending.

• All technical language should be minimal and fit for purpose.

Page 17: 3.3.2 Revision

TYPES OF CONTROL• Things to think about:

• Ease of use:

• Macros: Automate complex or repetitive tasks.

• Buttons: Navigation or activate macros.

• Forms: Assist in data entry (logical, validation and verification)

• Menus. Allows actions to be selected (can hide inappropriate actions)

Page 18: 3.3.2 Revision

METHODS OF DIALOGUE• You need to be able to discuss methods of dialogue between a computer and a person, a

person and a computer and a computer to another computer.

• They main ways that computers and humans communicate is via a user interface.

• Modern UI’s are graphical (GUIs).

• They make use of:

• Prompts

• Input styles and methods

• Feedback

Page 19: 3.3.2 Revision

PROMPTS• Prompts indicate something to the user.

• In a command line interface the prompt will indicate that a command needs to be entered.

• In a GUI, icons are used to prompt the user.

• Menus are also used to prompt the user to select certain actions.

Page 20: 3.3.2 Revision

NATURE OF INPUT• This describes how the input will be requested:

• Question based

• Form based

• The next response could be determined by the last input.

Page 21: 3.3.2 Revision

METHOD OF INPUT• Usually input methods include keyboard and mouse.

• Touch screens and audio inputs are also becoming more popular.

Page 22: 3.3.2 Revision

FEEDBACK• Providing limited number of responses to select from.

• Can be in the form of:

• Menus and Sub-Menus.

• Very specific options being available to control what the user can select.

Page 23: 3.3.2 Revision

FEEDBACK• Providing limited number of responses to select from.

• Can be in the form of:

• Menus and Sub-Menus.

• Very specific options being available to control what the user can select.

Page 24: 3.3.2 Revision

TAKING THE USER INTO ACCOUNT• You need to be able to explain how a potential user’s:

• Perception

• Attention

• Memory

• Learning

can be taken into account when designing an interface.

• The presentation on my website goes into a lot of detail about different things to consider...but they all inter-relate with each other.

Page 25: 3.3.2 Revision

PERCEPTION• Users perceive inputs from sights and sounds.

• Users have preconceived ideas about how things should be done.

• Red text = Bad

• Siren = Bad

• Ding = Good

• BONG = Bad

Page 26: 3.3.2 Revision

ATTENTION• Most people have a limited attention span.

• Designers need to think about how to increase the attention span of user:

• Uncluttered screens

• Easy to access information

• Clearly labelled input areas

• Pop up messages, flashing images and sounds can draw the user’s attention

• Keeping menus consistent so they are easily used and understood

• Keeping icon symbols consistent too – Floppy Disk for save icon

Page 27: 3.3.2 Revision

MEMORY• Keeping GUIs consistent with already made GUIs helps to shorten the learning curve.

• Users make use of pre-existing memory experiences to help them learn.

• Consistency aids in the recall of actions.

• It is also important as people have preconceptions about how things should work based on prior experiences.

Page 28: 3.3.2 Revision

LEARNING• Must look at previous user experience.

• New interfaces should try and match old system as far as possible.

• On-screen help is really important.

• Important to think about perception, attention and memory!