Waterfall SDLC Methodology According to a VersionOne survey (2007), nearly 70% of software development organizations are still using

the Waterfall Method/Methodology -- in other words, not only is it the oldest and most well tested methodology -- but you're also in good company if you use it. The Waterfall Method is comprised of a series of very definite phases, each one run intended to be started sequentially only after the last has been completed, with one or more tangible deliverables produced at the end of each phase. Essentially, it starts with a heavy, documented, requirements-planning-and-sign-off's phase that outlines all the requirements for the project, followed by sequential phases of design, coding, test-casing, optional documention, verification (alpha-testing), validation (beta-testing), and finally deploment/release. There are several pros for its insistence on a clear definition of requirements/goals up front (allowing better scheduling and estimating), but also some cons for it (hence the evolution of the Agile methodology). The original 10 step Waterfall Methodology The original SDLC -- the Waterfall Methodology -- is comprised of 10 steps intended to be executed sequentially, but -- depending on the size and complexity of the project -- phases can be combined or even overlap (see 6 Step Waterfall Methodology outlined below). 1. Initiation Phase: An opportunity is spotted, and is proposed in a formal Concept Proposal Document. 2. System Concept Phase: y Deliverables: y System Boundary Document (to define the scope or boundary of the concept), y Cost Benefit Analysis, y Risk Management Plan, y Feasibilty Study. Typically evaluated in three areas: o economical, o operational, o technical. o Note:The feasibility study is sometimes used to present the project to upper management in an attempt to gain funding. Planning Phase: y Used as a reference to keep the project on track and to evaluate the progress of the MIS team. y Deliverables: y A Project Management Plan is developed . y Note: Provides the basis of acquiring the resources needed to achieve a solution. Requirements Analysis Phase: Design Phase: The requirements are analysed in order to design the product's architecture.

Development Phase: The design is converted into reality and then white box tested by the development team. Integration and Test Phase: The product is tested by the development team, Quality Assurance staff, and final users. Implementation/Deployment Phase: The product is rolled out into a production environment. Operation and Maintenance Phase: The system is monitored to ensure it contiinues to meet performance requirements, with periodic In-Process Reviews to suggest ways on improving the system. Disposition Phase: The product is removed from service, with special enphasis on archiving the data, or moving to another system. In smaller shops, the above 10 steps are often combined as follows: Short Form (6 steps) of the Waterfall SDLC As stated above, in smaller shops, or on smaller projects, several of the steps are combined into the following sets (the percentages are only suggested amounts):
     

Initiation/Planning/Concept Phase (5% of the project) Requirements Analysis Phase (10% of the project) Design Phase (15% of the project) Development Phase (40% of the project) Integration and Test Phase (20% of the project) Implementation/Deployment Phase (10% of the project)

Note that the above numbers vary from shop to shop, although, according to this source, bestof-breed large shops have figures closer to the following: