Achieving traceability in large scale continuous integration and delivery deployment, usage and validation of the eiffel framework

Ståhl, Daniel; Hallen, Kristofer; Bosch, Jan

doi:10.1007/s10664-016-9457-1

Cited by 46 publications

(29 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Furthermore, even though there are numerous popular tools that do much of the heavy lifting in these integration systems, they only address isolated parts of a very large problem domain. In all our industry case studies [8,9,11,12] we have never found a complete off-theshelf solution for continuous integration. Rather, the integration systems we find often use similar tools, but configured differently, put to different purposes and integrated with one another in varying constellations.…”

Section: Discussionmentioning

confidence: 84%

Cinders

Ståhl

Bosch

2018

Proceedings of the 2018 International Conference on Software and System Process

Self Cite

View full text Add to dashboard Cite

show abstract

Section: Discussionmentioning

confidence: 84%

Cinders

Ståhl

Bosch

2018

Proceedings of the 2018 International Conference on Software and System Process

Self Cite

View full text Add to dashboard Cite

show abstract

“…Ståhl et al [195] Achieving traceability in large-scale continuous integration and delivery deployment, usage and validation of the Eiffel framework…”

Section: Springer Empirical Software Engineering Volume 22 Number 3mentioning

confidence: 99%

The ABC of Software Engineering Research

Stol

Fitzgerald

2018

ACM Trans. Softw. Eng. Methodol.

142

View full text Add to dashboard Cite

A variety of research methods and techniques are available to SE researchers, and while several overviews exist, there is consistency neither in the research methods covered nor in the terminology used. Furthermore, research is sometimes critically reviewed for characteristics inherent to the methods. We adopt a taxonomy from the social sciences, termed here the ABC framework for SE research, which offers a holistic view of eight archetypal research strategies. ABC refers to the research goal that strives for generalizability over Actors (A) and precise measurement of their Behavior (B), in a realistic Context (C). The ABC framework uses two dimensions widely considered to be key in research design: the level of obtrusiveness of the research and the generalizability of research findings. We discuss metaphors for each strategy and their inherent limitations and potential strengths. We illustrate these research strategies in two key SE domains, global software engineering and requirements engineering, and apply the framework on a sample of 75 articles. Finally, we discuss six ways in which the framework can advance SE research.

show abstract

“…To identify published literature, a Scopus search was conducted. The decision to use only one indexing service was based on that we in previous work have found Scopus to cover a large majority of published literature in the field, with other search engines only providing very small result sets not already covered by Scopus.…”

Section: Reviewing Literaturementioning

confidence: 99%

Test activities in the continuous integration and delivery pipeline

Mårtensson

Ståhl

Bosch

2019

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

Based on 25 interviews with participants from four case study companies that develop large‐scale software embedded systems, this paper presents the Test Activity Stakeholders (TAS) model. The TAS model shows how the continuous integration and delivery pipeline can be designed to include test activities that support four stakeholder interests: “Check changes,” “Secure stability,” “Measure progress,” and “Verify compliance.” The model is developed to show how each of the stakeholder interests are best supported by unit/component tests or system tests, by automated testing or manual testing and by tests executed in simulated environments or on real hardware. The TAS model may serve as a starting point for companies when evaluating and designing their continuous integration and delivery pipeline. The validation of the TAS model included twelve individuals from three case study companies. The validation showed that the TAS model is actionable and useful in practice, enabling the identification of stakeholders and showing where improvement efforts should be focused in order to support all stakeholder interests in the continuous integration and delivery pipeline.

show abstract

Achieving traceability in large scale continuous integration and delivery deployment, usage and validation of the eiffel framework

Cited by 46 publications

References 26 publications

Cinders

Cinders

The ABC of Software Engineering Research

Test activities in the continuous integration and delivery pipeline

Contact Info

Product

Resources

About