•  
  •  
 

Journal of Undergraduate Research

Keywords

scenario elicitation, system requirements, computer-based application

College

Marriott School of Management

Department

Information Systems

Abstract

In system development, no other phase is as fraught with difficulties as determining what exactly the system “should do” for a proposed project. These difficulties arise through a divergence in how the end user envisions the system should operate and how the analyst or developer perceives the user would like the system to operate. The search for a common language that both analyst and end user could use to effectively communicate what a system “should do”, or the system requirements, gave rise to the use of scenarios. Scenarios are textual narratives of how the system should operate in a given situation. The analyst then uses the scenarios to define the requirements of the system under development. Although both analysts and users can communicate system requirements relatively easily using scenarios, the effectiveness of their communication is directly dependent upon the quality of the scenarios in question (3).

Share

COinS