This document discusses and compares several system development methodologies:
Waterfall methodology is a linear and rigid approach that progresses through requirement analysis, design, implementation, testing, and deployment. Spiral methodology is an adaptive approach involving risk assessment, development and validation, and planning in cycles. Agile methodology emphasizes customer satisfaction, continuous delivery, and regular reviews. Rapid application development aims for fast delivery through object-oriented programming and visual tools.
3. What is System Development
Methodology?
This is a framework that is used to structure plan and
control the process of developing an Information
System.
4. System Development Life Cycle (SDLC)
Planning
Analysis
Design
Development
Implementatio
n
Maintenance
7. Waterfall Methodology:
Waterfall model is very famous method in System Development Methodologies.
This model describes a development methodology, that is rigid and linear.
Logical progression of steps throughout product life cycle
9. Advantages
Progress of System
Development is measurable
Conserves resources
Ideal for supporting less
experience project teams and
project managers
Disadvantages
Difficult to respond to changes
System performance cannot be
tested until the system is almost fully
coded
It has a rigid and inflexible
procedure
One phase must be
completed before the next
phase start
10. Basic Principles :
• Emphasis is on planning, time schedules,
target dates, budgets and implementation
of an entire system at one time.
• Tight control is maintained over the life of
the project through the use of extensive
written documentation, as well as through
formal reviews and approval by the user.
11.
12. Spiral Methodology :
In the "Spiral Model," task regions are divided into four phases. In 1988, Barry
Boehm created the spiral model, which is an adaptive SDLC strategy. It allows a
project to cycle through development processes until the project is finished.
14. Advantages &
Disadvantages
Advantages
High amount of risk analysis
Good for large and mission-critical projects
Software is produced early in the software
cycle
Disadvantages
Can be a costly model to use
Risk analysis requires highly specific
expertise
Project’s success is highly dependent on the
risk analysis phase
15. Basic Principles :
• Focus is on risk assessment and on
minimizing project risk by breaking a
project into smaller segments and
providing more ease-of-change during the
development process, as well as
providing the opportunity to evaluate
risks and weigh consideration of project
continuation throughout the life cycle
16.
17. Agile Methodology
• Agile Software Engineering combines a philosophy and a set of development
guidelines. A team is self-organizing and in control of its destiny. Design, over-
analysis and design are all part of an agile team's development process
19. Advantages &
Disadvantages
Advantages
Re-write to the program, as the client decides to
changes are expected
Additional Functionality can be added at a later
Good for large and mission-critical projects
Disadvantages
Can be a costly model to use
Project’s success is highly dependent on the
risk analysis phase
Risk analysis requires highly specific
expertise
20. Basic Principles :
• Customer Satisfaction - Highest priority
is to satisfy the customer through early
and continuous delivery of valuable
software
• Review the work regularly – At regular
intervals, the team reflects on how to
become more effective, then tunes and
adjusts its behavior accordingly
23. Rapid Application Development Methodology
Rapid Application usually embraces object-oriented programming methodology,
which inherently fosters software re-use. The most popular OOP languages, C++
and Java, are offered in Visual programming packages.
24. Advantages &
Disadvantages
Advantages
High amount of risk analysis
Good for large and mission-critical projects
Software is produced early in the software
cycle
Disadvantages
Can be a costly model to use
Risk analysis requires highly specific
expertise
Project’s success is highly dependent on the
risk analysis phase
25. Basic Principles :
• Key objective is for fast development and
delivery of high-quality systems
• Low investment cost
• Attempts to reduce inherent project risk
by breaking a project into smaller
segments providing more ease-of-
change during the development process