Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Interaction Design > 2-Requirements Analysis > Flashcards

2-Requirements Analysis Flashcards

1
Q

3 Components of understanding requirements

A
  1. who are the users
  2. what do they want
  3. what do they need/what should the system accomplish
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Why do requirements analysis

A
  1. failure at this stage is expensive and time consuming to fix
  2. customers may explain their needs ambiguously
  3. designers can understand customer wishes incorrectly
  4. programmers can implement something not asked for
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is a requirement

A
  1. statement about what and how a future software or product should perform
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Identifying needs

A

Understand as much as possible about users, task,

context

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Establishing requirements

A

Produce a stable set of requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Functional requirements

A

what the system should do

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Non-functional requirements

A

what are the constraints on

the system / development

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Four examples of non functional requirements

A
  1. data requirements
  2. environmental characteristics
  3. user characteristics
  4. usability goals and user experience goals
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Examples of NFRs from data

A
  1. data sources
  2. types of data
  3. storage mode (database)
  4. persistence duration
  5. accuracy and consistency
  6. representations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Examples of NFRs from environment

A
  1. physical characteristics (cold/crowded)
  2. social characteristics (collaboration or competition)
  3. organisation: person vs enterprise
  4. technical (backwards compatibility)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Examples of NFRs from user characteristics

A
  1. ICT ability
  2. age/nationality/education
  3. physical/mental characteristics
  4. do they like tech or not
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Examples of NFRs from usability and experience goals

A
  1. usability – is it intuitive to use/easy to learn

2. is it enjoyable to use / aesthetically pleasing/motivating

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Why focus on the user rather than concentrating solely on functional requirements?

A

avoids (if users don’t find system acceptable)
1. redesign
2. retraining of users (call centres)
time, money

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Define STM

A
  1. (context) Consider technical, social, organizational and human aspects of design
  2. (don’t isolate) Technology is not developed in isolation but as part of a wider organizational environment
  3. (avoid overruling human aspects) consider social and technical issues side by side  so that human issues are not overruled by technical considerations
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Two stages of STM+purpose of each

A
  1. Identify stakeholders (CUSTOM analysis)

2. Understand stakeholders (Requirements Development)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

CUSTOM model

A
  • ST methodology for use in SMALL ORGANISATIONS
  • identifies:
    1. who is involved with new system
    2. what are their FRs/NFRs
    3. what is the organisational structure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Stakeholder

A
  1. Anyone who is affected by the success or the failure of the system
  2. if organisation, not just end user .: need to know to get right set of requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

General stakeholders

A

users which:

  1. interact directly
  2. manage direct users
  3. input/output from system
  4. make purchasing decision
  5. use competitors’ products
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Primary

A

people who use the system (frequent, hands on, training)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Secondary

A

produce input/receive output but may not directly use it (occasional, via someone else)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Tertiary

A

people affected by system introduction OR influence its purchase, but are themselves neither primary nor secondary stakeholders

22
Q

Facilitating

A

people involved in system design, development, maintenance

23
Q

Data structures for stakeholder analysis and requirements development

A
  • matrix

- onion diagram

24
Q

Requirements development purpose

A

develop user centred requirements for system after the stakeholders have been identified

25
Q

List of 8 elements of RDM

A

 Aims
 Sources of satisfaction  Knowledge and skills
 Attitudes to work
 Work-group attributes  Nature of activities
 Responsibility
 Working conditions

26
Q

Aims

A

what has the stakeholder to achieve, how is success measured

e.g. waiter: cust sat, tip size

27
Q

Job sat

A

 What are the stakeholder’s sources of job satisfaction?  What are the sources of dissatisfaction and stress?

system aims to preserve/remove respectively

waiter: cust exp, working mem load

28
Q

Knowledge skills

A

stakeholder knowledge, asymmetries

chef vs waiter cooking knowledge

29
Q

Work attitude

A

What is the stakeholder’s attitude towards work and computer technology?

manager vs chef

30
Q

Work group attributes

A

Are there any work-group attributes that will affect the acceptability of the product to the stakeholder?

31
Q

Features of activity

A

What are the characteristics of the stakeholder’s task in terms of frequency, fragmentation, and choice of actions?

summary vs fragmented use by waiters

32
Q

Responsibilities

A

Does the stakeholder have to consider any particular issues relating to responsibility, security, or privacy?

discreetness, privacy, security of payments

33
Q

Work conditions

A

What are the typical conditions in which the stakeholder is working?

chef vs manager

34
Q

SSM definition and purpose

A
  1. broader than STM, consider organisation as a whole
  2. stakeholders and technology are components of the larger context
  3. aim – learning about problem situation between stakeholders + define the problem
    (vs STM – already well defined problem)
35
Q

Stages of SSM

A
  1. Rich picture
  2. Root definitions
  3. Conceptual model
36
Q

SSM flowchart

A

Real world

  1. problem situation considered problematic
  2. problem situation expressed

Systems thinking about real world

  1. root definitions of relevant purposeful activity systems
  2. conceptual models of the systems named in the root definitions

Real world

  1. comparison of models and real world
  2. changes: systematically desirable, culturally feasible
  3. action to improve the problem situation
37
Q

Rich picture def

A
  1. detailed description of problem situation
  2. who are the stakeholders
  3. what groups do they work in
  4. what tasks do they perform
38
Q

Root definitions def

A
  1. stakeholder perceptions
  2. moving from real world situation to definitions of what the stakeholders perceive to be the activities taking place in the organisation
  3. may be several different root definitions, representing different stakeholder perspectives
  4. need to reconcile the differing root definitions of different stakeholder perspectives at a later stage
39
Q

Conceptual model def

A
  1. model of real world constructed with details of what the system has to do to meet the root definitions
40
Q

CATWOE for root definitions

A

Purpose – list the perspectives of a situation that must be considered

Clients
Actors
Transformations (most important)
World view
owner
Environment
41
Q

Conceptual model –
what+why are transformations
the most important part
of the root definitions

A

1- used to build the conceptual model
2- used to define what is achieved and how
3- this is what the new system will modify
4-achievements: model hierarchically, list core relevant activities, provide different levels of detail=activities to carry out the transformations

42
Q

Conceptual model –purposes

A
  1. identify differences between real world situation and model of how stakeholders perceive system (root defs)
  2. different conceptual models can represent different viewpoints (basis for debate, inform change/development of systems)
43
Q

Outcome of SSM

A

for designers to have better understanding of context in which developed systems are to be placed

given rich picture, root defs, conceptual model move towards a possible solution/development of an appropriate system (e.g. waiter pads that speed up order taking, improve efficiency, reduce mistakes and complaints)

44
Q

Rich picture+root defs of restaurant billing

A

Situation: Order taking and payment process in the restaurant

Root defs: waiters want to increase customer satisfaction

  1. clients: diners (receive food, bill)
  2. actors: waiters, chefs
  3. txfs: orders -> bills
  4. wv: water sees current system as problematic (working memory)
  5. owner of restaurant chain owns billing system
  6. env: health and safety regulations
45
Q

Conceptual model example – restaurant

A

achievement of serving a diner involves core activities = (find out, serve, clear table, payment)

achievement of paying for the food involves sub-achievements = (produce bill, collect money, produce receipt optionally)

46
Q

Core activities of requirements ANALYSIS

A
  1. data gathering
  2. data analysis
  3. defining the requirements
    - iteration
47
Q

CATWOE: owner

A

who the system belongs to, and who can allow changes in

the system

48
Q

CATWOE: environment

A

what factors influence the system

49
Q

CATWOE: environment

A

what factors influence the system

50
Q

why are transformations the most important part of the root definitions

A

1- used to build the conceptual model
2- used to define what is achieved and how
3- this is what the new system will modify
4-achievements: model hierarchically, list core relevant activities, provide different levels of detail=activities to carry out the transformations

Interaction Design (9 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions