Re: [soa-rm] another possible SOA diagram (revised)

[Duane Nickull <dnickull@adobe.com>]

All:

As a point of order, can we please keep all these discussions under the 
thread entitled

[soa-rm] [issue:structure] draft 07, sect 2, line 201,  Figure  2-1]

I would like to suggest that the single most important issue we have to 
do is to get the basic RM diagram completed.  Most of the comments 
relate to this.

For the next call, I will propose on the agenda that most of the call be 
spent on this subject.

Duane

Gregory A. Kohring wrote:

>The comments I made about Core6RM(KJL).pdf apply to Core8RM(JKL).pdf.
>Namely, "Service Interface" is a concretization of the constraints
>appearing in "Contract". As such it is too concrete for a reference
>model.
>
>Also, an SOA should not allow access to resources without going
>through a service. For this reason, you would not want to indicate
>this possibility on a diagram which is intended to illucidate the
>concept of an SOA.
>
>-- Greg
>
>Ken Laskey wrote:
>  
>
>>Chris,
>>
>>My apologies for the sloppy drawing but I was in a meeting and trying to
>>answer quickly.  Please see the attached for something closer to what I
>>intended.  It was still done quickly, so please don't read too much into
>>the details of the dependency lines.
>>
>>Ken
>>
>>At 11:49 AM 5/23/2005, Christopher Bashioum wrote:
>>
>>    
>>
>>>Ken,
>>>
>>>I would have expected the service interface and the resource to be
>>>smaller
>>>boxes inside of the service box.  It looks funny to have the service
>>>off to
>>>the left, and the service interface and resource on top.
>>>
>>>-----Original Message-----
>>>From: Ken Laskey [mailto:klaskey@mitre.org]
>>>Sent: Monday, May 23, 2005 11:13 AM
>>>To: Christopher Bashioum
>>>Cc: 'SOA-RM'
>>>Subject: Re: [soa-rm] another possible SOA diagram (revised)
>>>
>>>The resource is the implementation that in many cases was created to
>>>satisfy needs outside the SOA and only becomes part of a SOA in the
>>>same way that any software package becomes part of your computer.
>>>Opacity says you know there is a resource but the only thing you know
>>>about it is what is exposed through the service description.
>>>
>>>Attached is a very quick attempt to include in Duane's last diagram.
>>>
>>>Ken
>>>      
>>>
>>-- 
>>    
>>---------------------------------------------------------------------------------
>>
>>  /   Ken
>>Laskey                                                                \
>> |    MITRE Corporation, M/S H305    phone:  703-983-7934   |
>> |    7515 Colshire Drive                    fax:      703-983-1379   |
>>  \   McLean VA 22102-7508                                              /
>>   
>>----------------------------------------------------------------------------------
>>
>>    
>>
>
>
>  
>