Trusted by 2+ million users, 1000+ happy students everyday
Showing pages 1 to 4 of 12 pages
Running head: SYSTEM ANALYSIS AND DESIGNSystem Analysis and Design: Examining the Case for the Waterfall Life CycleName of the StudentName of the UniversityAuthor Note
1 SYSTEM ANALYSIS AND DESIGNTable of Contents1. Introduction......................................................................................................................22. Waterfall Life cycle Methodology...................................................................................24. The importance of Waterfall Life cycle methodology....................................................55. Does it play a useful role in modern system development?............................................56. Role of Waterfall Methodology in modern system development: Stages.......................67. Advantages and Disadvantages.......................................................................................77. Conclusion.......................................................................................................................8References..........................................................................................................................10
2 SYSTEM ANALYSIS AND DESIGN1. Introduction Waterfall methodology was one of the first models to be introduced and it is referred toas linear or sequential model for project management. Since this is one of the first methodologyto be introduced, it is less complex in comparison with the modern project managementmethodologies that are in use. This methodology is conveniently used and applied in the small ormedium sized projects, as the phases and the concepts are simple to implement. The onlyrequirement of this methodology is that, the project phases are completed in a sequential manner,which indicates that a project phase cannot be implemented before the completion of theprevious phase (Balaji and Murugaiyan, 2012.). This ensures that the project is implemented in aplanned approach. Completion of each phase demands a feedback or review that formulateswhether the project is on a right track or not. However, in waterfall model, the testing phasestarts only after the development is completed, which indicates that this methodology does notallow the change in scope of the project once the project is initiated (Mahalakshmi andSundararajan 2013). The article elaborates the basic concept of waterfall methodology and itsimportance in the modern system development. 2. Waterfall Life cycle MethodologyWaterfall model is a sequential model of software development life cycle. In waterfallmethodology, the entire project is divided into a number of phases, which is further subdividedinto a series of planned tasks. Completion of one phase triggers the start of the next phase andhence it is an example of sequential model. This model is a pioneer of the software developmentlife cycle (Model 2015). Waterfall model is one of the oldest project managementmethodologies, which used to be widely applied in the software industry when proposed. One of
3 SYSTEM ANALYSIS AND DESIGNthe major consideration in the waterfall methodology is that, output of a single phase determinesthe start of the next phase and therefore, if one phase is delayed, it leads to the delay in the entireproject. This is one of the disadvantages of using waterfall methodology and therefore, a projectwhich is considerably larger in size does not follows this life cycle. However, since the output ofone phase determines the beginning of next phase, every phase of the waterfall model isprecisely well-defined. The model is named so as the phases fall from the higher level to a lowerlevel like a waterfall. The pictorial representation of the waterfall model are illustrated below- Figure 1: Representing the different phases of Waterfall Model(Source: Model 2015)In a more advanced waterfall model, there is an option of providing feedback andreviewing the phase after a phase is completed. Such waterfall model is termed as iterativewaterfall model. This model allows the change in scope of the project while projectimplementation if required. That is, it does not attempt to start will a full specifications of therequirements. This waterfall model is more commonly used nowadays as t enables to create a
Found this document preview useful?
You are reading a preview Upload your documents to download or Become a Desklib member to get accesss