Structuring Phase
      ysdn3006
PACT analysis
• used to scope a problem in a particular
  domain (sphere of activity)


                   Requirements

 ...
PACT analysis
• People have differing characteristics
   • physical differences (eg. weight and
      height, senses, disa...
PACT analysis
• Activities need to be considered by the design
  team
    •   purpose of the activity = important

       ...
PACT analysis
• Contexts are where activities occur
   •   physical context (eg. environment)

   •   social context (eg. ...
PACT analysis
• Technologies are used to perform functions
   •   input - people enter data, commands (eg. wiki postings)
...
Scoping a problem
     with PACT
• Important to harmonize the PACT elements
  in a particular domain
• Useful to understan...
Requirements
• goal is to bring about something new in what
  people do or might want to do
• are generated by conducting ...
Start a PACT Analysis
• think about   the communities in our public
  spaces
• how are the communities defined ?
 • context...
Structuring Phase
Structuring Phase
Structuring Phase
Structuring Phase
Structuring Phase
Structuring Phase
Upcoming SlideShare
Loading in …5
×

Structuring Phase

1,624 views

Published on

This is a slide show that discusses the PACT analysis and User Research leading to the generation of requirements.

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,624
On SlideShare
0
From Embeds
0
Number of Embeds
52
Actions
Shares
0
Downloads
17
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Structuring Phase

  1. 1. Structuring Phase ysdn3006
  2. 2. PACT analysis • used to scope a problem in a particular domain (sphere of activity) Requirements activities in People technologies contexts Opportunities
  3. 3. PACT analysis • People have differing characteristics • physical differences (eg. weight and height, senses, disabilities) • psychological (spatial ability, language, attention and memory) = support mental models • usage differences (novice, advanced, homogenous vs. heterogeneous
  4. 4. PACT analysis • Activities need to be considered by the design team • purpose of the activity = important • frequency (eg. everyday or once a year) • cooperation (alone or with others) • complexity (simple, complicated) • safety critical (dangerous, errors) • nature of content (amount of data)
  5. 5. PACT analysis • Contexts are where activities occur • physical context (eg. environment) • social context (eg. privacy ) • organizational context (eg. within companies, organizations)
  6. 6. PACT analysis • Technologies are used to perform functions • input - people enter data, commands (eg. wiki postings) • output - receive data (eg. video on YouTube) • communication - between people and devices (cellphone) • content - form and accuracy of data (eg.YSDN website)
  7. 7. Scoping a problem with PACT • Important to harmonize the PACT elements in a particular domain • Useful to understanding current situation and look for opportunities • This can be done by scoping out the variety of Ps As Cs and Ts • observing and talking to people - user study to generate requirements
  8. 8. Requirements • goal is to bring about something new in what people do or might want to do • are generated by conducting user research • interviews • observations • by analyzing this data, designers get a better sense of what the system will need to do
  9. 9. Start a PACT Analysis • think about the communities in our public spaces • how are the communities defined ? • contexts • activities • technologies • What are some communities we have identified in our public space research?

×