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] Re: Suggested Modification For Figure 24 Service Description

The OASIS SOA RM does specify functionality as part of Service Description so I see the importance of maintaining the relationship.

On a DoDAF project I am working now,  functionality is associated with higher level abstractions of the system and capability tends to be associated with lower level service specific details.  I quite like this.  This also flows well when discussing discovery of services based on service capabilities. 

In the Service Description section, we can add a one liner stating service functionality and service capability may be somewhat synonymous when describing a service.

I have a meeting scheduled tomorrow morning from 8 AM to 11 AM so I won't be able to make the call.  Someone will have to take good notes.


--- On Mon, 4/27/09, Ken Laskey <klaskey@mitre.org> wrote:

> From: Ken Laskey <klaskey@mitre.org>
> Subject: [soa-rm-ra] Re: Suggested Modification For Figure 24 Service Description
> To: "danny_thornton2@yahoo.com" <danny_thornton2@yahoo.com>
> Cc: "soa-rm-ra@lists.oasis-open.org RA" <soa-rm-ra@lists.oasis-open.org>
> Date: Monday, April 27, 2009, 4:17 AM
> My concern would be that a SOA service is defined as access
> to one or more capabilities, and having capability in the
> service description model in a different context will likely
> be confusing.  However, would it be useful to change
> Functions to Business Functions?  While this doesn't
> really say anything different, i.e. your business is
> whatever you are interested in doing, it would be consistent
> with an emphasis on the "business" use of SOA.
> Ken
> On Apr 27, 2009, at 3:11 AM, Danny Thornton wrote:
> > 
> > In Figure 24, Service Description, I propose changing
> "Service Functionality" and "Functions"
> to "Service Capability" and
> "Capabilities".  A service can be discovered in a
> registry based on a lookup of capabilities.
> > 
> > I don't think there is a common distinction
> between function and capability, however, I would say that
> function is closely related to requirements and the
> conception of a system while capability is more closely
> related to the description of a service.
> > 
> > Danny
> > 
> > 
> > 
> -----------------------------------------------------------------------------
> Ken Laskey
> MITRE Corporation, M/S H305      phone: 703-983-7934
> 7515 Colshire Drive                         fax:      
> 703-983-1379
> McLean VA 22102-7508
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the
> OASIS TC that
> generates this mail.  Follow this link to all your TCs in
> OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php


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