SDLC – Software Developement Lifecycle

LIFE CYCLE MODEL

A software life cycle model (also called process model) is a

descriptive and diagrammatic representation of the software life
cycle. A life cycle model represents all the activities required to
make a software product transit through its life cycle phases.

THE NEED FOR A SOFTWARE LIFE CYCLE MODEL

lWithout using of a particular life cycle model the development of a

software product would not be in a systematic and disciplined
manner.
lLead to chaos and project failure.
 Software Life Cycle models

lClassical Waterfall Model

lThe waterfall model is a breakdown of project activities into linear

sequential phases, where each phase depends on the deliverables

of the previous one and corresponds to a specialisation of tasks.

lIterative Waterfall Model

lDuring software development, more than one iteration of the

software development cycle may be in progress at the same time.

lSpiral Model
lSpiral Model is a combination of a waterfall model and iterative

model. Each phase in spiral model begins with a design goal and
ends with the client reviewing the progress.
Phases of Lifecycle
 REQUIREMENTS ANALYSIS AND SPECIFICATION

We can also call this phase as feasibility study phase .

lBefore we start to develop our software, it becomes quite essential for

us to understand and document the exact requirement of the customer.
l Experienced members of the development team carry out this job.

Business Analyst :

The analyst starts requirements gathering and analysis activity by

collecting all information from the customer which could be used to
develop the requirements of the system.
lThen analyzes the collected information to obtain a clear and thorough

understanding of the product tobe developed, with a view to remove all

ambiguities and inconsistencies from the initialcustomer perception of
the problem.
 REQUIREMENTS GATHERING

Team gathers business requirements from customers / client .

To gather requirements they have to meet TELOS .

T - Technical Feasibility --->Technically possible or not

E - Economic Feasibility ---> Budget (can be completed or not)
L - Legal Feasibility ---> As per cyber law can we make it or not
O - Operational Feasibility ---> Client expectation can be met or not
S - Schedule Feasibility ---> Within the time delivery can be made?

Once all the requirement are gathered it will recorded in BDD

( Business design document ) .
 REQUIRMENT ANALYSIS

System Analyst

All business requirements will be converted to technical requirements in

the name of SRS ( Software/System Requirement Specification ).
In this document both business & Technical requirement exist

The important parts of SRS document are:

lFunctional requirements of the system

lThe functional requirements part discusses the functionalities required

from the system. The system is considered to perform a set of high-

level functions
lNon-functional requirements of the system

lMaintainability of the system, portability of the system,usability of the

system, etc.
 SOFTWARE DESIGN

lSoftware design is a process to transform user requirements into

some suitable form, which helps the programmer in software coding
and implementation.
lNow we know what the system is for, we must set about designing it.

The aim being to achieve everything that we established in the

previous phase.

lTwo types of design :

lHigh Level Design --- >Main Modules ( done by Project Manager)
Low Level Design --- > Sub modules & Child Modules
(Done by
project leader & more)
In this phase also document exist which will knows us PDD (Project
Design Document) or TDD (Technical Design Document) .