Scribd
Upload
21 views16 pages

Lec 5

The document discusses the key activities involved in software processes: specification, development, validation, and evolution. It describes the requirements engineering process of establishing user needs. Design and implementation convert specifications into executable programs. Validation verifies systems meet specifications through testing. Testing has stages from component to acceptance. Evolution maintains software usefulness as requirements change over time. The basic activities are organized differently in process models like waterfall versus incremental development.

Uploaded by

mohammed.riad.bi.2020
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
21 views16 pages

Lec 5

The document discusses the key activities involved in software processes: specification, development, validation, and evolution. It describes the requirements engineering process of establishing user needs. Design and implementation convert specifications into executable programs. Validation verifies systems meet specifications through testing. Testing has stages from component to acceptance. Evolution maintains software usefulness as requirements change over time. The basic activities are organized differently in process models like waterfall versus incremental development.

Uploaded by

mohammed.riad.bi.2020
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Process Activities

Fifth Lecture

By
Dr. Ahmed Majid

1
Process activities

 Real software processes are inter-leaved sequences of


technical, collaborative and managerial activities with the
overall goal of specifying, designing, implementing and
testing a software system.
 The four basic process activities of specification,
development, validation and evolution are organized
differently in different development processes. In the
waterfall model, they are organized in sequence,
whereas in incremental development they are inter-
leaved.

2
Software specification

 The process of establishing what services are required


and the constraints on the system’s operation and
development.
 Requirements engineering process
 Feasibility study
• Is it technically and financially feasible to build the system?
 Requirements elicitation and analysis
• What do the system stakeholders require or expect from the system?
 Requirements specification
• Defining the requirements in detail
 Requirements validation
• Checking the validity of the requirements

3
The requirements engineering process

4
Software design and implementation

 The process of converting the system specification into


an executable system.
 Software design
 Design a software structure that realises the specification;
 Implementation
 Translate this structure into an executable program;
 The activities of design and implementation are closely
related and may be inter-leaved.

5
A general model of the design process

6
Design activities

 Architectural design, where you identify the overall


structure of the system, the principal components
(sometimes called sub-systems or modules), their
relationships and how they are distributed.
 Interface design, where you define the interfaces
between system components.
 Component design, where you take each system
component and design how it will operate.
 Database design, where you design the system data
structures and how these are to be represented in a
database.
7
Software validation

 Verification and validation (V & V) is intended to show


that a system conforms to its specification and meets the
requirements of the system customer.
 Involves checking and review processes and system
testing.
 System testing involves executing the system with test
cases that are derived from the specification of the real
data to be processed by the system.
 Testing is the most commonly used V & V activity.

8
Stages of testing

9
Testing stages

 Development or component testing


 Individual components are tested independently;
 Components may be functions or objects or coherent groupings
of these entities.
 System testing
 Testing of the system as a whole. Testing of emergent properties
is particularly important.
 Acceptance testing
 Testing with customer data to check that the system meets the
customer’s needs.

10
Testing phases in a plan-driven software
process

11
Software evolution

 Software is inherently flexible and can change.

 As requirements change through changing business


circumstances, the software that supports the business
must also evolve and change.

12
System evolution

13
Key points

 Software processes are the activities involved in


producing a software system. Software process models
are abstract representations of these processes.
 General process models describe the organization of
software processes. Examples of these general models
include the ‘waterfall’ model, incremental development,
and reuse-oriented development.

14
Key points

 Requirements engineering is the process of developing a


software specification.
 Design and implementation processes are concerned
with transforming a requirements specification into an
executable software system.
 Software validation is the process of checking that the
system conforms to its specification and that it meets the
real needs of the users of the system.
 Software evolution takes place when you change
existing software systems to meet new requirements.
The software must evolve to remain useful.
15
16

You might also like