Developing software is far from an exact science and without a structured system to guide the process a project is likely to fail. Defining and adhering to a Software Development Life Cycle (SDLC) early in the project will help to guide the development of a new information system. In addition to having the structure for the development team to work within a defined and agree upon SDLC will help to set the proper expectations for deliverables with the stakeholders and customer(s). Smith Consulting has been given the task of creating a Frequent Shopper program for Kudler Fine Foods. As a result Smith Consulting needs to decide on which SDLC will work best for this project. In addition to selecting a SDLC to use Smith Consulting will need to determine how testing will be conducted. The purpose of this paper is to compare and contrast Waterfall and Scrum SDLC's, including how testing will be performed for each, such that Smith Consulting will be able to make an informed decision on which methodology to use when creating the Frequent Shopper Program for Kudler Fine Foods.
The term SDLC has been tied to a certain type of development style as Waterfall. Waterfall SDLC is the concept where each phase of the development process is completed before the next begins. There has been much debate on who was the originator of the Waterfall SDLC process, most reference Dr. Winston Royce. Dr. Royce described a development methodology where each phase is completed before the next begins but never used the term Waterfall in its description. In his description of what is known now as Waterfall, Dr. Royce did not recommend this as a viable SDLC (Font, 2010). There are five phases that need to be completed in sequence during the Waterfall process which are: * Gather Requirements
* Design the software
* Implement the design
* Verify the implementation
The diagram shown in Figure 1 illustrates the phased development cycle that Waterfall...
Please join StudyMode to read the full document