SE-200

Software Engineering
Dr. Qurat-ul-Ain
Objectives

✓ Software Process
Models – Software
Developments Life
Cycle

✓ Process Activities
 “
Integration &
Configuration

3
Integration and Configuration

❖ Based on software reuse where systems

are integrated from existing components
or application systems
❖ Reused elements may be configured to
adapt their behaviour and functionality to
a user’s requirements
○ lower software production & maintenance
costs
○ faster delivery of systems
○ increased software quality

4
Types of Reusable Software
Stand-alone application systems
(sometimes called COTS) that are
configured for use in a particular
environment.

Collections of objects that are

developed as a package to be
integrated with a component framework
such as .NET or J2EE.

Web services that are developed

according to service standards and
which are available for remote
invocation. 5
Reuse-oriented Software Engineering

Reuse-
oriented SE

Application Object &

Component Concept
system function
reuse reuse
reuse reuse

6
Reuse-oriented Software Engineering
❖ Requirements specification
❖ Software discovery and evaluation
❖ Requirements refinement
❖ Application system configuration
❖ Component adaptation and integration

7
Reuse-oriented Software Engineering
Advantages Disadvantages

1. Reducing the amount 1. Requirements

of software to be compromises and
developed and so this may lead to a
reducing cost and system that does not
risks. meet the real needs
2. It usually also leads of users.
to faster delivery of 2. control over the
the software system evolution is
lost

8
 “
Process Activities

9
Process Activities
❖A structured set of activities required to
develop a software system.
❖ All software processes involve:
Meet customer’s
How will it do? changing need

Design & Validation Evolution

Specification
Implementation

What will system Does it do what

do? customers want? 10
Software Specification
❖ Establishing what services are required

11
Software Design and Implementation
❖ Process to convert system specification
into an executable
❖ Software design
○ Design a software structure that realizes
the specification;
❖ Implementation
○ Translate this structure into an executable
program;

System Software Executable

Specification Structure System

12
Software Design

Design Activity Description

Identify overall structure of the systems & principle
Architectural Design
component

Interface Design Define interfaces between system components

Component Design Design each system component

Database Design Design the system’s data structure and database

13
Software Design

14
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.
15
Software Validation

❖ Verification and Validation (V&V)

○ Checks the system conforms to its
specification

❖ Involves system testing

○ Executing the system with the test cases
derived from real data to be processed by
the system
○ Testing is the most used V&V activity

16
Testing Stages

Component System Acceptance

Testing Testing Testing

❖ Component Testing: individual functions

or objects
❖ System Testing: emergent properties of
system
❖ Acceptance Testing: check system meets
the customer’s need 17
Software Evolution
❖ Software is inherently flexible and can
change

❖ Softwaremust change to meet new

business needs
○ Most of the project’s time and cost

18
How to cope with the
change?
Summary

❖ Process models describe a sequence of

activities:
○ Waterfall model, incremental development,
and reuse-oriented development

❖ Software process are the activities

involved in producing a software system
○ Requirements engineering
○ Design & Implementation
○ Software Validation
○ Software Evolution
20
Thanks!
Any comment/questions?

21