Requirements Wrap-up (Chapter 31 of requirements text) and Interaction Design: Introduction (Chapters 1 of Interaction Design text)

1
Requirements Wrap-up (Chapter 31 of requirements
text)andInteraction Design Introduction(Chapte
rs 1 of Interaction Design text)

• CSSE 371 Software Requirements and Specification
• Don Bagert, Rose-Hulman Institute of Technology
• October 20, 2005
• Thanks to Steve Chenoweth for some of the slides
  included.

2
Outline

• Requirements Wrap-up
• Interaction Design - Introduction

3
Requirements Wrap-up
4
Requirements Process Steps

• Get Organized
• Understand the Problem Being Solved
• Understand User and Stakeholder Needs
• Define the System
• Continuously Manage Scope and Change
• Refine the System Definition
• Build the Right System
• Manage the Requirements Process

5
Interaction Design - Introduction
6
Introduction

• Interaction design (ID) is designing interactive
  products to support people in their everyday and
  working lives.
• The ID work itself is usually done as a team
  with different people having different skills.

7
Why Interaction Design is Important

• People will pay you to do this stuff well
• Its a pervasive part of software design
• Likewise for devices which use software
• You need to know when its good or bad, to make
  your systems acceptable to users

8
Whats good and whats poor

• Some examples What are they?

9
More examples
10
Another example
11
More examples
12
More examples
13
More examples
14
Goals of Interaction Design

• Usabilityand
• User experience

15
Heuristics and usability principles

• Heuristics Design principles used in practice
• Usability Principles Used mostly as the basics
  for evaluating prototypes and existing systems