Presentation on

SDLC - MODELS
Presenter

Swapnil Parate

Software Development Life Cycle Model

Model used for describing a software development process. A software development lifecycle model is a representation of the major components of software development work and their interrelationship, put in a framework that can be easily understood and communicated. It specifies the various phases/workflows of the software process, such as the requirements, analysis, design, implementation and post delivery maintenance, and the order in which they are to be carried out.

SDLC Models
Big-Bang model Code-and-Fix model

Waterfall model
V-Model

Big-Bang Model
Final Product

BOOM!! ?
Put in all the resources. Put in all the energy, money. All the effort to write code. Output comes the perfect software productor it doesnt.

Big-Bang Model
Advantages Simple. Disadvantages
Little or no planning, scheduling. No formal development process. Little or no formal testing. If error detected, correction is difficult because the isolation of the cause is complicated.

Code-and-Fix Model

First elementary model. Little idea about product requirements. A project team exists. Little planning, documentation.

Code-and-Fix Model
Advantages
Works well for small projects. Can be used on well known software products. A good introduction to software development. Requires little experience of programming.

Disadvantages Code purely structured. Dangerous for big projects. Testing is not specifically called out. Poor quality product.

Waterfall Model

Waterfall Model
Came up with good software engineering principles to replace ad hoc proprietary mechanisms. Simple, Elegant, Makes Sense and is a Nice Idea. Classical phases: hence Natural: Works. Smooth flow over the classical life cycle phases. As a framework for learning the different techniques used in software development.

Waterfall Model
Advantages
Works well on the right project/spec frozen. Time tested. Discrete steps, no overlap. Testing perspective: can create an accurate plan and schedule. Can be used as a framework for iterative method.

Waterfall Model
Disadvantages
Document Oriented. Risky for new projects. Cant go back from any step. Linear. Least flexible.

Testing protracted. Bugs correction hence expensive.

V-Model

V-Model
V-Model is an enhanced version of the classic waterfall model. Each phase must be completed before the next phase begins. It is a structured approach to testing. Brings high quality into the development of our products. The process steps are bent upwards after the coding phase, to form the typical V shape.

V-Model
Advantages
Simple and easy to use. Each phase has specific deliverables. Works well for small projects where requirements are easily understood. Higher chance of success over the waterfall model due to the development of test plans early on during the life cycle.

Disadvantages
Very rigid, like the waterfall model. Little flexibility and adjusting scope is difficult and expensive. Model doesnt provide a clear path for problems found during testing phases.

Thank You.
Questions please!!!