The Waterfall model was one of the very first of the development methodologies to be introduced. It is the methodology of choice when the customer wants a fixed price and timeline and prefers not to use Agile. With the Waterfall approach the project is divided into a number of sequential phases and each phase is completed fully before the following phase can begin. This methodology is most commonly used for the larger projects where the requirements are fully understood, documented, and signed-off. A review takes place at the end of each phase, to determine if the project is on track.  



  • Identifies high level business & technical requirements.
  • Allows us to understand the effort required for next phase.
  • Identifies the required skill sets for the project.
  • Submits proposal for the Business Requirements Gathering (BRG) exercise.

Business Requirements Gathering (BRG)

  • Series of meetings, workshops and telephone or IM calls
  • Ensures customer’s and Ascent’s expectations are aligned and synced.
  • Unambiguous, complete, realisable, and testable Functional Specification document is compiled.

Planning Architecture & Design

  • Development of planning, system architecture and technical documentation
  • Evaluation of impact on existing systems
  • Design of integration approach

Development & Testing

  • Development of the required functionality meeting all documented requirements.
  • Thorough and adequate series of testing – both manually and automated.

Training & Deployment

  • Training the users of the new systems.
  • Deployment in accordance with deployment plan such as “pilot” vs “big bang”.
  • Write user and technical documentation.

Early care & Support

  • Guiding of customer during the early days of the project
  • Beginning of a support engagement governed by a Service Level Agreement