Scribd
Upload
2 views

Copy of Lecture-3

The document discusses software process models, highlighting a generic process model that includes five framework activities: communication, planning, modeling, construction, and deployment, along with several umbrella activities. It specifically details the Waterfall Model, which is a traditional linear approach to software development, emphasizing its advantages in well-understood requirements but also noting its inflexibility to changes, late testing, and delayed delivery. Overall, it outlines the structure and challenges of using prescriptive process models in software engineering.

Uploaded by

legendsday23
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
2 views

Copy of Lecture-3

The document discusses software process models, highlighting a generic process model that includes five framework activities: communication, planning, modeling, construction, and deployment, along with several umbrella activities. It specifically details the Waterfall Model, which is a traditional linear approach to software development, emphasizing its advantages in well-understood requirements but also noting its inflexibility to changes, late testing, and delayed delivery. Overall, it outlines the structure and challenges of using prescriptive process models in software engineering.

Uploaded by

legendsday23
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 10

Lecture 4

Process Models

Software Engineering: A Practitioner’s Approach, 7/e


by Roger S. Pressman
A Generic process Model
 A software process is a
collection of activities, actions,
and tasks that are performed to
create a software product.
 These activities are organized
within a framework or model
that defines their relationships
with each other and with the
overall process.
 The software process consists of
five framework activities
(communication, planning,
modeling, construction, and
deployment)
 several umbrella activities that
are applied throughout the
process.
 The process flow describes how
these activities are organized in
Process Flow
Identifying A Task Set

Actual work that


needs to be done to accomplish the
objectives of a software engineering
action.
Chapter 2
Process Models

Software Engineering: A Practitioner’s Approach, 7/e


by Roger S. Pressman
Prescriptive Process Models

• Traditional process models


• Specialized process models
• Unified Process

(Source: Pressman, R. Software Engineering: A Practitioner’s Approach. McGraw-Hill, 2005)


Traditional Process Models
• Defines a distinct set of activities, actions, tasks,
milestones, and work products that are required to
engineer high-quality software
• The activities can be
– linear,
– incremental,
– evolutionary
Waterfall Model
(Diagram)
Communication
Project initiation
Requirements
gathering
Planning
Estimating
Scheduling
Tracking Modeling
Analysis
Design Construction
Code
Test Deployment
Delivery
Support
Feedback
14
Waterfall Model
(Description)

• Oldest software lifecycle model & best understood


by upper management

• Used when requirements are well understood and


risk is low

• Work flow is in a linear fashion (i.e., sequential)

• Used often with well-defined adaptations or


enhancements to current software
15
Waterfall Model
(Problems)
• Inflexibility to Changes: Once a phase is completed, going
back to make changes is difficult. It is not suitable for
projects where requirements may evolve over time.
• Late Testing and Feedback: Testing happens only after the
development phase is completed, making it harder to identify
and address issues early in the process.
• Delayed Delivery: Since the model follows a sequential
approach, the working product is delivered late, which can
delay user feedback and adjustments.

16

You might also like