EntitySpecification

EntitySpecification : public abstract class

Created:	3/12/2005 12:00:00 AM
Modified:	7/26/2006 6:46:20 PM

Project:
Author:	AutoMagic KB LLC
Version:	6.2
Phase:	SID
Status:	Approved
Complexity:	Medium
Advanced:
UUID:	{72B65D39-4DF6-48b1-B57C-C5E4191AD441}
Appears In:	Specification Generalization Tree, Specification Reduced Generalization Tree, ProductSpec-ServiceSpec-ResourceSpec, ServiceSpec-PhysicalSpec Interaction, Fig 5LR-13 - Resources and ResourceSpecification Overview, Fig 5LR-15 - ResSpecVersion, Fig 5LR-63 - CompoundResourceSpec Biz Model, Fig 5LR-64 - CompoundResourceSpec Subclass Biz Model, PhysicalDeviceRoleSummary, ResourceSpec Inheritance Diagram, Root Business Entities, Entity-EntitySpec Pattern, Figure RA.I19, Fig 30 - BusinessInteraction Specifications, Fig 32 - BusinessContractSpecs and BusinessInteractionSpecs, Fig 33 - Identification Pattern, Fig 34 - Contracts and Identification

Copyright TM Forum 2005 An EntitySpecification is an abstract class that extends the RootEntity class in order to define the invariant attributes in the business view (and methods, constraints, relationships and behavior in the system view) of an Entity. This specification can be used for ManagedEntities as well as UnManagedEntities. In the business view of the SID, the EntitySpecification class is used to define high-level business characteristics and relationships that apply to a Product and the Services and Resources that realize the Product. In the system view of the SID, the EntitySpecification class is also used to specify invariant behavior for instances of a Product and its Services and Resources.

Associations To
Associations From
Other Links

Element	Source Role	Target Role	Details
BusinessContractSpec Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of EntitySpecifications that are used to specify the invariant characteristics and behavior of Entities used in this BusinessContract.<br/></p><p><br/></p><p>Note that part of this specification includes specifying how such Entities are identified.<br/></p>
BusinessInteractionSpecAtomic Class	Name:	Name:

Element	Source Role	Target Role	Details
EntityIdentificationSpec Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of identification formats and acceptable content and behavior that is a part of an overall specification for an EntitySpecification.<br/></p><p><br/></p><p>The cardinality of the aggregate side of this relationship is not 1, since that is a mandatory relationship, and some objects don't have an associated EntitySpecification.<br/></p>
ManagedEntity Class	Name:	Name:	<p>Copyright TM Forum 2006<br/></p><p><br/></p><p>[From SID v6.2 Web Published Model]<br/></p><p><br/></p><p>This association defines the set of ManagedEntities whose invariant attributes, methods, relationships, and constraints are specified by this particular EntitySpecification.<br/></p><p><br/></p><p>Note that a ManagedEntity does not have to be associated with an EntitySpecification. However, if there can be more than one different instantiation of a ManagedEntity, or if several ManagedEntities are related to each other, then the use of this association is highly encouraged. This is because it enables all common characteristics and behavior of different ManagedEntities to be related to each other, and treated as an atomic unit.<br/></p>
EntitySpecCharacteristic Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This composition defines the particular set of important features and behavior, called Characteristics, that distinguishes this EntitySpecification from other EntitySpecifications.<br/></p>
RoleSpecification Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This aggregation defines the set of RoleSpecifications that are used as part of this EntitySpecification. This enables Roles to be used to abstract some, or all, of the functionality of the Entity specified by the EntitySpecification.<br/></p>
Entity Class	Name:	Name:	<p>Copyright TM Forum 2005<br/></p><p><br/></p><p>This association defines the set of Entities, including both ManagedEntities and UnManagedEntiites, whose invariant attributes, methods, relationships, constraints and behavior are specified by this particular EntitySpecification.<br/></p><p><br/></p><p>Note that ManagedEntities as well as UnManagedEntities do not have to be associated with an EntitySpecification. However, if there can be more than one different instantiation of a ManagedEntity (or UnManagedEntity), or if several ManagedEntities (or UnManagedEntities) are related to each other, then the use of this association is highly encouraged. This is because it enables all common characteristics and behavior of different ManagedEntities (or UnManagedEntities) to be related to each other, and treated as an atomic unit.<br/></p>

Object	Type	Connection	Notes
EntityIdentificationSpec	Class	Weak	Copyright TM Forum 2005 This aggregation defines the set of identification formats and acceptable content and behavior that is a part of an overall specification for an EntitySpecification. The cardinality of the aggregate side of this relationship is not 1, since that is a mandatory relationship, and some objects don't have an associated EntitySpecification.
BusinessInteractionSpec	Class	Tree
BusinessContractSpec	Class	Weak	Copyright TM Forum 2005 This aggregation defines the set of EntitySpecifications that are used to specify the invariant characteristics and behavior of Entities used in this BusinessContract. Note that part of this specification includes specifying how such Entities are identified.
Specification	Class	Tree
BusinessInteractionSpecAtomic	Class	Weak
ManagedEntity	Class	Weak	Copyright TM Forum 2006 [From SID v6.2 Web Published Model] This association defines the set of ManagedEntities whose invariant attributes, methods, relationships, and constraints are specified by this particular EntitySpecification. Note that a ManagedEntity does not have to be associated with an EntitySpecification. However, if there can be more than one different instantiation of a ManagedEntity, or if several ManagedEntities are related to each other, then the use of this association is highly encouraged. This is because it enables all common characteristics and behavior of different ManagedEntities to be related to each other, and treated as an atomic unit.
EntitySpecCharacteristic	Class	Strong	Copyright TM Forum 2005 This composition defines the particular set of important features and behavior, called Characteristics, that distinguishes this EntitySpecification from other EntitySpecifications.
RoleSpecification	Class	Weak	Copyright TM Forum 2005 This aggregation defines the set of RoleSpecifications that are used as part of this EntitySpecification. This enables Roles to be used to abstract some, or all, of the functionality of the Entity specified by the EntitySpecification.
Entity	Class	Weak	Copyright TM Forum 2005 This association defines the set of Entities, including both ManagedEntities and UnManagedEntiites, whose invariant attributes, methods, relationships, constraints and behavior are specified by this particular EntitySpecification. Note that ManagedEntities as well as UnManagedEntities do not have to be associated with an EntitySpecification. However, if there can be more than one different instantiation of a ManagedEntity (or UnManagedEntity), or if several ManagedEntities (or UnManagedEntities) are related to each other, then the use of this association is highly encouraged. This is because it enables all common characteristics and behavior of different ManagedEntities (or UnManagedEntities) to be related to each other, and treated as an atomic unit.
ResourceSpecification	Class	Tree
ProductOffering	Class	Generalization