Software Engineering

By:
Roger S. Pressman, 5th Edition, McGraw
Hill.

Satya Bahadur Maharjan 1

Chapter 1
 Overview

Satya Bahadur Maharjan 2

What is
Software?
Software is: (1) instructions (computer programs)
that when executed provide desired features,
function, and performance; (2) data structures
that enable the programs to adequately manipulate
information and (3) documentation that describes
the operation and use of the programs.

Satya Bahadur Maharjan 3

 What is
Software?
 Software is developed or engineered, it is not
manufactured in the classical sense.
 Software doesn't "wear out."
 Although the industry is moving toward
component-based construction, most software
continues to be custom-built.

Satya Bahadur Maharjan 4

Software
Applications
 system software
 application software
 engineering/scientific
software
 embedded software
 product-line software
 WebApps (Web
applications)
 AI software

Satya Bahadur Maharjan 5

Software—New Categories
 Open world computing— pervasive, distributed
computing. (Cloud computing)
 Netsourcing—the Web as a computing engine
 Open source—”free” source code open to the
computing community
 Also …
 Data mining

 Grid computing

 Cognitive machines

 Software for nanotechnologies

Satya Bahadur Maharjan 6

Legacy Software
Why must it change?
 software must be adapted to meet the
needs of new computing environments
or technology.
 software must be enhanced to
implement new business requirements.
 software must be extended to make it
interoperable with other more modern
systems or databases.
 software must be re-architected to
make it viable within a network
environment.

Satya Bahadur Maharjan 7

Characteristics of
WebApps-I
 Network intensiveness. A WebApp resides on a network and
must serve the needs of a diverse community of clients.
 Concurrency. A large number of users may access the
WebApp at one time.
 Unpredictable load. The number of users of the WebApp may
vary by orders of magnitude from day to day.
 Performance. If a WebApp user must wait too long (for
access, for server-side processing, for client-side formatting
and display), he or she may decide to go elsewhere.
 Availability. Although expectation of 100 percent availability is
unreasonable, users of popular WebApps often demand
access on a “24/7/365” basis.

Satya Bahadur Maharjan 8

Characteristics of
WebApps-II
 Data driven. The primary function of many WebApps is to use
hypermedia to present text, graphics, audio, and video content to
the end-user.
 Content sensitive. The quality and aesthetic nature of content
remains an important determinant of the quality of a WebApp.
 Continuous evolution. Unlike conventional application software
that evolves over a series of planned, chronologically-spaced
releases, Web applications evolve continuously.
 Immediacy. Although immediacy—the compelling need to get
software to market quickly—is a characteristic of many application
domains, WebApps often exhibit a time to market that can be a
matter of a few days or weeks.
 Security. Because WebApps are available via network access, it
is difficult, if not impossible, to limit the population of end-users
who may access the application.

Satya Bahadur Maharjan 9

Software Engineering
 Some realities:
 a concerted effort should be made to understand the
problem before a software solution is developed
 design becomes a key activity
 software should exhibit high quality
 software should be maintainable
 The seminal definition:
 [Software engineering is] the establishment and use of
sound engineering principles in order to obtain
economically software that is reliable and works efficiently
on real machines.

Satya Bahadur Maharjan 10

Software Engineering
 The IEEE definition:
 Software Engineering: (1) The application of a systematic,
disciplined, quantifiable approach to the development,
operation, and maintenance of software; that is, the
application of engineering to software. (2) The study of
approaches as in (1).

Satya Bahadur Maharjan 11

Software Process
It is the set of activities and associated results that
produce a software product.

There are four fundamental process activities:

•Software Specification:
customers and engineers define the software to
be produced and the constraints on its operation.

•Software development:
the software is designed and programmed.

Satya Bahadur Maharjan 12

 Software Process
• Software validation:
the software is checked to ensure that it is what the
customer requires.

• Software evolution:
the software is modified to adapt it to changing
customer and market requirements.

Satya Bahadur Maharjan 13

Software Model
 A software model is a simplification
description of a software process that
presents one view of that process.

 It may include activities that are part of

the software process, software products
and the people involved in software
engineering.

Satya Bahadur Maharjan 14

Software Model
 For Example:
 A workflow model: This shows the
sequence of activities in the process
along with their inputs, outputs and
dependencies. The activities in this model
represent human actions.

 A role/action model: This represents the

roles of the people involved in the
software process and the activities for
which they are responsible.
Satya Bahadur Maharjan 15
Attributes of good
software
 Maintainability:
Software should be maintainable to meet
the changing needs of customer.

 Dependability:
software dependability has a range of
characteristics, including reliability,
security and safety.

Satya Bahadur Maharjan 16

 Efficiency:
Efficiency includes responsiveness,
processing time, memory utilization etc.

 Usability:
software must be usable, without undue
effort, by the type of user for whom it is
designed.

Satya Bahadur Maharjan 17

Professional and
ethical responsibility
 Confidentiality:
The confidentiality of your employers and
clients

 Competence:
You should not misrepresent your level of
competence. You should not knowingly
accept work that is outside your
competence.

Satya Bahadur Maharjan 18

Professional and
ethical responsibility
 Intellectual Property rights:
Should be aware of local laws governing
the use of intellectual property such
as patents and copyright.

Computer misuse:
Use your technical skills to misuse
other people’s computer.

Satya Bahadur Maharjan 19

 Software
Myths
 Affect managers, customers (and
other non-technical stakeholders)
and practitioners
 Are believable because they often
have elements of truth,
but …
 Invariably lead to bad decisions,

therefore …
 Insist on reality as you navigate your
way through software engineering

Satya Bahadur Maharjan 20

How It all Starts
 SafeHome:
 Every software project is precipitated by some
business need—
• the need to correct a defect in an existing application;
• the need to the need to adapt a ‘legacy system’ to a
changing business environment;
• the need to extend the functions and features of an
existing application, or
• the need to create a new product, service, or system.

Satya Bahadur Maharjan 21