Software development life cycle slide

1. Software DevelopmentSoftware Development
Life CycleLife Cycle
SDLC

2. Software Development LifeSoftware Development Life
CycleCycle
 This refers to a process thatThis refers to a process that
produces software with theproduces software with the
highest quality and lowest costhighest quality and lowest cost
in the shortest time.in the shortest time.
 By lowering the cost of softwareBy lowering the cost of software
development we candevelopment we can
simultaneously improve qualitysimultaneously improve quality
and shorten production time.and shorten production time.

3. Software Development LifeSoftware Development Life
CycleCycle
 Software development life cycleSoftware development life cycle
includes a detailed plan toincludes a detailed plan to
develop, alter, maintain anddevelop, alter, maintain and
replace a software system.replace a software system.

4. Stages and best practices ofStages and best practices of
Software Development Life Cycle.Software Development Life Cycle.
There are several stages that formulateThere are several stages that formulate
the software development life cycle:the software development life cycle:
1.1. IdentifyIdentify
2.2. PlanPlan
3.3. DesignDesign
4.4. BuildBuild
5.5. TestTest
6.6. DeployDeploy
7.7. MaintainMaintain

5. Stage 1: IDENTIFYStage 1: IDENTIFY
 Identify the current problems. WhatIdentify the current problems. What
don’t we want?don’t we want?
 Involve all stakeholders, includingInvolve all stakeholders, including
customers, salespeople, industrycustomers, salespeople, industry
experts and programmers.experts and programmers.
 Learn the strengths and weaknessesLearn the strengths and weaknesses
of the current system, withof the current system, with
improvement as the goal.improvement as the goal.

6. Stage 2: PLANStage 2: PLAN
 What do we want?What do we want?
 Define the requirements of theDefine the requirements of the
new software and determine thenew software and determine the
cost and resources required.cost and resources required.
 Detail the risks involved, provideDetail the risks involved, provide
sub-plans for shortening thissub-plans for shortening this
risk.risk.
 Create a Software RequirementCreate a Software Requirement
Specification Document.Specification Document.

7. Stage 3: DESIGNStage 3: DESIGN
 How will we get what we want.How will we get what we want.
 Start by turning the software requirementStart by turning the software requirement
specifications document into a design plan,specifications document into a design plan,
called the design specifications.called the design specifications.
 All stakeholders then review the plan andAll stakeholders then review the plan and
offer feedback and suggestions. It is crucialoffer feedback and suggestions. It is crucial
to have a feature for collecting &to have a feature for collecting &
incorporating stakeholders input into thisincorporating stakeholders input into this
document.document.
 Failure at this stage will almost certainlyFailure at this stage will almost certainly
result in cost overruns at best or even totalresult in cost overruns at best or even total
collapse of the project at worst.collapse of the project at worst.

8. Stage 4: BUILDStage 4: BUILD
 This is actually the leastThis is actually the least
complicated step. Create whatcomplicated step. Create what
we want. Develop what we wantwe want. Develop what we want
by generating all the actualby generating all the actual
code.code.

9. Stage 5: TESTStage 5: TEST
 Did we get what we wanted.Did we get what we wanted.
Test for defects andTest for defects and
deficiencies.deficiencies.
 Fix those issues until theFix those issues until the
product meets the originalproduct meets the original
specifications.specifications.

10. Stage 6: DEPLOYStage 6: DEPLOY
 We start using what we got.We start using what we got.
This part happens in a limitedThis part happens in a limited
way at first.way at first.
 Depending on feedback fromDepending on feedback from
end users more adjustmentsend users more adjustments
can be made.can be made.

11. Stage 7: MAINTAINStage 7: MAINTAIN
 Get closer to what we want.Get closer to what we want.
When it meets reality often theWhen it meets reality often the
plan never turns out perfect.plan never turns out perfect.
 As conditions in the real worldAs conditions in the real world
change we need to update andchange we need to update and
advance the software to match.advance the software to match.