We automatically test REST API based on their specifications, particularly OpenAPI ones. To our surprise, many of our tests failed, meaning that the OpenAPI definition and the actual API were not an exact match.
We propose a model-based approach to compose data-driven REST APIs. Our approach creates a global API exposing a unified data model. This global model is exposed as an OData service
Our tool is able to visualize how end-users interact with open data sources regarding two types of metrics: (1) performance metrics and (2) semantic metrics. Among them, we include a UML heatmap to highlight the part of the open data schema that is most frequently requested
Our approach to automatically generate GraphQL schemas from UML class diagrams (and IFML interaction models)
Details of our UML Profile to model OData Web APIs. Once you have your UML model annotated with OData stereotypes you could automate the generation of your OData definition files.
