| 199 |
@Article{Abowd1995,
AUTHOR = {Abowd, Gregory and Allen, Robert and Garlan, David},
TITLE = {Formalizing Style to Understand Descriptions of Software Architecture},
YEAR = {1995},
MONTH = {October},
JOURNAL = {ACM Transactions on Software Engineering and Methodology},
VOLUME = {4},
NUMBER = {4},
PAGES = {319-364},
PDF = {http://www.cs.cmu.edu/afs/cs.cmu.edu/project/able/ftp/styleformalism-tosem95/styleformalism-tosem95.pdf},
PS = {http://www.cs.cmu.edu/afs/cs.cmu.edu/project/able/ftp/styleformalism-tosem95/styleformalism-tosem95.ps},
ABSTRACT = {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 specic, conventionalized ways. The informal, imprecise nature of these interpretations has a number of limitations. In this paper we consider these conventionalized interpretations as architectural styles and provide a formal framework for their uniform denition. In addition to providing a template for precisely dening new architectural styles, this framework allows for analysis within and between dierent architectural styles.},
KEYWORDS = {Architectural Analysis, Architectural Style, Landmark, Software Architecture}
}
|
|
