How to model APIs in HITA?

[stefgou]

Hi,

Until now, we've been using the "old" ARC metamodel to model our APIs, with the concept of IT services and the "service-defined" (for the provider) and "service-used" (for the consumers) relationships.
For example, we had Application A that defines IT services SA1 and SA2. IT service SA2 is an API. And Application B that calls IT service SA2 with the "service-used" relationship.

We would like to switch our model to the "new" HITA metamodel.
Despite carefully reading the documentation, we haven't been able to identify the simplest way to switch our APIs (as IT services) to the HITA metamodel.
What type of object should we use ?
How do we identify the provider and consumers of our APIs ?

[stefgou]

Thanks for the feedback.

I've done some testing with service interfaces and interactions. I must admit, I find it very complex.

If I understand correctly, we have to declare all our APIs as "service interfaces." Why isn't there an entry for service interfaces in the "Inventory" menu? Like there is for "IT services"?

Then, I created "request points" for consumers and "service points" for providers at the "Boundary Components" level of my applications, linking them to my service interface. But I can't seem to view the list of consumers for my service interface. Isn't there a property page or report for that?

[MAngouch]

Hi,

The definition of APIs (catalog of API) are documented using the MetaClass "Service Interface" which describes how/which data are being exchanged. The Metaclass "Service Interaction" is used to identify the provider, consumer and the API used, so the service interaction can be considered are the usage context of the API.

Regards,