OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-ra message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [soa-rm-ra] Question of Introduction Consistency


I've been playing around with the content of the wiki and the attached is where I have so far gotten with my comments.  I believe it makes some changes to the passage in the current discussion.

My apologies for not putting this directly on the wiki but I can't see just hacking what has already been put there without some consensus that there is value in the changes.

Also, my apologies for attaching this as a Word document but many don't have the software to edit a pdf and I'm not sure of a more useful format.  If there are suggestions on how else I could post this for a wide audience, please suggest away and I'll try to accommodate in the future.

Ken

SOA-RA wiki comments.doc



On Apr 3, 2006, at 9:27 PM, Michael Stiefel wrote:

How about something such as:

A reference architecture is like an abstract machine. It is built
to realize some function and it, in turn, relies on a set of
underlying requirements and properties that must be present for it to perform. In
the case of the SOA RA, its purpose is to enable a system to be a
Service Oriented Architecture. The underlying requirements and properties are the particular technologies and constraints on those technologies that are used to realize a particular SOA. An example of a property is that the architecture be securable. An example of a requirement is that  authentication and auditing  will result in a secure architecture.

A concrete architecture that properly implements the requirements of authentication and auditing will be considered securable.

Michael

At 12:43 PM 4/3/2006, Frank McCabe wrote:
You are right. We should pick a different word here.
Frank
Î
On Apr 2, 2006, at 7:39 AM, Michael Stiefel wrote:

The Introduction to the "Goals, Critical Success Factors and
Requirements starts out::

"A reference architecture is like an abstract machine. It is built
to realize some function and it, in turn, relies on a set of
underlying capabilites that must be present for it to perform. In
the case of the SOA RA, its purpose is to enable a system to be a
Service Oriented Architecture. The underlying capabilities are the
particular technologies that are used to realize the SOA; in
particular technology choices such as Web Service technologies,
implementation technologies are not part of an abstract RA. "

Are we not using the word capability here in a way that is
different from the use of the term in the RM? Here we seem to be
using the word capability to mean underlying technologies. In the
RM we used the term to indicated the underlying functionality that
is exposed through the SOA.

Michael





---
Ken Laskey
MITRE Corporation, M/S H305     phone:  703-983-7934
7515 Colshire Drive                        fax:        703-983-1379
McLean VA 22102-7508





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]