Skip to main content

Gropius — A Tool for Managing Cross-component Issues

Part of the Communications in Computer and Information Science book series (CCIS,volume 1269)

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.

Keywords

  • Issue management
  • Integration
  • Service-oriented architecture
  • Component-based architecture
  • Bug tracking
  • Microservices

This is a preview of subscription content, access via your institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • DOI: 10.1007/978-3-030-59155-7_7
  • Chapter length: 13 pages
  • Instant PDF download
  • Readable on all devices
  • Own it forever
  • Exclusive offer for individuals only
  • Tax calculation will be finalised during checkout
eBook
USD   109.00
Price excludes VAT (USA)
  • ISBN: 978-3-030-59155-7
  • Instant PDF download
  • Readable on all devices
  • Own it forever
  • Exclusive offer for individuals only
  • Tax calculation will be finalised during checkout
Softcover Book
USD   139.99
Price excludes VAT (USA)
Fig. 1.
Fig. 2.
Fig. 3.
Fig. 4.
Fig. 5.
Fig. 6.

Notes

  1. 1.

    https://youtu.be/dRhDINDbMkc.

References

  1. Multi project picker—atlassian marketplace. https://marketplace.atlassian.com/apps/1211709/multi-project-picker?hosting=server&tab=overview

  2. 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

  3. 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

  4. Bühler, F.: Grapheditor—mico grapheditor documentation 0.5.4 documentation. https://mico-grapheditor.readthedocs.io/en/stable/#

  5. Foundation, G.: Graphql—a query language for your API. https://graphql.org/

  6. Gropius: a cross-component issue management system for component-based architectures. https://github.com/ccims

  7. Jones, M., Bradley, J., Sakimura, N.: RFC 7519: Json web token (jwt). IETF, May 2015

    Google Scholar 

  8. K15t: Backbone issue sync for jira (2020). https://www.k15t.de/software/backbone-issue-sync-for-jira

  9. 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)

    Google Scholar 

  10. Redmine: relating an issue to multiple projects - redmine (2020). https://www.redmine.org/boards/1/topics/21939

  11. Reussner, R.H.: Modeling and Simulating Software Architectures: The Palladio Approach. MIT Press, Cambridge (2016)

    Google Scholar 

  12. Speth, S.: Issue management for multi-project, multi-team microservice architectures. Master’s thesis, University of Stuttgart (2019)

    Google Scholar 

  13. Szyperski, C., Gruntz, D., Murer, S.: Component Software: Beyond Object-Oriented Programming. Pearson Education, London (2002)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Sandro Speth .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and Permissions

Copyright information

© 2020 Springer Nature Switzerland AG

About this paper

Verify currency and authenticity via CrossMark

Cite this paper

Speth, S., Breitenbücher, U., Becker, S. (2020). Gropius — A Tool for Managing Cross-component Issues. In: , 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)