Supplementary Slides for
Software Engineering:
A Practitioner's Approach, 5/e
copyright © 1996, 2001
R.S. Pressman & Associates, Inc.
For University Use Only
May be reproduced ONLY for student use at the university level
when used in conjunction with Software Engineering: A Practitioner's Approach.
Any other reproduction or use is expressly prohibited.
This presentation, slides, or hardcopy may NOT be used for
short courses, industry seminars, or consulting purposes.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
1
Chapter 10
System Engineering
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
2
System Engineering
Focuses on a variety of elements,
analyzing, designing, and organizing those
elements into a system that can be a product,
a service, or a technology
for the transformation of information or
control
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
3
System Engineering Process
Called Business Process Engineering when
the engineering work focuses on a business
enterprise
Called Product Engineering when a product is
to be built
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
4
Computer-Based System
A set or arrangement of elements that are
organized to accomplish some predefined
goal by processing information
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
5
System Elements
Software
Hardware
People
Databases
Documentation
Procedures
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
6
The Hierarchy of System Engineering
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
7
Business Process Engineering
Goal: to define architectures that will enable a
business to use information effectively
Three kinds of architectures:
1. Data Architecture
2. Application Architecture
3. Technology Architecture
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
8
Business Process Engineering
uses an integrated set of procedures,
methods, and tools to identify how
information systems can best meet the
strategic goals of an enterprise
focuses first on the enterprise and then on
the business area
creates enterprise models, data models and
process models
creates a framework for better information
management distribution, and control
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
9
The BPE Hierarchy
Information strategy planning (ISP)
 strategic goals defined
 success factors/business rules identified
 enterprise model created
Business area analysis (BAA)
 processes/services modeled
 interrelationships of processes and data
Application Engineering
 a.k.a ... software engineering
 modeling applications/procedures that address
(BAA) and constraints of ISP
Construction and delivery
 using CASE and 4GTs, testing
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
10
Information Strategy Planning
Management issues
define strategic business
goals/objectives
isolate critical success factors
conduct analysis of technology impact
perform analysis of strategic systems
Technical issues
create a top-level data model
cluster by business/organizational
area
refine model and clustering
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
11
Defining Objectives and Goals
Objective—general statement of direction
Goal—defines measurable objective: “reduce
manufactured cost of our product”
Subgoals:
 decrease reject rate by 20% in first 6 months
 gain 10% price concessions from suppliers
 re-engineer 30% of components for ease of
manufacture during first year
objectives tend to be strategic while goals
tend to be tactical
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
12
Business Area Analysis
define “naturally cohesive groupings of
business functions and data” (Martin)
perform many of the same activities as ISP,
but narrow scope to individual business area
identify existing (old) information systems /
determine compatibility with new ISP model
define systems that are problematic
defining systems that are incompatible with new
information model
begin to establish re-engineering priorities
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
13
The BAA Process
admin.
manufacturing
sales
QC
distribution
acct
eng’ring
Process
Flow
Models
Data
Model
Process
Decomp.
Diagram
Matrices
e.g.,
entity/process
matrix
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
14
Business System Design (BSD)
The basic requirements of a specific
information system are modeled and these
requirements are translated into data
architecture, application architecture and
technology architecture
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
15
Construction and Integration
Focuses on implementation detail
Eg. Constructing appropriate database,
building application using software
components, selecting appropriate elements
of technology infrastructure to support the
design created during BSD
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
16
Product Engineering
Goal: to translate the customer’s desire of a
set of defined capabilities into a working
product
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
17
Product Engineering
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
18
Requirements Engineering
Elicitation — determining what the customer
requires
Analysis & negotiation — understanding the
relationships among various customer
requirements and shaping those relationships
to achieve a successful result
Requirements specification — building a
tangible model of requirements
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
19
Requirements Engineering
System Modeling — building a representation
of requirements that can be assessed for
correctness, completeness, and consistency
Validation — reviewing the model
Management — identify, control and track
requirements and the changes that will be
made to them
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
20
Elicitation
Problems of
Scope
Understanding
Volatility
++
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
21
Product Architecture Template
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
22
Architecture Flow Diagram
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001
23