Abstract:There is a myriad of system development methodologies, techniques, and tools that have been developed ever since businesses started using computers for information processing. However, there is no real consensus on the aptness or applicability of these methods. There are proponents and critics of each method, and different organizations use different methods. This article identifies many of the system development methods in use today. It, then, empirically assesses these methods on a comprehensive set of attributes. It also makes a contingency analysis of the applicability of the methods based on system life cycle stage, system type, and problem structure. These results should serve as a valuable set of inputs in method selection for system development. Keywords: System development life cycle; System development methodologies; System development techniques; System development method use; System development method evaluation; System type; Problem structure Article: Introduction 1 Many methodologies, techniques and tools (termed "methods" here) exist and continue to be developed [e.g., see 1,3,9,10,14] for accomplishing various tasks in the system life cycle (SLC). There are strong proponents and critics of each method; however, there is limited research concerning their effectiveness. Studies usually compare a few methods (often two or three) on a limited set of attributes [10,11,13,18,23,24].Designers, analysts, programmers, end users, and MIS managers are confronted with a wide array of methods and are poorly informed on their utility and desirability. Therefore, a comprehensive approach is essential to understand the attributes and appropriateness of these methods. Elements of such an approach were outlined in the Data Base Directions workshop of 1985 [5]. One comprehensive approach that was pursued was the STAR methodology [16], in the context of the ADA environment for the Department of Defense. Another approach by Doke and Myers [6] focused on the overall productivity aspects of the methods. An important contribution is by Colter [1], where he subjectively evaluated characteristics of various tools and techniques. With respect to DSS methodologies, Ginzberg [7] subjectively evaluated hem and presented a contingency model for their use.The literature does not present a comprehensive evaluation based on field experience. It is important to know how these methods fare with their users (i.e., IS professionals). Here, we examine a comprehensive set of techniques and methodologies from a field perspective. First, in order to clarify the distinction between the terms, we adopt the following definitions from [5]:Methodology: is an organized and systematic approach for handling the system life cycle or its parts. It will specify the individual tasks and their sequence.Technique:is a means of accomplishing a task in the system life cycle (SLC). Sometimes, it may become synonymous with the task.