Difference between revisions of "Human Factors to Requirements"

From Earth Science Information Partners (ESIP)
(Created page with "{| width="800" border="1" cellpadding="1" cellspacing="1" |- ! scope="col" | Requirement ! scope="col" | Barrier ! scope="col" | Enticement ! scope="col" | Note or Example |- | S...")
 
Line 51: Line 51:
 
|  
 
|  
 
|-
 
|-
|  
+
| Use-time design
|  
+
| Rigidity (prescribed functionality)
|  
+
| See work by G Fischer, e.g.
|  
+
| (Perhaps?) Evernote & its kin, Spreadsheets, Hypercard...
 
|}
 
|}

Revision as of 09:09, April 16, 2012

Requirement Barrier Enticement Note or Example
Support Private workspace Fear of being scooped; reluctance to make public incomplete results
Easy-as-pie sharing Difficulty in using tool
Support Private groups Fear of being scooped; reluctance to make public incomplete results
Support team collaboration
"My Contributions" Ownership Bias
Follow a contributor Learn from experts; Social proof
"Killer app" Status Quo bias Any ideas for the killer app that would serve to entice the users to modify how they work now?
"Official" contributions
Authority e.g., YouTube "Official" videos
View contributors / sort by number of contributions Reputation
Prepopulation with content Positive Mimicry; Network Effect
Use-time design Rigidity (prescribed functionality) See work by G Fischer, e.g. (Perhaps?) Evernote & its kin, Spreadsheets, Hypercard...