Versions Compared

Old Version 7

changes.mady.by.user maopeng zhang

Saved on

compared with

New Version 8

changes.mady.by.user Lingli Deng

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Based on the input from ECOMP Service IM input, ONAP R2+ Service IM is designed as below class diagram:


Image RemovedImage Added

  • In this diagram, both design time and run time service related objects are depicted.

  • For the design time section on the left side,

    • ServiceCatalogItem is used to model the design time representation of a service. 

      • Nested Service Design is supported by the association "ServiceComprisedOf", as a ServiceCatalogItem can be composed of other ServiceCatalogItem(s).

      • Complicated Service Design is supported by the association "ServiceComposedOf", as a ServiceCatalogItem can be composed of  at least 1 or more ServiceComponentCatalogItem(s).

      • Hybrid Service Design is also supported, as a part of a ServiceCatalogItem can be composed of ServiceComponentCatalogItem(s) and part of it can be composed of other ServiceCatalogItem(s).
    • ServcieComponentItem is used to model the design time represenation of a service component or network service.

      • Nested Service Component Design is supported by the association "ServiceComponentComprisedOf", as a ServiceComponentCatalogItem can be composed of other ServiceComponentCatalogItem(s).

      • Complicated Service Component Design is supported by the association "ServiceComponentComposedOf", as a ServiceComponentCatalogItem can be composed of  at least 1 or more ResourceCatalogItem(s).

      • Hybrid Service Component Design is also supported, as a part of a ServiceComponenetCatalogItem can be composed of ServiceComponentCatalogItem(s) and part of it can be composed of other ResourceCatalogItem(s).

    • ResourceCatalogItem is used to model the design time representation of a resource.

      • Cross reference in resource design is supported via the association "ResourceCatalogReferences".

  • For the run time section on the right side, similiar layering from top to bottom of instance items and relationship between is modeled, as the result of the model-driven instantiation process from a given ServiceCatalogItem. In particular,

    • Based on 1 ServiceCatalogItem, 0 or more ServiceInstance(s) can be instantiated, which also instantiate the association "ServiceCatalogItemMadeAvailableAs". A ServiceInstance can comprise other ServiceInstance(s) or ServiceComponentInstance(s), as modeled by the associations "ServiceComprisedOf" and "ServiceComposedOf".
    • Based on 1 ServiceComponentCatalogItem, 0 or more ServiceComponentInstance(s) can be instantiated, which also instantiate the association "ServiceComponentCatalogItemMadeAvailableAs". A ServiceComponentInstance can comprise other ServiceComponentInstance(s) or ResourceInstance(s), as modeled by the associations "ServiceComponentComprisedOf" and "ServiceComponentComposedOf".
    • Based on 1 ResourceCatalogItem, 0 or more ResourceInstance(s) can be instantiated, which also instantiates the association "ResourceCatalogItemMadeAvailableAs". A ResourceInstance can reference other ResourceInstance(s).

...