So the method most associated with traditional software development would be the waterfall sequence and it’s been this ways since the induction of software some fifty years ago. During the 1960s, “code and fix” was the method employed by software developers. As Christophe Thibuat describes, “one year of slamming code, one year of debugging”. Due to this difficult nature of “code and fix” approach, Winston Royce in 1970 proposed the waterfall methodology. The waterfall approach emphasizes a structured progression between defined phases. Each phase consists on a definite set of activities and deliverables that must be accomplished before the following phase can begin. The phases are always named differently but the basic idea is that the first phase tries to capture What the system will do, its system and software requirements, the second phase determines How it will be designed. The third stage is where the developers start writing the code, the fourth phase is the Testing of the system and the final phase is focused on Implementation tasks such as training and heavy documentation. However, in engineering practice, the term waterfall is used as a generic name to all sequential software engineering methodology.