{"title":"用例API——共享数据的设计模式","authors":"T. Górski, Ewa Wojtach","doi":"10.1109/ICSENG.2018.8638199","DOIUrl":null,"url":null,"abstract":"The paper explores aspect of exposing data for public usage from technical point of view. The main aim of this paper is to consider and propose the way of exposing read-only APIs, where state management is minor or no issue, but in the same case, domain complexity can reach high levels. In the paper, the authors propose complete approach to the process of API exposing, from use-case definition and description, to usage of proposed architectural design pattern for read-only API exposure. The paper encompasses the following aspects which were taken into account in proposed design pattern: API usability, developer experience, unit and integration testing, architecture constraints. Moreover, the authors summarize the paper and outline directions for further work.","PeriodicalId":356324,"journal":{"name":"2018 26th International Conference on Systems Engineering (ICSEng)","volume":"3 6","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2018-12-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":"{\"title\":\"Use Case API - design pattern for shared data\",\"authors\":\"T. Górski, Ewa Wojtach\",\"doi\":\"10.1109/ICSENG.2018.8638199\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The paper explores aspect of exposing data for public usage from technical point of view. The main aim of this paper is to consider and propose the way of exposing read-only APIs, where state management is minor or no issue, but in the same case, domain complexity can reach high levels. In the paper, the authors propose complete approach to the process of API exposing, from use-case definition and description, to usage of proposed architectural design pattern for read-only API exposure. The paper encompasses the following aspects which were taken into account in proposed design pattern: API usability, developer experience, unit and integration testing, architecture constraints. Moreover, the authors summarize the paper and outline directions for further work.\",\"PeriodicalId\":356324,\"journal\":{\"name\":\"2018 26th International Conference on Systems Engineering (ICSEng)\",\"volume\":\"3 6\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2018-12-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"1\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2018 26th International Conference on Systems Engineering (ICSEng)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ICSENG.2018.8638199\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2018 26th International Conference on Systems Engineering (ICSEng)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ICSENG.2018.8638199","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
The paper explores aspect of exposing data for public usage from technical point of view. The main aim of this paper is to consider and propose the way of exposing read-only APIs, where state management is minor or no issue, but in the same case, domain complexity can reach high levels. In the paper, the authors propose complete approach to the process of API exposing, from use-case definition and description, to usage of proposed architectural design pattern for read-only API exposure. The paper encompasses the following aspects which were taken into account in proposed design pattern: API usability, developer experience, unit and integration testing, architecture constraints. Moreover, the authors summarize the paper and outline directions for further work.