Software Architecture Knowledge Management

@article{Vliet2008SoftwareAK,
  title={Software Architecture Knowledge Management},
  author={Hans van Vliet},
  journal={19th Australian Conference on Software Engineering (aswec 2008)},
  year={2008},
  pages={24-31}
}
  • H. V. Vliet
  • Published 2008
  • Computer Science
  • 19th Australian Conference on Software Engineering (aswec 2008)
Software architecture is a recognized and indispensable part of system development. Software architecture is often defined in terms of components and connectors, or the "high-level conception of a system". In recent years, there has been an awareness that not only the design itself is important to capture, but also the knowledge that has led to this design. This so-called architectural knowledge concerns the set of design decisions and their rationale. Capturing architectural knowledge is… Expand
Beyond Software Architecture Knowledge Management Tools
  • A. Zalewski
  • Computer Science
  • KKIO Software Engineering Conference
  • 2016
TLDR
The main idea promoted here is that instead of separate architecture knowledge management tools, there needs an architectureknowledge management infrastructure that connects producers and consumers of architectural knowledge and easily integrates with tools they use for software development. Expand
Meta-model based framework for architectural knowledge management
TLDR
The architecture of an AK management framework to support software architects to manage AK is proposed and has been successfully implemented as part of an industrial project and is currently being evaluated in different domains. Expand
Communicating Architectural Knowledge: Requirements for Software Architecture Knowledge Management Tools
TLDR
This perspective is taken and specific requirements are derived for software architecture knowledge management tools with respect to the context-oriented communication model. Expand
A Model for Capturing and Managing Software Engineering Knowledge and Experience
TLDR
The main contribution of the model is that it enables an organization to consider knowledge and experience management activities as an integral part of its software projects, instead of being considered, as it was until now, as a follow-up activity that is (infrequently) carried out after the end of the projects. Expand
On the Semantics of Architectural Decisions
  • K. Sacha
  • Computer Science
  • Int. J. Softw. Eng. Knowl. Eng.
  • 2016
TLDR
This paper analyzes existing architectural decision models and provides a formal background for the basic notions that all the models have consensus on and proposes a set-theoretic definition of the semantics of architectural decisions. Expand
Towards architectural knowledge management practices for global software development
  • V. Clerc
  • Engineering, Computer Science
  • SHARK '08
  • 2008
TLDR
A light-weight pattern language is provided that is used to describe architectural knowledge management practices and a first validation of these practices from an ongoing case study is provided. Expand
Identification of Technology Features to Understand and Maintain Software Architectures
TLDR
This paper provides tool support and presents first results of the identification of technology features in open source systems, which are fundamental facts which support architects to understand the software architecture and to find alternative technology solutions. Expand
SOFTWARE ENGINEERING: ARCHITECTURE, DESIGN AND FRAMEWORKS
Software architecture is the high level structure of a software system, the discipline of creating such a high level structure, and the documentation of this structure. The architecture of a softwareExpand
Towards a framework for managing architectural design decisions
TLDR
A framework for managing architectural design decisions in large software-intensive projects is proposed that will allow an architectural knowledge management system to integrate with the design, development, and maintenance phases to support stakeholders not only to document design decisions but also to learn from decisions made in the past projects. Expand
Codifying architecture knowledge to support online evolution of software product lines
TLDR
An automated approach for evolving deployed systems of a SPL that uses the architecture knowledge harvested from a deployed system based on the meta-model to generate the list of tasks maintainers have to perform to evolve the system. Expand
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 23 REFERENCES
Eagle: Effective Tool Support for Sharing Architectural Knowledge
TLDR
This paper defines the main characteristics of architecting, based on observations in a large software development organization, and state-of-the-art literature in software architecture, and determines how best practices known from knowledge management could be used to improve architectural knowledge sharing. Expand
The Architect's Mindset
TLDR
Survey-based research in the Netherlands is performed to collect feedback on the importance of architectural knowledge for the daily work of practitioners in architecture using two perspectives: the architectural roles practitioners fulfill and the architecture level practitioners are engaged in. Expand
Architectural Knowledge: Getting to the Core
Different organizations or organizational units are likely to store and maintain different types of information about their software architectures. This inhibits effective management of architecturalExpand
Building Up and Reasoning About Architectural Knowledge
TLDR
A use-case model for an architectural knowledge base, together with its underlying ontology, is described and a small case study in which available architectural knowledge is model in a commercial tool, the Aduna Cluster Map Viewer, which is aimed at ontology-based visualization. Expand
Software Architecture: The Next Step
TLDR
The traditional view on software architecture suffers from a number of key problems that cannot be solved without changing the authors' perspective on the notion of software architecture. Expand
Global Software Development: Are Architectural Rules the Answer?
  • V. Clerc, P. Lago, H. V. Vliet
  • Engineering, Computer Science
  • International Conference on Global Software Engineering (ICGSE 2007)
  • 2007
TLDR
A study on how two organizations involved in GSD solve the GSD challenges and issues and concludes that rules regulating a combination of both proves valuable in handling G SD challenges. Expand
Documenting and Analyzing a Context-Sensitive Design Space
TLDR
This paper shows that when the knowledge in the FS-graph captures context-sensitive architectural knowledge, such as the concerns of different stakeholders, this representation can also be used to document and reason about architectural trade-offs. Expand
Constructing a Reading Guide for Software Product Audits
  • R. Boer, H. V. Vliet
  • Computer Science
  • 2007 Working IEEE/IFIP Conference on Software Architecture (WICSA'07)
  • 2007
TLDR
This paper discusses how the use of a technique called latent semantic analysis can guide the auditors through the documentation to the architectural knowledge they need and effectively construct a reading guide for software product audits. Expand
Using Architectural Decisions
TLDR
It is argued that the usage of architectural decisions by the corresponding stakeholders can enhance the quality of software architecture. Expand
Architectural Knowlege Management Strategies: Approaches in Research and Industry
  • M. Babar, R. Boer, Torgeir Dingsøyr, R. Farenhorst
  • Engineering, Computer Science
  • Second Workshop on Sharing and Reusing Architectural Knowledge - Architecture, Rationale, and Design Intent (SHARK/ADI'07: ICSE Workshops 2007)
  • 2007
TLDR
A preliminary review on current approaches to architectural knowledge management is presented, and a call for awareness of this gap between intention and reality is made to close this gap through focusing on hybrid approaches. Expand
...
1
2
3
...