[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [soa-rm-ra] Management Concept - update based on Ken's notes
Sorry, was swamped at work and could not make to the meeting,
but put a lot of comments in the doc. From: mpoulin@usa.com
[mailto:mpoulin@usa.com] Gentlemen, I
have attached updated version of the Management Concept where I tried to
address following notes( from Ken): - Need a
clearer connection to having maintainable connections (not just text to be
edited) from service description to collected information needed for
management. Consumers (including those creating compositions) need
information to determine sufficiency of service considering. Management
will have an interpretation of this information but not necessarily the final
word. - Is the term service contract used the
same way as in other parts of the document? This term has a lot of use in
the vendor and user world but little firm understanding beyond the idea that a
WSDL defines an interface. This often gets swallowed in SLAs. I
think we need to take this on at some point and I haven’t checked to see whether
other discussion in sections 3 and 4 are sufficient. - Management to operationalize
governance - Monitoring so you have data from
which to get status and make decisions - Capability to manage seems to require
policies from governance translated to rules and regulations that get to
specifics and then measurement and feedback on the specifics. I think, it would be unnecessary extra work to "Specific things to manage in a SOA ecosystem that weren’t of
consequence in traditional systems". Additionally, I elaborate a little on the relationships between
Service Description and Service Contract in the context of management. The text I added/modified and merged into is in blue in the attached
document. I hope, we will be able to discuss these changes during today
meeting. - Michael -----Original Message----- Michael, I had a chance to look through this and have some overall
comments. -
At line 2318, you added some words on risk but it seems strange
where placed because it’s followed by a list of benefits and then followed
again by a list of risks. Any reason your text shouldn’t be an addition
to the list of risks? -
Need a clearer connection to having maintainable connections (not
just text to be edited) from service description to collected information
needed for management. Consumers (including those creating compositions)
need information to determine sufficiency of service considering.
Management will have an interpretation of this information but not necessarily
the final word. -
In section 5.3, there are a bunch of short blurbs on an endless
set of manageabilities. What I get is life cycle manageability is the
ability to manage life cycles, …, X managemeability is the ability to manage
Xs. Does the elaboration through some 400 lines really add anything that
couldn’t concisely be presented as a bullet list in one page? -
Is the term service contract used the same way as in other parts
of the document? This term has a lot of use in the vendor and user world
but little firm understanding beyond the idea that a WSDL defines an
interface. This often gets swallowed in SLAs. I think we need to
take this on at some point and I haven’t checked to see whether other
discussion in sections 3 and 4 are sufficient. -
In section 5.3.5, the detail on what constitutes infrastructure is
beyond the scope of the RAF. However, the immediately following list of
things needed for service management is thought-provoking, but it should not be
presented as a complete list. -
How is section 5.3.6 different from what is in the section 5.3
life cycle chunk and how should it relate? (Above, I questioned whether
the 5.3 detail is needed.) There seems to be a few things on which we need to focus: -
Management to operationalize governance -
Monitoring so you have data from which to get status and make
decisions -
Specific things to manage in a SOA ecosystem that weren’t of
consequence in traditional systems Capability to manage seems to require policies from governance
translated to rules and regulations that get to specifics and then measurement
and feedback on the specifics. Ken --------------------------------------------------------------------------- Dr. Kenneth Laskey MITRE Corporation, M/S
H305
phone: 703-983-7934 7515 Colshire
Drive
fax: 703-983-1379 McLean VA 22102-7508 The information contained in this communication may be CONFIDENTIAL and is intended only for the use of the recipient(s) named above. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please notify the sender and delete/destroy the original message and any copy of it from your computer or paper files. |
OASIS-RAF_Management_Concept_-_Full_text__2-9-11(1).docx
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]