Civil Engineering Reference
In-Depth Information
7.3.2.2.3 Process Outcomes
This structured observation and probing process is the basis for collecting the necessary data to build a
solid and comprehensive understanding of the user, their needs, and their work. In order to present this
picture of work in a comprehensible and concise manner (Stage 3), the contextual design process incor-
porates the process of developing graphical work models including the flow, sequence, artifact, culture,
and physical work models (Beyer and Holtzblatt, 1998). Through a well-prescribed process of consolidat-
ing data and models, the contextual design team then “walks the data” to create a team focus for the
process of group brainstorming a series of visions, or large-scale, rough representations of the work
system components, structure, and work tasks. These visions are then used to direct work and organiz-
ational re-engineering, use scenarios, storyboards, and technical
hardware requirements.
From these consolidated work models, the vision diagrams, storyboards, and the like, a unique con-
textual design work system model is developed — the user environment diagram (UED; Beyer and
Holtzblatt, 1998). The UED represents the key concepts for the work system model and reveals how a
system can support work in terms of the fundamental activities of work tasks, the links and interdepen-
dency between these tasks and activities, and the purposes or goals that direct the work tasks. Finally, by
using the structural UED and sequential storyboards and some nifty reverse engineering, requirements
and specifications of the system can be developed from examining the coherent tasks and activities that
need to be supported, the types of data and artifacts needed to support the tasks, and the sequence and
interdependence of the task activities.
/
7.3.2.2.4 Summary
Arguably, the contextual design process will not always be the best or most appropriate method of RE and
UCD. For example, contextual design is particularly well suited for software-focused, computer-based
systems, which are fairly radical upgrades to the previous legacy systems that exist within the organiz-
ation. However, it is a good example of a work system design process that stresses the need to incorporate
the user into the design process and ensure that the needs and work processes of the user will be appro-
priately addressed in design solutions.
7.3.2.3 Stage 1: Defining the Needs
The first step in any endeavor of designing and developing a new system to be used to support work is to
understand the problem domain that the system is being designed and developing for. We refer to this
stage of the UCD process as defining the work system. Activities involved in this stage include identifi-
cation of the stakeholders, context of use analysis, and competitor analysis, all of which help to both
define the work system and help direct the choice and planning of RE techniques (i.e., activities of
Stages 2 and 3). Many of these activities are often associated with the preliminary planning and scope,
although a slight distinction can be made.
7.3.2.3.1 Project Planning
As practitioners can attest to, the first step in the system development lifecycle is planning and scoping
the project. Project planning and scope refer to those activities involved with determining the high-level
business goals and requirements, establishing the scope and boundaries of the project, determining the
UCD methods to use, researching the market and domain for the future system, and determining logis-
tics (i.e., resources, costs, timeline). Building executive buy-in and agreement on the overall business
goals and requirements is also necessary. While these activities are particularly involved for UCD prac-
titioners working in the industry, these details are often glazed over in academic and technical publi-
cations assuming that these activities have already been completed before starting up the RE process.
In keeping with tradition, no detailed discussion of these activities, and their associated issues, will be
provided here. It is necessary to acknowledge both the inclusion of these activities in the UCD process
and the importance of these activities — especially for practitioners working in the industry. However,
readers can refer to texts by Vredenburg et al. (2002) or Rouse (1991) or Mayhew (1999) for more
details on these preparatory activities and high-level issues related to the usability engineering or
system development lifecycles. It is important to note, however, that some of these activities help to
Search WWH ::
Custom Search