SDLC

SDLC
Software Development Life Cycle

Agenda
 Introduction
 SDLC Overview
 SDLC Phase
 SDLC Flow
 SDLC Model
 Waterfall Model
 Agile Model
 Advantages of SDLC
 Disadvantages of SDLC
 Conclusion
Introduction
 The SDLC is a framework that describes the

activities performed at each stage of a software
development project.
 SDLC process is used by the software industry to

design, develop and test high quality software.
 It aims to produce the quality software that meets or

exceeds customer expectations, reaches completion
within time and budget.
 ISO/IEC 12207 is an international standard for
software life-cycle processes. It aims to be the
standard that defines all the tasks required for
developing and maintaining software.
 Software Engineering Process Technology Company

(SEPT) is a firm specializing in meeting the software
process standards information needs of the
professional community, particularly concerning
ISO/IEC 12207.
International Electrotechnical
Commission(IEC)
International Organization for
Standardization(ISO)
SDLC Phases
SDLC Phases
1. Planning and Requirements Analysis

2. Defining Requirements
3. Designing the Software
4. Building or Developing the Software
5. Testing the Software
6. Deployment and Maintenance
1. Planning and Requirements Analysis
 Requirement analysis is the most important

and fundamental stage in SDLC.
 It is performed by the senior members of the team

with inputs from all the stakeholders and domain
experts or SMEs in the industry.
 Planning for the quality assurance requirements and

identification of the risks associated with the project
is also done at this stage.
Requirement Analysis
 Business Requirements
 Stakeholder Requirements
 Solution Requirements
Functional Requirements
Non-Functional Requirements
 Transition Requirements
2. Defining Requirements
 Once the Requirement Analysis is done the next step

is to clearly define and document the software
requirements and get them approved from the project
stakeholders.
 This is done through “ SRS ” –Software Requirement

Specification document which consists of all the
product requirements to be designed and develop
during the project life cycle.
Defining Requirements
 Enterprise Analysis
 Business Analysis Planning & Monitoring
 Elicitation
 Requirements Analysis
 Requirements Management & Communication
 Solution Assessment & Validation
3. Designing the Software
 Based on the requirements specified in SRS,

usually more than one design approach for the
product architecture is proposed and documented in a
DDS-Design Document Specification.
 In DDS is reviewed by all the stakeholders and based

on various parameters as risk assessment, design
modularity, budget & time constraints, the best
design approach is selected for the software.
4. Developing the Software
 In this stage of SDLC the actual development starts

and the product is built. The programming code is
generated as per DDS during this stage.
 Developers have to follow the coding guidelines

defined by their organization and programming tools
like compilers, interpreters, debuggers, etc are used to
generate and implement the code.
5. Testing the Software
 This stage is usually a subset of all the stages as in

the modern SDLC models, the testing activities are
mostly involved in all the stages of SDLC.
 However this stage refers to the testing only that

stage of the software where defects are reported,
tracked, fixed and retested, until the software reaches
the quality standards defined in the SRS.
6. Deployment and Maintenance
 Once the software id tested and no bugs or

errors are reported then it is deployed.
 Then based on the feedback, the software

may be released as it is or with suggested
enhancements in the target segment.
 After the software is deployed then its

maintenance starts.
SDLC Models
 To help understand and implement the SDLC phases

various SDLC models have been created by software
development experts, universities, and standard
organizations.
Reasons for using SDLC Models
 Provides the base for project planning, estimating &

scheduling.
 Provides framework for standard set of

terminologies, activities & deliverables.
 Provides mechanism for project tracking & control.
 Increases visibility of project progress to all

stakeholders.
Advantages of choosing an appropriate SDLC
 Increased development speed

 Increased product quality
 Improved tracking & control
 Improved client relations
 Decreased project risk
 Decreased project management overhead
SDLC Models
 Waterfall Model
 Iterative Model
 Agile Model
WATERFALL MODEL
Waterfall Model
 Oldest and most well-known SDLC model.
 Follows a sequential step-by-step process from

requirements analysis to maintenance.
 Systems that have well-defined and understood

requirements are a good fit for the Waterfall Model.
Waterfall Model : Advantages
 Easy to understand, easy to use

 Provides structure to inexperienced staff
 Milestones are well understood
 Sets requirements stability
 God for management control (plan, staff, track)
 Works well when quality is more important than cost
or schedule
Waterfall Model : Disadvantages
 All requirements must be fully specified upfront

 Deliverables created for each phase are considered
frozen – inhibits flexibility

 Can give a false impression of progress
 Does not reflect problem-solving nature of software
development – iterations of phases

 Integration is one big bang at the end
 Little opportunity for customer to preview the
system (until it may be too late)

When to the use Waterfall Model
 Requirements are very well known

 Product definition is stable
 Technology is understood
 New version of an existing software/product
 Porting an existing product to a new platform
Iterative Model
 Also called Incremental Model
 Project is break into small modules which can be
delivered
 A working version of software is produced during the
first module
 Each subsequent release of the module adds
functionality to the previous release. The process

continues till the complete system is achieved
 Model is very successfully when working with new
technology
 More than one iteration can be going at the same time
ITERAVTIVE MODEL
Iterative Model : Advantages
 Quick software is released during early phases of

software life cycle
 Less costly to change requirements as compared to
other models
 Easier to develop and test when iterations are small
 Customer can give his feedback quickly
 More than one iteration can be going parallel at same
time
Iterative Model : Disadvantages
 Comparatively more resources are required

 Skilled Manager is needed to manage otherwise
project costing is increased

 Project started with complete project architecture
design, can result issues in future

 Cost is higher than Waterfall model
AGILE MODEL
 Agile model believes that every project needs to be

handled differently and the existing methods needs to
be tailored to best suit the project requirements.
 In agile the tasks are divided to time boxes (small
time frames) to deliver specific features for a release.

 Iterative approach is taken and working software
build is delivered after each iteration. Each build is

incremental in terms of features; the final build holds
all the features required by the customer.
AGILE MODEL
Agile Model
 Speed up or bypass one or more life cycle phases
 Usually less formal and reduced scope
 Used for time-critical applications
 Used in organizations that employ disciplined

methods
Some Agile Methods
 Rapid Application Development (RAD)

 Scrum
 Extreme Programming (XP)
 Adaptive Software Development (ASD)
 Feature Driven Development (FDD)
 Crystal Clear
 Dynamic Software Development Method (DSDM)
 Rational Unify Process (RUP)
Agile Model : Advantages
 Is a very realistic approach to software development.

 Promotes teamwork and cross training.
 Functionality can be developed rapidly and
demonstrated.
 Resource requirements are minimum.
 Suitable for fixed or changing requirements.
 Delivers early partial working solutions.
 Little or no planning required.
 Easy to manage.
Agile Model : Disadvantages
 For larger projects, it is difficult to judge the efforts

and the time required for the project in the SDLC.
 Since the requirements are ever changing, there is
hardly any emphasis, which is laid on designing and

documentation. Therefore , chances of the project
going off the track easily are much more.
 Depends heavily on customer interaction, so if
customer is not clear, team can be driven in the

wrong direction.
Conclusion
 Project Management - Lead to an endeavor.

 Planning is a map, a guide, especially for team.
(Relatively simple and helpful techniques)

 SDLC is mostly about people, process, time
management & communication.

 Risks are inevitable, planning helps to avoid stupid
ones (Experience counts).

 Assessing the scope of work, timing, risks and
resources will lead to the project success.

SDLC

Uploaded by

Copyright:

Available Formats

SDLC

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SDLC

Uploaded by

Copyright:

Available Formats

SDLC

Software Development Life Cycle

 The SDLC is a framework that describes the

 SDLC process is used by the software industry to

 It aims to produce the quality software that meets or

 Software Engineering Process Technology Company

1. Planning and Requirements Analysis

 Requirement analysis is the most important

 It is performed by the senior members of the team

 Planning for the quality assurance requirements and

 Once the Requirement Analysis is done the next step

 This is done through “ SRS ” –Software Requirement

 Based on the requirements specified in SRS,

 In DDS is reviewed by all the stakeholders and based

 In this stage of SDLC the actual development starts

 Developers have to follow the coding guidelines

 This stage is usually a subset of all the stages as in

 However this stage refers to the testing only that

 Once the software id tested and no bugs or

 Then based on the feedback, the software

 After the software is deployed then its

 To help understand and implement the SDLC phases

 Provides the base for project planning, estimating &

 Provides framework for standard set of

 Provides mechanism for project tracking & control.

 Increases visibility of project progress to all

 Increased development speed

 Oldest and most well-known SDLC model.

 Follows a sequential step-by-step process from

 Systems that have well-defined and understood

 Easy to understand, easy to use

 All requirements must be fully specified upfront

frozen – inhibits flexibility

development – iterations of phases

system (until it may be too late)

 Requirements are very well known

functionality to the previous release. The process

 Quick software is released during early phases of

 Comparatively more resources are required

project costing is increased

design, can result issues in future

 Agile model believes that every project needs to be

time frames) to deliver specific features for a release.

build is delivered after each iteration. Each build is

 Speed up or bypass one or more life cycle phases

 Usually less formal and reduced scope

 Used for time-critical applications

 Used in organizations that employ disciplined

 Rapid Application Development (RAD)

 Is a very realistic approach to software development.

 For larger projects, it is difficult to judge the efforts

hardly any emphasis, which is laid on designing and

customer is not clear, team can be driven in the

 Project Management - Lead to an endeavor.

(Relatively simple and helpful techniques)

management & communication.

ones (Experience counts).

resources will lead to the project success.

You might also like