Life Cycle Management

Our life revolves around complex systems. Herein, a system can be any system such as software systems, admission systems, reservation systems, banking systems or much more. It is not easy to build systems without studying them completely before hand. A deep study about the requirements, design, implementation and maintenance of the system is required before it is actually implemented. The unorganized implementation of a system can result in a system failure which burns up valuable time and money.

Ready made life cycle models can successfully assist you in implementing the various types of systems. They are highly programmable models which can depict all the stages in the life cycle of a system. Lifecycle models basically describe the interrelationships between software development phases specifically.

These are based on careful studies which are based on the experiences and requirements of the particular system. The models cover stages in a generalized way so that the ideas can be expanded for any type of system.

The various models are listed below:

* Spiral model

* Waterfall model

* Throw away Prototyping model

* Evolutionary Prototyping model

* Incremental model (Iterative model)

* Reusable Software model

* Automated Software Synthesis model.

Let's understand each of these models in brief:

A brief synopsis on each model:

The Spiral Model: The model is based on a risk management strategy. This means evaluating the system as per the risk factors and search for measures to eradicate the inherent risks of the system. For this, a prototype of the model which employs low risk strategies is generated. The aim is to incorporate software quality objectives into the product. The model is also based on early detection and prevention measures. Generally this kind of model is most suitable for software and hardware systems.

The Waterfall Model: This model is the first publicly documented life cycle model. This model is most suited for projects that involve low risk factors for user interface and performance requirements but high contain high risk in the area of budget and schedule control.

The Throwaway Prototyping Model: This model is most useful in cases where the requirements and user needs are not clearly defined. A quick model based on certain parameters is implemented during the requirement phase. Partial implementation allows for iterative refinement and further enhancement.

The Evolutionary Prototyping Model: This model is most suitable in areas that involve low risks in the field of budgeting, scheduling, predictability and control but contains high risk factors in the field of user interface design.

The Incremental or Iterative Model: This model constructs almost every phase of the system development according to partial requirements. Each phase then increments with functionality development. This model is suitable when the systems require immediate implementation.

The Automated Software Synthesis Model: This model is based on active research. Under this model, all the requirements of the system are formally created and maintained using specific tools. The model relies on processes that convert requirements into practical operational tools.

Life cycle models are highly adaptable and their implementation may vary from organization to organization. Models are chosen for organizational best fit. They can also be synthesized and adapted according to end user needs and requirements.

Contact Us | Privacy Policy |