Meaning, stages, models of SDLC

1. 1

2. MEANING
• SDLC is also known as Software Development Process.
• SDLC is a framework defining tasks performed at each step in the software
development process.
• The life cycle defines a methodology for improving the quality of software.
• It consists of a detailed plan describing how to develop, maintain, replace and
alter the specific software.
2

3. STAGES OF SDLC
3

4. Stage 01 : Planning
Planning is done for the quality assurance requirenents and identification of risks
associated with the project.
Stage 02 : Analysis
Requirement analysis is important in SDLC
It is performed by senior members of the team.
Stage 03 : Design
Design is the reference for product architects to come out with the best
architecture for the product to be developed.
4

5. 5
Stage 04 : Development
In this stage of SDLC the actual development starts and the product is built.
Stage 05 : Testing
This stage refers to the testing only stage of the product where it’s defects are reported, tracked,
fixed and retested until the product reaches the quality standards defined.
Stage 06 : Implementation
Once the product is tested and ready to be deployed, it is released formally in the appropriate
market.
Stage 07 : Maintenance
After the product is released in the market, it’s maintenance is done for the existing customer
base.

6. SOFTWARE DEVELOPMENT MODELS
• Watefall model
• V- Model
• Spiral Model
• Big bang Model
• Interactive Model
• Agile Model
• RAD Model
• Prototyping Models
6

7. MOSTLY USED…..
WATERFALL MODEL
This model involves finishing the first phase completely before commencing the next one.
When the phase is completed successfully, it is reviewed to see if the project is on track and
whether it is feasible to continue.
V-SHAPED MODEL
This model focuses on execution of processes in a sequential manner, similar to the Waterfall
model but with more importance placed on testing.
Testing procedures are written even before the commencement of writing code.
A system plan is generated before starting the development phase.
7

8. STRENGHTS & WEAKNESSES
STRENGTHS
• Control.
• Monitor large projects.
• Detailed steps.
• Evaluate costs and completion targets.
• Documentation.
• Well defined user input.
• Ease of maintenance.
• Development and design standards.
• Tolerates changes in MIS staffing.
WEAKNESSES
• Increased development time.
• Increased development cost.
• Systems must be defined up front.
• Rigidity.
• Hard to estimate costs, project overruns.
• User input is sometimes limited.
8

9. 9