Civil Engineering Reference
In-Depth Information
While this division of approaches is not absolute, it does distinguish that there are clear differences
between these two types of approaches. For example, elicitation techniques are generally (arguably)
quick preliminary techniques, which involve direct interaction with the users to yield rough data that
often requires considerable interpretation, refinement, and validation. On the other hand, analysis
and modeling techniques are often more extensive follow-up efforts that are used to represent this
rough data in a manner that can be more easily communicated and interpreted and applied. For these
reasons, the following discussion will consider elicitation techniques (Stage 2: Examining the work
system) and analysis and modeling techniques (Stage 3: Representing the work system and its needs)
as independent stages in the RE process as shown in Figure 7.3.
Before talking about these approaches and techniques in greater detail, Table 7.3 outlines many of the
popular techniques of requirements elicitation and analysis
modeling commonly employed by UCD
professionals. For greater detail on these (and other) methods and techniques, readers should
examine some of the literature (e.g., Beyer and Holtzblatt, 1998; Maguire, 2001; Sommerville and
Sawyer, 1997) and Websites (http:
/
www.usabilitynet.org; http:
usability.jameshom.com
index.htm)
//
//
/
that provide detailed insight into different UCD techniques.
7.3.2.1.5 Selection of UCD Methods and Techniques
It is well-known that the UCD approach taken and the methods and tools chosen heavily depend on the
constraints of a given project-time, money, staffing, and accessibility to users. Readers will find that even
expert practitioners adopt their own unique combination of the techniques, as suits the needs and work
within the constraints of a project. In a recent article, Marcus (2005) summarized the factors that mostly
affect collection of UCD techniques used. These factors include: (1) availability of testing labs and equip-
ment; (2) availability of usability professionals; (3) availability of users; (4) budget; and (5) calendar
schedule.
A survey of UCD professionals showed that the cost-benefit tradeoff was instrumental in the consider-
ation of which UCD method, if any would be implemented in a given design process (Mao et al., 2001).
TABLE 7.3 Common Requirements Elicitation and Requirements Analysis and Modeling Techniques
Requirements Elicitation
Requirements Analysis and Modeling
RE stage
Stage 2: Examining the work system
Stage 3: Representing the work system and its needs
Approach summary
Gathering or capturing system requirements through
direct observation or interaction with stakeholders
or end-users
Defining system requirements through the development of
models based on the data collected using elicitation
techniques and documentation
Characteristics
Ethnographic in nature
Analytical in nature
Direct interaction with users
Direct involvement with data
Results in rough data
Refined representations of users, needs and tasks
Relatively quick and simple
Time and resource intensive
Requires more interpretation
Requires less interpretation
Preliminary activities
Common techniques
Surveys and questionnaires
Use cases
/
scenarios
Interviews
Visioning
Observation
/
ethnography
Personas
/
user profiles
Contextual inquiry
/
user interview
Error and critical incident analysis
Focus groups and brainstorming
Affinity diagramming
Think aloud
Work modeling
Laddering and card sorting
Decision
action diagrams
/
Documentation and product review
Cognitive work
task analysis
/
Search WWH ::
Custom Search