Slide 1

Requirements Wrap-up (Chapter 31 of requirements text)and

Interaction Design: Introduction(Chapters 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.

Slide 2

Outline

• Requirements Wrap-up

• Interaction Design - Introduction

Slide 3

Requirements Wrap-up

Slide 4

Requirements Process Steps

1. Get Organized2. Understand the Problem Being Solved3. Understand User and Stakeholder Needs4. Define the System5. Continuously Manage Scope and Change6. Refine the System Definition7. Build the Right System8. Manage the Requirements Process

Slide 5

Interaction Design - Introduction

Slide 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.

Slide 7

Why Interaction Design is Important

• People will pay you to do this stuff well

• It’s a pervasive part of software design

• Likewise for devices which use software

• You need to know when it’s good or bad, to make your systems acceptable to users

Slide 8

What’s good and what’s poor…

• Some examples… What are they?

Slide 9

More examples…

Slide 10

Another example…

Slide 11

More examples…

Slide 12

More examples…

Slide 13

More examples…

Slide 14

Goals of Interaction Design

• Usability

and

• User experience

Slide 15

Heuristics and usability principles

• Heuristics – Design principles used in practice

• Usability Principles – Used mostly as the basics for evaluating prototypes and existing systems