Database Reference
In-Depth Information
Implementation technique
Service models
Required functionality
Complete support of object- and
aspect-oriented programming (by de-
fault)
The following figure explains the table:
This framework is vendor-specific and is only related to the component/service imple-
mentation. Anything will do really, such as Spring Web Services / MVC, the .NET frame-
work, and so on.
For functional decomposition, we will the need combined efforts of business analysts, ser-
vice architects, and technical infrastructure experts for balancing SOA principles dis-
cussed previously with technical feasibility of redesigned services (in order to understand
the physical level of decomposition required). To follow the Contract-First principle, any
SDK is good.
The XML Modeling and Design framework
The third related framework, XML Design, is interrelated to Object Design and primarily
concerned with establishing a canonical business model for the service inventory. This
model is not a single entity; it's a collection of enterprise entities in the form of Enterprise
Business Objects closely related to the existing DB models that describe primary enter-
prise assets such as Order, Invoice, and CargoUnit. One possible source of them is already
mentioned in functional decomposition, which is the oldie but goodie reverse engineering
fashion that can harvest these entities for us. With the top-down approach, these entities
Search WWH ::
Custom Search