Abstract
Modern software systems often are structured as distributed component-based architectures, such as microservice architectures. However, such systems come with significant challenges in cross-component issue management. Each component usually manages its issues in an independent issue management system, and conventional issue management systems only have a project-specific scope. Therefore, issues that affect multiple components or propagate across various components cannot be displayed. Furthermore, issues cannot be linked semantically to issues in other components. Instead, emergency solutions, such as a URL to the other issue, must be used. This makes it challenging to recognize cross-component dependency information. This paper presents Gropius, a tool for integrated management of cross-component issues. Gropius graphically models such cross-component issues together with the system architecture in a notation similar to a UML component diagram. Additionally, other research and industry efforts to manage such issues are discussed and compared to Gropius.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
References
Multi project picker—atlassian marketplace. https://marketplace.atlassian.com/apps/1211709/multi-project-picker?hosting=server&tab=overview
Atlassian: how do others work with issues affecting multiple projects (2020). https://community.atlassian.com/t5/Jira-questions/How-do-others-work-with-issues-affecting-multiple-projects/qaq-p/399950
Atlassian: solved: Share one issue “ticket” across multiple projects ... (2020). https://community.atlassian.com/t5/Jira-Software-questions/Share-one-issue-quot-ticket-quot-across-multiple-projects-and/qaq-p/407534
Bühler, F.: Grapheditor—mico grapheditor documentation 0.5.4 documentation. https://mico-grapheditor.readthedocs.io/en/stable/#
Foundation, G.: Graphql—a query language for your API. https://graphql.org/
Gropius: a cross-component issue management system for component-based architectures. https://github.com/ccims
Jones, M., Bradley, J., Sakimura, N.: RFC 7519: Json web token (jwt). IETF, May 2015
K15t: Backbone issue sync for jira (2020). https://www.k15t.de/software/backbone-issue-sync-for-jira
Mahmood, S., Niazi, M., Hussain, A.: Identifying the challenges for managing component-based development in global software development: preliminary results. In: 2015 Science and Information Conference (SAI), pp. 933–938. IEEE (2015)
Redmine: relating an issue to multiple projects - redmine (2020). https://www.redmine.org/boards/1/topics/21939
Reussner, R.H.: Modeling and Simulating Software Architectures: The Palladio Approach. MIT Press, Cambridge (2016)
Speth, S.: Issue management for multi-project, multi-team microservice architectures. Master’s thesis, University of Stuttgart (2019)
Szyperski, C., Gruntz, D., Murer, S.: Component Software: Beyond Object-Oriented Programming. Pearson Education, London (2002)
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2020 Springer Nature Switzerland AG
About this paper
Cite this paper
Speth, S., Breitenbücher, U., Becker, S. (2020). Gropius — A Tool for Managing Cross-component Issues. In: Muccini, H., et al. Software Architecture. ECSA 2020. Communications in Computer and Information Science, vol 1269. Springer, Cham. https://doi.org/10.1007/978-3-030-59155-7_7
Download citation
DOI: https://doi.org/10.1007/978-3-030-59155-7_7
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-030-59154-0
Online ISBN: 978-3-030-59155-7
eBook Packages: Computer ScienceComputer Science (R0)