developing a complete semantic and service-level understanding of
your domain. Although the work required is pretty straightforward,
the amount of effort and time required is typically huge, and the
enabling technology or tools currently available are complex and
still emerging. So it pays to spend some time up front planning
exactly how you're going to do this step and what tools you may use
to make this job easier.
Why are we doing this? Because you can't deal with information you don
't understand, including information bound to behavior in
applications or existing services. It's extremely important for you
to identify all application semantics -- metadata, if you will -- and
services that exist in your domain so that you can properly deal with
the data and services that are there and understand the inner
workings as well. Remember, the goal here is to create a service-
level abstraction of existing systems, and at this point, you're
merely figuring out what's there.
The data landscape
An understanding of application semantics establishes the way and
form in which a particular application refers to properties of the
business process. For example, the very same customer number for one
application may have a completely different value and meaning in
another application.
Understanding the semantics of an application guarantees that there
will be no contradictory information when the application is
integrated with other applications at the information or service
levels -- which is really what SOA is all about. Achieving consistent
application semantics requires an application integration "Rosetta
stone," and as such represents one of the major challenges to
creating your SOA.
Defining application semantics is a tough job, because many of the
existing systems you'll be dealing with are older, proprietary, or
both. The first step in identifying and locating semantics is to
create a list of candidate systems. This list will make it possible
to determine which data repositories exist in support of those
candidate systems.>>
You can read this in full at:
<http://www.infoworld.com/article/06/05/08/77713_19FEsoalife3_1.html?
source=NLC-SOA2006-05-11>
Gervas
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
