@InCollection{Shaw1995,
      AUTHOR = {Shaw, Mary and Garlan, David},
      TITLE = {Formulations and Formalisms in Software Architecture},
      YEAR = {1995},
      BOOKTITLE = {Computer Science Today: Recent Trends and Developments},
      VOLUME = {1000},
      PAGES = {307-323},
      EDITOR = {Van Leeuwen, Jan},
      SERIES = {Lecture Notes in Computer Science},
      PUBLISHER = {Spring-Verlag},
      PDF = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/saformalisms-lncs1000/saformalisms-lncs1000.pdf},
      PS = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/saformalisms-lncs1000/saformalisms-lncs1000.ps},
      ABSTRACT = {Software architecture is the level of software design that ad- dresses the overall structure and properties of software systems. It provides a focus for certain aspects of design and development that are not appropriately addressed within the constituent modules. Architectural design depends heavily on accurate specications of subsystems and their interactions. These specications must cover a wide variety of properties, so the specication notations and associated methods must be selected or developed to match the properties of interest. Unfortunately, the available formal methods are only a partial match for architectural needs, which entail description of structure, packaging, environmental assumptions, representation, and performance as well as functionality. A prerequisite for devising or selecting a formal method is sound understanding of what needs to be formalized. For software architecture, much of this understanding is arising through progressive codication, which begins with real-world examples and creates progressively more precise models that eventually support formalization. This paper explores the pro- gressive codication of software architecture: the relation between emerging models and the selection, development, and use of formal systems.},
      KEYWORDS = {Software Architecture}
}