[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [soa-rm] SOA Diagrams
I liked the approach of the puzzle diagram which shows how that all the concepts fit together within 'SOA.' Although the new diagram appeals to the engineering side of me, I don't think it provides a visual to the less engineering-inclined. I believe 'in for a penny in for a pound' when it comes to working toward our charter. As such, I've strongly advocated that that we consider how the concept of service represents more than just the technologist perspective. Yes, we've restricted ourselves to services w/in the IT realm, and therefore technology is the cornerstone of our work. However, we cannot forget that technology without 'the other stuff' doesn't fill the entire bill. On that note, I've also struggled with the 'service piece' in the center of the puzzle diagram because it seems to go against where we're headed in the RM that recognizes that what is commonly termed 'service' is a culmination of these concepts together. Someone (Matt maybe) also mentioned on a telcon that the positioning of the pieces may suggest specific relationships between the concepts - which may or may not be actually intended relationships. Ok...let me get off my favorite soapbox and put my $$ where my mouth is. Since I've publicly stated that I'm not 100% on board with either graphic, I've engaged with our graphics folks here to come up with an alternative. Rebekah Rebekah Metz Associate Booz Allen Hamilton Voice: (703) 377-1471 Fax: (703) 902-3457 -----Original Message----- From: Ken Laskey [mailto:klaskey@mitre.org] Sent: Tuesday, December 06, 2005 1:00 PM To: Duane Nickull; soa-rm@lists.oasis-open.org Subject: Re: [soa-rm] Diagram Duane, In general, I like the diagram but have a few suggested mods: 1. "Capability Metadata" (not included in current diagram) describes a Capability, Service Description just describes the Service. However, as seems appropriate to the service provider, the Service Description can point to and otherwise reference the Capability Metadata if that is useful in describing the Service. 2. More appropriate to say Service accesses Capability rather than represents. A version hacked in Powerpoint is attached. Ken At 12:24 PM 12/6/2005, Duane Nickull wrote: >I tried to spin the puzzle diagram into a pseudo layered stack. > >D > >******************************* >Adobe Systems, Inc. - http://www.adobe.com >Vice Chair - UN/CEFACT http://www.uncefact.org/ >Chair - OASIS SOA Reference Model Technical Committee >Personal Blog - http://technoracle.blogspot.com/ >******************************* > > -- ------------------------------------------------------------------------ --------- / 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]