Chapter 10
System Engineering
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
The Hierarchy
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
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 Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
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 Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
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 Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
Defining Objectives and Goals
Objectivegeneral statement of direction
Goaldefines 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 Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
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 Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
The BAA Process
admin.
manufacturing
sales
QC
distribution
acct
engring
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 Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
Product Engineering
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
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 Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
10
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 Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
11
Product Architecture Template
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
12
Architecture Flow Diagram
These courseware materials are to be used in conjunction with Software Engineering: A Practitioners Approach, 5/e and are
provided with permission by R.S. Pressman & Associates, Inc., copyright 1996, 2001
13