Software engineering 18 user interface design
- 1. Software Engineering: 18
User Interface Design
Prof Neeraj Bhargava
Vaibhav Khanna
Department of Computer Science
School of Engineering and Systems Sciences
Maharshi Dayanand Saraswati University Ajmer
- 2. User interface design
• Designing effective interfaces for software
systems
• System users often judge a system by its
interface rather than its functionality
• A poorly designed interface can cause a user
to make catastrophic errors
• Poor user interface design is the reason why
so many software systems are never used
- 3. Graphical user interfaces
• Most users of business systems interact with
these systems through graphical interfaces
although, in some cases, legacy text-based
interfaces are still used
- 5. GUI advantages
• They are easy to learn and use.
• Users without experience can learn to use the
system quickly.
• The user may switch quickly from one task to
another and can interact with several different
applications.
• Information remains visible in its own window
when attention is switched.
• Fast, full-screen interaction is possible with
immediate access to anywhere on the screen
- 6. User-centred design
• The aim of this chapter is to sensitise software
engineers to key issues underlying the design
rather than the implementation of user interfaces
• User-centred design is an approach to UI design
where the needs of the user are paramount and
where the user is involved in the design process
• UI design always involves the development of
prototype interfaces
- 8. UI design principles
• UI design must take account of the needs,
experience and capabilities of the system users
• Designers should be aware of people’s physical
and mental limitations (e.g. limited short-term
memory) and should recognise that people make
mistakes
• UI design principles underlie interface designs
although not all principles are applicable to all
designs
- 10. Design principles
• User familiarity: The interface should be based on user-
oriented terms and concepts rather than computer
concepts. For example, an office system should use
concepts such as letters, documents, folders etc. rather
than directories, file identifiers, etc.
• Consistency : The system should display an appropriate
level of consistency. Commands and menus should
have the same format, command punctuation should
be similar, etc.
• Minimal surprise: If a command operates in a known
way, the user should be able to predict the operation
of comparable commands
- 11. Design principles
• Recoverability: The system should provide some
resilience to user errors and allow the user to
recover from errors. This might include an undo
facility, confirmation of destructive actions 'soft'
deletes, etc.
• User guidance: Some user guidance such as help
systems, on-line manuals, etc. should be supplied
• User diversity : Interaction facilities for different
types of user should be supported. For example,
some users have seeing difficulties and so larger
text should be available