We define API Management as an activity that enables organizations to design, publish and deploy their APIs for (external) developers to consume. API Management capabilities such as controlling API lifecycles, access and authentication to APIs, monitoring, throttling and analyzing API usage, as well as providing security and documentation. These capabilities are often implemented through an integrated platform. This data set describes the API Management Focus Area Maturity Model (API-m-FAMM). In a structured manner, this model aims to support organizations that expose their API(s) to third-party developers in their API management activities. Through a thorough Systematic Literature Review (SLR), 114 practices and 39 capabilities were collected. Subsequently, these practices and capabilities were categorized into 6 focus areas. Next, the practices and capabilities were analyzed and verified through inter-rater agreement and four validation sessions with all involved researchers. Then, the collection of practices and capabilities was verified by using information gathered from supplemental literature, online blog posts, websites, commercial API management platform documentation and third-party tooling. As a result, the initial body of practices and capabilities was narrowed down to 87 practices and 23 capabilities. These practices are described by a practice code, name, description, conditions for implementation, the role responsible for the practice, and the associated literature in which the practice was originally identified. Capabilities and focus areas are described by a code, description and, optionally, the associated literature in which it was originally identified. Using the API-m-FAMM, organizations may evaluate, improve upon and assess the degree of maturity their business processes regarding the topic of API management have.
翻译:我们把API管理定义为使各组织能够设计、出版和部署其供(外部)开发商消费的API管理的活动; API管理能力,例如控制API生命周期、访问和认证API的使用、监测、抽打和分析API的使用以及提供安全和文件; 这些能力往往通过一个综合平台加以实施; 该数据集描述了API管理焦点地区成熟度模型(API-m-FAMM); 该模型的目的是以结构化的方式支持那些在其API管理活动中向第三方开发商披露其API的组织; 通过彻底的系统化文学评论(SRR)、114种做法和39种能力得到收集; 随后,这些做法和能力被分类为6个重点领域,监测、抽打和分析API的使用情况,以及提供安全和文件; 然后,通过利用从补充文献、在线博客、网站、商业价格指数管理平台文件和第三方工具工具收集的信息,对做法和能力进行核实; 结果,通过彻底的系统文献审查,将最初的做法和能力分为87种做法和23种做法说明; 最初的文献描述为A型做法和23种做法确定了一个重点; 这些是A格式,这些是A级做法和A级做法的分类。