Cost-Justifying Usability 2005
DOI: 10.1016/b978-012095811-5/50014-6
|View full text |Cite
|
Sign up to set email alerts
|

Ethnography for Software Development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2006
2006
2008
2008

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(7 citation statements)
references
References 9 publications
0
7
0
Order By: Relevance
“…Summative studies such as beta testing can be used to determine a product's readiness for launch, or even to validate a design after it has launched. See Kirah, Fuson, Grudin, and Feldman (2003) and Hughes et al (1995) for examples of how field studies can be adapted to address questions throughout a product's development.…”
Section: How Are Field Methods Used?mentioning
confidence: 99%
See 2 more Smart Citations
“…Summative studies such as beta testing can be used to determine a product's readiness for launch, or even to validate a design after it has launched. See Kirah, Fuson, Grudin, and Feldman (2003) and Hughes et al (1995) for examples of how field studies can be adapted to address questions throughout a product's development.…”
Section: How Are Field Methods Used?mentioning
confidence: 99%
“…Woods (1996) described how he used initial interviews to enable him to be more goal driven in his contextual inquiry and observations. Kirah et al (2003) contrasted their user-driven ethnographic field method approach-used early in the development process-with the more product/feature-specific field studies conducted later in the development process.…”
Section: How Are Field Methods Used?mentioning
confidence: 99%
See 1 more Smart Citation
“…The literature on implementation of computerized clinical systems has consistently reported that neglecting to take user values, needs, and practices into consideration can lead to failed systems, lack of adoption by users, and unanticipated costs [2][3][4].…”
Section: Workflow Analysismentioning
confidence: 99%
“…Practitioners are frustrated by lack of integration across bibliographic databases; ready answers to questions (as opposed to lists of references or links to websites); and access to data tables and figures within publications which are a primary focus for gathering information for forming hypotheses and/or answering questions [6,[18][19][20]; 3. Premature adoption of computerized systems that fail to take into consideration user values, needs, and practices and organization issues may have unintended consequences that are costly and unsafe, such as failed systems, inefficient work, and inability to use data [1,[10][11]; and 4. As a new information system goes through its development and implementation stage, an iterative process must take place to integrate the assumptions made by the designers of the system and the people that use them [4].…”
Section: Workflow Analysismentioning
confidence: 99%