Identifying needs and establishing requirements What, how and why?

Slides:



Advertisements
Similar presentations
Requirements gathering
Advertisements

including File Management
THE PROCESS OF INTERACTION DESIGN
Identifying needs and establishing requirements. Overview The importance of requirements Different types of requirements Data gathering Task descriptions:Scenarios.
User and Task Analysis Howell Istance Department of Computer Science De Montfort University.
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
1 The Design Process Lecture 9 Date: 2 nd March. 2 Overview Life-Cycle Models in HCI 4 basic activities in HCI Requirements Design Develop/Build Evaluation.
User Centered Design Intro to UCD Explain its motivation Discuss key stages in the process Present basic methods and techniques.
Requirements: Gathering. Why  To understand what we are going to be doing  We build systems for others, not for ourselves  Requirements definition:
User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo FJK 2005.
Identifying needs and establishing requirements Chapter 7a.
Identifying needs and establishing requirements
1 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo 1.
Identifying needs and establishing requirements Chapter 7b.
Principles and Methods
ESTABLISHING REQUIREMENTS
Identifying needs and establishing requirements. Overview The importance of requirements Different types of requirements Data gathering Task descriptions:Scenarios.
Requirements and Task Analysis. Please attend!! Duke Hutchings: “Window interfaces for multiple monitor systems”: next Monday 2/6, 9:30-11, room 154 student.
Requirements Gathering
Requirements Gathering Methods for Requirements Gathering and Requirements Gathering.
User Centered Design Lecture # 5 Gabriel Spitz.
Requirements Gathering and Task analysis. Requirements gathering and task analysis 4 Requirements gathering is a central part of systems development understanding.
User Interface Theory & Design
CS3205: Identifying needs and establishing requirements
The importance of requirements Data gathering for requirements Task descriptions:Scenarios Use Cases Essential use cases Task analysis: HTA.
Requirements Gathering. Why are requirements important? To understand what we are going to be doing We build systems for others, not for ourselves Requirements.
Computer Science Department California Polytechnic State University San Luis Obispo, CA, U.S.A. Franz J. Kurfess CPE/CSC 484: User-Centered Design and.
Identifying needs and establishing requirements Chapter 10.
1www.id-book.com Identifying needs and establishing requirements Chapter 10.
The importance of requirements Data gathering for requirements Task descriptions:Scenarios Use Cases Essential use cases Task analysis: HTA.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
Designing Educational Web Sites to Support Student Learning Steven WarburtonTELRI Project.
Identifying needs and establishing requirements CS365 – HCI - Week 3.
22C:082:001 Human-Computer Interaction. Fall Copyright © 2013 Juan Pablo Hourcade. 1 Group Project Phase 1.
Working with users, data-gathering techniques. Design Hall of Fame.
Knowing What to Do: Constraints, Discoverability, and Feedback
 Please get out an 8.5 X 11 sheet of paper  Put your name & the title above.  Follow the lecture and write your answers for each of the “Par” questions.
Software cost estimation Predicting the resources required for a software development process 1.
Requirements Gathering …along with Ethics. Agenda Questions? Project part 0 Requirements gathering Ethics.
Innovative Interface Design  User Experience Goals  Usability Goals  Consistancy  Internal  External  Feedback  Constraints  Affordances.
CS305: Fall 2008 Identifying needs and establishing requirements Readings: 1) Chapter 10 of the ID-Book textbook 2) Chapter 2 from Task-Centered User Interface.
Ch 7 Identifying needs and establishing requirements Group 3: Lauren Sullivan Chris Moore Steven Pautz Jessica Herron.
1 The Design Process Lecture 6 DeSiaMorewww.desiamore.com/ifm.
Systems Software Operating Systems. What is software? Software is the term that we use for all the programs and data that we use with a computer system.
Learning Objective The students should be able to: a. state the definition of software b. state the usage of software c. list different types of software.
User Interface Theory & Design Lecture 6a 1.  User interface is everything the end user comes into contact with while using the system  To the user,
1 Lecture 5: (Ref. Chapter 7) Identifying Needs and Establishing Requirements.
Individual Differences in Human-Computer Interaction HMI Yun Hwan Kang.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It describes what is a user doing or will.
Task Analysis Lecture # 8 Gabriel Spitz 1. Key Points  Task Analysis is a critical element of UI Design  It specifies what functions the user will need.
Chapter 2. This presentation covers the following: – Command Line – Forms – Menus – Natural Language.
AVI/Psych 358/IE 340: Human Factors Data Gathering October 1, 2008.
Software Interfaces. Learning Objectives Describe the characteristics of different types of user interfaces. Discuss the types of user interfaces which.
Requirements Gathering CSCI 4800/6800 Feb. 25, 2003.
2 The importance of requirements Different types of requirements Data gathering for requirements Task descriptions:Scenarios Use Cases Essential use cases.
GATHERING DATA Supplementary Note. What are requirements? A requirement is a statement about an intended product that specifies what it should do or how.
ICAD3218A Create User Documentation.  Before starting to create any user documentation ask ‘What is the documentation going to be used for?’.  When.
Software Engineering Developing Requirements. © Lethbridge/Laganière 2001 Chapter 4: Developing requirements2 4.1 Domain Analysis The process by which.
Identifying Needs and Establishing Requirements Kelly Kim Haimin Lee.
Classifications of Software Requirements
ESTABLISHING REQUIREMENTS
Working with users, part 2
The Design Process Lecture 9 Date: 2nd March.
Copyright Catherine M. Burns
Identifying needs and establishing requirements
File Management.
Background: Currently CCP4i puts each structure determination into a separate project directory, and automatically keeps a “Project History Database” recording.
introduction to computers
Presentation transcript:

Identifying needs and establishing requirements What, how and why?

What Two aims: 1. Understand as much as possible about users, task, context 2. Produce a stable set of requirements How: Data gathering activities Data analysis activities Expression as ‘requirements’ All of this is iterative

What, how and why? Why: Requirements definition: the stage where failure occurs most commonly Getting requirements right is crucial

Establishing requirements What do users want? What do users ‘need’? Requirements need clarification, refinement, completion, re-scoping Input: requirements document (maybe) Output: stable requirements Why ‘establish’? Requirements arise from understanding users’ needs Requirements can be justified & related to data

Different kinds of requirements Functional: —What the system should do —Historically the main focus of requirements activities (Non-functional: memory size, response time...) Data: —What kinds of data need to be stored? —How will they be stored (e.g. database)?

Different kinds of requirements Environment or context of use: — physical: dusty? noisy? vibration? light? heat? humidity? …. (e.g. OMS insects, ATM) — social: sharing of files, of displays, in paper, across great distances, work individually, privacy for clients — organisational: hierarchy, IT department’s attitude and remit, user support, communications structure and infrastructure, availability of training

An extreme example example

Different kinds of requirements Users: Who are they? — Characteristics: ability, background, attitude to computers — System use: novice, expert, casual, frequent — Novice: step-by-step (prompted), constrained, clear information — Expert: flexibility, access/power — Frequent: short cuts — Casual/infrequent: clear instructions, e.g. menu paths

Different kinds of requirements Usability: learnability, throughput, flexibility, attitude Note that user requirements and usability requirements refer to different things

Kinds of requirements What factors (environmental, user, usability) would affect the following systems? Self-service filling and payment system for a petrol (gas) station On-board ship data analysis system for geologists searching for oil Fashion clothes website

Summary Getting requirements right is crucial There are different kinds of requirement, each is significant for interaction design