Processes and Process Models

1
 Process - 1
• A process is an organized set of
activities, which transforms inputs to
outputs
• We can use synonyms of process such
as: procedure, method, course of
action, etc.
• Processes are essential for dealing
with complexity in real world
2
 Process - 2
• Processes document the steps in solving a
certain problem

• They allow knowledge to be reused

• They allow people to apply the process in

3
 Examples of Processes - 1
• An instruction manual for operating a
microwave oven

• An instruction manual for assembling a

• A procedure manual for operating a motor

Such a manual describes the

5
 Software Processes
• Software engineering, as a discipline,
has many processes

• These processes help in performing

6
 Software Processes
• Requires creativity
• Provides interactions between a wide
range of different people
• Helps in engineering judgment
• Requires background knowledge
• Experience

7
Examples of Software Processes
• Software engineering development
process (SDLC)
• Requirements engineering process
• Design process
• Quality assurance process
• Change management process

8
Software Requirements Engineering
Process
• Before discussing different aspects of
requirements engineering process, let
us discuss the concept of process
models

9
 Process Models
• A process model is a simplified
description of a process presented
from a particular perspective
• There may be several different models
of the same process
• No single model gives a complete
understanding of the process being
modeled
10
 Variations in Process Models
• A process model is produced on the
anticipated need for that model. We may
need
– A model to help explain how process
information has been organized
– A model to help understand and improve a
process
– A model to satisfy some quality management
standard
11
 Types of Process Model
• Coarse-grain activity models
• Fine-grain activity models
• Role-action models
• Entity-relation models

12
 Coarse-grain Activity Model
• This type of model provides an overall
picture of the process
• Describes the context of different
activities in the process
• It doesn’t document how to enact a
process

13
 Context of Requirements
Engineering
• Software requirements follow the
“system requirements” and “system
design”
• The primary goal is understanding
• Software requirements are followed
by software design in a software
development life cycle
14
 Context of RE Process in
Waterfall Model
System
requirements
engineering Software
requirements
engineering
Software
design
Programming
and
unit testing
System
testing
System
operation

15
Another Perspective on Context
of RE Process

System
acquisition

Requirements
engineering

System
design

16
 Coarse-grain Activity Model of
the Requirements Engineering
Process
• Requirements engineering process is
an example of coarse-grain activity
model

17
 Coarse-grain Activity Model of
the Requirements Engineering
Process

Requirements Requirements
Requirements Requirements
Elicitation Analysis and
Specification Validation
Negotiation

User Needs,
Domain Information, Agreed
Existing System Requirements Requirements
Information, Regulations, Document
Standards, Etc.
18
 Spiral Model of RE Process
Informal statement
of
requirements

Requiremen Requirement
t analysis
elicitation and negotiation
Requirements START Agreed
document and
requirement
validation
s
report

Requirement
Requiremen documentatio
t n
validation
Draft
requirements 19
document
 Fine-grain Activity Models
• These are more detailed models of a
specific process, which are used for
understanding and improving existing
processes
• We’ll discuss some fine-grain
processes within the general
requirements engineering processes in
later lectures
20
 Role-action Models
• These are models, which show the
roles of different people involved in
the process and the actions which they
take

• They are useful for process

• They are useful in quality

22
 Summary
• A process is an organized set of activities
which transforms inputs to outputs, and
they help in coping with complexity in the
world
• Differences between these processes
usually emerge at the level of detailed
description
• A process model is a simplified description
of a process presented from a particular
perspective
23
 References
• ‘Requirements Engineering: Processes
and Techniques’ by G. Kotonya and I.
Sommerville, John Wiley & Sons,
1998

24