@InProceedings{Abowd93FSE,
      AUTHOR = {Abowd, Gregory and Allen, Robert and Garlan, David},
      TITLE = {Using Style to Understand Descriptions of Software Architecture},
      YEAR = {1993},
      MONTH = {December},
      BOOKTITLE = {Proceedings of SIGSOFT'93: Foundations of Software Engineering},
      KEY = {Abowd},
      VOLUME = {18},
      NUMBER = {5},
      PAGES = {9-20},
      SERIES = {Software Engineering Notes},
      PUBLISHER = {ACM Press},
      PDF = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/styleformalism-fse1/styleformalism-fse1.pdf},
      PS = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/styleformalism-fse1/styleformalism-fse1.ps},
      ABSTRACT = {The software architecture of most systems is described informally and diagrammatically. In order for these descriptions to be meaningful at all, figures are understood by interpreting the boxes and lines in specific, conventionalized ways. The imprecision of these interpretations has a number of limitations. In this paper we consider these convetionalized 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 the proof that the notational constraints on a style are sufficient to guarantee the meanings of all described systems and provides a unified semantic base through which different stylistic interpretations can be compared.},
      KEYWORDS = {Architectural Style, Software Architecture}
}