OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsdm message

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

Subject: [UArch] concepts diagram and words

In response to my AI [(Igor) to create words to explain the conceptual diagram.], I am providing the following text. Also attached is the MUWS concepts diagram aligned with UML 2.0.

The text describing the MUWS concepts is as follows.

Management using Web services defines how manageability of an arbitrary IT *resource* can be accessed via Web services. A manageable resource is a resource, in other words, manageability is yet another 'qualifity' of the resource. The manageability 'quality' is composed of a number of capabilities. Each capability has its own distinct semantics that could be expressed in a UML model, for example. Therefore manageable resource composes a set of manageability capabilities.

A manageable resource has to be accessible via Web services. The Web services concepts, according to WSDL, are defined as follows. A service is an aggregate of endpoints each offering the service at an address and accessible according to a bidning. A service has a number of interfaces that are realized by all of its endpoints. Each interface descibes a set of named messages that could be exchanged and their format. Properly formatted messages could be sent to an endpoint's address in a way prescribed by the binding. A description (document, artifact) is composed of definitions of interfaces and services. A description may contain both or either of the definitions.

According to the Web services concepts, access to the manageable resource must be provided by an endpoint. Such endpoint is called manageability endpoint. Implicitly, manageability endpoint belongs to a manageability service, which has a number of manageability interfaces that are realized by manageability endpoints. One manageability interface represents one manageability capability and vice versa. In other words, the distinct semantics of a capability is represented (rendered) in a set of possible message exchanges and message formats groupped in an interface.

For example, ability to offer metrics could be captured in a 'Metrics' UML model which is, teherfore, an instance of the manageability capability concept. The semantics of offering metrics could be rendered from the UML model into a WSDL interface description defined in a "urn:wsdm:common:manageability:metrics" namespace. That would be an instance of the manageability interface concept.

Note: changes to the UML diagram are:
- dashed lines changed to dotted lines to express implicit associations. This is vecause dashed lines are used to express dependencies and realizations.
- in a few cases aggregation was changed to composition. This is to avoid explicit existence implications.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788

-----Original Message-----
From: John DeCarlo [mailto:jdecarlo@mitre.org] 
Sent: Thursday, October 23, 2003 12:40 PM
Subject: [wsdm] [UArch] Minutes from 10/23/2003 conference call

Attached is the PDF version of the minutes.  Corrections welcome.



John DeCarlo, The MITRE Corporation, My Views Are My Own
email:      jdecarlo@mitre.org
voice:      703-883-7116
fax:        703-883-3383
DISA cube:  703-882-0593

MUWS Concepts.png

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