Traditional approaches, also known as “engineering” approaches, are defined at the very beginning of the software sciences. These are disciplined approaches where the stages of design and builds are predictable. Detailed stages of analysis and design precede the stage of building the software. These methodologies are well documented and thus are quite complex to apply. One of the main disadvantages is that these traditional methodologies are very bureaucratic. In practice, this highly detailed methodology leads to a high level of complexity. Often times, the work of managing the methodology are more than that of actually producing the product. Phases of the traditional approach are: requirements phase, architecture, design, code, test, and release
