Recovery of Architectural Structure: A Case Study

  • Authors:
  • Wolfgang Eixelsberger;Manfred Kalan;Michaela Ogris;Håkon Beckman;Berndt Bellay;Harald Gall

  • Affiliations:
  • -;-;-;-;-;-

  • Venue:
  • Proceedings of the Second International ESPRIT ARES Workshop on Development and Evolution of Software Architectures for Product Families
  • Year:
  • 1998

Quantified Score

Hi-index 0.00

Visualization

Abstract

Industrial software development is often an evolutionary process. Software products are developed for one specific customer and later on refined for other customers with different requirements in terms of a product family. Refinements happen at the implementation level (algorithms and data structures) and on the architectural level (the overall system structure). Recovery of architectural information is necessary to build up a complete and unambiguous description of the architecture of a system. In this paper, we describe an approach for the recovery of architectural structure that focuses on component and connector identification. We describe different strategies to define components and connectors of the system. The examples given in the paper were developed out of an industrial case study, a real-time Train Control System. The recovered architectural description allows reasoning about the quality of the system architecture: The description of the architectural structure revealed hardware-dependent components that in case of a hardware change would have to be changed completely. Therefore, our investigations showed that such a recovery of architectural structure is important to reduce future efforts in the development and maintenance of product lines.