Designing a next-generation continuous software delivery system

Steffens, Andreas; Lichter, Horst; Doring, Jan Simon

doi:10.1145/3194760.3194768

Cited by 16 publications

(16 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…-Design & Development: To realize an artifact in accordance to the beforehand identified objectives, first, we align the input of the three objectives' sources. Then, we design an abstract process model using Business Process Model and Notation (BPMN) [39] and implement it using JARVIS [35]. Our derived integrated EA maintenance process consists of activities, which will be implemented as microservices following JARVIS's architectural framework.…”

Section: Methodsmentioning

confidence: 99%

“…In recent research many challenges of adopting continuous delivery have been found [26,5,28] and coping with software evolution and heterogeneity can be identified as the major technical obstacles for a continuous delivery system. To overcome many of these obstacles, we proposed a generalized model and architecture for a new generation of continuous delivery systems [35].…”

Section: Related Workmentioning

confidence: 99%

“…To implement our deployment pipeline for EA model maintenance, we opt for our prototype JARVIS [35]. It allows integrating the proposed processes into a deployment pipeline and we create a BPMN version of the process as JARVIS is equipped to use BPMN as a modeling language.…”

Section: A Pipeline For Ea Model Evolutionmentioning

confidence: 99%

“…Our designed pipeline for EA model maintenance was implemented for the continuous software delivery system JARVIS [35] and each activity in the pipeline model was implemented as an independent microservice following the architectural framework of JARVIS. From JARVIS, we reused the complete infrastructure and general activities like the git checkout activity and the quality gate activity.…”

Section: Implementation Of the Pipelinementioning

confidence: 99%

See 3 more Smart Citations

A Continuous Delivery Pipeline for EA Model Evolution

Hacks

Steffens

Hansen

et al. 2019

Enterprise, Business-Process and Information Systems Modeling

Self Cite

View full text Add to dashboard Cite

The pace of changing structures and complexity within enterprise architecture (EA) models is expected to increase. This will challenge existing maintenance processes of EA models. To tackle this challenge, we propose to adapt the well-known concept of continuous delivery (CD) from the agile software development domain. We propose to automate the necessary steps to ensure EA model quality by applying multiple validation and analysis steps. Therefore, this results shorter feedback loops and helps to uncover possible conflict as early as possible.

show abstract

Section: Methodsmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: A Pipeline For Ea Model Evolutionmentioning

confidence: 99%

Section: Implementation Of the Pipelinementioning

confidence: 99%

See 2 more Smart Citations

A Continuous Delivery Pipeline for EA Model Evolution

Hacks

Steffens

Hansen

et al. 2019

Enterprise, Business-Process and Information Systems Modeling

Self Cite

View full text Add to dashboard Cite

show abstract

“…In recent research, many challenges of adopting continuous delivery have been found [10,42,44] and coping with software evolution and heterogeneity can be identified as the major technical obstacles for a continuous delivery system. To overcome many of these obstacles, we proposed a generalized model and architecture for a new generation of continuous delivery systems [60].…”

Section: Related Workmentioning

confidence: 99%

Implementation of a continuous delivery pipeline for enterprise architecture model evolution

2020

Self Cite

View full text Add to dashboard Cite

The discipline of enterprise architecture (EA) is an established approach to model and manage the interaction of business processes and IT in an organization. Thereby, the EA model as a central artifact of EA is subject to a continuous evolution caused by multiple sources of changes. The continuous evolution requires a lot of effort in controlling and managing the evolution of the EA model. This is especially true when merging the induced changes from different sources in the EA model. Additionally, the lack of tool and automation support makes this a very time-consuming and error-prone task. The evolutionary character and the automated quality assessment of artifacts is a well-known challenge in the software development domain as well. To meet these challenges, the discipline of continuous delivery (CD) has emerged to be very useful. The evolution of EA model artifacts shows similarities to the evolution of software artifacts. Therefore, we leveraged practices of CD to practices of EA maintenance. Thus, we created a conceptual framework for automated EA model maintenance. The concepts were realized in a first prototype and were evaluated in a fictitious case study against equivalence classes based on EA model metrics and a set of several requirements for automated EA model maintenance from research. Overall, the concepts prove to be a promising basis for further refinement, implementation, and evaluation in research in an industrial context.

show abstract