OpenModel Profile v0.2.13: ProfileLifecycle Profile v0.0.4 applied.
This stereotype defines the Open Model specific enhancements for attributes.
This property indicates if the attribute is part of the object key or not. Value = 0 (default) means the attribute is not part of the object key. Values > 0 indicate that the attribute is part of the object key and the value defines the order of the attribute in case the key is composed of more than one attribute. This property defines if the attribute is part of a set of attributes which together (i.e., their values) have to be unique among all instances within a defined context. No value means no uniqueness constraint. An integer value identifies the uniqueness set. An attribute may participate in more than one uniqueness sets.
This property defines at which time the attribute can be set. true = attribute can only be set at creation time; false = attribute can be set at any time.
This property provides the restriction on the attribute values. This optional property indicates if the attribute type is unsigned (value = true) or signed (value = false); if applicable, otherwise ignored. This optional property defines the counter type of the attribute type; if applicable. This optional property contains a textual definition of the unit associated with the attribute value. The spelling of the unit (not only SI units) shall be in accordance to the NIST Publication 811 “Guide for the Use of the International System of Units (SI)” (http://www.nist.gov/pml/pubs/sp811/index.cfm), section 9 “Rules and Style Conventions for Spelling Unit Names”.
This property qualifies the support of the attribute at the management interface.
This attribute contains the condition for the condition-related support qualifiers.
required
This stereotype defines the Open Model specific enhancements for data object classes.
This property qualifies the support of the object class at the management interface.
This attribute contains the condition for the condition-related support qualifiers.
required
This stereotype defines the Open Model specific enhancements for operations.
This property defines whether the operation is idempotent or not. Example: When an operation is going to create an object instance which does already exist, an idempotent operation would return success and a non-idempotent operation would return an exception.
This property identifies if the operation is best effort or is successful / not successful as a whole.
This property qualifies the support of the operation at the management interface.
This attribute contains the condition for the condition-related support qualifiers.
required
This stereotype defines the Open Model specific enhancements for parameters.
This property provides the restriction on the parameter value.
This property qualifies the support of the parameter at the management interface.
This attribute contains the condition for the condition-related support qualifiers.
required
This enumeration defines if a notification (of a specific type) has to be raised when the event occurs.
This literal means that this kind of Notification makes no sense for this object class, e.g., when it is abstract.
This literal means that the object class shall not send this kind of notification.
This literal means that the object class must send this kind of notification.
This stereotype identifies that the association is used to define the naming.
This enumeration defines the list of support qualifiers as defined in ITU-T Recommendation M.3020.
The model element shall be supported.
The model element may, but needs not to, be supported.
The model element shall be supported under certain conditions. If the specified conditions are met then the model element shall be supported.
The model element may, but needs not to, be supported under certain conditions. If the specified conditions are met then the model element may, but needs not to, be supported. If the specified conditions are not met then the model element shall be supported.
Used for model elements that have multiple constraints. Each constraint is worded as a condition for one kind of support, such as mandatory support, optional support or "no support". All constraints must be related to the same kind of support. Specifically: Each model element with C qualification shall have the corresponding multiple constraints defined in the specification. If all specified constraints are met and are related to mandatory, then the model element shall be supported. If all the specified constraints are met and are related to optional, then the model element may, but needs not to, be supported. If all the specified constraints are met and are related to "no support", then the model element shall not be supported.
This stereotype identifies an object class or a data type as a choice between different alternatives.
This stereotype defines a data type used for an operation exception.
This stereotype identifies that the dependency is used to define the naming.
This stereotype can only be applied to associations with a composite end (i.e., composite aggregation association). Means that the content of the "parts" classes is part of the "composed" parent class and has no opportunity for independent lifecycle. In this case although an instance of the "parts" classes can be created and deleted anytime, it has to be in the context of the "composed" parent class. In other words, the parent class instance has to exist and it is NOT possible for the "part" instance to move from one parent instance to another (allowed in regular composition).
This stereotype identifies that the relationship is conditional.
This attribute contains the condition.
This stereotype indicates that the entity is at a very early stage of development and will almost certainly change. The entity is NOT mature enough to be used in implementation.
This stereotype indicates that although the entity may be mature work in the area has indicated that change will be necessary (e.g. there are new insights in the area or there is now perceived benefit to be had from further rationalization). The entity can still be used in implementation but with caution.
This stereotype indicates that the entity is at a relatively early stage of development and is likely to change but is mature enough to be used in implementation.
This stereotype indicates that the entity should not be used in new implementation and that attempts should be made to remove it from existing implementation.
This stereotype indicates that the entity is NOT to be used in implementation and is in the model simply to assist in the understanding of the model (e.g., a specialization of a generalized class where the generalized class is to be used as is and the specialization is simply offered to more easily illustrate an application of the generalized class).
This stereotype indicates that the entity should not be used in new implementation and that attempts should be made to remove it from existing implementation as there is a problem with the entity. An update to the model with corrections will be released.
This stereotype defines the Open Model specific enhancements for interfaces.
This property qualifies the support of the interface at the management interface.
This attribute contains the condition for the condition-related support qualifiers.
required
This stereotype defines the Open Model specific enhancements for notifications.
This property provides the list of conditions that cause the notification.
This property qualifies the support of the notification at the management interface.
This attribute contains the condition for the condition-related support qualifiers. required This stereotype identifies that the realization association is used to identify pruning and refactoring. This stereotype indicates that the entity may become obsolete in the near future. It may still be used in new implementation. This stereotype indicates that the entity is fully developed and can be used in implementations without any constraints. This optional stereotype contains a reference upon which the UML artefact is based. A reference to a standard is preferred. This enumeration contains the defined bit length values. This enumeration contains the defined counter types. This enumeration contains the defined encoding types. This steoreotype indicates a more restrictive form of "StrictComposite" where the "extending" classes will never be explictly instantiated, but that the attributes defined by the “extending” class will be transferred to the class being “extended” at runtime, much like the UML “Generalization” relationship. In other words the "extending" classes are essentially carrying attributes of the “extended” class in a grouping-pack and often referred to as "_Pacs". The “Specify” stereotype is applied on the UML “Abstraction” relationship to indicate that the definition of the more abstract entity class in the abstraction relationship is augmented by the "specification" class definition at runtime. Furthermore there is a potential for an entity class definition to be augmented by more than one "specification" class definitions. In others words, one of the specification classes adds-to and expands the runtime-definition of the entity class. This also implies that the entity class cannot be aware of the existence of specification classes at design time. Since the “Specify” relationship is defined to support runtime code/schema generation and dependency injection, a stereotype-property “target” is defined to point to the actual node being augmented within the object/instance schema. The "target" value should be in the following format: [/<ModelName>:<ClassName>]+:<AttributeName>. Example: TopologyContext in TapiTopology augments Context in TapiCommon target=/TapiCommon:Context:_context Example: NodeEdgePointLpSpec in TapiOdu specifies LayerProtocol definition for NodeEdgePoint in TapiTopology target=/TapiTopology:TopologyContext/TapiTopology:Topology/TapiTopology:Node/Tapi:Topology:NodeEdgePoint/_layerProtocol This property indicates the target of the "Specification". It is recommended that this information is set as the “default” value in the concrete “Specification” class at design/modeling time. This property shall only be applied to attributes or parameters that have an object class as their type. The stereotype identifies that the attribute or the parameter that has the stereotype associated, contains only the identifier(s) of the referred object instance(s) when being transferred across the interface. Otherwise the attribute/parameter contains the complete information of the object instance(s) when being transferred across the interface. This optional stereotype can extend a shared aggregation and indicates a lifecycle dependency between the group instance and the shared part instances; similar to the lifecycle dependency of a composite aggregation. This option is intended to be used only when the shared part object class has another stronger lifecycle dependency (such as composition). The multiplicity at the grouping side of the «LifecycleAggregate» relationship defines the mode: single = exclusive mode, one or more = shared mode. In exclusive mode, a shared part object instance must not be aggregated by more than one group instance via a «LifecycleAggregate» relationship. In shared mode, a shared part object instance can be aggregated by more than one group instance via a «LifecycleAggregate» relationship. In this case, a shared part instance is automatically deleted when the last group instance aggregated the part instance is deleted. This is used by ONAP to indicate that the artifact will be in a Future release. This is used by ONAP to represent a proposal to a model. The "note" must contain the name of the person making the proposal and the associated contribution.