Life Cycle Models

Life Cycle Models

The software companies follow creative practices for building software as software can be easily modified and changed. Large contracts for software require a formal and structured manner in which code could be written. This process is called life cycle. These models basically specifies a techniques by which the coding for the software is preceded by design and analysis

Water fall model

The first life cycle model It depicts six stages arranged in steps or waterfall. The model is called life cycle as it refers to entire life of the software from creation to retirement and replacing it with a new one. Divided in to two stages upper and lower stages.

Water fall model

Project Requirements-feasibility analysis -Road map of the project -Output of this is a document which clearly outlines the budget ,scope the personnel involved and the key success indicators and milestones. Analysis Design Coding and testing Implementation and Integration Maintenance

Features of a Waterfall Model

A waterfall model is easy to follow. It can be implemented for any size project. Every stage has to be done separately at the right time so you cannot jump stages. Documentation is produced at every stage of a waterfall model allowing people to understand what has been done. Testing is done at every stage.

Advantages of a Waterfall Model

A waterfall model helps find problems earlier on which can cost a business less than if it was found later on. Requirements will be set and these wouldn't be changed. As everything is documented a new team member can easily understand what's to be done. Implementers have to follow the design accurately

Disadvantages of a Waterfall Model

If requirements may change the Waterfall model may not work. Many believe it is impossible to make one stage of the projects life cycle perfect. Difficult to estimate time and cost for each stage of the development process. Constant testing of the design is needed.

Alternatives to Waterfall model

Rapid Prototyping Spiral Model Agile methods-Extreme Programming -Scrum

Spiral Model
Since end-user requirements are hard to obtain/define, it is natural to develop software in an experimental way: e.g. 1. Build some software 2. See if it meets customer requirements 3. If no goto 1 else stop.

This loop approach gives rise to structured iterative lifecycle models. In 1988 Boehm developed the spiral model as an iterative model which includes risk analysis and risk management.

Key idea: on each iteration identify and solve the sub-problems with the highest risk.

Cumulative cost
Determine objectives, alternatives & constraints

Evaluate alternatives, Identify & resolve risks

Prototypes Start P1 P2 Review & RequirementsConcept commitment plan Of Operation Development plan Requirements validation Integration & Test plan
Plan next phase

P3

Operational Prototype

Design, Detailed design Validation & Verification

Coding Unit & Integration Testing
Develop & verify next-level product

End

Acceptance Testing

Each cycle follows a waterfall model by: 1. Determining objectives 2. Specifying constraints 3. Generating alternatives 4. Identifying risks 5. Resolving risks 6. Developing next-level product 7. Planning next cycle

Advantages
1. Realism: the model accurately reflects the iterative nature of software development on projects with unclear requirements 2. Flexible: incoporates the advantages of the waterfal and rapid prototyping methods 3. Comprehensive model decreases risk 4. Good project visibility.

Disadvantages
Needs technical expertise in risk analysis to really work Model is poorly understood by non-technical management, hence not so widely used Complicated model, needs competent professional management. High administrative overhead.

6.7. Rapid Prototyping

Key idea: Customers are non-technical and usually dont know what they want/can have.
Rapid prototyping emphasises requirements analysis and validation, also called: customer oriented development, evolutionary prototyping

Requirements Capture

Quick Design

Iterate

Build Prototype

Customer Evaluation of Prototype

The Rapid Prototype Workflow

Engineer Final Product

Advantages
1. Reduces risk of incorrect user requirements 2. Good where requirements are changing/uncommitted 3. Regular visible progress aids management 4. Supports early product marketing

Disadvantages
1. An unstable/badly implemented prototype often becomes the final product. 2. Requires extensive customer collaboration
Costs customers money Needs committed customers Difficult to finish if customer withdraws May be too customer specific, no broad market

Disadvantages
3. Difficult to know how long project will last 4. Easy to fall back into code-and-fix without proper requirements analysis, design, customer evaluation and feedback.

Agile Principles
Continuous delivery of software Continuous collaboration with customer Continuous update according to changes Value participants and their interaction Simplicity in code, satisfy the specification

Extreme Programming
Stories Short Releases Testing Iteration Refactoring Pair Programming Work Environment Metaphors

Scrum
Define number of roles for the project members -Product Owner -Scrum master -Team member -Product backlog and sprint backlog -Burn Down Chart