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

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

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


Subject: Re: [soa-rm] interesting definition of SOA


For your consideration, other definitions from a different project:

A framework is a set of assumptions, concepts, values, and practices that constitutes a way of viewing the current domain of interest.  For example, a software framework may exist which is defined using object-oriented concepts and states that software built in this framework will have a user interface layer, a service layer, and a resource layer.  The framework might also state the services will adhere to SOAP and WSDL descriptions for Web services. Microsoft defines the .NET Framework as a programming infrastructure for building, deploying, and running applications and services that use .NET technologies.  Mac OS X includes a variety of application frameworks built on top of the traditional UNIX APIs.
 
An architecture is a set of artifacts, i.e. principles, guidelines, policies, models, standards and processes, and the relationships between these artifacts, that guide the selection, creation, and implementation of solutions aligned with business goals. These artifacts are organized into a framework that a) communicates the salient components and properties of the architecture, and b) validates the completeness of the artifacts and their relationships.  To continue the example in the framework definition, the business goals require transparent data access to any data resource;  the architecture would specify that a General Data Access Service must be present and the requirements under which it must successfully support data access.  Any implementation of this architecture could develop independent instances of the service as long as these instances were consistent with the architectural description.

I didn't attempt reference model and you don't want to know what I said about enterprise architecture ;-)

Ken

At 08:13 PM 5/10/2005, Duane Nickull wrote:
SOA is not just an architecture of services seen from a technology perspective, but the policies, practices, and frameworks by which we ensure the right services are provided and consumed.


--
***********
Senior Standards Strategist - Adobe Systems, Inc. - http://www.adobe.com
Chair - OASIS Service Oriented Architecture Reference Model Technical Committee - http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=soa-rm
Vice Chair - UN/CEFACT Bureau Plenary - http://www.unece.org/cefact/
Adobe Enterprise Developer Resources  - http://www.adobe.com/enterprise/developer/main.html
***********

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

*** note: phone number changed 4/15/2005 to 703-983-7934 ***



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