1. 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

2. 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

3. The
HierarchyBusiness or
Product Domain
World view
Domain of interest
Domain view
System element
Element view
Detailed view
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

4. Business Process Engineering
t uses an integrated set of procedures,
methods, and tools to identify how
information systems can best meet the
strategic goals of an enterprise
t focuses first on the enterprise and then on
the business area
t creates enterprise models, data models and
process models
t 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
4

5. The BPE Hierarchy
t Information strategy planning (ISP)
t strategic goals defined
t success factors/business rules identified
t enterprise model created
t Business area analysis (BAA)
t processes/services modeled
t interrelationships of processes and data
t Application Engineering
t a.k.a ... software engineering
t modeling applications/procedures that address
(BAA) and constraints of ISP
t Construction and delivery
t 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
5

6. Information Strategy
t ManagementPlanning
issues
tdefine strategic business
goals/objectives
tisolate critical success factors
tconduct analysis of technology impact
tperform analysis of strategic systems
t Technical issues
tcreate a top-level data model
tcluster by business/organizational area
trefine 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
6

7. Defining Objectives and Goals
t Objective—general statement of direction
t Goal—defines measurable objective: “reduce
manufactured cost of our product”
tSubgoals:
Á 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
t 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
7

8. Business Area Analysis
t define “naturally cohesive groupings of
business functions and data” (Martin)
t perform many of the same activities as ISP,
but narrow scope to individual business area
t identify existing (old) information systems /
determine compatibility with new ISP model
tdefine systems that are problematic
tdefining systems that are incompatible
with new information model
tbegin 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
8

9. The BAA
admin.
Process
manufacturing
sales QC distribution
acct eng’ring
Process
Decomp. Matrices
Process Diagram e.g.,
Flow Data entity/process
Models Model 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
9

10. Product
Engineering The complete
product System analysis
(World view)
capabilities
hardware software Component
engineering
(Domain view)
Processing requirement
data function behavior
Analysis & Design
Modeling
(Element view)
program
component Software
Engineering
Construction
&
Integration
(Detailed view)
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

11. Requirements
Engineering
t Elicitation — determining what the customer
requires
t Analysis & negotiation — understanding the
relationships among various customer
requirements and shaping those relationships
to achieve a successful result
t 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
11

12. Requirements
Engineering
t System Modeling — building a representation
of requirements that can be assessed for
correctness, completeness, and consistency
t Validation — reviewing the model
t 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
12

13. Product Architecture
Template
user interface processing
input process and control output
processing functions processing
maintenance and self-test
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

14. Architecture Flow
operator
interface
Diagram
operator requests CLSS queries, reports, displays
operator
interface
subsystem
bar code acquisition request
shunt control status
sorting reports
CLSS processing & control report timing/location data
requests
part shunt shunt
bar code bar code number control controller
reader decoding subsystem
subsystem subsystem
raw bar bin
code data shunt commands
location
bar code
data base
access
subsystem report CLSS reports
line
sensor data speed key formating
acquisition subsystem
subsystem sort records
mainframe
communications
BCR status driver
diagnostics shunt status
pulse tach input sensor status
subsystem formated
communications status reporting data
data acquisition bar code
interface reader status diagnostic interface output interface
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