Information System Development Models
o Waterfall
o V-Model
o Shashimi Model
o Spiral Model
o Unified Process
Why do we need so many models? Can’t we use only one model for all?
Every team, every organizations, and every project is different
- Constraints are also different
Selection of a right model is important for a project
4/13/2023 1
Classification of IS Development Models
Predictive Vs Adaptive
Requirements of the project (product) are known upfront
Changes are not allowed during the development phase
Have an idea but requirements are not clear
Changes are common, outcome can be a new product – more aligned to user’s need
4/13/2023 2
Classification of IS Development Models
Incremental
Building on top
of the existing
product
Requirements are clear, building in increment
Might benefit from intermediate product, feedback can be incorporated
Iterative
Replacing your
product with
something
different
Have an idea but requirements are not clear
4/13/2023 3
Waterfall Model Requirements are well-defined and will not change
Team has experience in building similar product
Translation from requirements to product is perfect
Feasibility
Study Time
Each activity confined to its “phase” -
Analysis Unidirectional
Design
Implement
Testing
Predictive Model Delivery and
Useful for predictive Maintain
and repeatable work
• Simple and easy to understand
• Lacks flexibility for change
• Predictable
• First time release takes a long time
• Efficient – less rework
4/13/2023 4
Waterfall Model (with iterations)
Feasibility
Study
Analysis
Design
Implement
Testing
Delivery and
Maintain
Feedback is incorporated in each
phase to increase flexibility
5
Emphasis on
V-life cycle model parallel testing
at each phase
Project Testing
Project Definition and Validation
Predictive Model
Useful if requirement is
ambiguous and not well-
understood
• Earlier detection of defects
• More upfront work
through parallel testing
4/13/2023 6
Shasimi Model
Next phase can start before finishing the
Feasibility previous phase
Study
Analysis
Design
Implement Mostly Predictive Model
Feedbacks are incorporated
Testing Useful to shorten the time and
Delivery and resource utilization
Maintain
• Shorten the delivery time • May result in rework
• Resource can be utilized
• Can use the feedback early
4/13/2023 7
Incremental Model Build in increments
Increment 1 Increment phase can overlap
Feasibility Study Different models can be used for each
Analysis increment
Design
Implement
Testing
Delivery and Mostly Predictive Model
Maintain Feedbacks can be incorporated
Useful to shorten the time and
Feasibility Study
resource utilization
Analysis
Design Increment 2
Implement
Testing
Delivery and
Maintain • May result in rework
• Can produce value earlier • May cost more
• Can use the feedback early
4/13/2023 8
Spiral Model
Risk analysis is the key part
• Cyclic process
• Four basic steps as in Figure
• All activity need not be performed
4/13/2023 9
Spiral Model
Step 1: Determining Objectives
1. Define Objectives
2. Identify Constraints
3. Find Alternatives
Step 2: Evaluate Risks
1. Identify Risks
2. Resolve risks (partially)
Step 3: Development and Tests
1. Works done to meet objectives
Step 4: Plan for next iteration
1. Review work done and plan for
next iteration
START NEXT CYCLE Process Model Generator
Incorporates other models
4/13/2023 10
Spiral Model
• Risk driven approach
• Four basic activities in every cycle
• Risk determines level and degree of details
• Adaptive • Risk analysis requires special expertise –
• Risk analysis increases chance of might not be economical for small-scale
success projects
• Can apply any model • Need stakeholders' continuous
• Option of go/ no-go engagement
4/13/2023 12
Unified Process
Inception
• Short phase
• Establish business case
• Feasibility study
• Build or buy?
• Preliminary schedule and cost
Milestone: Lifecycle objective
4/13/2023 13
Unified Process
Elaboration
• Capture requirements
• Address known risks
• Validate system architecture
• Executable architecture baseline
Milestone: Lifecycle architecture
4/13/2023 14
Unified Process
Construction
• Largest phase
• Software is built
• Multiple iterations are done with a
release of the product
• Process is iterative and incremental
Milestone: Initial Operational Capability
4/13/2023 15
Unified Process
Transition
• Deployment
• Get feedback and refine
Milestone: Refined system
• It is a framework, incorporates other model
• Use case centric
• Architecture centric
4/13/2023 16
Unified Process
• Bigger and riskier project
• All requirements are not known early
in the project
• Need to deliver value earlier
• Adaptive • Complicated
• Increases chances of success • Need more resources
• Can incorporate other models • Too much overhead of a project
• Risk mitigation
4/13/2023 17
Variants of Unified Process
• Rational Unified Process
• Enterprise Unified Process
• Agile UP – agile focused
4/13/2023 18