Help and Support

Space shortcuts

Page tree

SID service operations

Angely ? Dec 19, 2016

Hi,

I recently asked a question about service specifications and I now have a question about service operations.

SID allows us to define the specification of a service (specification / characteristic pattern). Does it allow to define service operations (create, modifiy, delete, etc.) and the associated parameters?

Schematically:

It seems to be related to the TIP Service Management ABE and the Service Activation Interface (cf. GB922_Service_Overview_R16.0.1.pdf, "TIP Service Management ABE" section) but I am not sure since I didn't really succeed to populate the associated class diagram with my use case.

Thanks for the clarifications.

John Reilly Dec 23, 2016

Howdy, Angely. When we first started developing the SID we did include some example operations for entities. But once the TM Forum teams, such as the no longer active TIP program and the Open Digital API program, started developing APIs based on the SID they did not want to be constrained by the operations defined by SID modelers. They wanted to define the operations and publish them as part of the APIs. So, all the example operations were removed. The API teams also develop a data model based on the SID. So it would be a challenge to put them back into the SID. For example, if a class hierarchy was collapsed.

Here is a link to the APIs that have been developed - https://www.tmforum.org/strategic-program/apis/. If you have a requirement that is not supported by one of the many APIs, then you and your development team can develop an API, and if you choose to, add operations to your implementation of the SID associated with an API.

Angely ? Dec 23, 2016

Hi John Reilly.

The SID purposely does not include operations on any entity.

Is there a particular reason for that choice? I would say because SID is a structural view and not a behavioral one but that's not entirely true since during the system step, methods (behaviors) are added to entities.

The API teams are responsible for defining the actions to take on entities as part of their work.

Which team are you talking about? A team of the TMF (the Integration Framework team) or an internal team or our enterprise?

If you choose not to use the API actions then you can certainly add operations to your implementation of the SID.

Yes, but the thing is we don't want to misunderstand SID. Maybe the TMF does not originally include operations because it's considered as a bad practice.

However, just like characteristics, we think that allowing the definition of operations signature in SID brings even more flexibility and coherence for the services designer. I mean, where to define signatures if it is not in SID? In some specification documents? We also think that's the way to go to automatically generate HTML forms based on the signatures stored in the SID model.

Thanks again for your answers very valuable for us.

John Reilly Dec 22, 2016

Howdy, Angely. The SID purposely does not include operations on any entity. The API teams are responsible for defining the actions to take on entities as part of their work. If you choose not to use the API actions then you can certainly add operations to your implementation of the SID.

Duplicated specifcation?

Angely ? Dec 19, 2016

Hello,

I recently read a lot about SID since we want to implement it in our organization, including John Reilly's document entitled "Implementing the TM Forum Information Framework (SID)".

However, we are facing one comprehension issue about specifications. We do get that products, services and resources are described by specifications that contain characteristics. But what if the same characteristic appears at different levels (i.e., product, CFS and RFS) ?

Let's take the example of an end-to-end connectivity product characterized by two port numbers. In our example, let's consider that these numbers are two input parameters (i.e., given by the customer) and are part of the product specification. These parameters have to be propagated to the underlying CFSs and RFSs. Does it mean that the underlying CFSs and RFSs specification are also characterized by two port numbers? Hence, does it imply that the information is duplicated in the database (i.e., stored in different tables) ?

Thanks for the clarifications.

John Reilly Dec 16, 2016

In the book's Chapter 3 and 5 there is mention of how to share Characteristics among specification entities by using the EntitySpecCharUse entity. This entity, along with the EntitySpecCharValueUse entity enable the use of a CharacteristicSpecification and CharacteristicSpecValue entities by more than one specification entity. The Characteristic model can also be found in the Root Business Entities guide book."

 

  • No labels

3 Comments

  1. Unknown User ([email protected])

    I would like to know more about workforce management Does one order contains multiple work order items, and 1 work can associate with work order items I have an anquiries How does the system map 3 work items and assigned to a field staff, and the system map 1 work item but assigned 3 people with a time period? So may I know how to design the WORK database table for solving the scenario

  2. Juan Mark

    Read Here! What Should You Consider While Choosing React Native Database? 

    If you would more detail for react native development services team to contact!

  3. Tomasz Sobczyk

    It's great that you've done your research and identified the TIP Service Management ABE and Service Activation Interface as potential solutions to your question. It sounds like you're looking for more information on how to populate the associated class diagram with your use case. We'd be happy to help you with that. Please let us know if there's anything else we can do to assist you.