The document presents information on the Software Development Life Cycle (SDLC), including: 1) It describes the seven main phases of the SDLC - planning, analysis, design, development, testing, implementation, and maintenance. 2) It discusses several SDLC models like waterfall, iterative, prototyping, spiral and V-model and compares their strengths and weaknesses. 3) It emphasizes the important role of testing in the SDLC and describes different testing types done during the phases.

1. SHRI RAM MURTI SMARAK COLLEGE OF ENGINEERING
& TECHNOLOGY, BAREILLY (UTTAR PRADESH)
Research Paper Presentation
on
Software Development Life Cycle(SDLC)
Presented By:
Akash Gupta
Rupali Bhojpuria
Shobhana Singh

2. INTRODUCTION TO SDLC
 SDLC Stands for Software Development Life Cycle.
 The software development life cycle (SDLC) is
a framework defining tasks performed at each step in
the software development process.
 It consists of a detailed plan describing how
to develop, maintain and replace specific software.

3. OBJECTIVE OF SDLC
 SDLC has Three primary objectives:
 Ensure the delivery of high quality systems.
 Provide strong management control.
 Maximize productivity.

4. SDLC PHASES

5. Phase 1: Planning
 Determine if a new system is needed
 Three primary tasks:
 Define the problem.
 Suggest alternative solutions.
 Prepare a short report.

6. Phase 2: System Analysis
 In depth study of the existing system to
determine what the new system should do.
 In addition to observation and interviews,
examine:
 Formal lines of authority (org chart)
 Standard operating procedures
 How information flows
 Reasons for any inefficiencies

7. Phase 3: System Design
 It takes the initial input
 For each requirements design elements will be
produced
 It describes the software features and includes
hierarchy diagrams , screen layout diagrams
 The output of the stage describe the new
system as a collection of modules or
subsystems.

8. Phase 4: System Development
 Build the system to the design specifications
 Develop the software
 Acquire the hardware
 Create manuals for users and operators

9. PHASE 5: SYSTEM TESTING
 Test the new system
 Module (unit) test - tests each part of
system
 Integration testing - tests system as one
unit

10. Phase 6: System Implementation
 Convert from old system to new system.
 Train users
 Compile final documentation
 Evaluate the new system
 User Training

11. Phase 7: System Maintenance
 Physical repair of the system.
 Correction of new bugs found.
 System adjustments to environmental changes.
 Adjustments for users’ changing needs
(adaptive).
 Changes to user better techniques when they
become available (perfective).

12. SDLC MODELS
A framework that describes the activities performed at
each stage of a software development project.
 Waterfall model
 Iterative model
 Prototyping model
 Spiral Model
 V model

13. WATERFALLMODEL
TheWaterfall Model was first Process Model to be introduced. It is also
Referred to as a linear-sequential life cycle model .

14. Strengths of Waterfall model
 Strengths
 Structure minimizes wasted effort.
 Works well for technically weak or in
experienced staff.
 Minimizes planning overhead.
 Weakness
 Inflexible
 Only final stage produces documentation.
 Backing up to address mistake is difficult.

15. Iterative Model
In Iterative model ,iterative process start with a simple implementation
Of a small set of the software requirements and iteratively enhances
the Evolving version until the complete system is implemented and
ready to be deployed

16. Strengths of Iterative model
 Results are obtained early and periodically.
 Parallel development can be planned.
 Progress can be measured.
 Less costly to change the scope/requirements.
 Testing and debugging during smaller iteration is
easy.

17. WEAKNESS OF ITERATIVE MODEL
 More resources may be required.
 Although cost of change is lesser but it is not
very suitable for changing requirements.
 More management attention is required.
 System architecture or design issues may arise
because not all requirements are gathered in the
beginning of the entire life cycle.
 Defining increments may require definition of
the complete system.

18. Prototyping Model

19. Strengths& weakness of Prototyping model
 Strengths
 Customers can see steady progress.
 This is useful when requirements are changing
rapidly.
 Weakness
 It is impossible to know how long it will take.
 There is no way to know the no of iterations
will be required.

20. Spiral Model
The Spiral model combines the idea of iterative development
With the systematic , controlled aspects of the waterfall model.

21. Strengths &Weakness of Spiral model
 Strength
 Early iterations of the project are cheapest
 Risk decreases.
 All iterations meets the project needs
 Weakness
 Complicated
 Require attentive & knowledgeable
management

22. V- Model
The V-model is SDLC model where execution of processes happens in a
sequential manner in V-shape. It is also known as Verification and Validation
model.

23. Strengths of V model
 Emphasize planning for verification and validation
of the product in early stages of product development
 Each deliverable must be testable
 Project management can track progress by
milestones
 Easy to use

24. WEAKNESS OF V MODEL
 Does not easily handle concurrent events
 Does not handle iterations or phases
 Does not easily handle dynamic changes in
requirements
 Does not contain risk analysis activities

25. SOFTWARE DEVELOPMENT LIFE CYCLE:
THE ROLE OF TESTING
 Software development life cycle (SDLC) is an integral
part of any software application development. Testing
has a lot of influence in SDLC.
 In every company, testing is the most vital and precious
stage in the software development life cycle. But, the
technique by which it is performed, dissimilar from one
company to another company.

26. SDLC TESTING PHASE
The SDLC Testing phase is notionally designed to be
carried out after system development is complete.
With the help of different type of testing (e.g. assimilation tests,
element testing, user recognition testing system testing and
regression tests etc.) coder may produce a consistent and
reliable application. Testing also includes some process e.g. test
analysis, test plan, test design and test execution.
.

27. WHAT IS THE SDLC TESTING LIFE CYCLE?
 SDLC Test Analysis Phase
 SDLC Test Design Phase
 SDLC Test Execution Phase

28. MOST IMPORTANCE OF TESTING IN SDLC
Recognition of Error and Faults
Resolves the errors and faults in the software application. These
errors may be in unit level or in system level.
Statistics to Shareholders and Status of Organization
Helps to know the condition of product and work standards.
Enhancement in Product Standards
Helps to know the real result and the probable result. It also helps to
pick up the standards of the software.
Technical Significance
Significant for technical characteristics of any SDLC as the software.
Free from any Risk
Free everyone from any risk.

29. CONTD…
Confirmation and Corroboration
Compare among standards of several software application.
Demonstrate Accessibility and Feasibility
Application is delivering to a select assembly of users and their
functioning with the application is noticed.
Avoid fault immigration
Prohibited all faults from immigrating to the following
progress stage.

30. WHATARE THE TYPES OF SDLC TESTING?
Acceptance Testing –
Alpha Testing –
Beta Testing –
Functional Testing –
Independent Verification and Validation –
Load Testing –
Security Testing –

31. SECURITY IN SDLC
 Integrating security into the SDLC is essential for
developing quality software. While there are no standard
practices, these guidelines can help you develop a
custom process for a secure software development life
cycle.
Each phase of the SDLC is mapped with security
activities
 Requirements Gathering
Security Requirements
 Determine security needs
 Determine privacy needs

32.  Design
• Identify Design Requirements from security
perspective
• Architecture & Design Reviews
• Threat Modeling
 Coding
• Coding Best Practices
• Perform Static Analysis
 Testing
• Run security test cases
• Perform dynamic analysis

33.  Deployment
• Server Configuration Review
• Network Configuration Review
 Maintenance
• Continually monitor application security and update
as needed
• Utilize response plan as needed

34. SECURITY-ENHANCING LIFECYCLE
PROCESS MODELS
 Enhance security through a repeatable and measurable
process
 Provide guidance on secure software activities
 Provide secure software development reviews
 Include tactical resources
 Provision the use of automation tools
 Suggest roles for conducting the activities
 Integrate with foundational software development
activities

35. FREE FLOW MODEL
In the framework of Free Flow the development process
of a software is augmented at every stage by incorporating
different matrices and allowing free flow of control in the
software development hierarchy in order to save time in
situations where the testing team need to interact with the
another team.

36. FREE FLOW MODEL FRAMEWORK

37. FREE-FLOW SDLC FEATURES
 Requirement Capture
 Prototype and High Level Diagrams
 Module releases
–
 Check-List Method
 Well-Defined Architecture
 Task and bug tracking system

38. CONCLUSION
There are many SDLC models such as, Waterfall, spiral,
iterative, V-shaped etc. used in various organizations depending
upon the conditions prevailing there
In this paper we have compared the different software
development life cycle models on the basis of certain features
like- Requirement, specifications, Risk involvement, User
involvement, Cost etc.
On the basis of these features for a particular software project
one can decide which of these software development life cycle
models should be chosen for that particular project. Selecting the
correct life cycle model is extremely important in a software
industry as the software has to be delivered within the time
deadline & should also have the desired quality.

39. FUTURE WORK
The new proposed framework is a Comparative
Analysis of Free Flow software methodology
with different SDLC model.
Free-Flow Model eliminates the risks and errors
in early stages through pipelined flow of processes
and control more than other SDLC model.
Number of matrices added to make the system
robust and increase its efficiency.

40. REFERENCE
 WWW.GOOGLE.COM .
 www.encyclopedia.com
 www.yahoo.com
 Software Engineering Book –
K. K. Aggarwal, Yogesh Singh Software Engineering 3rd
Edition.
 Research guide.
 Sanjana Taya “Comparative Analysis of Software
Development Life” .

41. QUESTION

42. THANK YOU