Dr.

Nikita Jain
Associate Professor

7/28/2017 1
⚫ According to Dennis, Wixom, and Tegarden(2009),
”SDLC is the process of understanding how an
information system can support business needs by
designing a system, building it, and delivering it to
users.”(p.2)
⚫ SDLC is a systematic method for organizations to
successfully implement change.
⚫ A systematic strategy for large scale development
projects.
2
 DESIGN &
PLANNING ANALYSIS
DEVELOPMENT

OPERATION & IMPLEMENTATION

SUPPORT

3
  Do a feasibility study and look at options
 Do a project plan
 Review project requests
 Prioritize project requests
 Allocate resources
 Identify project development team

7/28/2017 4
  Analyze by breaking down into
parts(diagram)
 Conduct preliminary investigation
 Perform detailed analysis activities:
 Study current system
 Determine user requirements
 Recommend solution

7/28/2017 5
  Decide if the system will be created in house or outside.

 Identify how will it operate and how it will be used by

end users.

 Re examine the feasibility study done in analysis phase

7/28/2017 6
 System is built purchased and tested

 Training is implemented to end users.

 A technical support plan is put into place.

 Convert to new system

7
 Conduct post-implementation system review

 Identify errors and enhancements

 Monitor system performance

8
 Dr. Nikita Jain
Associate Professor

7/28/2017 1
1. First published model of the SDLC.
2. It is systematic and sequential approach to system development
that progresses through stages like- Analysis, Design, Coding,
Testing and maintenance.
3. The waterfall Model is a linear sequential flow.
4. In this process, progress is seen as flowing steadily downwards
through the phases.
5. The waterfall approach does not define the process to go
back to the previous phase to handle changes in
requirement.
6. They have huge reliance on elaborative documentation to
complete the task.
Requirements analysis and definitions:
 Goals and constrains are established
 Defined in-details and serve as a system
System and software design:
 Partition of hardware and software
 Establishes overall system architecture
Implementation and unit testing:
 Realized as a set of programs
 Verify the unit
Integration and system testing:
 Programs are integrated and tested
 Software system is delivered
Operation and maintenance:
 System is installed and put into practical use
 Advantages
⚫ Easy to explain to the users.
⚫ Structures approach.
⚫ Stages and activities are well
defined.
⚫ Helps to plan and schedule the
project
Disadvantages
⚫ Assumes that the requirements
of a system can be frozen.
⚫ Very difficult to go back to any
stage after it finished.
⚫ A little flexibility and adjusting
scope is difficult and expensive.
 Is is very basic system in which system is built, tested and
reworked based on the feedback.

 Prototyping is defined as the process of developing a working

replication of a product or system that has to be engineered.

 It offers a small-scale facsimile of the end product and is used

for obtaining customer feedback.

 In this model, a prototype of the end product is first

developed, tested, and refined as per customer feedback
repeatedly till a final acceptable prototype is achieved which
forms the basis for developing the final product.
Identify information system
requirements

Build the initial prototype rapidly

Modify the prototype successive

iterations- Test & Revise
 Advantages Disadvantages

⚫ Easier and faster ⚫ Expensive solution

⚫ Can be used for both small and ⚫ User can always make changes,
large scale which is time taking.
⚫ Nominal experience expert can ⚫ Needs to be complete by same
also work on this model. team.
 Proposed by Boohm (1988).
 Best for the business with volatile goals and can easily handle the
complexities in business procedures.
 It is combination of Waterfall technique (systematic and
controlled) & Prototype technique (iterative nature).
 In spiral models mostly large, expensive and complicated projects
are favored.
 Combination of both design and prototyping-in-stage.
 It is like a waterfall model, in essentially the same order, separated
by planning, risk assessment, and the building of prototypes and
simulations.
 Determine objective ,alternatives and constraints:
 Project are defined
 Product are identified and detailed arrangement
plan is drawn up
 Risk are identified alternative strategies
 Evaluate alternatives, identify and resolve risk:
 Risk assessment and reduction for each of the
identified project risk.
 System are developed
 Development and validation after risk evaluation:
 Development model is chosen for system
 Plan next phases:
 Decision made and plans are drawn
 Advantages
 Provides checkpoints.
 Early involvement of
developers.
 Manages risks and develops the
system into phases.
Disadvantages
 High cost and time to reach the
final product.
 Needs special skills to evaluate
the risks and assumptions.
 Highly customized limiting re-
usability
The Rapid Application Development Model was first proposed by IBM in
the 1980s.

The RAD model is a type of incremental process model in which there

is extremely short development cycle. When the requirements are fully
understood and the component-based construction approach is adopted
then the RAD model is used.

Various phases in RAD are Requirements Gathering, Analysis and

Planning, Design, Build or Construction, and finally Deployment.

A software project can be implemented using this model if the project

can be broken down into small modules wherein each module can be
assigned independently to separate teams. These modules can finally be
combined to form the final product to be delivery(time-box) is generally
60-90 days
 Software essentials restructuring

 Prototyping and verification designs

 Integrating all changes in the current model

 Minimizing the efforts of reviewing, testing and

other maintenance.
 Advantages
Disadvantages

 Speed and fast application  Less features due to fast

delivery
 Delivery of quality app.
 High cost
 Before change in env- model is
 Dependency on strong team to
delivered make
 Well versed professionals make  All application are not
it. compatible with RAD