Frequent Shopper Program, Part I and ll
University of Phoenix
Frequent Shopper Program, Part I
A development methodology is the framework that a developer or team uses to structure, plan, and control the process of developing a system or application. There is a wide variety of methodologies to choose from, each with its own strengths and weaknesses. Two of the more common and most used methodologies are the Waterfall method, and the agile method. This paper will focus on these two methods giving detailed descriptions, as well as advantages and disadvantages. Testing for each method will also be covered.
The Waterfall Method
The Waterfall Method of development is a linear-sequential life cycle model. This method is very simple to use and understand. In this model, each phase needs to be completed before the next phase can begin, phases cannot overlap, and once you finish a phase you cannot go back. A good example of this process is a literal waterfall flowing down the side of a mountain. "Once the water begins to flow over the mountain, it will hit each rock and continue down. The water can never go in the opposite direction." (Rouse, 2007) This is displayed in the following chart:
The waterfall method allows for departmentalization and easy managerial control. "A schedule can be set with deadlines for each stage of development and a product can proceed through the development process like a car in a carwash, and theoretically, be delivered on time". (Rouse, 2007) Development starts with the first step, usually known as analysis or system planning, and will continue through each step until the application is ready to deploy. If a change in a previous step is desired, the entire project would have to be started from scratch.
This being said, the Waterfall method is best used if the project is fixed-scope and price, and rapid changes in the scope are not expected for any reason....