718.
CHAPTER 7
SERVICE-ORIENTED DISCOVERY
AND ANALYSIS: IMPLEMENTATION
MECHANISMS
In our current information technology (IT) world, it is common to find a diverse inventory of
software libraries, components, systems, services, and other third-party partner applications that
keep piling up as time goes by. This growing asset community increases the burden on monitoring
and management efforts and introduces design and architectural challenges. More specifically,
there is a constant struggle to classify our software entities and establish their identities. But
this problem does not pertain only to individual applications or services. A major hindrance
in service-oriented analysis is the difficulty of evaluating groups of service-oriented assets and
identifying their combined contribution to a solution.
This challenge turns out to be even more difficult when it is required to abstract the
general functionality of a service collection. The major questions that are typically asked when
employing more than one service to accomplish a business and technological mission are related
to their collaborative offerings:
??? How can the workload among participating services be subdivided to offer a proper
remedy to a problem?
??? How many services should be employed?
??? What roles should the service-oriented legacy assets play?
??? What should be the ratio between ???new??? (service concepts) and ???old??? (legacy assets)
services that address a solution?
??? What are the best service structural formations that can be employed to provide a viable
business and technological analysis proposition?
??? How are business or technological processes grouped or decoupled?
To efficiently address these concerns and attain essential service analysis milestones, leverage
the set theory1 concept by which entities are treated as group members that share common
attributes.
Pages:
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247