TypesandDatatypes-ISOTC211.docVIP

Datatypes, Interfaces and Types John R. HerringUS/HMMG Introduction Three of the most commonly used stereotypes in the ISO TC 211 Harmonized Model are DataType, Interface, and Type. They represent in different ways, the two sides of an object; datatypes represent state, interfaces represent behavior and types are an interface with a canonical partial state structure. The definitions and descriptions culled from the UML specifications (both UML 1.x and UML 2.0) are: ?DataType? A data type is a type whose values have no identity (i.e., they are pure values). … In the metamodel, a DataType defines a special kind of Classifier in which Operations are all pure functions (i.e., they can return DataValues but they cannot change DataValues, because they have no identity). … A Primitive defines a predefined DataType, without any relevant UML substructure (i.e., it has no UML parts). A primitive datatype may have a logical algebra of operations and constraints defined outside of UML. ?Interface? [A] named set of operations that characterize the behavior of an element. … In the metamodel, an Interface contains a set of Operations that together define a service offered by a Classifier realizing the Interface. A Classifier may offer several services, which means that it may realize several Interfaces, and several Classifiers may realize the same Interface. … Interfaces may not have Attributes, Associations, or Methods. An Interface may participate in an Association provided the Interface cannot see the Association; that is, a Classifier (other than an Interface) may have an Association to an Interface that is navigable from the Classifier but not from the Interface. … All [operations] defined in an Interface are public. ?Type? Specifies a domain of objects together with the operations applicable to the objects, without defining the physical implementation of those objects. A type may not contain any methods, maintain its own thread of control, or be nested. However, it may