A Web Paper by Douglas A. Hughey
Written for IS 6840, taught by Dr. Vicki Sauter.
Introduction
Figure 1:
Systems Analysis and Design can be a complex process, involving a wide variety of resources and planning. Depending on the project, it can take years from the initial determination to begin the project to final roll-out and maintenance. During this time, a lot of factors can change, including the customer’s business needs, and the marketplace. In an effort to help compartmentalize and overcome the challenges, a standardized Systems Development Life Cycle (SDLC) has been devised for use by Systems Analysts. However, there is no one standard approach to making use of the SDLC to successfully bring a project from the initial planning stages to the final execution and maintenance stages. In fact, a variety of methodologies exist when it comes to approaching the best way to analyze and design a system.
In this paper, I will be defining and discussing some of the most popular Systems Analysis and Design methodologies. Furthermore, I will draw comparisons between the traditional Waterfall approach, and the newer agile methodologies. As there are a variety of agile methodologies currently in use, I will limit my discussion to Extreme Programming, Scrum, and Test-Driven Development. I will also provide evidence-based conclusions as to which methods are most useful in different situations.