Tools and Technologies for Architecture Knowledge Management

Liang, Peng; Avgeriou, Paris

doi:10.1007/978-3-642-02374-3_6

Cited by 20 publications

(16 citation statements)

References 192 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the field of AK, a number of KM approaches and tools have been developed for efficiently and effectively improving the practice of software architecting [13,14]. Software architecting is essentially a knowledge-intensive process that is composed of several activities, e.g., architectural analysis, synthesis, and evaluation [15].…”

Section: Introductionmentioning

confidence: 99%

Application of knowledge-based approaches in software architecture: A systematic mapping study

Liang

Avgeriou

2013

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Citation for published version (APA): Li, Z., Liang, P., & Avgeriou, P. (2013). Application of knowledge-based approaches in software architecture: A systematic mapping study. Information and Software Technology, 55(5), 777-794. DOI: 10.1016777-794. DOI: 10. /j.infsof.2012 Copyright Other than for strictly personal use, it is not permitted to download or to forward/distribute the text or part of it without the consent of the author(s) and/or copyright holder(s), unless the work is under an open content license (like Creative Commons).Take-down policy If you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim. Context: Knowledge management technologies have been employed across software engineering activities for more than two decades. Knowledge-based approaches can be used to facilitate software architecting activities (e.g., architectural evaluation). However, there is no comprehensive understanding on how various knowledge-based approaches (e.g., knowledge reuse) are employed in software architecture. Objective: This work aims to collect studies on the application of knowledge-based approaches in software architecture and make a classification and thematic analysis on these studies, in order to identify the gaps in the existing application of knowledge-based approaches to various architecting activities, and promising research directions. Method: A systematic mapping study is conducted for identifying and analyzing the application of knowledge-based approaches in software architecture, covering the papers from major databases, journals, conferences, and workshops, published between January 2000 and March 2011. Results: Fifty-five studies were selected and classified according to the architecting activities they contribute to and the knowledge-based approaches employed. Knowledge capture and representation (e.g., using an ontology to describe architectural elements and their relationships) is the most popular approach employed in architecting activities. Knowledge recovery (e.g., documenting past architectural design decisions) is an ignored approach that is seldom used in software architecture. Knowledge-based approaches are mostly used in architectural evaluation, while receive the least attention in architecture impact analysis and architectural implementation. Conclusions: The study results show an increased interest in the application of knowledge-based approaches in software architecture in recent years. A number of knowledge-based approaches, including knowledge capture and representation, reuse, sharing, recovery, and reasoning, have been employed in a spectrum of architecting activities. Knowledge-based approaches have been applied to a wide range of application domains, among which ''Embedded software'' has received the most attention.

show abstract

Section: Introductionmentioning

confidence: 99%

Application of knowledge-based approaches in software architecture: A systematic mapping study

Liang

Avgeriou

2013

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

show abstract

“…The latter was also identified by Tang et al [6]. In 2009, Liang and Avgeriou [8] surveyed nine existing tools to what extent they support the following categories of use cases: consuming AK, knowledge management, intelligent support, and producing AK. They found that the tools lack of the ability to identify stakeholders, to apply decisions to produce the design (synthesis), to evaluate AK, and to support the assessment design maturity.…”

Section: Related Workmentioning

confidence: 89%

“…However, multiple studies identified that these tools are often only applicable during certain stages of the architecting process and have been designed to only support a particular activity or only work under certain conditions [6], [7], [8]. In addition, van Heesch et al [9] argued that the proposed approaches, i.e.…”

Section: Introductionmentioning

confidence: 99%

Industrial Implementation of a Documentation Framework for Architectural Decisions

Manteuffel

Tofan

Koziolek³

et al. 2014

2014 IEEE/IFIP Conference on Software Architecture

Self Cite

View full text Add to dashboard Cite

Abstract-Architecture decisions are often not explicitly documented in practice but reside in the architect's mind as tacit knowledge, even though explicit capturing and documentation of architecture decisions has been associated with a multitude of benefits. As part of a research collaboration with ABB, we developed a tool to document architecture decisions. This tool is an add-in for Enterprise Architect and is an implementation of a viewpoint-based decision documentation framework. To validate the add-in, we conducted an exploratory case study with ABB architects. In the study, we assessed the status quo of architecture decision documentation, identified architects' expectations of the ideal decision documentation tool, and evaluated the new add-in. We found that although awareness of decision documentation is increasing at ABB, several barriers exist that limit the use of decisions in practice. Regarding their ideal tool, architects want a descriptive and efficient approach. Supplemental features like reporting or decision sharing are requested. The new add-in, was well-perceived by the architects. As a result of the study, we propose a clearer separation of problem, outcomes, and alternatives for the decision documentation framework.

show abstract

“…The Knowledge Architect entails specialized support for integrating the various architecting activities [11] and supporting collaboration between the stakeholders of these activities. The different tools support different activities (e.g.…”

Section: The Knowledge Architect (Ka)mentioning

confidence: 99%

“…Several research prototype tools [11], [14] for capturing, using, and documenting architectural design decisions have recently appeared; many of these use templates and metamodels for capturing knowledge attributes and managing decision dependencies [15], [16]. Tools such as PAKME, ADDSS, Archium, The Knowledge Architect, and AREL offer traceability mechanisms between decisions and other software artifacts at different levels.…”

Section: Related Workmentioning

confidence: 99%

An Enhanced Architectural Knowledge Metamodel Linking Architectural Design Decisions to other Artifacts in the Software Engineering Lifecycle

Capilla

Zimmermann

Zdun

et al. 2011

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. Software architects create and consume many interrelated artifacts during the architecting process. These artifacts may represent functional and nonfunctional requirements, architectural patterns, infrastructure topology units, code, and deployment descriptors as well as architecturally significant design decisions. Design decisions have to be linked to chunks of architecture description in order to achieve a fine-grained control when a design is modified. Moreover, it is imperative to identify quickly the key decisions affected by a runtime change that are critical for a system's mission. This paper extends previous work on architectural knowledge with a metamodel for architectural decision capturing and sharing to: (i) create and maintain fine-grained dependency links between the entities during decision identification, making, and enforcement, (ii) keep track of the evolution of the decisions, and (iii) support runtime decisions.

show abstract

Tools and Technologies for Architecture Knowledge Management

Cited by 20 publications

References 192 publications

Application of knowledge-based approaches in software architecture: A systematic mapping study

Application of knowledge-based approaches in software architecture: A systematic mapping study

Industrial Implementation of a Documentation Framework for Architectural Decisions

An Enhanced Architectural Knowledge Metamodel Linking Architectural Design Decisions to other Artifacts in the Software Engineering Lifecycle

Contact Info

Product

Resources

About