Formalizing Style to Understand Descriptions of Software Architecture
journal contributionposted on 01.01.1972 by Gregory Abowd, Robert Allen, David Garlan
Any type of content formally published in an academic journal, usually following a peer-review process.
The software architecture of most systems is usually described informally and diagrammatically by means of boxes and lines. In order for these descriptions to be meaningful, the diagrams are understood by interpreting the boxes and lines in specific, conventionalized ways. The informal, imprecise nature of these interpretations has a number of limitations. In this article we consider these conventionalized interpretations as architectural styles and provide a formal framework for their uniform definition. In addition to providing a template for precisely defining new architectural styles, this framework allows for analysis within and between different architectural styles.