Project:
ServiceSpecification : Public abstract <<TMF_BusinessEntity>> Business Entity
Created:
1/10/2022 12:00:40 PM
Modified:
1/16/2025 11:01:30 AM
Project:
Author:
Giu Platania
Version:
1.0.0
Phase:
24.5.0
Status:
Team Approved
Complexity:
Easy
Difficulty:
Priority:
Multiplicity:
Advanced:
UUID:
{FA0C5DD9-4363-428f-A57D-6FFB2BB003BC}
Appears In:
Figure SOr.01 - Service Order Entities , Figure SO.08 - Service Specifications and other Domains , Figure SO.09 - VPNService – VPNServiceSpecification Example , Figure SO.03 - Subclassing ServiceSpecification (OLD SO.10) , Figure SO.11 - Modeling Stand-Alone and Aggregate ServiceSpecifications , Figure SO.13 - Modeling the Versioning of a ServiceSpecification , Figure SO.14 - The Concept of a ServiceSpecificationType , Figure SO.18 - Interaction Between ServiceSpecRoles and ResourceSpecRoles , Figure SO.17 - The Concept of ServiceSpecificationRoles (OLD SO.21) , Figure SO.22 -The Concept of ServiceSpecCharacteristic , Figure SO.23 - ServiceCharacteristicValue and ServiceSpecCharacteristicValue , Figure SO.28 - Relationship Between ServiceBundleSpec and ServicePackageSpec , DUPLICATE Cat.05 – Service Catalog Entities and Associations, DUPLICATE Figure CP.01 - Configuration Spec and Configuration, DUPLICATE Figure U.04 - Resource/Service Usage, Figure SO.39 - Associating Service Level Specifications with Products and Services , Figure SO.32 TIP Service Management - Service Characteristics , Figure SO.31 TIP Service Management - Service Definition and Service Template , Figure T.04 - Product, Service and Resource Test Entities (Copy from Common) , Figure PF.02 - Service, Resource, and Performance , Figure CP.01 - Configuration Spec and Configuration (copy from Common) , Figure T.04 - Product, Service and Resource Test Entities (Copy from Common) , NOT USEFUL Figure PR.33 - Relationship Between ProductSpec, ResourceSpec and ServiceSpec, DUPLICATE Figure CP.01 - Configuration Spec and Configuration, DUPLICATE Figure U.04 - Resource/Service Usage, DUPLICATE Figure T.04 - Product, Service, and Resource Test Entities, DUPLICATE Figure CP.01 - Configuration Spec and Configuration, Figure Pr.02a - Product, Service, Resource Domain Relationships , Figure Pr.44a - Product and Service Characteristic Associations , Figure A.06 - Aggrement Item Inherited Associations With Product, Service, and Resource , Figure A.10 - Commitment Deliverables , Figure BI.09 - Business Interaction Item Association with Product, Service, and Resource Domain Entities , Figure BI.15 - Business Interaction Model (BusinessInteractionVersion not shown) , Figure CM.06 - Basic Service Capacity Entities , Figure CM.09 - Basic Service Demand Entities , Figure Cat.02 – Catalog Entities and Associations , Figure Cat.05 – Service Catalog Entities and Associations , Figure CP.01 - Configuration Spec and Configuration , Figure PF.02 - Service, Resource, and Performance , Figure PF.04 - Performance Specification Interval , Figure Proj.00b - project deliverables , Figure R.05 - View of the EntitySpecification Class Hierarchy , Figure R.08 - Interaction Between EntitySpecification and Entity Classes , Figure R.07 - EntitySpecificationType Inheritance , Figure PT.01 - Product, Service and Resource Test Entities , Figure U.04 - Resource and Service Usage , UNUSED Figure P.13 - Resource/Service Usage, Figure An.02 - Anomaly Management Entity Relationship With Other SID Entities
ServiceSpecification is the base entity for defining the ServiceSpecification hierarchy. All Services are characterized as either being related to Products or Resources. Each instance of a Service is made up of changeable as well as invariant attributes, relationships and constraints. A ServiceSpecification defines the shared characteristics of a Service. It can be conceptually thought of as a template that different Service instances can be instantiated from. Each of these Service instances will have the same shared characteristics. However, the characteristics' values of the instantiated Service will be specific to each instance.<br/><br/><br/><br/>This class can be thought of as a template, which represents a generic specification for implementing a particular type of Service. A ServiceSpecification may consist of other ServiceSpecifications supplied together as a collection.<br/><br/><br/><br/>ServiceSpecification inherits from EntitySpecification, which inherits from RootEntity.<br/>
Associations To
Associations From
Tagged Values
Advanced
Other Links
Tag
Value
IsCoreEntity
true
Details:
Values: true,false Default: False
rsa_guid
_3E3F0EC000E93D5092210347
Details:
Property
Value
isActive:
0
isFinalSpecialization:
0