\
 

Start Date

16-8-2018 12:00 AM

Description

Small and Mid-sized Enterprises (SMEs), in particular, suffer from cost-inefficient projects for the integration of cloud applications due to conceptual differences from local applications and a variety of related technical obstacles. Open source projects have been around for 20 years and tackle highly complex and comprehensive problems in a cost-effective manner. Following design science research, we gather and identify requirements for the development of an open integration Platform as a Service (iPaaS). We conducted a total of 20 interviews and obtained insights from cloud service providers (CSPs), integration service providers (ISPs), and SMEs. In this work, 641 requirements are collected and 67 sub-themes are identified as a result of extensive analysis. Furthermore, we outline 10 themes that align with three layers (provider, integration, and user) forming the target architecture of the underlying open source project in this paper. Finally, multiple insights are gathered for further employment, development, and research.

Share

COinS
 
Aug 16th, 12:00 AM

Requirements Analysis for an Open iPaaS: Exploring the CSP, ISP, and SME View

Small and Mid-sized Enterprises (SMEs), in particular, suffer from cost-inefficient projects for the integration of cloud applications due to conceptual differences from local applications and a variety of related technical obstacles. Open source projects have been around for 20 years and tackle highly complex and comprehensive problems in a cost-effective manner. Following design science research, we gather and identify requirements for the development of an open integration Platform as a Service (iPaaS). We conducted a total of 20 interviews and obtained insights from cloud service providers (CSPs), integration service providers (ISPs), and SMEs. In this work, 641 requirements are collected and 67 sub-themes are identified as a result of extensive analysis. Furthermore, we outline 10 themes that align with three layers (provider, integration, and user) forming the target architecture of the underlying open source project in this paper. Finally, multiple insights are gathered for further employment, development, and research.