Chris, (01)
Please correct me if I am going astray.... (02)
However, it was my impression (being in the board meetings) that we were
looking for areas in which the TOG could best add value to the SOA
discussion.
As such the definition team (not really a good name) was supposed to define
the elements of the SOA initiative as it related to Boundaryless
Information Flow. As such we are not looking to create the definitive SOA
definition. Potentially the body of work we create will help provide
insight into a greater definition. (03)
As an aside - I don't know many folks in the industry who are enamored with
the OASIS work to date. (04)
Regards, (05)
Andras (06)
Andras Robert Szakal
Chief Architect IBM Federal Software Group
Distinguished Engineer & Senior Certified IT Architect
Member Open Group Board of Directors
Tie Line: 930-9215
External Line: 202-595-1678
text message: andras1@xxxxxxxxx
email: aszakal@xxxxxxxxxx (07)
Ken Laskey
<klaskey@xxxxxxxx
g> To
Service-Oriented Architecture CoP
05/06/2006 01:03 <soa-forum@xxxxxxxxxxxxxx>
AM cc
Andras Szakal/Raleigh/IBM@IBMUS,
"Chris Harding"
<c.harding@xxxxxxxxxxxxx>, Rob
Cardwell
<RCardwell@xxxxxxxxxxxxxx>,
soa@xxxxxxxxxxxxx
Subject
Re: [soa-forum] RE: Definitions of
SOA (08)
Any interesting thread and certainly one that has occurred in numerous
places at numerous times. Again, I'd like to point you to the SOA-RM,
currently going through final editing to incorporate comments from its
60-day public review. The PR version can be downloaded from
http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/16628/wd-soa-rm-pr1.pdf
. It is relatively short and provides compact descriptions of both SOA and
service. As a reference model, it contains a minimum number of concepts
(such as service in the singular) from which more advanced concepts (e.g. a
combination of several services) can be readily derived. So far it has
been found to be fairly robust acting as a basis for the continuing work in
SOA reference architecture. As one of the editors, I'm not exactly
impartial, but for those who haven't seen it, I think it is worth the read. (09)
Back to occasional lurking, (010)
Ken (011)
On May 5, 2006, at 7:11 PM, Charles Mosher wrote: (012)
This could be addressed by generalizing the definition of "customer"
and
"client" to include customers and clients within the organization, as
well as without. And I agree; it is often such internal customers
that
first see the need and ROI for a service-based approach to the
integration of company systems. (013)
I did notice that the concept of service partitioning, i.e., various
specializations of services from the higher level business
process/functional level (perform credit check) to the lower level
(retrieve customer record) is hard to describe with the layers as
they
are depicted. In particular, services which can uniformly serve up
data
(semantically and structurally mediated and rationalized) to business
services that are built on top of them are likely an important first
step to realizing a SOA system. These fundamental services are not
really represented in this architecture, where such detail is
relegated
to the standards/implementation layer. There is the "thinking about
services throughout" admonition, which perhaps ameliorates this
concern
somewhat. (014)
My 2 centavos. (015)
Best regards, (016)
Chuck (017)
-----Original Message-----
From: soa-forum-bounces@xxxxxxxxxxxxxx
[mailto:soa-forum-bounces@xxxxxxxxxxxxxx] On Behalf Of Graham Meaden
Sent: Friday, May 05, 2006 3:33 PM
To: Andras Szakal; Chris Harding
Cc: Service-Oriented Architecture CoP; soa@xxxxxxxxxxxxx
Subject: [soa-forum] RE: Definitions of SOA (018)
FOR CONSIDERATION: (019)
I suggest an alteration to part of the definition enclosed with the
presentation. (020)
Having worked as an Architect for a number of organisations with
50,000+
personnel, the need to flatten organisations, remove silos and
achieve
agility is a perennial theme. For organisations of such size, the
application of a service oriented approach to organisation and
service
design of internal services is as valid to the application of S.O. to
the provisioning of external services. On slide 3, the phrase
<business
layer> "A set of services that an enterprise wants to expose to
customers and clients" seems of exclude applying S.O. to the internal
design of organisations. I believe this to be too prescriptive. I
suggest a change. (021)
Graham Meaden
DIRECTOR, Enterprise Architect (022)
Celestial Consulting Ltd.
Mobile: + 44 7770 672 442
Telephone: + 44 870 421 5601
Facsimile: + 44 20 7900 6547
Email: gmeaden@xxxxxxxxxxxxxxx
Skype id: gmeaden.celestial.co.uk
Skype in: + 44 20 7193 0565 (023)
-----Original Message-----
From: Andras Szakal [mailto:aszakal@xxxxxxxxxx]
Sent: 05 May 2006 14:50
To: Chris Harding
Cc: soa@xxxxxxxxxxxxx; Service-Oriented Architecture CoP
Subject: Re: Definitions of SOA (024)
Team, (025)
I offer this additional chart which depicts the outcome of our
discussion
last week. I am still working the chart but it's a decent start. We
agreed
that SOA is actually only one aspect of this very interesting
industry
initiative that needs our focus. (026)
I think we need to focus on service orientation as a superset of the
SOA
discussion. In fact one could argue that service orientation may be
implemented by a combination of architectural styles and not just
SOA/web
services. (027)
(See attached file: Service_Orientation_Def_v1.ppt) (028)
Regards, (029)
Andras (030)
Andras Robert Szakal
Chief Architect IBM Federal Software Group
Distinguished Engineer & Senior Certified IT Architect
Member Open Group Board of Directors
Tie Line: 930-9215
External Line: 202-595-1678
text message: andras1@xxxxxxxxx
email: aszakal@xxxxxxxxxx (031)
Chris Harding (032)
<c.harding@opengr (033)
oup.org>
To
Service-Oriented Architecture
CoP (034)
05/05/2006 08:31 <soa-forum@xxxxxxxxxxxxxx>, (035)
AM "'Service-Oriented
Architecture (036)
CoP'" <
soa-forum@xxxxxxxxxxxxxx> (037)
cc
soa@xxxxxxxxxxxxx (038)
Subject
Definitions of SOA (039)
Hi - (040)
As a further update, here is the definition of SOA that was presented
at
The Open Group conference last week (and which we have shared with
the
OMG). (041)
SOA is an architectural style that supports service orientation (042)
*Service orientation
A way of a way of thinking in terms of services and service based
development and the outcomes that services bring (043)
*Service
A logical representation of a repeatable business activity that has a
specified outcome (e.g., check customer credit; provide weather data,
consolidate drilling reports), is self-contained and maybe composed
of
other Services. It is a black box to consumers of the Service (044)
*Architectural Style
The combination of distinctive features in which Enterprise
Architecture
is
done, or expressed (045)
*The SOA Architectural style's distinctive features:
- Based on the design of the services comprising an enterprise's
(or inter-enterprise) business processes. Services mirror
real-world
business activity
- Service representation utilizes business descriptions. Service
representation requires providing its context (including
business
process, goal, rule, policy, service interface and service
component)
and service orchestration to implement service
- Has unique requirements on infrastructure. Implementations are
recommended to use open standards, realize interoperability and
location transparency.
- Implementations are environment specific, they are constrained or
enabled by context and must be described within their context.
- Requires strong governance of service representation and
implementation
- Requires a "Litmus Test", which determined a "good service" (046)
At 20:31 04/05/2006, Cory Casanave wrote: (047)
As an update from the OMG meeting last week, the SOA SIG
adopted
the
following definition of SOA; (048)
Service Oriented Architecture is an architectural style for a
community of providers and consumers of services to achieve
mutual
value, that:
Allows participants in the communities to work together
with
minimal co-dependence or technology dependence
Specifies the contracts to which organizations, people
and
technologies must adhere in order to participate in the
community
Provides for business value and business processes to be
realized by the community
Allows for a variety of technology to be used to
facilitate
interactions within the community (049)
The corresponding definition of service has not yet been
finalized
but the sense of the group is that there would be both a
business/domain centric notion of service as well as an
interaction
focused definition. (050)
In both cases this seems to fit well with the notion of SOA
that
is
evolving in this group and in the SOA Demo. (051)
Regards, (052)
Cory Casanave (053)
_________________________________________________________________
Subscribe/Unsubscribe/Config:
http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki:
http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP (054)
Regards, (055)
Chris
+++++ (056)
========================================================================
Dr. Christopher J. Harding
Forum Director for SOA and Semantic Interoperability
THE OPEN GROUP
Thames Tower, 37-45 Station Road, Reading RG1 1LX, UK
Mailto:c.harding@xxxxxxxxxxxxx Phone (mobile): +44 774 063 1520
http://www.opengroup.org
******************************************************************
IT Architecture Practitioners Conference
Hyatt Regency, Coral Gables, FL July 17-19, 2006
Member Meetings - July 17-21, 2006
http://opengroup.org/miami2006/
========================================================================
TOGAF is a trademark of The Open Group (057)
_________________________________________________________________
Subscribe/Unsubscribe/Config:
http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki:
http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP (058)
_________________________________________________________________
Subscribe/Unsubscribe/Config:
http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki:
http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP (059)
---
Ken Laskey
MITRE Corporation, M/S H305 phone: 703-983-7934
7515 Colshire Drive fax: 703-983-1379
McLean VA 22102-7508 (060)
_________________________________________________________________
Subscribe/Unsubscribe/Config: http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP (061)
|