The Intersection of Continuous Deployment and Architecting Process: Practitioners' Perspectives

@article{Shahin2016TheIO,
  title={The Intersection of Continuous Deployment and Architecting Process: Practitioners' Perspectives},
  author={Mojtaba Shahin and M. Babar and Liming Zhu},
  journal={Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement},
  year={2016}
}
  • Mojtaba Shahin, M. Babar, Liming Zhu
  • Published 2016
  • Engineering, Computer Science
  • Proceedings of the 10th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement
Context: Development and Operations (DevOps) is an emerging software industry movement to bridge the gap between software development and operations teams. DevOps supports frequently and reliably releasing new features and products-- thus subsuming Continuous Deployment (CD) practice. Goal: This research aims at empirically exploring the potential impact of CD practice on architecting process. Method: We carried out a case study involving interviews with 16 software practitioners. Results: We… Expand
An empirical study of architecting for continuous delivery and deployment
TLDR
A conceptual framework to support the process of (re-) architecting for CD is presented and evidence-based insights about practicing CD within monolithic systems are provided and the principle of “small and independent deployment units” is characterized as an alternative to the monoliths. Expand
DevOps in practice: A multiple case study of five companies
TLDR
This exploratory study presents detailed descriptions of how DevOps is implemented in practice, particularly in small and medium sized companies, and contributes to the overall understanding of DevOps concept, practices and its perceived impacts. Expand
Problems and Solutions of Continuous Deployment: A Systematic Review
TLDR
This paper is a systematic literature review of the problems and the solutions found when implementing the continuous deployment practice inside an organization and presents which solution can be applied to which problem. Expand
Towards a Theory on Architecting for Continuous Deployment
Context: As the adoption of continuous delivery practices increases in software organizations, different scenarios struggle to make it scale for their products in a long-term evolution. This studyExpand
Quality-Aware DevOps Research: Where Do We Stand?
TLDR
Existing efforts in quality-aware DevOps are surveyed, categorizing them according to the stage of the DevOps lifecycle to which they primarily contribute, looking in particular at AI for DevOps and DevOps for AI software. Expand
Adopting Continuous Delivery and Deployment: Impacts on Team Structures, Collaboration and Responsibilities
TLDR
This study provides insights into how software organizations actually improve collaboration among teams and team members for practicing CD, and highlights new responsibilities and skills, which are needed in this regard. Expand
What We Know About Software Architecture Styles in Continuous Delivery and DevOps?
This paper takes a software architect’s perspective to DevOps/CD and attempts to provide a consolidated view on the architecture styles for which empirical publications indicate to be suitable in theExpand
Designing Software Architecture to Support Continuous Delivery and DevOps: A Systematic Literature Review
TLDR
This paper presents a systematic literature review of software architecture approaches that support the implementation of Continuous Delivery (CD) and DevOps and indicated that micro-services are a dominant architectural style in this context. Expand
DevOps Round-Trip Engineering: Traceability from Dev to Ops and Back Again
TLDR
Tornado is proposed, a two-way Continuous Integration framework that automatically updates D&C specifications when the corresponding system changes, enabling bi-directional traceability of the modifications. Expand
Software Reuse and Continuous Software Development: A Systematic Mapping Study
Context: As software applications become more complex and competition between companies demands shorter time-to-market, the methodologies to develop these applications needs to adapt to this newExpand
...
1
2
3
4
...

References

SHOWING 1-10 OF 43 REFERENCES
DevOps - A Software Architect's Perspective
TLDR
The First Complete Guide to DevOps for Software Architects provides the organizational, technical, and operational context needed to deploy DevOps more efficiently, and review DevOps impact on each development phase. Expand
Continuous software engineering: A roadmap and agenda
TLDR
It is argued a similar continuity is required between business strategy and development, BizDev being the term the authors coin for this, and a number of continuous activities are identified which together are labelled as ‘Continuous  * ’ (i.e. Continuous Star) which are presented as part of an overall roadmap for Continuous Software engineering. Expand
Toward Design Decisions to Enable Deployability: Empirical Study of Three Projects Reaching for the Continuous Delivery Holy Grail
TLDR
This paper interviews three project teams striving to practicing continuous delivery and summarizes the deploy ability goals, design decisions, and deploy ability tactics derived from the interviews in the form of an initial draft version hierarchical deploy ability tactic tree. Expand
On the journey to continuous deployment: Technical and social challenges along the way
TLDR
It is concluded that organisations need to be well prepared to handle technical and social adoption challenges with their existing expertise, processes and tools before adopting the CD process. Expand
Towards Architecting for Continuous Delivery
  • Lianping Chen
  • Computer Science
  • 2015 12th Working IEEE/IFIP Conference on Software Architecture
  • 2015
TLDR
It is observed that CD has created a new context for architecting these applications, and this work will try to characterize such a context, explain why the authors need to architect for CD, describe the implications of architecting forCD, and discuss the challenges this new context creates. Expand
Reconciling agility and architecture: a theory of agile architecture
TLDR
The thesis presents a theory that describes how agile software teams design an agile architecture with reduced up-front design and which is able to respond to change, helping teams find a balance between architecture and agility. Expand
SQA-Mashup: A mashup framework for continuous integration
TLDR
A quality awareness framework for CI-data and its conceptional model used for the data integration and visualization called SQA-Mashup that allows for a tailoring of integrated CI- data according to information needs of different stakeholders such as developers or testers is introduced. Expand
Software architecture in practice
TLDR
This second edition of this book reflects the new developments in the field and new understanding of the important underpinnings of software architecture with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters. Expand
Techniques for improving regression testing in continuous integration development environments
TLDR
This work presents algorithms that make continuous integration processes more cost-effective, involving algorithms that are relatively inexpensive and do not rely on code coverage information -- two requirements for conducting testing cost- effective in this context. Expand
Enriching Architecture Knowledge with Technology Design Decisions
TLDR
The main goal in this exploratory study is to understand how technology solutions are being considered by the architects during the design process, and how can existing architecture knowledge concepts be enhanced to support technology decision making. Expand
...
1
2
3
4
5
...