10 years of software architecture knowledge management: Practice and future

Capilla, Rafael; Jansen, Anton; Tang, Antony; Avgeriou, Paris; Babar, Muhammad Ali

doi:10.1016/j.jss.2015.08.054

Cited by 117 publications

(71 citation statements)

References 73 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The software architecting process aims at designing, documenting, evaluating, and evolving software architecture [43]. Recently, Software Architecture (SA) research has been experiencing a paradigm shift from describing SA with quality attributes and the constraints of context (i.e., the context and requirement aspect) and structuring it as components, connectors and views (i.e., the structure aspect) to focusing on how stakeholders (e.g., the architect) make architectural decisions and reason about the chosen structures and decisions (i.e., the decision aspect) [28,44]. Whilst current research and practice mostly consider architecting as a decision-making process, it has recently been argued that SA in the new digitalization movements (e.g., DevOps) should cover the realization aspect as well [28].…”

Section: Architecting For CI and Cd Practicesmentioning

confidence: 99%

An empirical study of architecting for continuous delivery and deployment

et al. 2018

Self Cite

View full text Add to dashboard Cite

Recently, many software organizations have been adopting Continuous Delivery and Continuous Deployment (CD) practices to develop and deliver quality software more frequently and reliably. Whilst an increasing amount of the literature covers different aspects of CD, little is known about the role of software architecture in CD and how an application should be (re-) architected to enable and support CD. We have conducted a mixed-methods empirical study that collected data through indepth, semi-structured interviews with 21 industrial practitioners from 19 organizations, and a survey of 91 professional software practitioners. Based on a systematic and rigorous analysis of the gathered qualitative and quantitative data, we present a conceptual framework to support the process of (re-) architecting for CD. We provide evidence-based insights about practicing CD within monolithic systems and characterize the principle of "small and independent deployment units" as an alternative to the monoliths. Our framework supplements the architecting process in a CD context through introducing the quality attributes (e.g., resilience) that require more attention and demonstrating the strategies (e.g., prioritizing operations concerns) to design operations-friendly architectures. We discuss the key insights (e.g., monoliths and CD are not intrinsically oxymoronic) gained from our study and draw implications for research and practice.

show abstract

Section: Architecting For CI and Cd Practicesmentioning

confidence: 99%

An empirical study of architecting for continuous delivery and deployment

et al. 2018

Self Cite

View full text Add to dashboard Cite

show abstract

“…“A Mechanism to Explore Proactive Knowledge Retention in Open Source Software Communities” is authored by Rashid, Clarke, and O'Connor. Knowledge management and knowledge retention is a classic topic in software organizations and its connection with Open Source Software is very promising. In this paper, authors present a method towards the formation of proactive knowledge retention practices in Open Source Software projects to transform contributor's use of knowledge and engagement into knowledge relevant activities like knowledge sharing and transfer.…”

Section: About the Special Issuementioning

confidence: 99%

Addressing evolving requirements faced by the software industry

Bíró

Colomo‐Palacios

Messnarz³

2020

J Software Evolu Process

View full text Add to dashboard Cite

“…Modern software systems are expected to evolve to satisfy the changing needs of their users and the changes in the technical environment, and remain economically viable [19,6,9]. Software architecture lies at the core of the evolution process.…”

Section: Background and Motivationmentioning

confidence: 99%