Which Systems Analysts Are More Likely to Prototype?

Abstract

Prototyping has become a valuable tool for systems development because it accelerates the development process, helps define system requirements, and encourages end-user involvement. Because prototyping is a valuable tool, a study of the training environment and characteristics of systems analysts more likely to use the tool can help IS managers formulate policies to encourage its use. This article examines a nationwide survey of 104 systems analysts in education, government, and for-profit organizations and is designed to elicit information concerning the personal characteristics and training backgrounds of systems developers who choose the prototyping technique. The study also analyzes organizational environments in which prototyping is used.

Additional information

Notes on contributors

Marion G. Sobol

Marion G. Sobol is a professor and chairman of the MIS department in the Edwin L. Cox School of Business at Southern Methodist University. She received her PhD from the University of Michigan. Her research interests are the economics of computerization, human resource economics, systems implementation and design, and computer literacy

Albert Kagan

Albert Kagan is an assistant professor of information systems in the College of Business Administration at North Dakota State University. He received his PhD degree from Iowa State University. His research interests are in systems implementation, data base design for business, and the economics of MIS.