user interface design (ch. 11) - emory universitycengiz/cs540-485-soft-eng-fa14/...(mcgraw-hill,...
TRANSCRIPT
User Interface Design (Ch. 11)
Cengiz GünayCS485/540 Software Engineering
Fall 2014, Some slides courtesy of Joan Smith, Roger Pressman, Ian Sommerville, and theInternets
Günay (Emory MathCS) UI Design Fall 2014 1 / 10
(c) thedailywtf.com
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 2!
Interface Design!
(c) COBE Design
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 3!
Interface Design!
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 4!
Golden Rules!
! Place the user in control!! Reduce the userʼs memory load!! Make the interface consistent!
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 5!
Place the User in Control!
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 6!
Reduce the Userʼs Memory Load!
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 7!
Make the Interface Consistent!
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e
(McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman. 15
Interface Design Steps
Using information developed during interface analysis, define interface objects and actions (operations).
Define events (user actions) that will cause the state of the user interface to change. Model this behavior.
Depict each interface state as it will actually look to the end-user.
Indicate how the user interprets the state of the system from information provided through the interface.
These slides are designed to accompany Software
Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill,
2009). Slides copyright 2009 by Roger Pressman.
14
Activity Diagram enter password
and user ID
select major funct ion
valid passwor ds/ ID
prompt for reent ry
invalid passwor ds/ ID
input t r ies r em ain
no input
t r ies r em ain
select surveillance
ot her f unct ions
m ay also be
select ed
t hum bnail views select a specif ic cam er a
select camera icon
prompt for
another v iew
select specif ic
camera - thumbnails
exit t his f unct ionsee anot her cam er a
view camera output
in labelled window
Supplements the use
case by providing a
graphical representation
of the flow of interaction
within a specific scenario
These slides are designed to accompany Software
Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill,
2009). Slides copyright 2009 by Roger Pressman.
15
Swimlane
Diagrams
Allows the modeler to represent the flow of activities described by the use-case and at the same time indicate which actor (if there are multiple actors involved in a specific use-case) or analysis class has responsibility for the action described by an activity rectangle:
•Actors
•Timing
•Flow
enter password
and user ID
select m ajor funct ion
valid p asswo r d s/ ID
prom pt for reent ry
in valid
p asswo r d s/ ID
in p u t t r ies
r em ain
n o in p u t
t r ies r em ain
select surveillance
o t h er f u n ct io n s
m ay also b e
select ed
t h u m b n ail views select a sp ecif ic cam er a
select cam era icon
generate video
output
select specif ic
cam era - thum bnails
exit t h is
f u n ct io n
see
an o t h er
cam er a
h o m e o w n e r c a m e ra i n t e rf a c e
prom pt for
another v iew
view cam era output
in labelled window
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 11!
User Analysis!! Are users trained professionals, technician, clerical, or manufacturing workers?!! What level of formal education does the average user have?!! Are the users capable of learning from written materials or have they expressed
a desire for classroom training?!! Are users expert typists or keyboard phobic?!! What is the age range of the user community?!! Will the users be represented predominately by one gender?!! How are users compensated for the work they perform? !! Do users work normal office hours or do they work until the job is done?!! Is the software to be an integral part of the work users do or will it be used only
occasionally?!! What is the primary spoken language among users?!! What are the consequences if a user makes a mistake using the system?!! Are users experts in the subject matter that is addressed by the system?!! Do users want to know about the technology the sits behind the interface?!
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 16!
Design Issues!! Response time!! Help facilities!! Error handling!! Menu and command
labeling!! Application accessibility!! Internationalization!
Usability Testing
Define tasks
user storiesuse cases
Define users
TestersRegular users
Test and collect measurements
Time to complete taskCommon errorsComplaintsBugs
Günay (Emory MathCS) UI Design Fall 2014 8 / 10
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 17!
WebApp Interface Design!! Where am I? The interface should !
! provide an indication of the WebApp that has been accessed !! inform the user of her location in the content hierarchy.!
! What can I do now? The interface should always help the user understand his current options!! what functions are available?!! what links are live?!! what content is relevant?!
! Where have I been, where am I going? The interface must facilitate navigation. !! Provide a “map” (implemented in a way that is easy to understand)
of where the user has been and what paths may be taken to move elsewhere within the WebApp.!
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 18!
Effective WebApp Interfaces!! Bruce Tognozzi [TOG01] suggests…!
! Effective interfaces are visually apparent and forgiving, instilling in their users a sense of control. Users quickly see the breadth of their options, grasp how to achieve their goals, and do their work.!
! Effective interfaces do not concern the user with the inner workings of the system. Work is carefully and continuously saved, with full option for the user to undo any activity at any time.!
! Effective applications and services perform a maximum of work, while requiring a minimum of information from users.!
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 23!
Mapping User Objectives!
objective #1objective #2objective #3objective #4objective #5
objective #n
List of user objectives
Home page text copy
graphic
graphic, logo, and company name
Navigationmenu
Menu barmajor functions
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 25!
Aesthetic Design!! Donʼt be afraid of white space.!! Emphasize content.!! Organize layout elements from top-left to
bottom right. !! Group navigation, content, and function
geographically within the page.!! Donʼt extend your real estate with the scrolling
bar.!! Consider resolution and browser window size
when designing layout.!
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e (McGraw-Hill, 2009) Slides copyright 2009 by Roger Pressman.! 26!
Design Evaluation Cycle!
12 Techniques for UI Design
From: “12 Useful Techniques For Good User Interface Design”by Dmitry Fadeyev
1 Highlight important changes2 Enable keyboard shortcuts in your Web application3 Upgrade options from the account page4 Advertise features of the application5 Use color-coded lists6 Offer personalization options7 Display help messages that attract the eye8 Design feedback messages carefully9 Use tabbed navigation10 Darken background under modal windows11 Lightboxes and Slideshows12 Short sign-up forms
Günay (Emory MathCS) UI Design Fall 2014 10 / 10