S556 SYSTEMS ANALYSIS
& DESIGN
Week 9
Team Process Presentation on April 4
2




15 minutes
Present your teamwork process, not the findings
about the project
Use artifacts
Everyone should be involved in the presentation
SLSI S556
Idea for Design/Usability Testing
Report
3

The report should include three components:
 Idea
for design (this can be a sketch, etc.)
 Usability testing report
 Feedback from users/clients

2-3 pages
SLIS S556
Feedback Meeting (Block, 2011)
4
Be honest
& authentic
SLIS S556
Consolidated Models
5



Show where the breakdowns and bottlenecks
are
Elevate what would otherwise be a bunch of
anecdotes to reveal systemic problems
Give the IT dept a way to talk back to the
business about prioritization decisions
SLIS S556
Consolidating Sequence Models
6



Show the common structure of a task across a
customer population
Use the flow model to identify the important
tasks
Only consolidate tasks that the system will
support, that you will redesign, or that you need
to understand in detail
SLIS S556
Example of Consolidated
Sequence Model
7

Prepare study guide for class/make lecture notes available to students
Activity
Intent
Abstracted Steps
Create
study guide
Create
additional
materials based on
course lecture to
help students
prepare for
assignments
Finding
Share
lecture/
study
guide
Share
Upload
Share
lecture
study guide
with students
Breakdowns
digital versions of
images that match the text
book images
List image #s (DIDO #s or
textbook #s) to be
reviewed
List terms necessary
lecture to
Oncourse
Schedule office hours to
review lecture
Upload
study guide to
Oncourse
20 MB per PPT lecture
requirement in
Oncourse which either
suggest faculty to break
up lectures or to meet
size requirements
SLSI S556
Consolidating Flow Models
8





Step 1: generate complete list of responsibilities for
each individual
Step 2: examine each responsibility
Step 3: recognize when different people play the
same roles
Step 4: how roles map to individuals
Step 5: consolidate the artifacts and communications
between people
SLIS S556
Consolidated Flow Model: Consider
Roles First
9
Head chef
- Keep track of what’s in the kitchen
- Provide oversight & instruct other cooks as necessary
- Make sure cooks are working together
- Communicate exact needs to shopper
- Decide on desired meals for special event with event planner
- Find out what’s needed to restock inventory
Cook
- Negotiate meals and who will
make them with other cooks
- Coordinate with head chef on
use of kitchen
- Make sure ingredients for planned
meal are available
- Coordinate with head chef on
how to make meal
Shopper
-Find out from head chef what to buy
and when to go
- Make on-the-spot decisions about
substitutions
-Bring accounting of expense to
fund manager
Event planner
S556
FundsSLIS
manager
Consolidated Flow Model: Add
Artifacts & Interactions
10
Head chef
- Keep track of what’s in the kitchen
- Provide oversight & instruct other cooks as necessary
- Make sure cooks are working together
- Communicate exact needs to shopper
- Decide on desired meals for special event with event planner
- Find out what’s needed to restock inventory
list of ingredients
Manage cooks
Cook
- Negotiate meals and who will
make them with other cooks
- Coordinate with head chef on
use of kitchen
- Make sure ingredients for planned
meal are available
- Coordinate with head chef on
how to make meal
Shopper
-Find out from head chef what to buy
and when to go
- Make on-the-spot decisions about
substitutions
-Bring accounting of expense to
fund manager
Event planner
S556
FundsSLIS
manager
Consolidating Artifact Models
12


Individual models show the structure and usage
of the things people create and use
Consolidated artifact models shows common
organizing themes and concepts that people use
to pattern their work
SLIS S556
Consolidating Artifact Models
13




Step 1: group artifacts of a similar type
Step 2: identify the common parts of the
artifacts
Step 3: identify structure, intent, and usage
within similar parts
Step 4: identify differences & determine how to
integrate them
SLIS S556
Consolidated Artifact Model
14

How it chunks
 Use
the structure of the artifact to guide the
structure of the system
 Maintain the distinctions that matter to users

What it looks like
 Determine
the intent of the presentation details
 Mimic the intent of presentation details, not the
details themselves
SLIS S556
Consolidating Physical Models
15


Individual physical models show the workplace
and site for each user interviewed
Consolidated physical models show the common
physical structure across the customer population
& the key variants that a system will have to
deal with
SLIS S556
Consolidating Physical Models
16


Step 1: separate the models into types of spaces
Step 2: catalog the common large structures &
organization, e.g., buildings, rooms, walls, sitting
area, etc.
 Identify
types of hardware, software, and network
connections
SLIS S556
Consolidating Physical Models
17


Step 3: identify constraints a system must live with &
problems it might overcome
Step 4: identify movement on the physical models
SLIS S556
Consolidated Physical Model
18

The reality check
 Don’t
depend on what’s not there
 Account for movement and multiple locations
 Take advantage of what is there
SLIS S556
Consolidated Physical Model
19

Pitfalls
 Not
taking the physical environment seriously
 E.g.,
if people don’t have printers by their desks, don’t
build a system that requires frequent trips to the printer
 E.g., If your users walk around all the time, don’t try to
tie them to a desk by giving them a product that only
runs on a desktop
SLIS S556
20
SLIS S556
Consolidating Cultural Models
21


Indicates a direction for the design
Shows within that direction what constraints have to
be accounted for
SLIS S556
Consolidating Cultural Models
22



Step 1: walk through each individual model,
cataloging and grouping influences (bubbles)
Step 2: consolidate influences. Reduce redundancies
Step 3: focus on influences, not on communication
flow (See B&H Figure 9.24, p. 196)
SLIS S556
Consolidated Cultural Model
23


Managers need to monitor and manage the
values of an organization
Make sure the changes you introduce will cause
someone in the customer population to take
notice (get buy-in)
SLIS S556
Consolidation
24

The affinity diagram:
 Data

from individual users to groups
Consolidation helps us understand intent, strategy,
structure, concepts, and mind-sets to support
customers
SLIS S556
Comparing Various Consulting Models
(Schwen, 1995)
25



Product consulting
Prescription consulting
Collaborative (Process) consulting
 ~=
Block’s Flawless consulting
SLIS S556
26
Dealing with Resistance (Block,
Chapter 9)

Step 1: Pick up the cues
Name the resistance
Be quiet, let the client respond

Consulting with a stone (p. 157)


 Don’t
take it personally
SLSI S556
Feedback Session (Block Ch 14, p. 223)
27
User Language That Is
Avoid Language That Is
Descriptive
Judgmental
Focused
Global
Specific
Stereotyped
Brief
Lengthy
Simple
Complicated
SLIS S556
Feedback Session (Block Ch 14)
28

Consultant as witness




Consultant as judge
Consultant as jury
Consultant as
prosecutor
Consultant as
defendant
SLIS S556
29
A Structure of a Feedback Meeting
(Block, p. 229, 2nd ed.)



Problem statement
Why the problem exists
What happens if the problem is not fixed
 In
the short term
 In the long term


Recommended solutions
Expected benefits
SLIS S556
AFFINITY DIAGRAM
The Affinity Diagram (see Chapter 8 in
HWW)
31





Shows the scope of the customer problem
Defines the key quality requirements on the system,
e.g., reliability, performance, hardware support, etc.
The hierarchical structure groups similar issues
A designer can learn the key issues and the data
It is recommended to build the affinity in a day
SLSI S556
The Affinity Diagram
32
Problem Label
data
data
Sub-problem
data
Labels
Sub-problem
Sub-problem
SLSI S556
Contextual Design for Invention
33




Get diverse perspectives
Inquiry into the consolidated work models
Brainstorms new work practice
Develop multiple solutions
SLSI S556
Using Models for Design
34



Synthesize across the models
Discuss the models and possible metaphors in the
team, which leads to shared understanding and
perspectives
Data  consolidated models  design
SLSI S556
Goals of Work Redesign
35



To look across the different models and see a
unified picture of work practice
To use multiple perspectives to reveal the issues
To use multiple possibilities to drive the invention of
a creative design solution
SLSI S556
Affinity Model Exercise
36





Goal: Build affinity model based on these cards
Each team will fill out 20 index cards (interpretation
notes) + 5 color index cards (category notes)
Write down “data (e.g., The principle includes a
personal note on each printed e-mail that he sends to
the teacher)” from either interviews or observations
on the 20 index cards
Chunk these 20 cards into some categories
Use the color index cards to label these categories
SLSI S556
Affinity Notes
37
SLIS S556