???1 He also argued that there are two types of constraints: negotiable
and nonnegotiable. Therefore, he continued, a design process should first identify and classify the
various constraints and thereafter manipulate variables that can comply with the nonnegotiable
constraints.
The service-oriented design model presented obviously must be tuned to business requirements,
technological environments, business strategies, and business models that can be conceived
as nonnegotiable constraints. These aspects must be complied with. An effective design dogma
must also address loosely coupled and distributed software assets and must tackle challenges
that arise because of diverse business formations and complex management. But what are the
negotiable aspects of the service-oriented model? Are these the various opportunities that enable
an agile business landscape? Are these reusability opportunities that can enable an organization to
reduce time-to-market? And are these asset consolidation opportunities that can reduce enterprise
expenditure?
Simply put, the service-oriented design model offers tools and guidance to connect the
dots, meaning that practitioners logically accommodate the need for message routing between
services and their corresponding consumers, devise service collaboration and interface mechanisms,
establish solid service formations that can coexist in a well-coordinated ecosystem, and
manage transactions.
Pages:
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400