Lifecycle Models and Project Planning

Lifecycle Models and Project Planning

Business & nbsp; (general)

Life cycle Models and Project Planning

Paper I.D.: 46936

Lifecycle Models and Project Planning

Three Lifecycle Models

The purpose of this work is to describe three life cycle models and to explain the advantages and disadvantages of each model. Further this work will explain which phase or phases that Systems Integration is most frequently used and why. Three techniques or processes will be described that assist the manager in developing and directing the project. Finally, explained will be the reason that a manager plans and when this project planning occurs.

There are several project "Lifecycle" models that are utilized in developing models in project planning. The 'classical' or 'traditional' model is named the "Pure Waterfall" model. Other models, which will be reviewed in this work, are the "Spiral" model and the "Staged Delivery" model.

"Pure Waterfall Lifecycle Model"

The 'classical' or 'Pure Waterfall' model consists of discontinuous phases which are the 1) Concept 2) Requirements 3) Architectural design 4) Detailed design 5) Coding and development; and 6) Testing and implementation. The strengths in this model are that the planning overhead is minimized because it can be done in advance and secondly the development structure minimizes the effort wasted therefore it is workable for staff that is either weak or inexperienced. The weaknesses in the "Pure Waterfall" lifecycle model is that it tends to be inflexible, the only deliverable produced is in the final phase, and addressing mistakes after the fact proves to be very difficult. This model is best utilized when the product is clarified as to the requirements and when using well-known tools of a technical nature. If the desired development is to be in a rapid-paced environment modification of this model will likely prove to be more effective in the process.

"Spiral Lifecycle Model"

The "Spiral" model is used in a project that requires 'risk-reduction' in the within the framework of the project and it generally used in software development that requires breaking the overall project down into 'mini-projects' in order to individually and specifically address each risk After having addressed all risks the termination of the "Spiral" model is the same as termination of the "Pure Waterfall" model. Six steps are involved in the 'Spiral" model which are 1) Determination of objectives 2) Alternatives and restraints3) Evaluation of alternatives 4) Development of the deliverables and verification of their correctness 5) Plan the next iteration 6) Commit an approach for the next iteration. The strengths of this model are that early iterations of the projects are the least costly and enables the highest risk to be addressed at the least overall cost ensuring upon increase of costs a decrease in risks and secondly that each iteration of the spiral may be custom made to satisfy the needs within the project. Weaknesses in this model are the ambiguous natured milestones, activities performed in parallel are subject to miscommunications and mistaken assumptions and unplanned interdependence is a factor that can create problems.

The "Staged-Delivery" Lifecycle Model