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] Service Management Model (simplified)

I'm good with it, too.


At 8:50 AM -0700 6/26/08, Duane Nickull wrote:
>+ me too
>On 25/06/08 7:29 PM, "Francis McCabe" <frankmccabe@mac.com> wrote:
>After some soul searching, :), I decided that the diagram works for me...
>On Jun 25, 2008, at 7:21 PM, Danny Thornton wrote:
>So Manageability Capability would conatain aggregations for 
>Life-cycle Management Capability, Monitoring Management Capability, 
>QoS Managment Capability, and Other Resource Management Capability?
>-------- Original Message --------
>Subject: [soa-rm-ra] Service Management Model (simplified)
>From: "Jeffrey A. Estefan" <jeffrey.a.estefan@jpl.nasa.gov>
>Date: Wed, June 25, 2008 6:39 pm
>To: <soa-rm-ra@lists.oasis-open.org>
>I've uploaded the following candidate Service Management Model to 
>our Kavi site:
>Keeping with our architectural principle of parsimony, I wanted to 
>keep this very simple to start.
>Couple of items of note.
>1) No cardinality is shown.  A one-to-one association between the 
>entities is implied.
>2) Though not shown on the visual model, in the supporting text, we 
>need to differentiate the notion of manageable service (or resource) 
>from managed service (or resource).  A managed service is a 
>manageable service but a manageable service is not necessarily a 
>managed service.  In other words, just because a service has been 
>instrumented so that it can be managed does not mean that it 
>actually is managed.
>3) The supporting text needs to state other examples of manageable 
>resources (e.g., policies & contracts, descriptions, etc.).
>4) I chose not to show on this first diagram the types of 
>manageability capabilities (e.g., lifecycle manageability 
>capability, monitoring manageability capability, QoS manageability 
>capability, etc.).  I figured we could show these in another diagram 
>when we introduce and talk about those specializations of 
>manageability capability.  It could just be a simple inheritance 
>hierarchy starting with the abstract manageability capability.  This 
>helps us simplify the associations.
>The definition of terms can start with the original set Frank 
>started, but we'll need to clean up a few.  For example, I'm 
>suggesting manageable service is not the same as managed service.
>OK.  This should get us started!
>- Jeff
>To unsubscribe from this mail list, you must leave the OASIS TC that 
>generates this mail. You may a link to this group and all your TCs 
>in OASIS 
>Senior Technical Evangelist - Adobe Systems, Inc.
>Duane's World TV Show - 
>Blog - <http://technoracle.blogspot.com>http://technoracle.blogspot.com
>Community Music - <http://www.mix2r.com>http://www.mix2r.com
>My Band - 
>Adobe MAX 2008 - 

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670

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