Software Architecture

Slides:



Advertisements
Similar presentations
Chapter 15 User Interface Design.
Advertisements

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 16 Slide 1 User interface design.
Input Design and User Interface Design
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
User Interface Design Yonsei University 2 nd Semester, 2013 Sanghyun Park.
Chapter 13 User Interface Design.
User interface design. Objectives l To suggest some general design principles for user interface design l To explain different interaction styles and.
Introduction to Software Engineering
Soft. Eng. II, Spr 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 4 Title: the user interface Reading: I. Sommerville, Chap. 15.
1 SWE Introduction to Software Engineering Lecture 27 – User Interface Design (Chapter 16)
7M701 1 User Interface Design Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 15
COMP365: DESIGN Information systems architecture
1 SWE Introduction to Software Engineering Lecture 26 – User Interface Design (Chapter 16)
1 / 31 CS 425/625 Software Engineering User Interface Design Based on Chapter 15 of the textbook [SE-6] Ian Sommerville, Software Engineering, 6 th Ed.,
User Interface Design: Methods of Interaction. Accepted design principles Interface design needs to consider the following issues: 1. Visual clarity 2.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 15Slide 1 User interface design l Designing effective interfaces for software systems.
7. User Interface Design.
ESE Einführung in Software Engineering
User Interface Design. Overview The Developer’s Responsibilities Goals and Considerations of UI Design Common UI Methods A UI Design Process Guidelines.
User interface design Designing effective interfaces for software systems Objectives To suggest some general design principles for user interface design.
User interface design. Recap User Interface GUI Characteristics (Windows, Icons, Menus, Pointing, Graphics) User Centered Design User Interface Design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
User interface design.
Chapter 29 - Interaction design
Software Engineering User Interface
Object Oriented Programming 31465
MULTIMEDIA TECHNOLOGY AND APPLICATIONS CHAPTER 7. MULTIMEDIA SOFTWARE DEVELOPMENT TECHNOLOGY.
User interface design. Recap OOD is an approach to design so that design components have their own private state and operations Objects should have constructor.
CSC 480 Software Engineering Lecture 19 Nov 11, 2002.
©RavichandranUser interface Slide 1 User interface design.
Computer Graphics Lecture 28 Fasih ur Rehman. Last Class GUI Attributes – Windows, icons, menus, pointing devices, graphics Advantages Design Process.
Software Engineering Chapter 16 User Interface Design Ku-Yaw Chang Assistant Professor Department of Computer Science and Information.
Slide 1 Chapter 9 User interface design. Slide 2 The user interface l User interfaces should be designed to match the skills, experience and expectations.
Software Engineering User Interface Design Slide 1 User Interface Design.
COOP Seminar – Fall 2006 Slide 1 HOUSTON COMMUNITY COLLEGE SYSTEM SAIGONTECH SAIGON INSTITUTE OF TECHNOLOGY User Interface Design.
User interface design. Objectives l To suggest some general design principles for user interface design l To explain different interaction styles and.
CS.436 Software Engineering By Ajarn..Sutapart Sappajak,METC,MSIT Chapter 11 User Interface Design Slide 1 1 Chapter 11 User Interface Design.
Input Design Lecture 11 1 BTEC HNC Systems Support Castle College 2007/8.
Chapter 16: User Interface Design Omar Meqdadi SE 273 Lecture 16 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 15Slide 1 User interface design l Designing effective interfaces for software systems.
Ch16: User Interface Design Users often judge a system by its interface rather than its functionality Poorly designed interfaces can cause users to make.
CSC 480 Software Engineering High Level Design. Topics Architectural Design Overview of Distributed Architectures User Interface Design Guidelines.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 15Slide 1 Chapter 15 User Interface Design.
©Ian Sommerville 2004bzupages.com. Chapter 16 Slide 1 User interface design.
IT323 - Software Engineering 2 1 Tutorial 3.  Suggest ways in which the user interface to an e-commerce system such as an online stores might be adapted.
Chapter 2: Advanced programming concepts Part 3: The user interface Lecture 5 1.
Chapter 29 - Interaction design Chapter 29 is available online:
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
User interface design. Objectives  To suggest some general design principles for user interface design  To explain different interaction styles and.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 16 Slide 1 User interface design.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
Chapter 15 User Interface Design.
Chapter 6 : User interface design
User interface design.
User interface design.
CHAPTER 7: USER INTERFACE DESIGN
Software Engineering User Interface
Unit 2 User Interface Design.
User interface design.
User interface design.
Software engineering USER INTERFACE DESIGN.
GUI Week 9.
User interface design.
User interface design.
GRAPHICAL USER INTERFACE GITAM GADTAULA. OVERVIEW What is Human Computer Interface (User Interface) principles of user interface design What makes a good.
GRAPHICAL USER INTERFACE GITAM GADTAULA KATHMANDU UNIVERSITY CLASS PRESENTATION.
Presentation transcript:

Software Architecture User interface design Designing effective interfaces for software systems Objectives To suggest some general design principles for user interface design To explain different interaction styles To introduce styles of information presentation To introduce usability attributes and system approaches to system evaluation Manish Kumar,MSRIT Software Architecture

Software Architecture The user interface 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 Most users of business systems interact with these systems through graphical user interfaces (GUIs) In some cases, legacy text-based interfaces are still used Manish Kumar,MSRIT Software Architecture

Software Architecture GUI characteristics Manish Kumar,MSRIT Software Architecture

Software Architecture 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 Manish Kumar,MSRIT Software Architecture

User interface design process Manish Kumar,MSRIT Software Architecture

Software Architecture UI design principles User familiarity The interface should be based on user-oriented terms and concepts rather than computer concepts E.g., 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 Manish Kumar,MSRIT Software Architecture

UI design principles (cont.) 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 E.g., some users have seeing difficulties and so larger text should be available Manish Kumar,MSRIT Software Architecture

User-system interaction Two problems must be addressed in interactive systems design How should information from the user be provided to the computer system? How should information from the computer system be presented to the user? User interaction and information presentation may be integrated through a coherent framework such as a user interface metaphor Manish Kumar,MSRIT Software Architecture

Software Architecture Interaction styles Direct manipulation Easiest to grasp with immediate feedback Difficult to program Menu selection User effort and errors minimized Large numbers and combinations of choices a problem Form fill-in Ease of use, simple data entry Tedious, takes a lot of screen space Command language Easy to program and process Difficult to master for casual users Natural language Great for casual users Tedious for expert users Manish Kumar,MSRIT Software Architecture

Information presentation Information presentation is concerned with presenting system information to system users The information may be presented directly or may be transformed in some way for presentation The Model-View-Controller approach is a way of supporting multiple presentations of data Manish Kumar,MSRIT Software Architecture

Information display factors Is the user interested in precise information or data relationships? How quickly do information values change? Must the change be indicated immediately? Must the user take some action in response to a change? Is there a direct manipulation interface? Is the information textual or numeric? Are relative values important? Manish Kumar,MSRIT Software Architecture

Analog vs. digital presentation Compact - takes up little screen space Precise values can be communicated Analog presentation Easier to get an 'at a glance' impression of a value Possible to show relative values Easier to see exceptional data values Manish Kumar,MSRIT Software Architecture

Alternative information presentations Manish Kumar,MSRIT Software Architecture

Software Architecture Information display Manish Kumar,MSRIT Software Architecture

Displaying relative values Manish Kumar,MSRIT Software Architecture

Software Architecture Textual highlighting Manish Kumar,MSRIT Software Architecture

Software Architecture Data visualisation Concerned with techniques for displaying large amounts of information Visualisation can reveal relationships between entities and trends in the data Possible data visualisations are: Weather information State of a telephone network Chemical plant pressures and temperatures A model of a molecule Hyperweb Manish Kumar,MSRIT Software Architecture

Software Architecture Colour displays Colour adds an extra dimension to an interface and can help the user understand complex information structures Can be used to highlight exceptional events What are some common mistakes in the use of colour? The use of colour to communicate meaning Over-use of colour in the display Manish Kumar,MSRIT Software Architecture

Software Architecture Error messages Error message design is critically important. Poor error messages can mean that a user rejects rather than accepts a system Messages should be polite, concise, consistent and constructive The background and experience of users should be the determining factor in message design Manish Kumar,MSRIT Software Architecture

Nurse input of a patient’s name Manish Kumar,MSRIT Software Architecture

System and user-oriented error messages Manish Kumar,MSRIT Software Architecture

User interface evaluation Some evaluation of a user interface design should be carried out to assess its suitability Full scale evaluation is very expensive and impractical for most systems Ideally, an interface should be evaluated against a usability specification However, it is rare for such specifications to be produced Manish Kumar,MSRIT Software Architecture

Software Architecture Usability attributes Manish Kumar,MSRIT Software Architecture

Simple evaluation techniques Questionnaires for user feedback Video recording of system use and subsequent tape evaluation. Instrumentation of code to collect information about facility use and user errors. The provision of a “gripe” button for on-line user feedback. Manish Kumar,MSRIT Software Architecture

Software Architecture Key points Interface design should be user-centred. An interface should be logical and consistent and help users recover from errors Interaction styles include direct manipulation, menu systems form fill-in, command languages, and natural language Graphical displays should be used to present trends and approximate values. Digital displays when precision is required Colour should be used sparingly and consistently Manish Kumar,MSRIT Software Architecture

Software Architecture Key points Ideally, a user interface should be evaluated against a usability specification What about help for the user? Systems should provide on-line help. This should include “help, I’m in trouble” and “help, I want information” A range of different types of user documents should be provided Manish Kumar,MSRIT Software Architecture

Software Architecture Any Question ??? Manish Kumar,MSRIT Software Architecture

Software Architecture Thank you !!! Manish Kumar,MSRIT Software Architecture