Unit - 2

SDLC and Various Methods: Systems Development Life

Cycle, Various methodologies of IS development, Agile
and Continuous Delivery Models, Design and
Implementation of Innovative Process models.
System
Development
Life Cycle
• What is System
Development Life Cycle?
• A system development life
cycle or SDLC is essentially
a project management
model. It defines different
stages that are necessary to
bring a project from its
initial idea or conception all
the way to deployment and
later maintenance.
7 Stages of the System
Development Life Cycle
There are seven primary stages of the modern system
development life cycle. Here’s a brief breakdown:
• Planning Stage
• Feasibility or Requirements of Analysis Stage
• Design Stage
• Software Development Stage
• Software Testing Stage
• Implementation and Integration
• Maintenance Stage
Planning Stage
• It helps to define the problem and scope of any existing systems, as
well as determine the objectives for their new systems.
• By developing an effective outline for the upcoming development
cycle, they'll theoretically catch problems before they affect
development.
• And help to secure the funding and resources they need to make their
plan happen.
• Perhaps most importantly, the planning stage sets the project
schedule, which can be of key importance if development is for a
commercial product that must be sent to market by a certain time.
Analysis Stage
• The analysis stage includes gathering all the specific details required for a new system
as well as determining the first ideas for prototypes.
• Developers may:
• Define any prototype system requirements
• Evaluate alternatives to existing prototypes
• Perform research and analysis to determine the needs of end-users
• Furthermore, developers will often create a software requirement specification or
SRS document.
• This includes all the specifications for software, hardware, and network requirements
for the system they plan to build. This will prevent them from overdrawing funding or
resources when working at the same place as other development teams.
Design Stage
Developers will first outline the details for the overall application, such as its:
•User interfaces
•System interfaces
•Network and network requirements
•Databases
They’ll typically turn the SRS document they created into a more logical
structure that can later be implemented in a programming language.
Operation, training, and maintenance plans will all be drawn up so that
developers know what they need to do throughout every stage of the cycle
moving forward.
Once complete, development managers will prepare a design document to
be referenced throughout the next phases of the SDLC.
Development Stage
• The development stage is the part where developers actually write
code and build the application according to the earlier design
documents and outlined specifications.
• Product program code is built per the design document specifications.
In theory, all of the prior planning and outlined should make the
actual development phase relatively straightforward.
• Developers will follow any coding guidelines as defined by the
organization and utilize different tools such as compilers, debuggers,
and interpreters.
Testing Stage
• Building software is not the end.
• Now it must be tested to make sure that there aren’t any bugs and
that the end-user experience will not be affected at any point.
• During the testing stage, developers will go over their software with a
fine-tooth comb, noting any bugs or defects that need to be tracked,
fixed, and later retested.
• it’s important that the software overall ends up meeting the quality
standards that were previously defined in the SRS document.
Implementation and Integration
Stage
• After testing, the overall design for the software will come
together. Different modules or designs will be integrated into
the primary source code through developer efforts, usually
by leveraging training environments to detect further errors
or defects.
• The information system will be integrated into its
environment and eventually installed. After passing this
stage, the software is theoretically ready for market and may
be provided to any end-users.
Maintenance Stage
• The SDLC doesn’t end when software reaches the market. Developers
must now move into a maintenance mode and begin practicing any
activities required to handle issues reported by end-users.
• Furthermore, developers are responsible for implementing any
changes that the software might need after deployment.
• This can include handling residual bugs that were not able to be
patched before launch or resolving new issues that crop up due to
user reports. Larger systems may require longer maintenance stages
compared to smaller systems.
1. Waterfall Model
• The classical waterfall model is
the basic
software development life cycl
e
model. It is very simple but
idealistic. Earlier this model
was very popular but
nowadays it is not used. But it
is very important because all
the other software
development life cycle models
are based on the classical
waterfall model.
1. Feasibility Study
• The main goal of this phase is to determine whether it
would be financially and technically feasible to develop
the software.
The feasibility study involves understanding the
problem and then determining the various possible
strategies to solve the problem. These different
identified solutions are analyzed based on their benefits
and drawbacks, The best solution is chosen, and all the
other phases are carried out as per this solution
strategy.
2. Requirements Analysis and Specification
• The aim of the requirement analysis and specification
phase is to understand the exact requirements of the
customer and document them properly.
3. Design Phase:
• This phase aims to transform the requirements gathered into a
suitable form which permits further coding in a programming
language. It defines the overall software architecture together
with high level and detailed design. All this work is
documented as a Software Design Document (SDD).
4. Coding and Unit Testing
• In the coding phase software design is translated into source
code using any suitable programming language. Thus each
designed module is coded. The aim of the unit testing phase is
to check whether each module is working properly or not.
5. Integration and System Testing: This phase
is highly crucial as the quality of the end product
is determined by the effectiveness of the testing
carried out. The better output will lead to satisfied
customers, lower maintenance costs, and
accurate results. Unit testing determines the
efficiency of individual modules. However, in this
phase, the modules are tested for their
interactions with each other and with the system.
6.Operation and maintenance
phase: Maintenance is the task performed by
every user once the software has been delivered
to the customer, installed, and operational.
V-Model
• V model or verification and validation modeling
• V-Modeling represent a development process that
may be considered an extension of the waterfall
model
• In V-Model project development and testing should go
parallel
Advantages of V-Model
• If project is small and easy to understand, V-Model is the best approach
as its easy and simple to use
• Many testing activities are performed in the beginning like planning and
design which saves lots of testing time
• Most of the defects and bugs are found in the beginning of the project
development. So less chances of defects or bug to be occered at final
testing phase.
• Disadvantages
• Guessing the error in the beginning of the project could take more time
• Less flexibility
• Time consuming model- like testing and documentation.
Incremental Model
 In it the whole requirement is divided into many builds.
 Many development cycles take place which makes the life cycle a
multi-waterfall cycle. The cycles are divided up into smaller and more
easily manageable modules.
 Each subsequent release of the module adds function to previous
release.
Advantages of V-Model
• Generates working software quickly and early during the software life
cycle
• This model is more flexible – less costly to change scope and
requirements.
• Its is easier to test and debug during a small iteration
• Lowers initial delivery cost
• Easier to manage risk
Disadvantages
• Need good planning and design
• Needs a clear and complete definition of the whole system before it
can be broken down and built incrementally.
• Total cost is higher than water fall model
Prototype Model
In this model, instead of freezing the
requirements before a design or coding can
proceed, the throw
away prototype is built to understand all the
requirements.
This prototype is developed based on all the
currently known requirements.
Prototype Model
• Advantages:
1. Users are actively involved in the

development.
2. Errors can be detected much earlier.
Disadvantages:
1. Leads to implementing and then
repairing way of building systems.
2. This methodology may increase the
complexity of the system.
Spiral Model
•  It is similar to the incremental model, but
more emphasis is placed on risk analysis.
 The software project repeatedly passes
through these phases in iterations (called
Spirals).
 Each subsequent spirals is build on the
baseline spiral.
Advantages of Spiral Model
• It reduces high amount of risk
• It is good for larger and critical projects.
• Its gives strong approval and documentation control
• In spiral model the software is produced earlier in the life cycle
process
• Disadvantages
• It can be costly to develop a software model
• It is not used for small project
• Project success is highly dependent on the risk analysis phase
Agile methodology
• Process for developing software
• Agile means
• Ability to move quickly
• Responding swiftly to change