Advertisement

Towards Continuous Reference Architecture Conformance Analysis

  • Georg Buchgeher
  • Rainer Weinreich
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7957)

Abstract

Reference architectures (RA) are reusable architectures for artifacts in a particular domain. They can serve as a basis for designing new architectures, but also as a means for quality control during system development. Quality control is performed through checking the conformance of systems in development to (company-wide) reference architectures. If performed manually, reference architecture conformance checking is a time- and resource-intensive process. In this paper we outline an approach for reference architecture conformance checking of application architectures in the banking domain. Reference architectures are defined on the basis of reusable rules, consisting of roles and of constraints on roles and role relationships. Conformance checking can be performed semi-automatically and continuously by automating important steps like the extraction of the actual application architecture, the binding of reference architecture roles to the elements of a specific application architecture, and the evaluation of the reference architecture rules for an application architecture.

Keywords

Software Architecture Reference Architectures Conformance Analysis 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Nakagawa, E.Y., Oliveira Antonino, P., Becker, M.: Reference Architecture and Product Line Architecture: A Subtle But Critical Difference. In: Crnkovic, I., Gruhn, V., Book, M. (eds.) ECSA 2011. LNCS, vol. 6903, pp. 207–211. Springer, Heidelberg (2011)CrossRefGoogle Scholar
  2. 2.
    Angelov, S., Trienekens, J.J.M., Grefen, P.W.P.J.: Towards a method for the evaluation of reference architectures: Experiences from a case. In: Morrison, R., Balasubramaniam, D., Falkner, K. (eds.) ECSA 2008. LNCS, vol. 5292, pp. 225–240. Springer, Heidelberg (2008)CrossRefGoogle Scholar
  3. 3.
    Hofmeister, C., Nord, R., Soni, D.: Applied Software Architecture. Addison-Wesley Professional (November 1999)Google Scholar
  4. 4.
    Greefhorst, D., Proper, E.: Architecture Principles: The Cornerstones of Enterprise Architecture, vol. 4. Springer (2011)Google Scholar
  5. 5.
    Cloutier, R., Muller, G., Verma, D., Nilchiani, R., Hole, E., Bone, M.: The concept of reference architectures. Systems Engineering, 14–27 (2009)Google Scholar
  6. 6.
    Weinreich, R., Miesbauer, C., Buchgeher, G., Kriechbaum, T.: Extracting and facilitating architecture in service-oriented software systems. In: 2012 Joint 10th IEEE/IFIP Working Conference on Software Architecture & 6th European Conference on Software Architecture (WICSA-ECSA 2012). IEEE (2012)Google Scholar
  7. 7.
    Schmerl, B., Garlan, D.: Acmestudio: supporting style-centered architecture development. In: Proceedings of 26th International Conference on Software Engineering, ICSE 2004, pp. 704–705 (2004)Google Scholar
  8. 8.
    Monroe, R.T.: Capturing Software Architecture Design Expertise with Armani. Carnegie-mellon univ pittsburgh pa school of computer Science (October 2001)Google Scholar
  9. 9.
    Deiters, C., Rausch, A.: A constructive approach to compositional architecture design. In: Crnkovic, I., Gruhn, V., Book, M. (eds.) ECSA 2011. LNCS, vol. 6903, pp. 75–82. Springer, Heidelberg (2011)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2013

Authors and Affiliations

  • Georg Buchgeher
    • 1
  • Rainer Weinreich
    • 2
  1. 1.Software Competence Center HagenbergAustria
  2. 2.Johannes Kepler University LinzAustria

Personalised recommendations