Database Reference
In-Depth Information
Obviously, two new linked frameworks have to be introduced, although there is nothing
new about them; they are as follows:
• The Object Modeling and Design framework must be adopted for proper imple-
mentation of the separation of concerns principle. As a practical outcome of its
application, functional boundaries of the services must be rearranged; autonomy
of the services improved due to resource isolation, if it's possible; and the negat-
ive couplings resolved by the application of logic-to-contract positive coupling.
• The XML Design framework as a support of canonical business model must be
presented. XML message is a serialized transportable representation of the busi-
ness object, encapsulated in service logic. Therefore, this framework in general is
the extension of objects' modeling and design.
It is hard to say which one of these two frameworks is the primary one as both of them
have a particular purpose, that is, to promote the Contract-First design rule as much as
possible. Surely, this design rule is more applicable in the top-down approach when we
have the possibility to design a service from scratch. Redesigning a bulky legacy applica-
tion significantly limits our options, but functional decomposition together with the dis-
cussed ABCS's layer still makes it possible.
The Object Modeling and Design framework
The details of the GF02: Object Modeling and Design framework are as shown in the fol-
lowing table:
Implementation technique
Service models
Required functionality
Avoid the generation of a con-
tract (WSDL) from the service
logic
All service models that include Utility services, Entity Services, Task
Services, and so on (with some limitations for orchestrated services)
Object-to-XML mappings
Identify all service metadata ele-
ments
Flexible XML marshalling
Register metadata elements in
an individual service profile
Support of WS-Security
Persistence support (mapping rela-
tional data to XML and object mod-
el)
Search WWH ::
Custom Search