Authors: Scott Cox, Susan J. Harrington
Tags: 2005
While much has been written and taught about how
systems analysts should approach a new development
project during iterative or agile modeling, little is known
about how successful analysts think. Browne and Rogich
(2001) proposed generic information requirements
categories that may characterize the breadth and depth of
information requirements that analysts elicit as they
proceed through analysis and design. However, it is not
known whether analysts actually think in terms of these
categories, or whether analysts examine system goals (the
goal-level category) in depth prior to examining the breadth
of information requirements overall (the process-, task- and
information-level categories). A goal-level view may
define the scope and objectives of the system, whereas the
breadth-first overview may enable the analyst to understand
and deal with architectural and other project risks. This
research will use protocol analysis to understand the
thinking of successful analysts in order to better understand
effective analysis techniques during the inception phase of
an iterative development project.
Cite as:
Cox S., Harrington S.J. (2005). “Information Requirements Elicitation: Determination of Priorities During the Inception Phase of Iterative Development,” in AIS SIGSAND 2005, Cincinnati, OHIO, United States, April 23-24, 2005.
