The document discusses the software development life cycle (SDLC) and the waterfall model. The SDLC describes the stages of a software project from requirements specification through maintenance. The waterfall model outlines the sequential stages of requirement analysis, system design, implementation, testing, deployment, and maintenance. Each stage serves as input for the next. The document provides details on the activities in requirement analysis, system design, implementation approaches, testing and debugging, and deployment.

4. SDLC
S SOFTWARE
D DEVELOPMENT
L LIFE
C CYCLE

5. A framework that
describes the activities
performed at each stage
of a software development
project
SDLC

6. Requirement
Specification
System analysis
and design
Implementation
Testing and
debugging
Deployment
Maintenance
WATER FALL MODEL

7. 1.REQUIREMENT ANALYSIS
The term defines all possible
requirement of the software in this
phase.
 Functionality
 Capability
 Performance
 User Interface
 Inputs
 Outputs

8. Requirement
specification
Functionalit
y
Capability
Performanc
e
Output
Input
User
interface

9. SYSTEM ANALYSIS
• System analysis phase answer the questions of what will use the system ,what the
system will do , where and when it will be used
• Analysis strategy
• Requirment gathering
• System proposals

10. 2.SYSTEM DESIGN
It includes following steps.
System design documents
System architecture
Hierarchy of software component
Rules for component selection
Interfaces b/w components
• The design document serves as input to the
next phase of the model.

11. SYSTEM IMPLEMENTATION
This phase is also known as construction or code
generation. This is because in this phase, the team constructs
the various software components specified in system design
documents.

12. To constructs a software components, the team first divides it into
modules, and then codes each module separately.
The team codes and tests each module independently

13. Direct
Implementation
Phased
Implementation
Pilot
Implementation
Parallel
Implementation

14. DIRECT IMPLEMENTATION
• In direct implementation the entire new system completely replaces entire old system in
one step.

15. PARALLEL IMPLEMENTATION
• In parallel implementation both systems are operated side by side until the new system
proves itself

16. PHASED IMPLEMENTATION
• A phased implementation is one in which the organization eases into the new system
one step at a time so that all the users are working with some of the system

17. PILOT IMPLEMENTATION
• In this type of conversion, one part of the organization uses the new system and the rest
of the organization uses old system. When one part of the organization is satisfied with
the new system the rest one of the organization can start using it.

18. TESTING AND DEBUGGING
• In this phase the team integrates the independently developed
and tested modules into a complete system to check if all
modules coordinates properly with each other and the system
as a whole behaves as per the specifications. They debug any
bug that they find during integrated system,and repeat testing
of that functionality of the system after the team completes this
phase successfully,the software is ready for release and
deployment

19.  Software deployment is the process of getting
your program ready for market.
 A newly created program may work fine on your
computer, but that doesn’t mean it is really ready
for others to use.

20. 6.Maintenance
Evolution Methods
Systems audit - performance compared to original
specifications
Periodic evolution – “ checkups ” from time to time,
modifications if necessary