Software Engineering Methodology for Development of APIs for Network Management using the MEF LSO Framework

Pugaczewski, J.; Cummings, Tara; Hunter, Donald; Michalik, Bartosz

doi:10.1109/mcomstd.2017.1600004st

Cited by 1 publication

(3 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example [30] describes a case where OpenAPI 2.0 is used in combination of other tools from the life sciences community and points out that the specification extension mechanism of OpenAPI 3.0 (that we use in this article) might be an interesting opportunity of improvement. Another example in the telecommunication domain is presented in [14] which provides a section to emphasizes the trade-offs of Model-Driven Engineering and argues that they can be overcomed "with increased investment in the tools that support the development process"; we share the same vision in the present proposal.…”

Section: Related Workmentioning

confidence: 91%

“…Yet the service meta-model in OpenAPI is not a superset of ours because of two lacks that require it to be extended. First, each service must be associated to a component instance that describes its behavior 14 . Second, if a service has a requestBody property (that describes the type of the data required in the request body), the RequestBody object must contain a variable name 15 .…”

Section: Extending Openapi 30mentioning

confidence: 99%

“…Their paths are components > x-swsg-ac and components > x-swsg-cc 14. In the x-swsg-ci property of the service 15.…”

mentioning

confidence: 99%

See 2 more Smart Citations

A Model-Driven Method for Fast Building Consistent Web Services from OpenAPI-Compatible Models

Sferruzza

Rocheteau

Attiogbé

et al. 2019

Communications in Computer and Information Science

View full text Add to dashboard Cite

Lots of software companies rely on web technologies to test market hypotheses in order to develop viable businesses. They often need to quickly build web services that are at the core of their Minimum Viable Products (MVPs). MVPs must be reliable whereas they are based on specifications and hypotheses that are likely to change. Web services need to be well documented, to make it easy to develop applications that consume them. Model Driven Engineering approaches have been proposed and used to develop and evolve web services on one hand, and document them on the other hand. However, these approaches lack the ability to be suitable for both (i) rapid prototyping, (ii) model verification, (iii) compatibility with common programming languages and (iv) alignment between documentation and implementation. Here we propose a meta-model to express web services, the related tool to verify models consistency and an integration of this approach into the OpenAPI Specification. We adopt a shallow verification process to allow rapid prototyping by developers who are not formal methods experts, while still offering design-time guarantees that improve product quality and development efficiency. Web services are defined using parametric components which enable to express and formally verify web service patterns and to safely reuse them in other contexts. We built a tool to check consistency of extended OpenAPI 3.0 models and associated components implementations in order to generate corresponding web services. This allows us to give flexibility and verification support to developers, even in the context of an incremental development, as illustrated by a case study.

show abstract

Section: Related Workmentioning

confidence: 91%

Section: Extending Openapi 30mentioning

confidence: 99%