0% found this document useful (0 votes)
8 views15 pages

Lecture 10

The document discusses software process activities, highlighting the interleaved nature of technical, collaborative, and managerial tasks involved in software development. It outlines key activities such as specification, design, implementation, validation, and evolution, emphasizing their organization in various development models like waterfall and incremental. Additionally, it covers the requirements engineering process, software validation methods, and the importance of testing throughout the software lifecycle.

Uploaded by

ranahassan7674
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views15 pages

Lecture 10

The document discusses software process activities, highlighting the interleaved nature of technical, collaborative, and managerial tasks involved in software development. It outlines key activities such as specification, design, implementation, validation, and evolution, emphasizing their organization in various development models like waterfall and incremental. Additionally, it covers the requirements engineering process, software validation methods, and the importance of testing throughout the software lifecycle.

Uploaded by

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

Lecture

-10
University of Management & Technology
School of Systems and Technology

Software Engineering
CC-2101

Software Process Activities


Somerville | Ch-2 (Pg.
54)
⮚ 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
Process system.
activitie ⮚ The four basic process activities of
s specification, development, validation
and evolution are organized differently in
different development processes.

⮚ For example, in the waterfall model, they


are organized in sequence, whereas in
incremental development they are
2

interleaved.
The requirements engineering process

3
Software specification
The process of establishing what services are
required and the constraints on the system’s
operation and development.
Requirements elicitation and
analysis
• What do the system
stakeholders require or expect
from the system?
Requirements Requirements specification
engineering process • Defining the requirements in
detail
Requirements validation
• Checking the validity of the
4
requirements
Software design and implementation
The process of converting the system specification
into an executable system.

Design a software structure


Software design that realises the specification;

Translate this structure into an


Implementation 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 Database design,
overall structure of the where you design the
system, the principal system data structures
components (subsystems and how these are to be
or modules), their represented in a
relationships and how database.
they are distributed.

Component selection
Interface design, where and design, where you
you define the interfaces search for reusable
between system components. If
components. unavailable, you design
how it will operate.
7
System implementation
The software is implemented either by developing a
program or programs or by configuring an
application system.

Design and implementation are interleaved activities


for most types of software system.

Programming is an individual activity with no standard


process.

Debugging is the activity of finding program faults and


correcting these faults.
8
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.

9
Stages of testing

10
Testing stages

Component System testing Customer


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

11
Testing phases in a plan-driven software process
(V-model)

12
⮚ Software is inherently flexible and can change.

Softwar ⮚ As requirements change through changing


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

n ⮚ Although there has been a demarcation


between development and evolution
(maintenance) this is increasingly irrelevant as
fewer and fewer systems are completely new.

1
3
System evolution

14
Thankyou
Q&A

15

You might also like