Rik Farenhorst

Learn More
Different organizations or organizational units are likely to store and maintain different types of information about their software architectures. This inhibits effective management of architectural knowledge. We experimented with a model of architectural knowledge to characterize the use of architectural knowledge in four different organizations. Based on(More)
The software architecture community has recently gained an increasing interest in managing architectural knowledge. However, up until now there have been no attempts to obtain an overview of the work in the field. In this paper we present a preliminary review on current approaches to architectural knowledge manage- ment. To this end, we compare approaches(More)
The software architecture community puts more and more emphasis on 'architectural knowledge'. However, there appears to be no commonly accepted definition of what architectural knowledge entails, which makes it a fuzzy concept. In order to obtain a better understanding of how different authors view 'architectural knowledge', we have conducted a systematic(More)
Knowledge management plays an important role in the software architecting process. Recently, this role has become more apparent by a paradigm shift that views a software architecture as the set of architectural design decisions it embodies. This shift has sparked the discussion in both research and practice on how to best facilitate sharing of so-called(More)
In recent years, management of architectural knowledge has become a more prominent theme in software architecture research. Although various specialized tools have been proposed for use in the architecting process, observations show that architects in industry have yet to meet a tool environment that matches their knowledge needs. In order to discover what(More)
Knowledge management plays an important role in the software architecting process. Recently, this role has become more apparent by a paradigm shift that views a software architecture as the set of architectural design decisions it embodies. This shift has sparked the discussion in both research and practice on how to best facilitate sharing of so-called(More)
Sharing knowledge pertaining to software architectures becomes increasingly important. If this knowledge is not explicitly stored or communicated, valuable knowledge dissipates. However, stakeholders will only share knowledge with each other if they are motivated to do so, or in other words if the necessary incentives are created. In this paper we identify(More)
2 1 1 2 4 5 5 5 5 5 concrete content 1 1 1 1 3 5 5 5 4 4 packing input for development 1 1 1 1 3 4 5 5 4 4 output of development descriptive / static 1 1 1 1 3 3 5 5 4 4 use / time dimension app. functionality 1 1 1 1 3 3 3 4 5 5 system administration design 1 1 1 1 3 4 3 5 5 5 deployment conceptual 1 1 1 2 2 4 3 4 5 5 concrete/instance high level 5 3 1 1 2(More)
Sharing knowledge pertaining to software architectures becomes increasingly important. If this knowledge is not explicitly stored or communicated, valuable knowledge dissipates. However, knowledge sharing is challenged by the fact that stakeholders are often located at large distances from each other, now that offshoring and virtual organizations become the(More)
Although the benefits are well-known and undisputed, sharing architectural knowledge is not something architects automatically do. In an attempt to better understand what architects really do and what kind of support they need for sharing knowledge, we have conducted large-scale survey research. The results of our study indicate that architects can be(More)