ctivity. Often the planning stage of strategy represents the most critical stage. During the systems requirements phase of product development, success hinges on management’s ability to effectively gather vital information. Such a process results in better decision-making and more effective strategies.
Despite these needs, organizations often fail to resolve problems in an efficient and effective manner. This is particularly true with Information System Development, a relatively new discipline compared to mature disciplines like mathematics, physics or philosophy. One of the biggest failures with respect to information system development is the failure to include all stakeholders in the systems requirements phase of product development. This is particularly true with respect to end users. The JAD method of collaboration helps resolve this problem by representing a “joint venture between the users and the software engineers” in addition to a variety of other stakeholders (Joint, 1995, 1). Information system development based on the JAD method is also enhanced through the use of CASE tools that add efficiency and cut costs during product development phases.
The context for JAD stems from trends in the contemporary business environment that aim at cutting costs, increasing efficiency and productivity, and embracing work teams or groups over individuals. With respect to information system development, the efforts of teams and the significance of end users are underscored via the JAD method. JAD was originally developed by Toby Crawford and Chuck Morris of IBM in the late 1970s. The method was developed to resolve the conflict between end users and information technology professionals, with respect to requirement and design specifications. In Human Performance Engineering, Robert W. Bailey (1996) argues the importance of end users in the development of information systems, “The human is the most complex of all...