Sharing architecture knowledge through models: Quality and cost

  • Authors:

  • Peng Liang;Anton Jansen;Paris Avgeriou

  • Affiliations:

  • Department of mathematics and computing science, university of groningen, 9700 ak, groningen, the netherlands/ e-mail: liangp@cs.rug.nl, anton@cs.rug.nl, paris@cs.rug.nl;Department of mathematics and computing science, university of groningen, 9700 ak, groningen, the netherlands/ e-mail: liangp@cs.rug.nl, anton@cs.rug.nl, paris@cs.rug.nl;Department of mathematics and computing science, university of groningen, 9700 ak, groningen, the netherlands/ e-mail: liangp@cs.rug.nl, anton@cs.rug.nl, paris@cs.rug.nl

  • Venue:
  • The Knowledge Engineering Review
  • Year:
  • 2009

Quantified Score

Hi-index 0.00

Visualization

Abstract

In the field of software architecture, there has been a paradigm shift from describing structural information, such as components and connectors, to documenting architectural knowledge (AK), such as design decisions and rationale. To this end, a series of industrial and academic domain models have been proposed for defining the concepts and their relationships in the field of AK. To a large extent the merit of this new paradigm is to share and reuse AK across organizations, especially in geographically distributed settings. However, the employment of different AK domain models by different parties makes effective AK sharing challenging, as it needs to be mapped from one domain model to another. In this paper, we investigate two different approaches for sharing AK, based on either direct or indirect mapping between different AK domain models. We compare the cost and quality of these two approaches, with respect to the processing of large amounts of AK instances. To predict the quality and costs of this processing in advance, a prediction model is proposed and validated with a concrete AK sharing case. Based on the comparison results, stakeholders involved with AK sharing can select an appropriate approach by trading off quality and cost in their own context.