requirements -k8凯发
loading
requirements
dtaxbdopno
oct 16, 2020
download
map outline
requirements
different requirements
usability / user experiences requirements
usability goals
user experiences goals
evaluate performance of the system
user requirements
who are the users?
what are the characteristics?
nationality
education background
personal circumstances
physical or mental disabilities
system use
novice
clear step-by-step guidance
constrained
expert
flexibility
access to advance features
frequent
shortcuts
casual/infrequent
clear menu paths
environment requirements
physical
dusty / noisy / light / heat / humidity?
social
collaboration and coordination
data sharing
distributed
synchronous or asynchronous
privacy
organizational
user support
communication structure and infrastructure
availability of training
technical
andriod
ios
others
data requirements
what kinds of data need to be stored?
type
volatility
size/amount
persistent
accuracy
value
how to store?
database
files
functional requirements
what the system should do?
what the system must to do?
prioritizing requirements
must have
fundamental requirements
minimum usable subset
should have
essential if have more time
system still usable without it
could have
can be left out of current development
want to have but won't have this time round
can wait until a later development
user profile
pact framework
people use technologies to undertake activities in context.
people
who will be using the product or system?
individual differences
physical
physical characteristics
variation in five senses
pcychological
spatial awareness
different attention span and memory
language and cultural differences
experiences
personalities
different goals, needs, reasons and motivations for using systems
activity
what task will they be performing with the product?
temporal
regular or infrequent
single continuous set of actions or done with interrupted actions
cooperation
done alone?
awareness of others
communication
complexity
how complicated?
defined steps or vague activity?
safety-critical
allow to make mistakes?
what are the critical consequences of errors?
nature/data and content
type of information
data changes with time?
resource of the data
choice of interface technology and communication technology
context
where and under what circumstances does the activity occur?
organizational context
social context
physical context
technology
what do you need to consider in your design?
input
speech input
motion, air pressure, vibrations using sensors
eye tracking
output
screen and monitor
multi-touch surface
printers
sound
haptics
communications between people and between devices
bandwidth and speed
data and type of contents to be communicated
outcome
difference between the designer and the user
what users want in reality?
need to investigate to verify information and to understand activity
must analyze with activity together
data gathering
key issues
setting goals
purposes of gathering
how to analyze
decide from whom to gather data - how many participants?
probabilistic sampling
non-probabilistic sampling
relationship with participants
participant information sheet
consent form
clear and professional
triangulation
more than one type of data
more than one type of data collecting methods
provide different perspectives
data validation
pilot studies
test run questions and analysis approach
make adjustments if you are not getting the information that expect
small trial of main study
recording methods
notes
video
audio
photographs
useful alternative of note-taking
gathering techniques
survey
measuring attitudes, awareness, intent, feedback….user experiences, characteristics of users and over-time comparisons
precise measurements or identifying usability problems in an interface
questionnaire
target respondents
purpose of the research
recruitment and sampling
design
open-ended responses
better understanding of phenomena
must be carefully worded
closed-ended responses
ordered response
number of choices in a logical order
single choice selection
e.g. ranking / likert scale
unordered response
number of choices but no order in responses
either single or multiple-choice selections
e.g. preference applications / demographic information
mode of administration
paper
email
web
surveymonkey
google form
microsoft form
recruitment
define the target population
determine sampling methods
contact the members of target population
sampling
probabilistic sampling
known probability of someone being chosen
census
random sampling
stratified sampling
non-probabilistic sampling
unknown likely of being chosen
snowball recruitment
self-selected surveys
volunteer
must collect demographic data
deploying online questionnaires
plan the timeline
design offline
program / complete online template
test the survey
test the survey with a group that will not be the part of survey
recruit participants
advantages
collect large number of responses quickly from users that are geographically dispersed
do not need special equipment
low costs
non-intrusive
disadvantages
problematic if population size is unknown
data is 'shallow'
unable to follow up immediately
biased data when the questions are related to patterns of usage
appropriate
less appropriate
interviews
initial exploration, requirements gathering, evaluation and subjective reactions
looking for information from large sample of population
types
unstructured
list of topics or questions as guide
start of with initial question and let interviewee discuss topic of choice
if conversation is stalled, introduce another topic from guide
allows interviewee to focus on topics/concerns of they find important
semi structured
more room to get clarification
start with a set of questions, similar to questions in fully structured interview
probe depending on response
fully structured
use rigid script to present question inn a well-defined order
easy to analyze
difficult to follow-up if answer is unanticipated
appropriate for deep digging / unfamiliar with problem domain or set of users / participants educate you to understand their needs
appropriate when hope to compare the responses across individuals
planning
identify objectives of the study
select type of interview
decide how will you analyze the data
write the questions
test your questions
determined the player in the activity
prepare activity materials
writing questions
break the interview into multiple sessions
not conduct the interview beyond two hours
word the questions clearly, understandable and impartial
keep the questions short
avoid double-barreled questions that address more than one issue
running the interview
digital conferencing system
participants are in their own environment
no need to travel
for sensitive issues, participants can be anonymous
1. introduction
2. warm-up
3. main body
4. a cool-off period
5. closure
advantages of using digital ways
things to note
don't pre-empt the answer
the body language of the interviewer matters
prestige response bias
advantages
collect 'deep' data
can be open-ended and exploratory
disadvantages
potential unbounded discussions
high effort to conduct - skill, resources
high amount of data
problems of recall
not appropriate
appropriate
focus groups
interview people in groups
facilitator guides and prompts discussion
advantages
allows for diverse or sensitive issues to be raised
good at gaining a consensus
increase interactivity between participants
disadvantages
inappropriate for controversial topics
depends highly on people in the group
high effort to conduct - skill, resources
appropriate for investigating shared issues
observations
direct obervation
silent
think loud
constructive interaction
advantages
different kinds of insights
good for understanding context of user activity
capture the detail of what individuals do
disadvantages
very time-consuming
huge amount of data
results may be limited use in normal environment
indirect observation
interaction logging
diaries ( feedback, elicitaion)
video and photographs collected remotely
advantages
observing users without disturbing their activities
can extend over long periods of time
more accurate time recording than survey
disadvantages
a large amount of quantitative data needs tool support to analyze (logging)
participants' memories may exaggerate (diary)
contextual inquiry
combination of interview and observation
main principles
context
go to the users whenever they are, and seeing what they do as they do it
partnership
user and interviewer explore user's life together
interpretation
observations interpreted by user and interviewer together
focus
guide interview setup and focus on inquiry
ethnography
combination of interview and observation
immerse themselves in the culture that they study
researcher's degree of participation can vary and affect study
requires cooperation and acceptance
requires skills to conduct
studying documentation
rules and procedures are often written down in manuals
good source of data
not to be used in isolation
good for understanding legislation and getting background information
no stakeholder time
choosing techniques
focus of the study - purpose / kinds of data
participants involved - characteristics / type of access
nature of technique - specialist equipment or training?
resources - available resources
data analysis
quantitative analysis
data cleansing
avoid human errors
reasonableness
inappropriate formatting
data makes sense
coding data
convert original data to numeric
descriptive statistics
mean
median
mode
standard deviation
statistical testing
significant test - comparing means
identifying relationships between factors
correlations testing
tools
excel
simple functionality
good for quick analysis
spss
comprehensive with advance functions, gui
expensive
r
comprehensive, scriptable
free!!!
qualitative analysis
looking for critical incidents
specific incidents that are significant
e.g. evaluation study
identifying themes
exploratory studies
identify patterns and themes
affinity diagram
categorizing data
top-down approach
set of categories determined beforehand
combination of inductive and deductive
tools
nvivo
dedoose
closed questions and some open questions (each analyzed separately)
most of open questions, but still depends
present findings
structured notations
use-case diagram
use cases
essential use cases
division of tasks
user intentions
product responsibilities
normal courses
set of actions most commonly performed
alternative courses
other possible sequences
captured at the bottom of the use case
no implementation/interaction details
actors
system
associations
functional requirements, capture interaction --> step-by-step descriptions
stories / storytelling
storytelling
e.g. goldilocks and the three bears
personas
user profile - rich description of typical users
synthesized from real people based on user research
typical, but not idealized
reminds who will use the product
no elastic users
no self-referential
no edge cases
make design decisions
advantages
types
primary - target of interface
secondary
primary needs
additional features
supplementary - combination of primary and secondary
customer
not end user
may be primary user
served - not users directly affected
negative - users' product is not mean for
how to create?
identify behavioral variables from demographical data
identify common pattern by mapping participants to behavioural data
synthesize and build model
scenario
narrative describes tasks performed by the persona
elements
persona involved
triggers of using?
what happens?
outcome
summarizing findings
e.g. tables, graphs, diagrams, video
task analysis
logic of task
sequence of steps
textual form or diagram
e.g. hta
identify task to be analyzed
break to 4-8 sub-tasks
level of details
plans
tree diagrams
outcomes
manuals & tuition
detailed interface design
cognitive task analysis
cognitive processes required to achieve goal
e.g. cognitive walkthrough
evaluate user interface usability
used in the design lifecycle of an interface
based on norman's 7 stages of action
preparation
interface
characteristics of typical users
sample tasks that focus on the aspects of the interface to be evaluated
clear sequence of actions needed for users to complete the task
process
analyst walk thought the action sequences for each task, placing it within the context of a typical scenario
takes notes
a record of critical information is compiled particular assumptions about what would cause problems and why
e.g. goms
goals - what the user wants to achieve
operators - basic actions that the user must perform
methods - sequences of subtasks
selection rules - rules that people use to choose between methods of achieving the same subtask.
conceptual design (model)
interface metaphor (physical entity)
conceptualizing what users are doing
a conceptual model instantiated at the interface
visualizing an operation
choosing
understand functionality
identify potential problems areas
generate metaphors
evaluate suitability of metaphors
advantages
makes it easy to learn new systems
helps to better understand the conceptual model
supports a diverse set of users
strengthen innovation
disadvantages
constrains the conceptual design to metaphors
limit the user to understand the system in terms of metaphor
poor designs can be used as the metaphor
rely on metaphors might hinder coming up with new conceptual models
some times may break conventional and cultural rules
interaction types
instructing
tell the system what to do
e.g. typing in commands
e.g.selecting menus
conversing
have a dialog with the system
menu-based dialogues
text-based dialogues
virtual agents
manipulating
manipulating objects and users experiences
based on users experience with real objects (affordance)
exploring
moving through virtual or physical environments
e.g. vr
responding
initiative to alert, describe, or show the user sth. of interesting
relevance to time or context
interface types
types of input and output methods
interface used by the users to support the interaction
choose the most appropriate or a combination
envisionment
make ideas visible and externalize thoughts
represent design work
occurs throughout development
different representations
sketches
ideas and thoughts can be quickly visualized
quick, timely, inexpensive, disposable and plentiful
o allow quick test of new ideas during brainstorming
o reduce attachment to design
basic elements, people, objects - depends on the purpose
context, user view, snapshot
advantages
storyboards
sequence of actions or events
user journey
3-7 steps
each picture labelled with 1 short description
context of interaction is visible
correct level of details
wireframes (e.g. wireflow)
single screen or interaction page
plan the layout and interaction patterns
different level of details
prototypes
low-fidelity
medium unlike the final medium
capture early design thinking
quick and easy to produce
high-fidelity
similar in look and feel with anticipated final product
detailed evaluation of the main design elements
paper prototypes
produce quickly
enables non-technical people to interact easily with the design team
flexibility - 'redesigned'
advantages
faking interaction
wizard of oz (lo-fi)
human is responding to output rather than the system
video prototype
how the prototype is 'used' in real-life
early stage - fake interaction
later stage - communicate what product looks like and can do
focus on information to be conveyed
limited by imgination, time and materials
compromises
horizontal - wide range but little details
vertical - lots of details but a few functions
special permission and leads to privacy issues
wireframes
user journey
wireflow
adv and disadv
more maps from user
embed code
copy the code to embed this map into your article. the embeded map can even be zoomed in / out
网站地图