Index
A
Application program interfaces (API),
31,
372
Attractive business process model,
28
B
Best practices
impossibility statements,
154
necessity statements,
153
obligation statements,
148
organization models,
95–97
overly large and complex,
63
picking business rules forms,
155
prohibitive statements,
150
restricted permissive statement,
151
restricted possibility statement,
155
solely software activities,
108
Business continuity workshop,
227–228
Business motivations and processes,
128–129
Business transformations,
5–6
Business activity monitoring (BAM),
372–374
Business modeling, xi,
attractive models, appeal of,
27–29
business transformations and,
5–6
enterprise architecture,
38–40
fundamentals
classic business model,
21–22
generating business value, ways of,
10–16
IDEF family of languages,
26
motivation models with,
27
organizational
dynamic and detail complexity,
9–10
rise,
simulation technique,
32–33
enterprise architecture and,
38–40
tools
general-purpose drawing tools,
29–30
publication functionality and API,
31
traceability model,
33–36
ugly business process model,
28
analysis techniques,
31–32
post-merger integration,
285
business purpose
communications of project scope,
12
complexity and simplicity,
191
hierarchy and decomposition,
195–196
iterative modeling process,
190–191
organization chart of,
21
quality of
straight through modeling process,
189–191
tracing two activities,
35
value destruction, analysis,
184–187
Business motivation models,
xii,
23,
38
channel efforts toward,
51
course of action and desired result,
49–50
objectives
strategies and tactics,
50–52
Unisys Corporation case study,
70–76
Business organization models xii,
23,
78
black box organization model,
93
interaction deliverables,
90,
92
project organization model,
85
physical positioning of model elements,
96
white box organization model,
93
business process model notation (BPMN) standard,
132–133
compensation and conditions in,
120–121
flows
default and conditional sequence,
116–117
Business Process Management (BPM),
366
Business Process management systems (BPMS),
360–361,
366
Business Process Monitoring of,
366–368
motivation, relationship to,
169–173
specialization association,
160
tactic sets enforcement level of,
173
Business transformation,
5–6,
104
C
Case studies
ERP systems, case study,
17–18
health insurance company case study,
236–239
Unisys Corporation case study,
70–76
US Customs and Border Protection (CBP) case study,
134–137
actuators, balancing of,
65–66
management discussion,
68
Channel efforts toward,
51
Contributing subject matter expert,
247
D
E
Enterprise architecture (EA),
38–40
Enterprise Resource Planning (ERP),
17–18
F
G
H
Hierarchy and decomposition,
195–196
I
IDEF family of languages,
26
Impossibility rule statement,
153–154
IT alignment and business modeling,
4–5
Iterative modeling process,
190–191
J
resource utilization,
340
K
L
M
Merger integration workshop,
226–227
Model,
missing participants,
259
attendees, personalities in,
251–255
business purposes and strategies,
220–230
business continuity workshop,
227–228
merger integration workshop,
226–227
performance improvement workshop,
228–229
solution rollout workshops,
222–223
system transition workshop,
224
technology alignment workshop,
221–222
participating and contributing subject matter expert,
246–247
scoping and planning,
245
techniques
uses
assumptions validation,
219
persuasion and selling,
218
training and learning,
217
N
O
Objectives
Organization
and motivation models,
97–98
P
Participating subject matter expert,
246–247
Performance improvement workshop,
228–229
Post-merger integration,
285
Prohibitive rule statement,
149–150
Q
R
Regulatory compliance,
144
Restricted permissive rule statement,
150–151
Restricted possibility rule statement,
154–155
external organizations and,
86–88
reporting relationship,
84–85
S
Selective revelation,
95,
193
development, requirements for,
15
software engines, execution,
15
Unified Modeling Language (UML),
Standards
UML,
Straight through modeling process,
189–191
Strategies and tactics,
50–52
System transition workshop,
224
T
Technology alignment workshop,
221–222
tracing two activities,
35
U
V
W