Identifying Architecture Attributes in the Context of Software Ecosystems Based on a Mapping Study
Currently, software acquirers and suppliers as well as their relations have been investigated as a software ecosystem (SECO). In a SECO, an organization wants to achieve its business objectives supported by technologies based on a common ecosystem platform. Modifications on technologies can make essential systems unsupported or low performance. Thus, IT managers should consider information about technologies and their relationships. Such information may be spread in different documents and/or difficult to analyze due to the lack of support. As such, related attributes assist IT managers and architects in making decisions on the IT architecture modification, i.e., the set of technologies supporting products and services adopted by an organization. This research aims to identify architecture attributes that affect a SECO and its platform and technologies from the literature. With the intention of comparing this research to a well-accepted standard, ISO/IEC 25000 characteristics were analyzed against architecture attributes. Then, we have evaluated such attributes with experts from industry and academia based on a survey research. As a result, 64 attributes were identified and grouped by 11 critical factors. Critical factors are macro attributes that encompass other attributes. Then, a better understanding on how IT managers and architects’ choices can affect SECO could help them to take actions to mitigate negative effects.
KeywordsSoftware ecosystems Architecture Survey research Reuse Information integration
This study was financed in part by the Coordenação de Aperfeiçoamento de Pessoal de Nível Superior - Brasil (CAPES) - Finance Code 001.
- 1.Albert, B.E., et al.: Software ecosystems governance to enable IT architecture based on software asset management. In: Proceedings of the 2013 7th IEEE International Conference on Digital Ecosystems and Technologies (DEST) Complex Environment Engineering (CEE), Menlo Park, pp. 55–60 (2014)Google Scholar
- 2.Basili, V.R., et al.: The goal question metric approach. Encycl. Softw. Eng. 1, 528–532 (1994)Google Scholar
- 5.Santos, R.P., Werner, C., Finkelstein, A.: Ecosystems effects on software-consuming organizations: an experience report on two observational studies. In: 2018 12th European Conference on Software Architecture: Companion Proceedings (ECSA), Madrid, pp. 23:1–23:7 (2018)Google Scholar
- 6.ISO/IEC 25000: ISO/IEC 25000: Systems and software engineering – Systems and software Quality Requirements and Evaluation (SQuaRE) – Guide to SQuaRE. ISO (2014)Google Scholar
- 8.Lagerström, R., et al.: Visualizing and measuring software portfolio architectures: a flexibility analysis. J. Mod. Proj. Manag. 3(2), 14–121 (2014)Google Scholar
- 9.Lima, T., et al.: A survey on socio-technical resources for software ecosystems. In: Proceedings of the ACM 7th International Conference on Management of Computational and Collective Intelligence in Digital Ecosystems (MEDES), Caraguatatuba, pp. 72–79 (2015)Google Scholar
- 10.Lima, T.: SECO-AM: an approach for maintenance of IT architecture in software ecosystems. Computer Science and Systems Engineering Department COPPE/UFRJ – Federal University of Rio de Janeiro. Master Dissertation (2018). http://reuse.cos.ufrj.br/files/publicacoes/mestrado/Mes_Thaiana.pdf
- 15.Barbosa, O., Santos, R.P., Alves, C., Werner, C., Jansen, S.: A systematic mapping study on software ecosystems from a three-dimensional perspective. In: Jansen, S., Brinkkemper, S., Cusumano, M.A. (eds.) (Org.). Software Ecosystems: Analyzing and Managing Business Networks in the Software Industry, Cheltenham/UK & Northampton/USA: Edward Elgar Publishing, pp. 59–81 (2013)Google Scholar