User type and problem type: A classification of development environments and CASE tools
If organizations do not research CASE tool usage, the organization may chose the `incorrect' CASE tool. An `incorrect' CASE is a tool that does not meet the organizational's functional needs. Azani (1990), Martin (1990) and Snell (1993) provides examples of organizations that have chosen the `incorrect' CASE tool Martin (1990) explained that organizations should divide CASE tools into categories that meet functional needs, and choose a CASE tool that meets those needs. An `incorrect' CASE tool can be detrimental for an organization not only in monetary terms, but also we respect to worker productivity, changes in organizational culture, changes in standardization, and time in training. Given that choosing a CASE tool is a difficult and multi-faceted decision, the purpose of this paper is to describe how to choose the `correct' CASE tool. This paper classifies CASE tools and development environments, and matches each environment with an appropriate CASE tool. Based upon the framework, an organization can determine the `correct' CASE tool classification. Once the CASE tool classification has been identified, vendors must be evaluated and individual CASE tools must be considered.
Information Technology and Cybersecurity
Barrier, Tonya B.; Kim, Chung S.; and Kaula, Rajeev, "User type and problem type: A classification of development environments and CASE tools" (1996). Articles by College of Business Faculty. 896.
Proceedings - Annual Meeting of the Decision Sciences Institute