SlideShare a Scribd company logo
4
Most read
8
Most read
18
Most read
System Development Life Cycle
(SDLC)
By:
Amandeep Singh
Rochna Dhatwalia
What is SDLC?
• It is a conceptual model used in project management that describes
  the stages involved in an information system development project.
Recognition of Need
• It can be environmental based or organizational
  based.
• Ideas are generated to advance technology.
• User originated ideas prompt initial
  investigation.
Feasibility Study
• Economic: Cost benefit analysis.
• Technical: We need to check whether existing
  computer can support the system.
• Behavioral: An estimate should be made of how
  strong a reaction the user staff is likely to have
  toward the development of a computerized
  system.
Feasibility Study (Steps)
• Form a project team and appoint a leader.
• Prepare System flowcharts.
• Enumerate potential candidate system.
• Describe and identify characteristics of
  candidate system.
• Evaluate performance.
• Select best candidate system.
Analysis
• In the Analysis stage an in-depth analysis is
  performed to obtain a detailed understanding of
  the business needs.
• Tools Used: DFD’s, interviews, on-site
  observation, questionnaire etc.
• Training, experience and common sense are
  required for collecting information to do
  anlaysis.
Design
• It is the most creative and challenging phase of
  SDLC.
• It defines the final system and refers to the
  technical specifications.
• DFDs are used to show the flow of system.
• Two phases: 1. Logical Design and Physical
  Design
• Logical Design: Specifies user needs.
• Physical Design: Tells the programmer what the
  candidate system must do.
Implementation
• Less creative then designing phase.
• It is of 3 types:
1. Implementation of a computer system to
    replace a manual system.
2. Implementation of a new computer system to
    replace an existing one.
3. Implementation of a modified application to
    replace existing one on same computer.
• Parallel Runs: In this new system runs with old
  system which provides assurance, and even
  helps user staff gain experience.
Post Implementation
• The Post-Implementation Review is used to
  evaluate the effectiveness of the system.
• The objectives are to determine if the system
  does what it is designed to do
• Does it support the user as required in an
  effective and efficient manner
• The review should assess how successful the
  system is in terms of
  functionality, performance, and cost versus
  benefits.
Maintenance
• The emphasis during this phase is to ensure that
  needs continue to be met and that the system
  continues to perform according to specifications.
• Routine hardware and software maintenance
  and upgrades are performed to ensure effective
  system operations.
• User training continues during this phase, as
  needed, to acquaint new users to the system or
  to introduce new features to current users.
SDLC with Prototyping
Why do we use prototyping approach?
• It is used because of failures that occurred in the
  final version of the software application
  developed using the other SDLC approach.
• There were various limitations with the other
  approach of SDLC and to overcome these
  limitations, the concept of prototyping was
  introduced.
Diagram for SDLC with prototyping

                    Analyze
Identify User   Prototype (Input        Implement
Requirements       Processing            Prototype
                    Output)
                  Revised through
                  iterative process




                     Post
                                      Final Conversion
                Implementation
What is Prototyping?
• It is an advanced technology which recognizes
  problem and uses advanced computer
  technology.
• The system is built through trial and error and
  refined using iterative process.
• It is of two types: Throwaway or Rapid
  Prototype and evolutionary prototype.
Throwaway or Rapid Prototype
• It is also called closed ended prototype.
• In this we create a model that will eventually be
  discarded instead of becoming part of final
  system.
• After preliminary analysis, a simple working
  model of the system is constructed so that the
  user has an idea what the final system may look
  like.
• Speed is crucial in rapid prototype.
• Since with a limited budget and time, little can
  be expected from a system that will eventually be
  discarded.
Evolutionary Prototyping
• It is different from Rapid prototyping as its main
  goal is to build a robust prototype in every
  manner and constantly refine it.
• This technique allows the development team to
  add features that couldn’t be added in
  requirement and design phase.
• In this, developers will focus and develop only
  those parts of the system which they understand
  perfectly.
Evolutionary Prototyping
• The developer will not implement a poorly
  understood feature to help minimize risk.
• Once the partial system is done, it is sent to
  customer sites so that they can detect
  opportunities for new featured.
• These new features are then implemented by the
  developers.
• Software design is updated and code is retested.
Thank You
 Amandeep Singh
 Rochna Dhatwalia

More Related Content

PPTX
Software Process Models
PPTX
Software project management- Software Engineering
PPTX
Requirements modeling
PPT
Analysis modeling & scenario based modeling
PPTX
Software Engineering
PPTX
Software Configuration Management (SCM)
PPTX
Software Project Management - Staffing
Software Process Models
Software project management- Software Engineering
Requirements modeling
Analysis modeling & scenario based modeling
Software Engineering
Software Configuration Management (SCM)
Software Project Management - Staffing

What's hot (20)

PPT
Use Case Diagram
PPTX
Assemblies
PPT
Unit1
PPT
Spm unit 4
PPT
Agile development, software engineering
PPTX
Software requirement specification
PPTX
Software project planning
PPT
Flow oriented modeling
PPTX
Software process
PDF
Software Development Life Cycle (SDLC)
PPT
Software System Engineering - Chapter 1
PPTX
Waterfall model in SDLC
PPT
Rad model
PPT
Coupling and cohesion
PPT
Software Requirements in Software Engineering SE5
PPT
Software estimation
PPTX
System testing
PPTX
SRS(software requirement specification)
Use Case Diagram
Assemblies
Unit1
Spm unit 4
Agile development, software engineering
Software requirement specification
Software project planning
Flow oriented modeling
Software process
Software Development Life Cycle (SDLC)
Software System Engineering - Chapter 1
Waterfall model in SDLC
Rad model
Coupling and cohesion
Software Requirements in Software Engineering SE5
Software estimation
System testing
SRS(software requirement specification)
Ad

Viewers also liked (8)

PPT
ppt on sOFTWARE DEVELOPMENT LIFE CYCLE
PPT
Software Development Life Cycle (SDLC)
PPTX
Software Engineering Practice
PPTX
Execution of rizal
PDF
Software Development Life Cycle (SDLC)
PPT
Software Development Life Cycle Model
PPTX
PPTX
System Development Life Cycle (SDLC)
ppt on sOFTWARE DEVELOPMENT LIFE CYCLE
Software Development Life Cycle (SDLC)
Software Engineering Practice
Execution of rizal
Software Development Life Cycle (SDLC)
Software Development Life Cycle Model
System Development Life Cycle (SDLC)
Ad

Similar to System development life cycle (sdlc) (20)

PPTX
SDLC and Software Process Models
PPSX
Class prototype
PPTX
PROTOTYPING
PPT
Prototyping.eveningclass.ppt
PPT
Prototyping.eveningclass.ppt.slideshare.information.system.analysis
PPT
system development life cycle
PPT
Kelis king - software development life cycle (sdlc)
PPT
Kelis king - software development life cycle (sdlc)
PPTX
System development lifecycle in grade 12
DOCX
Report on SOFTWARE DEVELOPMENT LIFE CYCLE SDLC
PPT
SE_models_1.ppt
PPT
SE_models_1.ppt
PPT
SE_models_1.ppt
PPT
SE_models_1.ppt
PPTX
SAD_SDLC.pptx
PPTX
sdlc.pptx
PPT
System Analysis And Design Management Information System
PPTX
PROTOTYPE MODEL
PPTX
Mis unit iii by arnav
PPT
Planning, design and implementation of information systems
SDLC and Software Process Models
Class prototype
PROTOTYPING
Prototyping.eveningclass.ppt
Prototyping.eveningclass.ppt.slideshare.information.system.analysis
system development life cycle
Kelis king - software development life cycle (sdlc)
Kelis king - software development life cycle (sdlc)
System development lifecycle in grade 12
Report on SOFTWARE DEVELOPMENT LIFE CYCLE SDLC
SE_models_1.ppt
SE_models_1.ppt
SE_models_1.ppt
SE_models_1.ppt
SAD_SDLC.pptx
sdlc.pptx
System Analysis And Design Management Information System
PROTOTYPE MODEL
Mis unit iii by arnav
Planning, design and implementation of information systems

More from Mukund Trivedi (20)

PPTX
Process of design
PPT
New file and form 2
PPT
File organisation
PPTX
Evaluation
PPTX
Database
PPTX
Case tools
PPTX
Evaluation
PPTX
Dfd final
DOCX
C++ file
PPT
Ff40fnatural resources (1)
PPT
Ff40fnatural resources
PPT
F58fbnatural resources 2 (1)
PPT
F58fbnatural resources 2
PPT
F6dc1 session6 c++
DOC
Ee2fbunit 7
PPT
E212d9a797dbms chapter3 b.sc2 (2)
PPT
E212d9a797dbms chapter3 b.sc2 (1)
PPT
E212d9a797dbms chapter3 b.sc2
PPT
C96e1 session3 c++
Process of design
New file and form 2
File organisation
Evaluation
Database
Case tools
Evaluation
Dfd final
C++ file
Ff40fnatural resources (1)
Ff40fnatural resources
F58fbnatural resources 2 (1)
F58fbnatural resources 2
F6dc1 session6 c++
Ee2fbunit 7
E212d9a797dbms chapter3 b.sc2 (2)
E212d9a797dbms chapter3 b.sc2 (1)
E212d9a797dbms chapter3 b.sc2
C96e1 session3 c++

Recently uploaded (20)

PDF
KodekX | Application Modernization Development
PDF
Encapsulation_ Review paper, used for researhc scholars
PDF
Empathic Computing: Creating Shared Understanding
PDF
Review of recent advances in non-invasive hemoglobin estimation
PDF
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
PPTX
A Presentation on Artificial Intelligence
PDF
Encapsulation theory and applications.pdf
PDF
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
PDF
Modernizing your data center with Dell and AMD
PDF
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
PPTX
MYSQL Presentation for SQL database connectivity
DOCX
The AUB Centre for AI in Media Proposal.docx
PDF
Approach and Philosophy of On baking technology
PDF
Advanced methodologies resolving dimensionality complications for autism neur...
PDF
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
PDF
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
PPTX
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
KodekX | Application Modernization Development
Encapsulation_ Review paper, used for researhc scholars
Empathic Computing: Creating Shared Understanding
Review of recent advances in non-invasive hemoglobin estimation
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
A Presentation on Artificial Intelligence
Encapsulation theory and applications.pdf
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
Modernizing your data center with Dell and AMD
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
MYSQL Presentation for SQL database connectivity
The AUB Centre for AI in Media Proposal.docx
Approach and Philosophy of On baking technology
Advanced methodologies resolving dimensionality complications for autism neur...
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
NewMind AI Weekly Chronicles - August'25 Week I
Diabetes mellitus diagnosis method based random forest with bat algorithm
How UI/UX Design Impacts User Retention in Mobile Apps.pdf
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx

System development life cycle (sdlc)

  • 1. System Development Life Cycle (SDLC) By: Amandeep Singh Rochna Dhatwalia
  • 2. What is SDLC? • It is a conceptual model used in project management that describes the stages involved in an information system development project.
  • 3. Recognition of Need • It can be environmental based or organizational based. • Ideas are generated to advance technology. • User originated ideas prompt initial investigation.
  • 4. Feasibility Study • Economic: Cost benefit analysis. • Technical: We need to check whether existing computer can support the system. • Behavioral: An estimate should be made of how strong a reaction the user staff is likely to have toward the development of a computerized system.
  • 5. Feasibility Study (Steps) • Form a project team and appoint a leader. • Prepare System flowcharts. • Enumerate potential candidate system. • Describe and identify characteristics of candidate system. • Evaluate performance. • Select best candidate system.
  • 6. Analysis • In the Analysis stage an in-depth analysis is performed to obtain a detailed understanding of the business needs. • Tools Used: DFD’s, interviews, on-site observation, questionnaire etc. • Training, experience and common sense are required for collecting information to do anlaysis.
  • 7. Design • It is the most creative and challenging phase of SDLC. • It defines the final system and refers to the technical specifications. • DFDs are used to show the flow of system. • Two phases: 1. Logical Design and Physical Design • Logical Design: Specifies user needs. • Physical Design: Tells the programmer what the candidate system must do.
  • 8. Implementation • Less creative then designing phase. • It is of 3 types: 1. Implementation of a computer system to replace a manual system. 2. Implementation of a new computer system to replace an existing one. 3. Implementation of a modified application to replace existing one on same computer. • Parallel Runs: In this new system runs with old system which provides assurance, and even helps user staff gain experience.
  • 9. Post Implementation • The Post-Implementation Review is used to evaluate the effectiveness of the system. • The objectives are to determine if the system does what it is designed to do • Does it support the user as required in an effective and efficient manner • The review should assess how successful the system is in terms of functionality, performance, and cost versus benefits.
  • 10. Maintenance • The emphasis during this phase is to ensure that needs continue to be met and that the system continues to perform according to specifications. • Routine hardware and software maintenance and upgrades are performed to ensure effective system operations. • User training continues during this phase, as needed, to acquaint new users to the system or to introduce new features to current users.
  • 12. Why do we use prototyping approach? • It is used because of failures that occurred in the final version of the software application developed using the other SDLC approach. • There were various limitations with the other approach of SDLC and to overcome these limitations, the concept of prototyping was introduced.
  • 13. Diagram for SDLC with prototyping Analyze Identify User Prototype (Input Implement Requirements Processing Prototype Output) Revised through iterative process Post Final Conversion Implementation
  • 14. What is Prototyping? • It is an advanced technology which recognizes problem and uses advanced computer technology. • The system is built through trial and error and refined using iterative process. • It is of two types: Throwaway or Rapid Prototype and evolutionary prototype.
  • 15. Throwaway or Rapid Prototype • It is also called closed ended prototype. • In this we create a model that will eventually be discarded instead of becoming part of final system. • After preliminary analysis, a simple working model of the system is constructed so that the user has an idea what the final system may look like. • Speed is crucial in rapid prototype. • Since with a limited budget and time, little can be expected from a system that will eventually be discarded.
  • 16. Evolutionary Prototyping • It is different from Rapid prototyping as its main goal is to build a robust prototype in every manner and constantly refine it. • This technique allows the development team to add features that couldn’t be added in requirement and design phase. • In this, developers will focus and develop only those parts of the system which they understand perfectly.
  • 17. Evolutionary Prototyping • The developer will not implement a poorly understood feature to help minimize risk. • Once the partial system is done, it is sent to customer sites so that they can detect opportunities for new featured. • These new features are then implemented by the developers. • Software design is updated and code is retested.
  • 18. Thank You Amandeep Singh Rochna Dhatwalia