Software Engineering and

Project Management

21CS61

Module 1
• Software & Software Engineering

• Process Models
Chapter 1

 Software & Software Engineering

Slide Set to accompany

Software Engineering: A Practitionerʼs Approach, 7/e
by Roger S. Pressman

Slides copyright © 1996, 2001, 2005, 2009 by Roger S. Pressman

For non-profit educational use only

May be reproduced ONLY for student use at the university level when used in conjunction
with Software Engineering: A Practitioner's Approach, 7/e. Any other reproduction or use is
prohibited without the express written permission of the author.

All copyright information MUST appear if these slides are posted on a website for student
use.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 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.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 3
Nature of Software
Software takes on a dual role. It is a product, and at the same time,
the vehicle for delivering a product.

(1) Product - Software is an information transformer—producing,

managing, acquiring, modifying, displaying, or transmitting
information

(2) Vehicle - Software acts as the basis for the control of the computer
(operating systems), the communication of information (networks),
and the creation and control of other programs.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 4
 Defining 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.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 5
Wear vs. Deterioration

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 6
Software Applications
 system software
 application software
 engineering/scientific
software
 embedded software
 product-line software
 WebApps (Web
applications)
 AI software

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 7
Software—New Categories
 Open world computing—pervasive, distributed
computing
 Ubiquitous computing—wireless networks
 Netsourcing—the Web as a computing engine
 Open source—”free” 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

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 8
 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.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 9
 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.
 Aesthetics. An undeniable part of the appeal of a WebApp is its look and
feel.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 10
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.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 11
What is Engineering?
Engineering is:

 The branch of science and technology concerned with

the design, building, and use of engines, machines, and
structures.

 It is the application of science, tools and methods to

find cost effective solution to simple and complex
problems.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 12
 Software Engineering
 The IEEE definition:
 Software Engineering: The application of a systematic,
disciplined, quantifiable approach to the development,
operation, and maintenance of software;
 that is, the application of engineering to software.

 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
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 13
A Layered Technology

Software Engineering

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 14
A Layered Technology
 Any engineering approach must rest on an organizational
commitment to quality.

 Process forms the basis for management control of software

projects and establishes the context in which technical methods are
applied, work products are produced, milestones are established,
quality is ensured, and change is properly managed.

 Methods encompass a broad array of tasks that include

communication, requirements analysis, design modeling, program
construction, testing, and support

 Tools provide automated or semi-automated support for the

process and the methods.
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 15
 Software Myths
 Myths are widely held but false beliefs and
views which propagate misinformation and
confusion.

 Three types of myth are associated with

software:

 Management myth
 Customer myth
 Practitioner’s myth

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 16
 Software Myths
 MANAGEMENT MYTHS

 Myth(1) - The available standards and procedures for

software are enough.

 Myth(2) - Each organization feel that they have state-of-art

software development tools since they have latest
computer.

 Myth(3) - Adding more programmers when the work is

behind schedule can catch up.

 Myth(4) - Outsourcing the software project to third party, we

can relax and let that party build it.
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 17
 Software Myths
 CUSTOMER MYTHS
 Myth(1)- General statement of objective is enough to begin
writing programs, the details can be filled in later.
 Myth(2)-Software is easy to change because software is
flexible
 PRACTITIONER’S MYTH
 Myth(1) - Once the program is written, the job has been done.
 Myth(2) - Until the program is running, there is no way of
assessing the quality.
 Myth(3) - The only deliverable work product is the working
program
 Myth(4) - Software Engineering creates voluminous and
unnecessary documentation and invariably slows down
software development.
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 18
The Software Process
 A process is a collection of activities, actions, and tasks that
are performed when some work product is to be created.

 An activity strives to achieve a broad objective (e.g.,

communication with stakeholders) and is applied regardless of the
application domain, size of the project, complexity of the effort.

 An action (e.g., architectural design) encompasses a set of tasks

that produce a major work product (e.g., an architectural design
model).

 A task focuses on a small, but well-defined objective (e.g.,

conducting a unit test) that produces a tangible outcome.
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 19
 A Process Framework

• A process framework establishes the foundation for a complete

software engineering process by identifying a small number of
framework activities that are applicable to all software projects.
• The process framework encompasses a set of umbrella activities that
are applicable across the entire software process.
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e 20
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
 Framework Activities
 Communication
 Planning
 Modeling
 Analysis of requirements
 Design
 Construction
 Code generation
 Testing
 Deployment

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 21
 Umbrella Activities
 Software project management
 Formal technical reviews
 Software quality assurance
 Software configuration management
 Work product preparation and production
 Reusability management
 Measurement
 Risk management

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 22
 Adapting a Process Model

 the overall flow of activities, actions, and tasks and the

interdependencies among them
 the degree to which actions and tasks are defined within each
framework activity
 the degree to which work products are identified and
required
 the manner which quality assurance activities are applied
 the manner in which project tracking and control activities are
applied
 the overall degree of detail and rigor with which the
process is described
 the degree to which the customer and other stakeholders are
involved with the project
 the level of autonomy given to the software team
 the degree to which team organization and roles are
prescribed These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e 23
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
The Essence of Practice

 Polya suggests:
1. Understand the problem (communication and analysis).
2. Plan a solution (modeling and software design).
3. Carry out the plan (code generation).
4. Examine the result for accuracy (testing and quality assurance).

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 24
 Understand the Problem

 Who has a stake in the solution to the problem? That is,

who are the stakeholders?

 What are the unknowns? What data, functions, and

features are required to properly solve the problem?

 Can the problem be compartmentalized? Is it possible to

represent smaller problems that may be easier to
understand?

 Can the problem be represented graphically? Can an

analysis model be created?
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 25
 Plan the Solution

 Have you seen similar problems before? Are there patterns that are
recognizable in a potential solution? Is there existing software
that implements the data, functions, and features that are
required?

 Has a similar problem been solved? If so, are elements of the

solution reusable?

 Can subproblems be defined? If so, are solutions readily apparent

for the subproblems?

 Can you represent a solution in a manner that leads to effective

implementation? Can a design model be created?
These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 26
 Carry Out the Plan

 Does the solution conform to the plan? Is source code

traceable to the design model?

 Is each component part of the solution provably correct?

Has the design and code been reviewed, or better,
have correctness proofs been applied to algorithm?

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 27
 Examine the Result

 Is it possible to test each component part of the solution?

Has a reasonable testing strategy been implemented?

 Does the solution produce results that conform to the data,

functions, and features that are required? Has the software
been validated against all stakeholder requirements?

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 28
Hookerʼs General Principles

 1: The Reason It All Exists

 2: KISS (Keep It Simple, Stupid!)
 3: Maintain the Vision
 4: What You Produce, Others Will Consume
 5: Be Open to the Future
 6: Plan Ahead for Reuse
 7: Think!

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 29
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.

These slides are designed to accompany Software Engineering: A Practitionerʼs Approach, 7/e
(McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman. 30