Hi.
I'm also in the progress of creating a SOA Reference Architecture. It's
not an easy task, but I have used the OASIS Reference Model as a
starting point. There is many issues I'm looking into, and some of them
are:
- A more detailed model of a service that makes it possible to use
a common langauge, i.e. relationships between messages, operations,
interface, ports, service and service provider. Seems like an easy
task, but I'm not able to construct a model that satisfies everybody.
E.g should there be a 1-1 relationship between a service and a service
interface (there could be many ports into the same service, but they
all use the same interface) or should a service be able to implement
many interfaces?
- I'm using the above model to create UML 2.0 notation for a
service (I have looked at the UML-profile from Rational / IBM for
services but I'm not found of it).
- A taxonomy for service, i.e. a service layer model and
descriptions of different kinds of services.
- Principles for services
- Patterns for services
The biggest problem, as I see it, is the question about how to apply
the principle of autonomy for services. If you apply this principle you
will get really big services that comes very close to systems in their
own right. It does not fit very well with my layered approach that has
the following layers:
- process layer
- activity layer
- base layer
- utility layer
- application layer
- infrastructure layer
The most important layer is the base layer where services like
products, customers e.t.c will be. If those services should be autonomy
they will be very big, with lots of business logic and maybe even some
process logic. There will not be many services in the activity layer
(we have not identified any services in this layer yet). The process
layer will have have processes that span the big base services. I'm not
sure if this is the right approach. Feedback is appreciated!
Dennis
Brian Mikesell wrote:
Jason,
I'm tasked with the same thing you are, and we, too, are largely an
IBM shop, so maybe we can help each other out on this task.
The approach I'm taking is to define at a very high level what our
most common use cases are. These come down to pretty simple message
exchange patterns such as request/reply, one way, notification, etc.
Out of those patterns, request/reply is our most common, so that's
where I'll focus first.
A reference architecture must satisfy your major use cases and your
non-functional requirements, so I try to define a logical component
model that satisfies these requirements. Major architectural elements
(such as an enterprise service bus) emerge as you look harder at the
non-functionals. Once you get to a certain level of maturity with
your component model, run your use cases through the component
diagram. I'm taking an iterative approach, so I get to a certain
point, run use cases through, review that with a larger group, and
make appropriate changes.
Let me know if that's in-line with your approach. I'm interested in
other ideas.
Brian
--- In [email protected], Jason Lenhart
<[EMAIL PROTECTED]> wrote:
Hello and thank you for starting such a wonderful
group,
I am tasked with creating a SOA Reference Architecture
for my organization.
In reading the OASIS 'Reference Model for Service
Oriented Architecture' has the concept I really
latched onto about 8 months ago (prior to me receiving
this assignment).
Essentially that a Ref. Arch is to identify abstract
solutions to the problem domains in my organization.
That being said - I work in a very large organization
and we have a ton of problem domains (but I suppose
they can be derived easily down to architectural
patterns). I was wondering if anyone had any
direction on this. I also believe that the intent of
this is to outline how our current suites/toolsets
will align (we are an IBM shop).
Any direction is appreciated.
Thank you in advance,
Jason
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Groups gets a make over. See the new email design.
http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/NhFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
__._,_.___
![]()
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___
|
