The document compares the Software Development Life Cycle (SDLC) and the Software Test Life Cycle (STLC) by outlining their respective phases, including requirements gathering, design, coding, testing, deployment, and maintenance. Each phase is detailed with specific activities and objectives relevant to both cycles, highlighting the distinct yet complementary roles of development and testing teams. The presentation serves as an overview to better understand the processes and enhance collaboration between development and testing functions.

1. SDLC VS STLC
DAVID TZEMACH
WWW.MACHTESTED.COM
MAY 17 2017

2. AGENDA
IN THIS PRESENTATION, WE WILL REVIEW THE FUNDAMENTAL CONCEPTS
OF SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC) AND SOFTWARE TEST
LIFE CYCLE (STLC) THROUGHOUT THE TRADITIONAL DEVELOPMENT
METHODOLOGIES.

3. THE FUNDAMENTAL
DIFFERENCES BETWEEN
SDLC AND STLC

4. PHASE 1 : REQUIREMENTS GATHERING AND ANALYSIS
Software Development Life Cycle (SDLC) Software Test Life Cycle (STLC)
In the first phase, the team members (Usually by
the PM/Analyst) collect and document all possible
requirements and specifications of the application
to be developed based on the client demands and
expectations.
Each requirement definition must be detailed as
possible to remove any misunderstanding in the
later phases.
Once all the customer specifications are gathered
and documented, there is a meeting with the
that should provide his approval.
In the first part, the testing team will review and
analyze the customer requirements and
specifications.
In the second part, the testing team will determine
the types of testing that they will use during the
testing cycles.

5. PHASE 2 : DESIGN
Software Development Life Cycle (SDLC) Software Test Life Cycle (STLC)
In the second phase, the team will review and study the
requirements and specifications that were gathered in
phase 1 that they need to use during the preparation of
the plan and design of the application to be developed.
Examples:
• Determine the coding languages and platforms.
• Determine the development schedule.
• Design the Application Architecture.
• Determine the process that the team will use during
the coding phase.
• Determine the software and hardware that will be
per model.
• Determine the applications components and
integrations.
In this phase, the test lead/architect will design the High-
level testing plan that will be carried out in the Testing
phase (Software Test Plan).
Examples:
• Determine the testing methodology.
• Determine the test environments.
• Determine the test resources.
• Determine the testing tools.
• Determine the testing types to be used by the testing
teams.

6. PHASE 3 : CODING
Software Development Life Cycle (SDLC) Software Test Life Cycle (STLC)
In this phase, a development team will use the
system design to develop the application (Units,
modules and integrations).
The testing team will use the STP from the previous
step to create a detailed test plan (STD).
Examples:
• Expected test inputs and outputs.
• Time estimations per test.
• Test configuration.
• Test prioritization.
• Test Scenarios
• Test cases

7. PHASE 4 : TESTING
Software Development Life Cycle (SDLC) Software Test Life Cycle (STLC)
Once the development phase is done, the
testing team has a working system that
they can use to execute the tests and
validate that all requirements are
implemented based on the client
expectations.
The testing team will execute the tests
(Manual & Automated) as planned, report
for defects and retest as needed.

8. PHASE 5 : DEPLOYMENT
Software Development Life Cycle (SDLC) Software Test Life Cycle (STLC)
Once all tests are done, the application is
ready to be implemented on real
production environments(GA)
The testing team will review the test
and test artifacts, based on this analysis
test team can determine/improve the
testing strategy for future projects.
In addition, the testing team will generate
the final test report.

9. PHASE 6 : MAINTENANCE
Software Development Life Cycle (SDLC) Software Test Life Cycle (STLC)
After the product deployment, the company will
provide support and technical assistance to the
clients.
Examples:
• Technical assistance.
• Patches releases.
• Bug Fixes.
Test plans are updated based on the analysis
results in addition to testing the enhancements
support requests.

10. FOR ADDITIONAL KB’S PLEASE
VISIT MY BLOG
WWW.MACHTESTED.COM