Foreword |
|
ix | |
|
Foreword |
|
xi | |
|
Preface |
|
xiii | |
|
|
1 | (30) |
|
|
1 | (2) |
|
Aligning IT with Business - Speaking a Common Language |
|
|
3 | (5) |
|
|
6 | (2) |
|
What is Service Oriented Architecture? |
|
|
8 | (11) |
|
|
16 | (3) |
|
|
19 | (1) |
|
|
20 | (3) |
|
Benefits, Pitfalls and Prospects |
|
|
23 | (3) |
|
|
24 | (1) |
|
|
25 | (1) |
|
|
26 | (1) |
|
|
27 | (3) |
|
|
30 | (1) |
|
Architecture - Objects, Components, Services |
|
|
31 | (40) |
|
|
31 | (11) |
|
Architecture as High Level Structure |
|
|
32 | (5) |
|
Architecture as Design Rationale or Vision |
|
|
37 | (4) |
|
|
41 | (1) |
|
Architecture through the Ages |
|
|
42 | (7) |
|
|
49 | (8) |
|
Components for Flexibility |
|
|
53 | (1) |
|
|
54 | (2) |
|
How Services Relate to Components |
|
|
56 | (1) |
|
|
57 | (6) |
|
|
63 | (3) |
|
Practical Principles for Developing, Maintaining and Exploiting SOA |
|
|
66 | (2) |
|
|
68 | (2) |
|
|
70 | (1) |
|
Approaches to Requirements Engineering |
|
|
71 | (40) |
|
|
71 | (7) |
|
Approaches Based on Human Factors |
|
|
73 | (5) |
|
Classic Requirements versus Use Cases |
|
|
78 | (7) |
|
|
78 | (2) |
|
|
80 | (3) |
|
|
83 | (2) |
|
|
85 | (3) |
|
Requirements and Business Rules |
|
|
88 | (1) |
|
Establishing and Prioritizing the Business Objectives |
|
|
89 | (4) |
|
Soft Techniques for Requirements Elicitation |
|
|
93 | (13) |
|
Using Interviewing Techniques |
|
|
93 | (3) |
|
|
96 | (1) |
|
Hierarchical Task Analysis |
|
|
97 | (4) |
|
Object Discovery Techniques |
|
|
101 | (5) |
|
|
106 | (4) |
|
|
110 | (1) |
|
Business Process Modelling |
|
|
111 | (28) |
|
The Origins of and Need for Business Process Modelling |
|
|
111 | (3) |
|
Business Process Modelling in a Nutshell |
|
|
114 | (2) |
|
|
116 | (2) |
|
|
118 | (9) |
|
Fundamental Business Process Modelling Patterns |
|
|
121 | (3) |
|
|
124 | (3) |
|
|
127 | (2) |
|
Orchestration and Choreography |
|
|
129 | (1) |
|
Process Algebra and Petri Nets |
|
|
130 | (5) |
|
The Human Side of Business Process Management |
|
|
135 | (1) |
|
|
136 | (1) |
|
|
136 | (3) |
|
Catalysis Conversation Analysis |
|
|
139 | (26) |
|
What is a Business Process? |
|
|
139 | (2) |
|
|
141 | (4) |
|
Conversation Stereotypes and Scripts |
|
|
145 | (4) |
|
|
147 | (2) |
|
Conversations as Components |
|
|
149 | (2) |
|
|
151 | (4) |
|
Conversations, Collaborations and Services |
|
|
155 | (5) |
|
Checking Model Consistency |
|
|
160 | (1) |
|
|
161 | (2) |
|
|
163 | (2) |
|
Models of Large Enterprises |
|
|
165 | (16) |
|
Business Process Modelling and SOA in the Large |
|
|
165 | (8) |
|
Business Rules in the Mission Grid |
|
|
173 | (3) |
|
The Mission Grid as a Roadmap for SOA |
|
|
176 | (1) |
|
|
177 | (1) |
|
|
177 | (1) |
|
|
178 | (3) |
|
|
181 | (40) |
|
From Requirements to Specification |
|
|
181 | (1) |
|
Some Problems with the Conventional Approach to Use Cases |
|
|
182 | (7) |
|
Overemphasis on Functional Decomposition |
|
|
183 | (1) |
|
|
183 | (1) |
|
|
184 | (1) |
|
|
184 | (1) |
|
Essential or Generic Use Cases |
|
|
185 | (1) |
|
|
186 | (1) |
|
|
186 | (1) |
|
|
187 | (2) |
|
Describing Boundary Conversations or Use Cases |
|
|
189 | (3) |
|
Establishing the Type Model |
|
|
192 | (6) |
|
|
193 | (5) |
|
Finding Services from State Models |
|
|
198 | (3) |
|
Cartooning Using Agents or Co-ordinators |
|
|
199 | (2) |
|
|
201 | (6) |
|
Ontology, Type Models and Business Rules |
|
|
207 | (5) |
|
|
208 | (4) |
|
Documenting the Specification |
|
|
212 | (1) |
|
Associations, Rules and Encapsulation |
|
|
212 | (6) |
|
Integrity Rules, Rulesets and Encapsulation |
|
|
216 | (2) |
|
|
218 | (2) |
|
|
220 | (1) |
|
|
221 | (8) |
|
|
221 | (3) |
|
|
224 | (1) |
|
Other Miscellaneous Standards |
|
|
224 | (4) |
|
|
228 | (1) |
Appendix A Requirements Engineering and Specification Patterns |
|
229 | (42) |
Appendix B The Fundamental Concepts of Service Oriented Architecture |
|
271 | (10) |
References and Bibliography |
|
281 | (8) |
Index |
|
289 | |