Software Engineering

Process Models

Yoones A. Sekhavat, Ph.D.

Spring 2025
Software Process Model
2.1 The Meaning of Process

• A process: a series of steps involving activities, constraints, and

resources that produce an intended output of some kind
• A process involves a set of tools and techniques
2.1 The Meaning of Process
Process Characteristics

• Prescribes all major process activities

• Uses resources, subject to set of constraints (such as
schedule)
• Produces intermediate and final products
• May be composed of subprocesses with hierarchy or links
• Each process activity has entry and exit criteria
• Activities are organized in sequence, so timing is clear
• Includes goals of each activity
2.1 The Meaning of Process
The Importance of Processes

• Impose consistency and structure on a set of activities

• Guide us to understand, control, examine, and improve the
activities
• Enable us to capture our experiences and pass them along
2.2 Software Process
Models
Reasons for Modelling a Process
• To form a common understanding
• To find inconsistencies, redundancies, omissions
• To find and evaluate appropriate activities for reaching process
goals
• To tailor a general process for a particular situation in which it
will be used
 2.2 Software Process Models
Software Life Cycle

• When a process involves building a software, the process may be referred to as

software life cycle

• Requirements analysis and definition

• System (architecture) design
• Program (detailed/procedural) design
• Writing programs (coding/implementation)
• Testing: unit, integration, system
• System delivery (deployment)
• Maintenance
2.2 Software Process
Models
Software Development Process Models

• Waterfall model
• V model
• Prototyping model
• Phased development: increments and iteration
• Spiral model
• Agile methods
2.2 Software Process
Models
Waterfall Model
• One of the first process development models proposed
• Works for well understood problems with minimal or no changes in
the requirements
• Simple and easy to explain to customers
• It presents
• a very high-level view of the development process
• sequence of process activities
• Each major phase is marked by milestones and deliverables
(artifacts)
2.2 Software Process
Models
Waterfall Model (continued)
2.2 Software Process
Models
Drawbacks of The Waterfall Model
• Views software development as manufacturing process
• No guidance how to handle changes to products and activities
during development
• There is no iteration
• The clients may not know the requirements
• Changing requirements in later stages cause increased overall
project cost
• Long wait before a final product
2.2 Software Process
Models
V Model
• A variation of the waterfall model
• Uses unit testing to verify module design
• Uses integration testing to verify system design
• Uses acceptance testing to validate the requirements
• If problems are found during verification and validation, the left
side of the V can be re-executed before testing on the right
side is re-enacted
• Adoption by medical device industry
2.2 Software Process
Models
V Model (continued)
2.2 Software Process
Models
Drawbacks of The V Model
• Has similar drawbacks as the waterfall model
• Too simple - may not reflect the software process
accurately
• Use of inefficient and ineffective testing techniques
• Rigid link between left-side and right-side
(acceptance testing corresponds to the user
requirements)
2.2 Software Process
Models
Prototyping Model
• Reduces risk and uncertainty in the development as well as time
and cost
• Online systems and HCI
2.2 Software Process
Models
Drawbacks of The Prototype Model
• Not sufficient analysis (functionality, scalability, maintainability)
• User misunderstanding (prototype vs. final product)
• Developer misunderstanding the user reqs.
• Too much time spent on prototype development
• Increased cost
• Increased involvement and attachment to prototype
2.2 Software Process Models
Phased Development: Increments and
Iterations
• Shorter cycle time
• System delivered in pieces
• enables customers to have some functionality while the rest is
being developed
• Allows two systems functioning in parallel
• the production system (release n): currently being used
• the development system (release n+1): the next version
• Supported by US DoD, NASA
2.2 Software Process
Models
Phased Development: Increments and Iterations
(continued)
2.2 Software Process
Models
Phased Development:
•(continued) Increments and Iterations
Incremental development: starts with small
functional subsystem and adds functionality with
each new release
• Iterative development: starts with full system, then
changes functionality of each subsystem with each
new release
2.2 Software Process
Models
Phased Development: Increments and Iterations
(continued)
• Phased development is desirable for several reasons
• Markets can be created early for functionality that has never before
been offered
• The development team can focus on different areas of expertise
with different releases
• Easier to test and debug
• Regression testing after each iteration
2.2 Software Process
Models
Spiral Model
• Suggested by Boehm (1988)
• Combines development activities with risk management to
minimize and control risks
• The model is presented as a spiral in which each iteration is
represented by a circuit around four major activities
• Plan
• Determine goals, alternatives and constraints
• Evaluate alternatives and risks
• Develop and test
2.2 Software Process
Models
Spiral Model (continued)
 The Unified Process (UP)

elaboration
Elaboration

Inception
inception

23

construction
Release
transition
software increment

production
These slides are designed to accompany Software Engineering: A Practitioner’s
Approach, 7/e (McGraw-Hill, 2009). Slides copyright 2009 by Roger Pressman.
UP
Phases UP Phases
Inception Elaboration Construction Transition Production

Workflows

Requirements

Analysis

24
Design

Implementation

Test

Support

Iterations #1 #2 #n-1 #n

These slides are designed to accompany Software Engineering: A Practitioner’s

Approach, 7/e (McGraw-Hill, 2009). Slides copyright 2009 by Roger Pressman.
 UP Work Products
Inception phase

Elaboration phase
Vision document
Initial use-case model
Initial project glossary
Construction phase
Use-case model
Initial business case Supplementary requirements
Initial risk assessment. including non-functional Design model
Transition phase
Project plan, Analysis model Software components
phases and iterations. Software architecture Delivered software increment
Integrated software
Business model, Description. increment Beta test reports
if necessary. Executable architectural
25 Test plan and procedure General user feedback
One or more prototypes prototype.
I nc ept i o
Test cases
n Preliminary design model Support documentation
Revised risk list user manuals
Project plan including installation manuals
iteration plan description of current
adapted workflows increment
milestones
technical work products
Preliminary user manual

These slides are designed to accompany Software Engineering: A Practitioner’s

Approach, 7/e (McGraw-Hill, 2009). Slides copyright 2009 by Roger Pressman.
2.7 What this Chapter
Means for You

• Process development involves activities, resources,

and product
• Process model includes organizational, functional,
behavioural and other perspectives
• A process model is useful for guiding team
behaviour, coordination and collaboration
Quiz
• Q.1 If requirements are easily understandable and defined then
which model is best suited?

A) Spiral model.
B) Waterfall model.
C) Prototyping model
D) None of the above.

Q.2 Project risk factor is considered in which model.

A) Spiral model.
B) Waterfall model.
C) Prototyping model
D) None of the above.
Quiz
• Q.3 What is the meaning of requirement elicitation in software
engineering?

A) Gathering of requirement.
B) Understanding of requirement.
C) Getting the requirements from client.
D) All of the above.

Q.4 The prototyping model of software development is well suited?

A) When requirements are well defined.

B) For projects with large development teams.
C) When a customer cannot define requirements clearly.
D) None of the above.
References

• http://eceweb1.rutgers.edu/~marsic/books/SE/instructor/slides/
• http://www.cs.ucf.edu/~turgut/COURSES/COP4331C_OOD_Fall19/CO
P4331C_OOD_Fall19.html