Eliciting requirements from users and other stakeholders is of central importance to information systems development. Despite this importance, surprisingly little research has measured the effectiveness of various requirements elicitation techniques. The present research first discusses theory relevant to information requirements determination in general and elicitation in particular.We then develop a model of the requirements elicitation process. This model and its underlying theory were then used to construct a new requirements elicitation prompting technique. To provide a context for testing the relative effectiveness of the new technique, two other questioning methodologies were also operationalized as prompting techniques: (1) the interrogatories technique, which involves asking "who," "what," "when," "where," "how," and "why"; questions; and (2) a semantic questioning scheme, which involves asking questions based on a theoretical model of knowledge structures. To measure the usefulness of the prompting techniques in eliciting requirements, a set of generic requirements categories was adapted from previous research to capture requirements evoked by users. The effectiveness of the three methods in eliciting requirements for a software application was then tested in an experiment with users. Results showed that the new prompting technique elicited a greater quantity of requirements from users than did the other two techniques. Implications of the findings for research and systems analysis practice are discussed.

Requirements determination is a critical stage in systems development. Despite its importance, however, few studies have provided empirical tests of requirements determination issues (Vessey and Conger, 1994). The present study tested several questioning approaches in structured interviews. an Interrogatories technique (Couger, 1996), a Semantic questioning technique (Lauer, 1994), and a Task Characteristics technique developed as pan of the current research. Experimental results showed that the Task Characteristics technique elicited a higher quantity of requirements and more detailed requirements from subjects in an application development task than did the other two approaches. Further, the three approaches elicited qualitatively similar requirements, indicating that the use of only the Task Characteristics tool is likely best for systems analysis practice.