Characteristics of the Project Life Cycle

More specifically, what is a project? It’s a temporary endeavor undertaken to create a unique product, service or result. A project is temporary in that it has a defined beginning and end in time, and therefore defined scope and resources.

A project is an endeavor to accomplish a specific objective through a unique set of interrelated tasks and the effective utilization of resources. A project has a well-defined objective—an expected result or product. The objective of a project is usually defined in terms of scope, schedule, and cost.

• The Initiation Phase: Starting of the project.
• The Planning Phase: Organizing and Preparing.
• The Execution Phase: Carrying out the project.
• The Termination Phase: Closing the project.

The seven stages of Waterfall include: Conception: This stage starts with an idea and a baseline assessment of the project, its cost analysis, and its benefits. Initiation: Once the idea is created, the project team is hired and objectives, scope, purpose, and deliverables are defined.

The five-stage waterfall model, which is based on the requirements of Winston W. Royce, divides development processes into the following project phases: analysis, design, implementation, testing, and operation.

In this model phases are processed and completed one at a time. Phases do not overlap. Waterfall model works well for smaller projects where requirements are clearly defined and very well understood.

Waterfall model is an example of a Sequential model. In this model, the software development activity is divided into different phases and each phase consists of a series of tasks and has different objectives. In waterfall, development of one phase starts only when the previous phase is complete.

There are no ambiguous requirements (no confusion). It is good to use this model when the technology is well understood. The project is short and cast is low. Risk is zero or minimum.

As an internal process, the Waterfall methodology focuses very little on the end user or client involved with a project. Its main purpose has always been to help internal teams move more efficiently through the phases of a project, which can work well for the software world.

Waterfall Model – Disadvantages High amounts of risk and uncertainty. Not a good model for complex and object-oriented projects. Poor model for long and ongoing projects. Not suitable for the projects where requirements are at a moderate to high risk of changing.

Some drawbacks to the waterfall approach are the lack of flexibility and room for error. The project is mapped out detail by detail before the engagement even begins, leaving no room for error.

The pros and cons of Waterfall Development

• Pro: Everyone gets up to speed quickly.
• Pro: Timescales are kept.
• Pro: No financial surprises.
• Pro: Testing is made easy.
• Pro: The outcome is crystal clear.
• Pro: Deal with issues in the design.
• Pro: What you plan is what you get.
• Con: Needs can be difficult to define.