LlosengCh07E2 - Object-Oriented Software Engineering...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
© Lethbridge/Laganière 2005 Chapter 7: Focusing on Users and Their Tasks 2 7.1 User Centered Design Software development should focus on the needs of users Understand your users Design software based on an understanding of the users’ tasks Ensure users are involved in decision making processes Design the user interface following guidelines for good usability Have users work with and give their feedback about prototypes, on-line help, and draft user manuals
Background image of page 2
© Lethbridge/Laganière 2005 Chapter 7: Focusing on Users and Their Tasks 3 The importance of focusing on users Reduced training and support costs Reduced time to learn the system Greater efficiency of use Reduced costs by only developing features that are needed Reduced costs associated with changing the system later Better prioritizing of work for iterative development Greater attractiveness of the system, so users will be more willing to buy and/or use it
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
© Lethbridge/Laganière 2005 Chapter 7: Focusing on Users and Their Tasks 4 7.2 Characteristics of Users Software engineers must develop an understanding of their users and their. ... Goals for using the system Potential patterns of use Demographics Knowledge of the domain and of computing systems
Background image of page 4
© Lethbridge/Laganière 2005 Chapter 7: Focusing on Users and Their Tasks 5 7.3 Basics of User Interface Design User interface design should be done in conjunction with other software engineering activities. Do use case analysis to help define the tasks that the UI must help the user perform. Do iterative UI prototyping to address the use cases. Results of prototyping will enable you to finalize the requirements.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
© Lethbridge/Laganière 2005 Chapter 7: Focusing on Users and Their Tasks 6 Usability vs. Utility Does the system provide the capabilities to allow users to achieve their goals? This is utility . Does the system allow users to learn and to use the capabilities easily ? This is usability . (Usually considered a non-functional requirement) Both utility and usability are essential
Background image of page 6
© Lethbridge/Laganière 2005 Chapter 7: Focusing on Users and Their Tasks 7 Aspects of usability Usability can be divided into separate aspects: Learnability The speed with which a new user can become proficient with the system. Efficiency of use How fast an experienced user can do work. Error handling
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/21/2012 for the course CS 307 taught by Professor Staff during the Fall '08 term at Purdue University-West Lafayette.

Page1 / 26

LlosengCh07E2 - Object-Oriented Software Engineering...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online