Software

Engineering

Zaira hassan
Lecturer at sbbu sba
BS IT (16 )
 Reference material

1. Software Engineering 8E by Ian Summerville, Addison Wesley; 8th Edition (2006).

ISBN-10: 0321313798
2. Systems Analysis and Design by Gary B. Shelly, Thomas J. Cashman and Harry J.
Rosenblatt, Course Technology; 7th Edition (2007). ISBN-10: 1423912225
3. Software Engineering: A Practitioner's Approach by Roger S. Pressman, McGraw-
Hill Science/Engineering/Math; 7th Edition (2009). ISBN-10: 0073375977

These slides are designed to accompany Software Engineering: A Practitioners Approach, 7/e (McGraw-Hill
2009). Slides copyright 2009 by Roger Pressman.
Course objective

This course should help you understand theories, methods, and technologies applied for
professional software development.
This lecture
Introduction
Software

Software engineering

Myths & its reality

Software process
Introduction to software engineering
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
 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
Wear vs. Deterioration
Software products
Generic products
Stand-alone systems that are marketed and sold to any customer who wishes to buy them.
Examples PC software such as editing, graphics programs, project management tools;
CAD software; software for specific markets such as appointments systems for dentists.

Customized products
Software that is commissioned by a specific customer to meet their own needs.
Examples embedded control systems, air traffic control software, traffic monitoring
systems.
Why Software is Important?
The economies of all developed nations are dependent on
software.

more and more systems are software controlled ( transportation,

medical, telecommunications, military, industrial,
entertainment,)

Expenditure on software represents a significant fraction of

GNP in all developed countries.
 Software Applications
system software

application software

engineering/scientific software

embedded software

product-line software

WebApps (Web applications)

AI software
Software application

1. System software: such as compilers, editors, file management utilities

2. Application software: stand-alone programs for specific needs that run on a
local computer, such as a PC.
3. Engineering/scientific software: Applications range from astronomy to
volcano logy, from automotive to space shuttle orbital dynamics, and from
molecular biology to automated manufacturing Computer-aided design,
system simulation, and other interactive applications etc.
Software application

4 Embedded software resides within a product or system. (key pad control of a microwave oven,
digital function of dashboard display in a car)
5 Product-line software designed to provide a specific capability for use by many different
customers.(computer graphics, business financial applications, database management
6 WebApps (Web applications) network centric software. As web 2.0 emerges, more sophisticated
computing environments is supported integrated with remote database and business applications
7 AI software uses non-numerical algorithm to solve complex problem. Robotics, expert system,
pattern recognition game playing
Essential attributes of good software
Product characteristic

Maintainability

Software should be written in such a way so that it can evolve to meet the changing needs
of customers. This is a critical attribute because software change is an inevitable
requirement of a changing business environment.
Dependability and security
Software dependability includes a range of characteristics including reliability, security
and safety. Dependable software should not cause physical or economic damage in the
event of system failure. Malicious users should not be able to access or damage the
system.
Efficiency
Software should not make wasteful use of system resources such as memory and
processor cycles. Efficiency therefore includes responsiveness, processing time, memory
utilisation, etc.
Acceptability
Software must be acceptable to the type of users for which it is designed. This means that
it must be understandable, usable and compatible with other systems that they use.
SoftwareNew Categories
Open world computingpervasive, distributed
computing
Ubiquitous computingwireless networks
Net sourcingthe Web as a computing engine
Open sourcefree source code open to the
computing community (a blessing, but also a
potential curse!)
Also (see Chapter 31)
Data mining
Grid computing
Cognitive machines
Software for nanotechnologies
 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
Software Engineering
Some realities:
a concerted effort should be made to
understand the problem before a software
solution is developed

design becomes a pivotal activity

software should exhibit high quality

software should be maintainable
 The seminal definition :
[Software engineering is] the establishment and
Software use of sound engineering principles in order to
Engineering obtain economically software that is reliable and
works efficiently on real machines.

SE is an engineering discipline which is concerned

with all aspects of software production and
maintenance...

project management and the development of

tools, methods, etc., to support development and
maintenance.

Software engineering is concerned with theories,

methods and tools for professional software
development.
FAQ about software engineering
Question Answer

What is software? Computer programs, data structures and associated documentation.

Software products may be developed for a particular customer or may be
developed for a general market.

What are the attributes of good software? Good software should deliver the required functionality and performance
to the user and should be maintainable, dependable and usable.

What is software engineering? Software engineering is an engineering discipline that is concerned with
all aspects of software production.

What is the difference between software engineering Computer science focuses on theory and fundamentals; software
and computer science? engineering is concerned with the practicalities of developing and
delivering useful software.

What is the difference between software engineering System engineering is concerned with all aspects of computer-based
and system engineering? systems development including hardware, software and process
engineering. Software engineering is part of this more general process.
Key challenges Coping with increasing variety, demands for reduced
delivery times, and developing software that is
obviously trustworthy. Related issues:
Heterogeneity increasingly, systems are
distributed and include a mix of hardware and
software.
Business and social change there is increasing
pressure for faster delivery of software.
Security and trust as software is intertwined
with all aspects of our lives, it is essential that
we can trust software.
A Layered Technology

tools

methods

process model

a quality focus

Software Engineering
 wrong beliefs about software and the process
that is used to build it.
Affect managers, customers (and other non-
Software Myths technical stakeholders) and practitioners
Are believable because they often have
elements of truth,
but
always lead to bad decisions,
therefore
Insist on reality as you navigate your way
through software engineering
 Myth 1: Once we write the program and get it to work, our job is
Myths and reality done.
Reality: the sooner you begin writing code, the longer it will take
you to get done. 60% to 80% of all efforts are spent after software
is delivered to the customer for the first time.

Myth 2: Until I get the program running, I have no way of

assessing its quality.
Reality: technical review are a quality filter that can be used to find
certain classes of software defects from the inception of a project.

Myth 3: Software engineering will make us create huge and

unnecessary documentation and will always slow us down.
Reality: it is not about creating documents. It is about creating a
quality product. Better quality leads to a reduced rework. Reduced
work results in faster delivery times.
 Myth 4: We already have a book thats full of standards and
Myths and reality procedures for building software. Wont t hat provide my
people with everything they need to know?
Reality: The book of standards may very well exist, but is it
used? Are software practitioners aware of its existence?
Does it reflect modern software engineering practice? Is it
complete? Is it adaptable?

Myth 5: If we get behind schedule, we can add more

programmers and catch up (sometimes called the Mongolian
horde concept).
Reality: Software development is not a mechanistic process
like manufacturing. However, as new people are added,
people who were working must spend time educating the
newcomers.
 A process is a collection of activities, actions and tasks that are
performed when some work product is to be created. It is not a rigid
prescription for how to build computer software. Rather, it is an
adaptable approach that enables the people doing the work to pick
and choose the appropriate set of work actions and tasks.
Software Process
Purpose of process is to deliver software in a timely manner and with
sufficient quality to satisfy those who have sponsored its creation and
those who will use it.
Thank you