Software Development Life Cycle (SDLC)

Manoj V. NikumAhinsa

Polytechnic,Dondaicha

Software Development Life CycleSystems development life cycle (SDLC)

Provides overall framework for managing systems development process

Two main approaches to SDLCPredictive approach – assumes project can

be planned out in advance

Adaptive approach – more flexible, assumes project cannot be planned out in advance

All projects use some variation of SDLC

SDLC Architecture

Working of SDLC Systems analysis, requirements definition: Defines

project goals into defined functions and operation of the intended application. Analyzes end-user information needs.

Systems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudo code and other documentation.

Development: The real code is written here. Integration and testing: Brings all the pieces together into

a special testing environment, then checks for errors, bugs and interoperability.

Acceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business.

Maintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This is often the longest of the stages.

Working of SDLC (Cont.)

SDLC ModelA framework that describes the

activities performed at each stage of a software development project.

There are various software development approaches defined and designed which are used/employed during development process of software, these approaches are also referred as "Software Development Process Models".

Waterfall Model

Waterfall StrengthsEasy to understand, easy to useProvides structure to

inexperienced staffMilestones are well understoodSets requirements stabilityGood for management control

(plan, staff, track)Works well when quality is more

important than cost or schedule

Waterfall DeficienciesAll requirements must be known upfrontDeliverables created for each phase are

considered frozen – inhibits flexibilityCan give a false impression of progressDoes not reflect problem-solving nature of

software development – iterations of phases

Integration is one big bang at the endLittle opportunity for customer to preview

the system (until it may be too late)

When to use the Waterfall ModelRequirements are very well

knownProduct definition is stableTechnology is understoodNew version of an existing

productPorting an existing product to a

new platform.

V-Shaped SDLC Model

Incremental SDLC Model

Spiral SDLC Model

Other ModelsCOCOMO ModelRapid Application Development (RAD)Phased ModelPrototyping SDLCThrowaway Prototyping Model

Some Agile MethodsAdaptive Software Development (ASD) Feature Driven Development (FDD) Crystal Clear Dynamic Software Development

Method (DSDM) Rapid Application Development (RAD)Scrum Extreme Programming (XP) Rational Unify Process (RUP)

Strength & Weakness of SDLC

StrengthControlMonitor Large

ProjectsDetailed StepsEasy To Maintain

WeaknessIncreased

Development Time & Cost

RigidityHard To Estimate

Project Overruns

ConclusionWithout an SDLC Model to follow, developers

can have a free hand of developing software. There are so many programs out there that were created with a vision of need instead of following a certain model.

On the other hand SDLC will ensure everything is laid out. Businesses will have a clear idea of what will happen and what is expected from a software.

Maintenance and development of the software is also possible since parts could be possibly be reused in different programs.

Thank You