Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Life Cycle
(SDLC)
AMIT K. BHARDWAJ
The System Development Life
Cycle
It was started in the 1960s and 1970s as the first
documented approach to computer systems
development. All the stages of the development
system are thought about, planned, monitored
and Completed. SDLC is the process by which an
Information System comes to life and maintains
its usefulness to a business as it moves from
inception to replacement.
AMIT K. BHARDWAJ
System Development Life
Cycle
Business need - changing business
conditions prompt request for
new/improved computer system
System development - analyse, design
and implement a system to meet the
business need
System installation - move new system
into production
AMIT K. BHARDWAJ
System Development Life
Cycle
System operation - period of active
use
System obsolescence - system no
longer reflects changed business
needs
AMIT K. BHARDWAJ
System Life Cycle - illustration
Need
Obsolete
Develop
Install
Operate
AMIT K. BHARDWAJ
System Development
Challenges
Critical Success Factors for Systems
Development:
effectively meet the stated business needs
build a flexible and maintainable system
AMIT K. BHARDWAJ
Terminologies for the SDLC phases
AMIT K. BHARDWAJ
System Development Life Cycle
(Kendall & Kendall terminology)
Investigation
Identify problems and opportunities
Determine requirements
Analysis
Design
Develop software
System Test
Implement and evaluate
AMIT K. BHARDWAJ
System Development Life Cycle
(Kendall & Kendall terminology)
AMIT K. BHARDWAJ
Systems Development Life Cycle
(Shelly terminology)
Systems planning
Preliminary investigation report
Systems analysis
System requirements document
Systems design
System design specification
Systems implementation
Complete functioning information system
Systems operation and support
Operational information system
AMIT K. BHARDWAJ
SDLC – (Shelly terminology)
AMIT K. BHARDWAJ
Systems Development Life Cycle
Systems planning
Purpose – identify problem’s nature/scope
Systems request – begins the process &
describes desired changes/improvements
Systems planning – includes preliminary
investigation or feasibility study
End product – preliminary investigation report
AMIT K. BHARDWAJ
Systems Development Life Cycle
Systems analysis
Purpose is to learn exactly how the current
system operates
Fact-finding or requirements
determination is used to define all
functions of the current system
AMIT K. BHARDWAJ
Systems Development Life Cycle
Options
Develop a system in-house
Purchase a commercial package
Modify an existing system
Stop development
The end product for this phase is the systems
requirements document
AMIT K. BHARDWAJ
Systems Development Life Cycle
Systems design
Purpose is to satisfy all documented
requirements
Identify all outputs, inputs, files, manual
procedures, & application programs
Avoid misunderstanding through manager and
user involvement
End product is system design specification
AMIT K. BHARDWAJ
Systems Development Life Cycle
Systems implementation
Construct/deliver information system
Prepares functioning, documented system
Write, test, document application programs
User and manager approval obtained
File conversion occurs
Users, managers, IS staff trained to operate and
support the system
Post-implementation evaluation performed
AMIT K. BHARDWAJ
Systems Development Life Cycle
Systems operation and support
New system supports business operations
Maintenance changes correct errors or meet
requirements
Enhancements increase system capability
After several years of operation, systems
experience need for extensive changes
Systems development life cycle ends with
system replacement
AMIT K. BHARDWAJ
System Development Life Cycle illustration
4. Design
6. System Test
5. Develop software
AMIT K. BHARDWAJ
Other Terminology for SDLC phases
AMIT K. BHARDWAJ
System Development Life Cycle
(Powers et al terminology)
Investigation phase
Analysis and General Design phase
Detailed Design and Implementation
phase
Installation phase
Review phase
AMIT K. BHARDWAJ
Investigation phase
Initial investigation
Feasibility study
Financial feasibility
Technical feasibility
Operational feasibility
AMIT K. BHARDWAJ
Analysis and General Design phase
Existing system review
build model of existing system
New system requirements
from User’s point of view
New system design
sufficient information for management to decide
whether to proceed
Implementation and Installation planning
plan to cover next phases
AMIT K. BHARDWAJ
Detailed Design and Implementation
phase
Technical design
for programs (pseudo-code), files, records,
reports, screens
Test specifications and Testing
prepare test plans
Programming and Testing
write and test program code
User Training
System and Acceptance test
by Users, simulating production conditions
AMIT K. BHARDWAJ
Installation phase
File conversion
run programs to convert files into new format
System installation
critical system transition to production
Options for installation are:
Cutover can be abrupt
Operate old and new systems in parallel
(for 2 weeks)
Phase in new system, over time
Install version of the system
AMIT K. BHARDWAJ
Review phase
Development recap
team review of project, for benefit of
future projects
Post implementation review
evaluate how well the system is working
to what extent are project benefits being
achieved?
AMIT K. BHARDWAJ
S D L C Phases (general)
Business Survey
Feasibility
Systems Analysis
Systems Design
Programming
Testing
Implementation
Post Implementation Review
Maintenance
AMIT K. BHARDWAJ
AMIT K. BHARDWAJ
Why have a System Development Life Cycle?
AMIT K. BHARDWAJ
1. Business Survey
Initial broad term report
Estimate:
project cost
project resources (people)
project time
Recommend whether go on to
Feasibility
AMIT K. BHARDWAJ
2. Feasibility
Assess feasibility of the project:
operational feasibility
technical feasibility
financial feasibility
AMIT K. BHARDWAJ
4. Systems Design
Convert User Requirements into
computer terms
Specify
how system will operate
what programs are needed
AMIT K. BHARDWAJ
5. Programming and Design Aim
Convert specifications into program
code
Prepare test plans
for unit testing (individual programs)
AMIT K. BHARDWAJ
5. Programming and Design Aim
Design aim must ensure that the system
is:
Accurate • Implementable
Maintainable • Acceptable
Timely • Flexible
Robust • Economic
Efficient • Secure
Compatible • Portable
AMIT K. BHARDWAJ
6. Testing - make system “bullet
proof”
System Testing & Acceptance
Testing
System Testing
test program as part of the whole
system e.g. new program in whole
payroll system
AMIT K. BHARDWAJ
6. Testing - make system “bullet
proof”
Acceptance Testing
Customers / Users now involved
usually have their own test plans
AMIT K. BHARDWAJ
7. Implementation
Implementation Plan or Update Log
Provides project leader with a list of all:
files - new / amended
screen messages - new / amended
AMIT K. BHARDWAJ
8. Post Implementation
Review
BUILDING of the system is now complete
Development recap
team review - what can be learned from the
project
Post Implementation Review (after 3 or 4
months)
degree to which system meets objectives
often results in recommended improvements
AMIT K. BHARDWAJ
9. Maintenance
Ensure customer changes to the system:
retain quality
adhere to standards and procedures
Now back at the beginning of the SDLC
Size of maintenance change will
determine whether all (or subset of)
phases of the system Development Life
Cycle are required
AMIT K. BHARDWAJ
Life-Cycle Models
AMIT K. BHARDWAJ
Each Phase of SDLC has an
“Output”
Phase Output
Requirements analysis Software Requirements
Specification (SRS),
AMIT K. BHARDWAJ
“Life-Cycle” Models
Single-Version Models
Incremental Models
Single-Version with Prototyping
Iterative Models
AMIT K. BHARDWAJ
“Life-Cycle” Models (1)
Single-Version Models
Waterfall Model
Waterfall Model with “back flow”
“V” model: Integrating testing
AMIT K. BHARDWAJ
Incremental vs. Iterative
These sound similar, and sometimes are
equated.
Subtle difference:
Incremental: add to the product at each phase
Iterative: re-do the product at each phase
Some of the models could be used either way
AMIT K. BHARDWAJ
The Waterfall model
AMIT K. BHARDWAJ
Waterfall Model
Requirements
Design
Implementation
AMIT K. BHARDWAJ
Waterfall Model
AMIT K. BHARDWAJ
Waterfall Model
Traditional life cycle
Analysis, design, code, test & maintenance
AMIT K. BHARDWAJ
Why Not Waterfall?
2. Requirements are not stable/unchanging.
The market changes—constantly.
AMIT K. BHARDWAJ
Why Not Waterfall?
3. The design may need to change during
implementation.
AMIT K. BHARDWAJ
V - Model
AMIT K. BHARDWAJ
V - Model
Each phase has corresponding test or validation counterpart
Requirements Acceptance
Analysis Test
Implementation
AMIT K. BHARDWAJ
V - Model
Client’s Understanding
Level of Detail
Developer’s Understanding
Requirements Acceptance
Low Elicitation Testing
Problem with V-Model:
Client’s Perception is the same as the
Developer’s Perception
System
Analysis
Testing
Project Time
AMIT K. BHARDWAJ
Problems with V - Model
The V model does not model iteration
AMIT K. BHARDWAJ
Boehm Spiral Model
Four major activities
1. Determination of objectives, alternatives,
and constraints
2. Risk analysis and prototyping
3. Waterfall approach to next level product
4. Plan for the next phase cycle:
AMIT K. BHARDWAJ
Boehm Spiral Model
AMIT K. BHARDWAJ
Spiral Model Deals with Iteration
Identify risks
Assign priorities to risks
Develop a series of prototypes for the identified risks
starting with the highest risk.
Use a waterfall model for each prototype
development (“cycle”)
If a risk has successfully been resolved, evaluate the
results of the “cycle” and plan the next round
If a certain risk cannot be resolved, terminate the
project immediately
AMIT K. BHARDWAJ
Limitations of the Waterfall
and Spiral Models
Neither of these model deals well with
frequent change
The Waterfall model assume that once you are
done with a phase, all issues covered in that
phase are closed and cannot be reopened
The Spiral model can deal with change between
phases, but once inside a phase, no change is
allowed
What do you do if change is happening more
frequently? (“The only constant is the
change”)
AMIT K. BHARDWAJ
Rapid Application
Development
RAD is a methodology for compressing
the analysis, design, build, and test
phases into a series of short, iterative
development cycles.
This has a number of distinct
advantages over the traditional
sequential development model.
AMIT K. BHARDWAJ
AMIT K. BHARDWAJ
Rapid Application Development
AMIT K. BHARDWAJ
Rapid Application Development
Like prototyping, uses iterative
development
Uses tools to speed up development
GUI
reusable code
code generation
programming, language testing and debugging
AMIT K. BHARDWAJ
Rapid Application Development
AMIT K. BHARDWAJ
Rapid Application Development
High Speed
High Quality
And Lower Cost
Quality is a primary concept in the RAD
environment. Systems developed using
the RAD development path meet the
needs of their users effectively and
have low maintenance costs.
AMIT K. BHARDWAJ
Prototyping
Preliminary working version of a system (or
one of its parts)
built quickly and inexpensively
using “friendly, powerful” software
reviewed by end users
suggest changes for system improvements.
AMIT K. BHARDWAJ
Prototyping
AMIT K. BHARDWAJ
Prototyping Process
Identify Basic User Requirements
AMIT K. BHARDWAJ
Prototype
*
AMIT K. BHARDWAJ
Prototyping
Prototyping can help to obtain complete
and reliable system requirements
Prototyping process:
iterative
User works with latest version of prototype
to determine the refined requirements
prototype quickly amended (by the User
and systems analyst)
AMIT K. BHARDWAJ
Prototyping tools
Interactive software development tools
Allows designer to quickly:
design screens, create files, data entry
routines,
basic reporting functions
AMIT K. BHARDWAJ
Prototyping and the SDLC
Prototyping goal is to enhance the System
development process. Prototyping focuses
on the Analysis and General Design
phase.
Outcome –
one extreme is prototype actually becomes the
finished system (after many iterations)
other extreme is throw away prototype and
build system using conventional methods
BUT now have very high level of confidence
with accuracy and completeness of User
Requirements
AMIT K. BHARDWAJ
Prototyping
Performing analysis, design, and
implementation phases concurrently,
and repeatedly
Users see system functionality quickly
and provide feedback
Decision maker learns about problem
But can lose gains in repetition
AMIT K. BHARDWAJ
Prototyping
Need
Planning
Analysis
Design
Implementation
Prototype
Prototype Not OK
Prototype OK
System
AMIT K. BHARDWAJ
Uses of Prototyping
Verifying user needs
AMIT K. BHARDWAJ
Uses of Prototyping
Testing a design under varying environments
AMIT K. BHARDWAJ
Prototyping
Proposed Advantages Disadvantages in practice
Improved user Prototypes are used “as is”
Users like it
difficult
Design flaws
Low risk
Poor performance
Avoids over-design
Difficult to manage process
Experimentation
Creates unrealistic
and innovation expectations
Spreads labor to Documentation is difficult
user department
AMIT K. BHARDWAJ
Advantages of Prototyping
Short development time
Low cost
AMIT K. BHARDWAJ
Disadvantages of Prototyping
Gains may be lost in
Thorough understanding information
System’s benefits and costs
Detailed description of information needs
Easy to maintain IS design
Well-tested IS
Well-prepared users
AMIT K. BHARDWAJ
Alternative system development
methodologies
Alternative methodologies to SDLC are:
Structured approaches.
Structured System Analysis & Design
Methodology
Yourdon
Merise
Prototyping.
AMIT K. BHARDWAJ
Alternative system development
methodologies
AMIT K. BHARDWAJ
JAD
AMIT K. BHARDWAJ
OOAD
AMIT K. BHARDWAJ
Review Questions