As per Traditional systems development methodology, also known as Waterfall Model, derives its name due to the cascading effect from one phase to the other, each phase has well defined starting and ending point, with identifiable deliveries to the next phase. It’s shown in picture attached to the blog (Figure 10.1)
The model consist of six distinct stages, namely-Requirements analysis phase, Specification phase, System and Software Design phase, Implementation and Testing phase, Integration and System Testing phase, and Maintenance. Often considered the classic approach to the systems development life cycle, the waterfall model describes a development method that is rigid and linear. Waterfall development has distinct goals for each phase of development where each phase is completed for the next one is started and there is no turning back.
The perceived advantages of the waterfall process are that it allows for departmentalization and managerial control. A schedule is typically set with deadlines for each stage of development and a product can proceed through the development process. In theory, this process leads to the project being delivered on time because each phase has been planned in detail.In practice, waterfall development often falls short of expectations as it does not embrace the inevitable changes and revisions that become necessary with most projects. Once an application is in the testing stage, it is very difficult to go back and change something that was not thought of in the concept stage. Agile software development is a conceptual framework for undertaking software engineering projects, is based on a collection of principles, such as the importance of assuming simplicity when you are modelling and embracing change as you are working because requirements will change over time. Most agile methods attempt to minimize risk by developing software in short time boxes, called iterations, which typically last one to four weeks. Each of iteration is like a miniature software project of its own, and includes all the tasks necessary to release the mini-increment of new functionality: planning, requirements analysis, design, coding, testing, and documentation. While iteration may not add enough functionality to warrant releasing the product, an agile software project intends to be capable of releasing new software at the end of each of iterations. At the end of each of iterations, the team re-evaluates project priorities. Agile methods emphasize realtime communication, preferably face-to-face, over written documents. and also emphasize working software as the primary measure of progress. Combined with the preference for face-to-face communication, agile methods produce very little written documentation relative to other methods.
