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: [MUWS] text and diagram for the UML section


Title: [MUWS] text and diagram for the UML section

Here it is, modified properly.

[
Each capability is formally expressed in a UML diagram using the following approach.

ole0

Figure 1.        MOWS manageability capability UML sample

Figure 1 expresses that a ManageableXSampleCapabilityY is a concept X manageability capability, which is also a manageability capability in a general, conceptual, sense. The name of the capability identifies the distinct semantics that the capability bears. Semantics is then expressed in properties, operations, events and metadata contained in the capability model representation (UML class).

Properties and operations are expressed as regular UML properties and operations. The meaning of properties and operations is expressed in the text. Properties are defined with and operations act upon the information types that are captured by UML classes. SamplePropertyType1 is an example of such information type. Simple information types may also be used directly when defining properties and operations. For example, xsd:int is an example of a simple information type that belongs to XML Schema Data Types UML package. For simplification of the look of the UML diagrams this document uses a convention that all simple information types which name starts from xsd: belong to that package. XML Schema simple information types (data types) are defined by the W3C specification at http://www.w3.org/TR/xmlschema-2/.

Events are expressed as UML properties with an <<event>> strereotype. Name of the property is the name of the event. Text describes why and when an event occurs and the specific information that is generated (captured) when it occurs. The information type of an event is captured in a UML class which contains proper information element definitions. SampleEventInformationType1 is an example of an event information type.

Optionality of properties and events is indicated by multiplicity of the corresponding model elements: [1] indicates that an element is mandatory, [0..1] indicates that an element is optional. For array properties, [0..*] indicates optional and [1..*] indicates mandatory.

The metadata about various model elements is captured as UML constrains. For example, sampleReadOnlyProperty has an {ro} constraint. This document uses the following common constraints in the models.

]

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

ole0.bmp



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