ArchBibliography

From WICSA Conference Wiki

Jump to: navigation, search

@Comment *** BIBLIOGRAPHIC ITEMS START HERE --- RELATEED ABBREVIATIONS ARE ON A SEPARATE PAGE ***

@Manual{ATT1991,

title =	 {Best current practices: software architecture
                validation},
year =	 1991,
organization = {AT\&T Bell Laboratories}

}

@Unpublished{Abd-Allah94,

author =	 {A. Abd-Allah},
title =	 {Architecture Description Languages State of the Art
                Presentation},
note =	 {Knowledge Summary of the USC-CSE Focused Workshop on
                Software Architectures},
year =	 1994,
month =	 jun

}

@TechReport{Abd-Allah95,

author =	 {A. Abd-Allah},
title =	 {Composing heterogeneous software architectures},
institution =	 {USC Center for Software Engineering},
year =	 1995,
number =	 {USC-CSE TR 95-502}

}

@TechReport{Abd-Allah97,

author =	 {A. Abd-Allah},
title =	 {Extending reliability block diagrams to software
                architectures},
institution =	 {Center for Software Engineering, Computer Science
                Department, University of Southern California},
year =	 1997,
number =	 {USC--CSE--97--501}

}

@TechReport{Abd-AllahBoehm95,

author =	 {A. Abd-Allah and Barry W. Boehm},
title =	 {Reasoning about the composition of heterogeneous
                architectures},
institution =	 {University of Southern California},
year =	 1995,
number =	 {USC--CSE--95--503}

}

@article{Abowd+:TOSEM95,

author =	 "G.D.~Abowd and R.~Allen and D.~Garlan",
title =	 "{Formalizing Style to Understand Descriptions of
                Software Architecture}",
journal =	 ACM-TOSEM,
volume =	 4,
number =	 4,
month =	 oct,
year =	 1995,
pages =	 "319--364"

}

@Article{AbowdAllenGarlan93,

author =	 {G. Abowd and R. Allen and D. Garlan},
title =	 {Using style to understand descriptions of software
                architectures},
journal =	 {ACM Software Engineering Notes},
year =	 1993,
volume =	 18,
number =	 5,
pages =	 {9--20},
month =	 dec

}

@Manual{AirForce:AFSSM-9000,

title =	 {Air Force Systems Security Memorandum Command,
                Control, Communications, and Computer Systems
                Security Glossary},
year =	 1993,
month =	 jan

}

@TechReport{Aksit+1995,

author =	 {M. Aksit and F. Marcelloni and B. Tekinerdogan and
                C. Vuijst and L. Bergmans},
title =	 {Designing Software Architectures as Specializations
                of Knowledge Domains},
institution =	 {University of Twente},
year =	 1995,
type =	 {Memoranda Informatica},
number =	 {95-44},
month =	 dec

}

@Book{Alexander1977,

author =	 {Christopher Alexander},
title =	 {A pattern language},
publisher =	 {Oxford University Press},
year =	 1977

}

@Book{Alexander1979,

author =	 {Christopher Alexander},
title =	 {The timeless way of building},
publisher =	 {Oxford University Press},
year =	 1979

}

@inproceedings{Allen+:FSE6,

author =	 "R.~Allen and D.~Garlan and J.~Ivers",
title =	 "{Formal Modeling and Analysis of the HLA Component
                Integration Standard}",
booktitle =	 FSE6,
organization = SIGSOFT,
month =	 nov,
year =	 1998,
pages =	 "70--79"

}

@PhdThesis{Allen1997,

author =	 {Robert J. Allen},
title =	 {A Formal Approach to Software Architecture},
school =	 CMU,
year =	 1997,
note =	 {Distributed as CMU-CS-97-144},
month =	 may

}

@InProceedings{AllenDouenceGarlan1998,

author =	 {Robert Allen and Remi Douence and David Garlan},
title =	 {Specifying and analyzing dynamic software
                architectures},
booktitle =	 {Proceedings of 1998 Conference on Fundamental
                Approaches to Software Engineering},
year =	 1998,
month =	 mar

}

@InProceedings{AllenGarlan1996,

author =	 {Robert Allen and David Garlan},
title =	 {A Case Study in Architectural Modelling: The {AEGIS}
                System},
booktitle =	 IWSSD8,
organization = IEEE-CS,
month =	 mar,
year =	 1996,
pages =	 "6--15"

}

@techreport{AllenGarlan:CMU92,

author =	 "R.~Allen and D.~Garlan",
title =	 "{Towards Formalized Software Architectures}",
institution =	 CMU,
address =	 CMU-add,
number =	 "CMU--CS--92--163",
month =	 jul,
year =	 1992

}

@inproceedings{AllenGarlan:ICSE16,

author =	 "R.~Allen and D.~Garlan",
title =	 "{Formalizing Architectural Connection}",
booktitle =	 ICSE16,
organization = IEEE-CS,
month =	 may,
year =	 1994,
pages =	 "71--80"

}

@inproceedings{AllenGarlan:IFIP92,

author =	 "R.~Allen and D.~Garlan",
title =	 "{A Formal Approach to Software Architectures}",
booktitle =	 IFIP,
publisher =	 Elsevier,
month =	 sep,
year =	 1992

}

@Article{AllenGarlan:TOSEM97,

author =	 "R.~Allen and D.~Garlan",
title =	 "{A Formal Basis for Architectural Connection}",
journal =	 ACM-TOSEM,
volume =	 6,
number =	 3,
month =	 jul,
year =	 1997,
pages =	 "213--249"

}

@Article{Avizienis1986,

author =	 {Algirdas Avizienis},
title =	 {Dependable Computing: From Concepts to Design
                Diversity},
journal =	 Proc-IEEE,
year =	 1986,
volume =	 74,
number =	 5,
month =	 may

}

@InProceedings{BBKLNOW96,

author =	 {Francois Bronsard and Douglas Bryan and
                W. Kozaczynski and Edy S. Liogosari and Jim Q. Ning
                and Asgeir Olafsson and John W. Wetterstrand},
title =	 {Toward Software Plug-and-Play},
editor =	 {Medhi Harandi},
booktitle =	 {Proceedings of the 1997 Symposium on Software
                Reusability},
year =	 1997,
note =	 {Published in Software Engineering Notes, May 1997}

}

@Misc{Baldwin+1997,

author =	 {R. Baldwin and D. Emery and R. Hilliard and T. Rice
                and S. Schwarm},
title =	 {Views and viewpoints workshop},
year =	 1997,
month =	 sep

}

@Book{Ball1981,

author =	 {John E. Ball},
title =	 {Architectural Drafting},
publisher =	 {Reston},
year =	 1981

}

@InProceedings{Balsamo+:WOSP98,

author =	 "S.~Balsamo and P.~Inverardi and C.~Mangano",
title =	 "{An Approach to Performance Evaluation of Software
                Architectures}",
booktitle =	 WOSP98,
organization = IEEE-CS,
month =	 oct,
year =	 1998,
x-pages =	 "77--84"

}

@Book{Bass-Clements-Kazman1998,

editor =	 "L.~Bass and P.~Clements and R.~Kazman",
title =	 "{Software Architecture in Practice}",
publisher =	 Addison,
address =	 Addison-add,
year =	 1998

}

@InProceedings{Beck-Johnson1994,

author =	 {Kent Beck and Ralph Johnson},
title =	 {Patterns generate architectures},
booktitle =	 {European Conference on Object-Oriented Programming},
year =	 1994,
publisher =	 {Springer--Verlag}

}

@inproceedings{Bertolino+:ICECCS97,

author =	 "A.~Bertolino and P.~Inverardi and H.~Muccini and
                A.~Rosetti",
title =	 "{An Approach to Integration Testing Based on
                Architectural Descriptions}",
booktitle =	 ICECCS97,
organization = IEEE-CS,
month =	 sep,
year =	 1997,
pages =	 "77--84"

}

@inproceedings{Bertolino+:ICSE00,

author =	 "A.~Bertolino and F.~Corradini and P.~Inverardi and
                H.~Muccini",
title =	 "{Deriving Test Plans from Architectural
                Descriptions}",
booktitle =	 ICSE00,
organization = ACM,
month =	 jun,
year =	 2000,
pages =	 "220--229"

}

@Book{Best1990,

author =	 {Laurence J. Best},
title =	 {Application Architecture: Modern, Large-Scale
                Information Processing},
publisher =	 {Wiley and Sons},
year =	 1990

}

@InProceedings{Boehm1995,

author =	 {Barry W. Boehm},
title =	 {Software process architectures},
booktitle =	 IWASS1,
year =	 1995,
address =	 {Seattle, WA}

}

@article{Boehm:Software96,

author =	 "B.~Boehm",
title =	 "{Anchoring the Software Process}",
journal =	 IEEE-Software,
volume =	 13,
number =	 4,
month =	 jul,
year =	 1996,
pages =	 "73--82"

}

@InProceedings{Briand-Melo-Seaman-Basili95,

author =	 {Lionel Briand and Walcelio Melo and Carolyn Seaman
                and Victor Basili},
title =	 {Characterizing and assessing a large-scale software
                maintenance organization},
year =	 1995,
booktitle =	 {Proceedings 17th International Conference on
                Software Engineering},
annote =	 {Describes early use of Yu and Myopoulos'
                Actor-Dependency approach to organization modeling.}

}

@Misc{Brown,

author =	 {Kyle Brown},
title =	 {Crossing Chasms: The architectural patterns},
url =
                {http://www.ksccary.com/Articles/ArchitectualPatterns/ArchitecturalPatterns.htm}

}

@Article{Burns-Lister91,

author =	 {A. Burns and M. Lister},
title =	 {A Framework for Building Dependable Systems},
journal =	 {The Computer Journal},
year =	 1991,
volume =	 34,
number =	 2,
abstract =	 {The authors address design of dependable systems in
                the face of non-functional requirements for domains
                such as avionics, process control, military and
                other safety-critical applications. Paper is a case
                study designing a pump control system for a mine
                shaft with a good handling of reliability, security
                and safety (non-functional) requirements. Design is
                viewed as ``a progression of increasingly specific
                {\em commitments} ... properties of the system
                design which [detailed] designers are not at liberty
                to change. Those aspects of a design to which no
                commitment is made ... are the subject of {\em
                obligations} that lower levels of a design must
                address. The process of refining obligations into
                commitments is often subject to {\em constraints}
                imposed primarily by the execution environment.
                They outline two views --- a logical architecture
                which is object-oriented, and a physical
                architecture which specifies distribution of
                objects, adds instances and non-functional
                attributes to the logical classes.}

}

@book{Buschmann+:Wiley96,

author =	 "F.~Buschmann and R.~Meunier and H.~Rohnert and
                P.~Sommerlad and M.~Stal",
title =	 "{Pattern-Oriented Software Architecture: A System of
                Patterns}",
publisher =	 Wiley,
address =	 Wiley-add,
year =	 1996

}

@Manual{C2STA98,

title =	 {{The Air Force's Command and Control System Target
                Architecture} version 1.0},
organization = {DII--AF Chief Architects' Office},
year =	 1998

}

@Manual{C4ISR,

title =	 {{C4ISR} Architecture Framework},
organization = {US Department of Defense},
edition =	 {2.0},
month =	 dec,
year =	 1997

}

@article{Carney+:ATT85,

author =	 "D.L.~Carney and J.I.~Cochrane and L.J.~Gitten and
                E.M.~Prell and R.~Staehler",
title =	 "{Architectural Overview}",
journal =	 "{AT\&T Technical Journal}",
editor =	 "W.S.~Hayward, Jr.",
publisher =	 "AT\&T",
volume =	 64,
number =	 6,
year =	 1985,
pages =	 "1339--1356"

}

@inproceedings{Carzaniga+:ISAW3,

author =	 "A.~Carzaniga and E.~Di~Nitto and D.S.~Rosenblum and
                A.L.~Wolf",
title =	 "{Issues in Supporting Event-Based Architectural
                Styles}",
booktitle =	 ISAW3,
month =	 nov,
year =	 1998,
pages =	 "17--20"

}

@InProceedings{Cazzola+1998,

author =	 {Walter Cazzola and Andrea Savigni and Andrea Sosio
                and Francesco Tisato},
title =	 {{Architectural Reflection: Bridging the Gap Between
                a Running System and its Architectural
                Specification}},
booktitle =	 {Proceedings of 6th Reengineering Forum (REF'98)},
year =	 1998,
address =	 {Firenze, Italia},
organization = {IEEE},
pages =	 {12-1--12-6}

}

@TechReport{Cazzola+1999,

author =	 {Walter Cazzola and Andrea Savigni and Andrea Sosio
                and Francesco Tisato},
title =	 {{Architectural Reflection: Concepts, Design, and
                Evaluation}},
institution =	 {DSI, University degli Studi di Milano},
type =	 {Technical Report},
number =	 {RI-DSI 234-99},
year =	 1999,
month =	 May,
URL =
                {http://www.disi.unige.it/person/CazzolaW/references.html}

}

@InProceedings{ChandrasekharanMcGowan1987,

author =	 {M. Chandrasekharan and C. McGowan},
title =	 {Using simulations to resolve practical performance
                issues of specifications and architectures},
booktitle =	 {Proceedings of 4th International Workshop on
                software specification and design},
year =	 1987,
address =	 {Monterey, CA}

}

@Book{Ching1979,

author =	 {Francis D. K. Ching},
title =	 {Architecture: Form, Space, and Order},
publisher =	 vanNos,
year =	 1979,
address =	 vanNos-add,
annote =	 {NA2760.C46. A deceptively simple hand-drawn graphic
                introduction to architectural ideas, and great
                architectural drawing style, all at once!}

}

@InProceedings{Chung-Yu1998,

author =	 {L. Chung and E. Yu},
title =	 {Achieving System-Wide Architectural Qualities},
booktitle =	 {OMG-DARPA-MCC Workshop on Compositional Software
                Architectures},
year =	 1998,
month =	 jan

}

@TechReport{Clapp-Hazle1978,

author =	 {J. A. Clapp and M. Hazle},
title =	 {Building Blocks for {C3} Systems},
institution =	 {The MITRE Corporation},
year =	 1978,
number =	 {MTR--3504}

}

@InProceedings{Clements-Bass-Kazman-Abowd95,

author =	 {P. Clements and L. Bass and R. Kazman and G. Abowd},
title =	 {Predicting Software Quality by Architecture-Level
                Evaluation},
booktitle =	 {Proceedings of 5th International Conference on
                Software Quality},
year =	 1995

}

@InProceedings{Clements1996,

author =	 {Paul C. Clements},
title =	 {A survey of architecture description languages},
booktitle =	 IWSSD8,
year =	 1996,
publisher =	 IEEE-CS-press

}

@Book{Clements2002,

editor =	 {Paul Clements},
title =	 {Documenting Software Architectures: Views and
                Beyond},
publisher =	 Addison,
year =	 2002

}

@techreport{Compare+:CU-CS-828-97,

author =	 "D.~Compare and P.~Inverardi and A.L.~Wolf",
title =	 "{Uncovering Architectural Mismatch in Component
                Behavior}",
institution =	 CU-CS,
address =	 CU-add,
number =	 "CU-CS-828-97",
month =	 feb,
year =	 1997

}

@unpublished{Compare+:FSE4,

author =	 "D.~Compare and P.~Inverardi and A.L.~Wolf",
title =	 "{Uncovering Architectural Mismatch in Dynamic
                Behavior}",
month =	 oct,
year =	 1996,
note =	 available-s

}

@article{Compare+:SCP99,

author =	 "D.~Compare and P.~Inverardi and A.L.~Wolf",
title =	 "{Uncovering Architectural Mismatch in Component
                Behavior}",
journal =	 SCP,
volume =	 33,
number =	 2,
month =	 feb,
year =	 1999,
pages =	 "101--131"

}

@techreport{Compare:UA95,

author =	 "D.~Compare",
title =	 "{Specifica ed Analisi del CERN Compressing Proxy con
                la CHAM}",
institution =	 "Dipartimento di Matematica Pura ed Applicata",
address =	 "L'Aquila, Italy",
number =	 "Tesi di Laurea",
month =	 dec,
year =	 1995

}

@inproceedings{CompareInverardi:COORD96,

author =	 "D.~Compare and P.~Inverardi",
title =	 "{Modelling Interoperability by CHAM: A Case Study}",
booktitle =	 COORD96,
publisher =	 Springer,
series =	 LNCS,
number =	 1061,
month =	 apr,
year =	 1996,
pages =	 "428--431"

}

@inproceedings{CordySchneider:CASE95,

author =	 "J.R.~Cordy and K.A.~Schneider",
title =	 "{Architectural Design Recovery Using Source
                Transformations}",
booktitle =	 "{Proceedings of the Seventh International Workshop
                on Computer-Aided Software Engineering}",
organization = IEEE-CS,
month =	 jul,
year =	 1995

}

@InCollection{Coutaz-Nigay-Salber95,

author =	 {J. Coutaz and L. Nigay and D. Salber},
title =	 {Agent-Based Architecture Modelling for Interactive
                Systems},
booktitle =	 {Critical Issues in User Interface Engineering},
pages =	 {191--209},
publisher =	 Springer,
year =	 1995,
editor =	 {P. Palanque and D. Benyon},
address =	 {London}

}

@techreport{Cramer:UD95,

author =	 "J.~Cramer",
title =	 "{Interconnecting and Reusing Component
                Specifications}",
institution =	 UDortmund,
address =	 UDortmund-add,
number =	 78,
month =	 jan,
year =	 1995

}

@Misc{DISA:JTA,

title =	 Template:Joint Technical Architecture,
howpublished = {http://www.itsi.disa.mil/jta},
year =	 1996,
URL = 	 {http://www.itsi.disa.mil/jta}

}

@Proceedings{DSSA,

title =	 {Proceedings of the workshop on domain-specific
                software architectures},
year =	 1990,
editor =	 {K. Lee},
address =	 {Hidden Valley, PA},
month =	 {9--12 July}

}

@InProceedings{DeJohn,

author =	 {Dan DeJohn},
title =	 {The {Tyndall Range Control System}: bringing network
                computing to {C2} systems},
editor =	 {Charles B. Engle},
pages =	 {474--485},
booktitle =	 {TRI--Ada '94 Proceedings},
year =	 1994,
publisher =	 {ACM}

}

@InProceedings{DeMillo-Young95,

author =	 {Richard A. DeMillo and Michal Young},
title =	 {Quantitative aspects of software architecture},
editor =	 {D. Garlan},
booktitle =	 IWASS1,
year =	 1995,
note =	 {Published as CMU--CS--TR--95--151}

}

@article{DeRemerKron:TSE76,

author =	 "F.~DeRemer and H.H.~Kron",
title =	 "{Programming-in-the-Large Versus
                Programming-in-the-Small}",
journal =	 IEEE-TSE,
volume =	 "SE-2",
number =	 2,
month =	 jun,
year =	 1976,
pages =	 "80--86"

}

@Article{Dean-Cordy95,

author =	 {Thomas Dean and James Cordy},
title =	 {A Syntactic Theory of Software Architecture},
journal =	 {IEEE Transactions on Software Engineering},
year =	 1995,
volume =	 21,
number =	 4,
month =	 apr

}

@Article{Denning-Dargan94,

author =	 {Peter Denning and Pamela Dargan},
title =	 {A Discipline Of Software Architecture},
journal =	 {Interactions},
year =	 1994,
volume =	 1,
number =	 1,
abstract =	 {We propose that a new skill called {\em ontological
                mapping} is the basis of a discipline of software
                architecture. This skill consists of observing the
                ontology of a domain, constructing its ontological
                dictionary, and constructing a workflow map of its
                recurring standard processes. The map can be used by
                the software architect to review with the client how
                the system will satisfy each concern, and to
                coordinate the implementation of the information and
                software structure with the software engineers. It
                can be used later to assess and reconfigure the
                system. The one map can be used by the designer, the
                implementor, the assessor, and the
                maintainer. Evidence of this skill can be seen i the
                examples of award-winning software packages and
                systems. The field of architecture illustrates that
                the skill can be learned. We propose this
                interpretation not as a final answer, but as a
                preliminary step. We offer it as an opening for a
                new direction in the investigation of software
                design.},
keywords =	 {software architecture, ontological mapping,
                dictionary, workflow map, recurring standard
                processes, software structure, software engineers,
                software design, user interface}

}

@TechReport{Druffel-Loy-Rosenberg-Sylvester-Volz94,

author =	 {L. Druffel and N. E. Loy and R. A. Rosenberg and
                R. J. Sylvester and R. A. Volz},
title =	 {Information architectures that enchance operational
                capability in peacetime and wartime},
institution =	 {US Air Force Science Advisory Board},
year =	 1994,
month =	 feb

}

@InProceedings{Egyed-Gacek99,

author =	 {Egyed, A. and Gacek, C.},
title =	 {Automatically Detecting Mismatches during
                Component-Based and Model-Based Development},
booktitle =	 {Proceedings of the 14th IEEE International
                Conference on Automated Software Engineering},
pages =	 {191--198},
year =	 1999,
address =	 {Cocoa Beach, Florida},
month =	 oct

}

@InProceedings{Egyed-Hilliard2000,

author =	 {Alexander Egyed and Rich Hilliard},
title =	 {Architectural Integration and Evolution in a Model
                World},
booktitle =	 ISAW4,
pages =	 {37--40},
year =	 2000,
editor =	 {Bob Balzer and Henk Obbink}

}

@InProceedings{Egyed-Hilliard2000,

author =	 {Alexander Egyed and Rich Hilliard},
title =	 {Architectural Integration and Evolution in a Model
                World},
booktitle =	 ISAW4,
pages =	 {37--40},
year =	 2000,
editor =	 {Bob Balzer and Henk Obbink}

}

@TechReport{Egyed99,

author =	 {Alexander Egyed},
title =	 {Integrating Architectural Views in {UML}},
institution =	 {Center for Software Engineering, University of
                Southern California},
year =	 1999,
type =	 {Technical Report},
number =	 {USC/CSE-99-TR-514},
address =	 {Los Angeles, CA}

}

@TechReport{Egyed99,

author =	 {Alexander Egyed},
title =	 {Integrating Architectural Views in {UML}},
institution =	 {Center for Software Engineering, University of
                Southern California},
year =	 1999,
type =	 {Technical Report},
number =	 {USC/CSE-99-TR-514},
address =	 {Los Angeles, CA}

}

@Unpublished{Egyed99a,

author =	 {Alexander Egyed},
title =	 {Automatically detecting modeling mismatches between
                heterogeneous views},
booktitle =	 {},
note =	 {Submitted to {\em 22nd International Conference on
                Software Engineering}, Limerick, Ireland 2000}

}

@Unpublished{Egyed99a,

author =	 {Alexander Egyed},
title =	 {Automatically detecting modeling mismatches between
                heterogeneous views},
booktitle =	 {},
note =	 {Submitted to {\em 22nd International Conference on
                Software Engineering}, Limerick, Ireland 2000}

}

@InProceedings{Ellis-Hilliard-Poon-Rayford-Saunders-Sherlund-Wade96,

author =	 {Walter J. Ellis and Rich Hilliard and Peter T. Poon
                and David Rayford and Thomas F. Saunders and Basil
                Sherlund and Ronald L. Wade},
title =	 {Toward a Recommended Practice for Architectural
                Description},
booktitle =	 {Proceedings of 2nd IEEE International Conference on
                Engineering of Complex Computer Systems, Montreal,
                Quebec, Canada, October 21--25, 1996},
year =	 1996

}

@InProceedings{Ellis-Hilliard-Poon-Rayford-Saunders-Sherlund-Wade96,

author =	 {Walter J. Ellis and Rich Hilliard and Peter T. Poon
                and David Rayford and Thomas F. Saunders and Basil
                Sherlund and Ronald L. Wade},
title =	 {Toward a Recommended Practice for Architectural
                Description},
booktitle =	 {Proceedings of 2nd IEEE International Conference on
                Engineering of Complex Computer Systems, Montreal,
                Quebec, Canada, October 21--25, 1996},
year =	 1996

}

@InProceedings{Emery-Hilliard-Rice96,

author =	 {David E. Emery and Rich Hilliard and Timothy
                B. Rice},
title =	 {Experiences Applying a Practical Architectural
                Method},
booktitle =	 {Reliable Software Technologies--Ada-Europe '96},
editor =	 {Alfred Strohmeier},
number =	 1088,
series =	 {Lecture Notes in Computer Science},
year =	 1996,
publisher =	 {Springer},
URL =		 {http://www.pithecanthropus.com/\homedir
                awg/CaseStudies.pdf}

}

@InProceedings{Emery-Hilliard95,

author =	 {David E. Emery and Rich Hilliard},
title =	 {``{A}rchitecture, methods and open issues},
booktitle =	 IWASS1,
pages =	 {80--84},
editor =	 {D. Garlan},
year =	 1995,
address =	 {Seattle, WA},
note =	 {Published as CMU--CS--TR--95--151}

}

@InProceedings{Emery-Hustad-Alford-Christeson-Nixon-Rice-Stevenson94,

author =	 {D. Emery and J. Hustad and T. Alford and
                M. Christeson and P. Holton and K. Jordan and M
                Kinnebrew and R. T. Nixon and T. Rice and
                J. Stevenson},
title =	 {Using {Ada} to develop client-server applications in
                an open systems environment},
booktitle =	 {Proceedings Sixth Software Technology Conference},
year =	 1994,
address =	 {Salt Lake City, UT},
month =	 apr

}

@Article{Estrin,

author =	 {G. Estrin and R. Fenchel and R. Razouk and
                M. Vernon},
title =	 {SARA: ({System Architects Apprentice}): Modeling,
                Analysis, and Simulation Support for Design of
                Concurrent Systems},
journal =	 {IEEE Transactions on Software Engineering},
year =	 1986,
volume =	 {SE--12},
number =	 2,
pages =	 {293--311},
month =	 feb

}

@InProceedings{Fiadeiro,

author =	 {J. L. Fiadeiro},
title =	 {On the Emergence of Properties in Component-Based
                Systems},
booktitle =	 {AMAST'96},
pages =	 {421--443},
year =	 1996,
editor =	 {M. Wirsing and M. Nivat},
volume =	 1101,
series =	 {LNCS},
publisher =	 Springer

}

@InProceedings{Fiadeiro-Lopes97,

author =	 {J. L. Fiadeiro and A. Lopes},
title =	 {Semantics of Architectural Connectors},
booktitle =	 {TAPSOFT'97},
pages =	 {505--519},
year =	 1997,
editor =	 {M. Bidoit and M. Dauchet},
volume =	 1214,
series =	 {LNCS},
publisher =	 Springer

}

@InProceedings{Fiadeiro-Maibaum95,

author =	 {Jose Luiz Fiadeiro and Tom Maibaum},
title =	 {Interconnecting formalisms: supporting modularity,
                reuse and incrementality},
pages =	 {72--80},
booktitle =	 {Proceedings Third Symposium on the Foundations of
                Software Engineering},
editor =	 {Gail Kaiser},
year =	 1995,
publisher =	 {ACM Press},
annote =	 {Suggests an approach to using category theory as a
                uniform underlying foundation for the multiple
                notations and formalisms used in software
                engineering. This would be a good approach to
                implementing the open semantics of architectural
                descriptions which we are proposing. To quote: ``The
                idea is that the integration that is necessary for
                being able to reason about the properties of a
                system can be effected by relating the way the
                different formalisms structure the application
                instead of the ontologies they use to model the
                universe of discourse.}

}

@InProceedings{Fiadeiro-Maibaum96,

author =	 {Jose Luiz Fiadeiro and Tom Maibaum},
title =	 {A Mathematical Toolbox for the Software Architect},
editor =	 {J. Kramer and A. Wolf},
pages =	 {46--55},
booktitle =	 {Proceedings of the Eighth International Workshop on
                Software Specification and Design},
year =	 1996,
publisher =	 {IEEE Computer Society Press}

}

@InProceedings{Fradet-Metayer-Perin99,

author =	 {Pascal Fradet and Daniel Le M\'{e}tayer and
                Micha\"{e}l P\'{e}rin},
title =	 {Consistency checking for multiple view software
                architectures},
booktitle =	 {Proceedings ESEC/FSE'99},
year =	 1999,
publisher =	 {Springer}

}

@InProceedings{Fradet-Metayer-Perin99,

author =	 {Pascal Fradet and Daniel Le M\'{e}tayer and
                Micha\"{e}l P\'{e}rin},
title =	 {Consistency checking for multiple view software
                architectures},
booktitle =	 {Proceedings ESEC/FSE'99},
year =	 1999,
publisher =	 {Springer}

}

@InProceedings{Gacek-Abd-Allah-Clark-Boehm95,

author =	 {C.~Gacek and A.~Abd-Allah and B.~Clark and
                B.W.~Boehm},
title =	 {On the definition of software system architecture},
booktitle =	 IWASS1,
year =	 1995,
address =	 {Seattle, WA}

}

@InProceedings{Gacek-Boehm98,

author =	 {Cristina Gacek and Barry Boehm},
title =	 {Composing Components: How Does One Detect Potential
                Architectural Mismatches?},
booktitle =	 {Proceedings of the OMG-DARPA-MCC Workshop on
                Compositional Software Architectures},
year =	 1998,
month =	 jan,
URL =		 {http://www.objs.com/workshops/ws9801/}

}

@Unpublished{Gacek94,

author =	 {Cristina Gacek},
title =	 {Software Architecture, the Architecting Process, and
                Examples of Architecting Infrastructures State of
                the Art Presentation},
note =	 {Knowledge Summary of the USC-CSE Focused Workshop on
                Software Architectures},
year =	 1994,
month =	 jun

}

@PhdThesis{Gacek98,

author =	 {Cristina Gacek},
title =	 {Detecting Architectural Mismatches During Systems
                Composition},
school =	 {Center for Software Engineering, University of
                Southern California},
year =	 1998,
address =	 {Los Angeles},
month =	 dec

}

@book{Gamma+:AW95,

editor =	 "E.~Gamma and R.~Helm and R.~Johnson and
                J.~Vlissides",
title =	 "{Design Patterns: Elements of Reusable
                Object-Oriented Software}",
publisher =	 Addison,
address =	 Addison-add,
year =	 1995

}

@inproceedings{Garlan+:CASCON97,

author =	 "D.~Garlan and R.~Monroe and D.~Wile",
title =	 "{ACME: An Architecture Description Interchange
                Language}",
booktitle =	 "Proceedings of CASCON '97",
organization = "IBM Center for Advanced Studies",
month =	 nov,
year =	 1997,
pages =	 "169--183"

}

@misc{Garlan+:CMU95,

author =	 "D.~Garlan and D.~Kindred and J.M.~Wing",
title =	 "{Interoperability: Sample Problems and Solutions}",
howpublished = available-s,
institution =	 CMU,
address =	 CMU-add,
year =	 1995

}

@inproceedings{Garlan+:FSE2,

author =	 "D.~Garlan and R.~Allen and J.~Ockerbloom",
title =	 "{Exploiting Style in Architectural Design
                Environments}",
booktitle =	 FSE2,
organization = sigsoft,
month =	 dec,
year =	 1994,
pages =	 "175--188"

}

@inproceedings{Garlan+:ICSE17,

author =	 "D.~Garlan and R.~Allen and J.~Ockerbloom",
title =	 "{Architectural Mismatch or Why it's Hard to Build
                Systems Out of Existing Parts}",
booktitle =	 ICSE17,
organization = ACM,
month =	 apr,
year =	 1995,
pages =	 "179--185"

}

@article{Garlan+:SEN95,

author =	 "D.~Garlan and W.~Tichy and F.~Paulisch",
title =	 "{Summary of the Dagstuhl Workshop on Software
                Architecture}",
journal =	 SEN,
volume =	 20,
number =	 3,
month =	 jul,
year =	 1995,
pages =	 "63--83"

}

@article{Garlan+:Software95,

author =	 "D.~Garlan and R.~Allen and J.~Ockerbloom",
title =	 "{Architectural Mismatch: Why Reuse is So Hard}",
journal =	 IEEE-Software,
volume =	 12,
number =	 6,
month =	 nov,
year =	 1995,
pages =	 "17--26"

}

@InProceedings{Garlan-Allen-Ockerbloom94,

author =	 {David Garlan and Robert Allen and John Ockerbloom},
title =	 {Exploiting style in architectural design
                environments},
booktitle =	 {Proceedings of {SIGSOFT'94}, Foundations of Software
                Engineering},
year =	 1994,
publisher =	 {ACM Press},
month =	 dec

}

@Misc{Garlan-Monroe-Wile95,

author =	 {David Garlan and Robert Monroe and David Wile},
title =	 {{Acme}: Software Architecture Interchange Language},
URL =
                {http://www.cs.cmu.edu/afs/cs/project/able/www/acme-web/},
year =	 1995

}

@InProceedings{Garlan-Monroe-Wile97,

author =	 {David Garlan and Robert T. Monroe and David Wile},
title =	 {Acme: An Architecture Description Interchange
                Language},
booktitle =	 {Proceedings of CASCON '97},
year =	 1997,
pages =	 {169--183},
month =	 nov

}

@InProceedings{Garlan-Shaw93,

author =	 {David Garlan and Mary Shaw},
title =	 {An Introduction to Software Architecture},
booktitle =	 {Advances in Software Engineering and Knowledge
                Engineering},
year =	 1993,
publisher =	 {World Scientific Publishing Company},
editor =	 {V. Ambriola and G. Tortora},
address =	 {Singapore},
pages =	 {1-39}

}

@Misc{Garlan-Wang98,

author =	 {David Garlan and Zhenyu Wang},
title =	 {A Case Study in Software Architecture Interchange},
howpublished = {Submitted for publication to the Workshop on
                Software and Performance 98 },
year =	 1998,
month =	 mar

}

@Article{Garlan95,

author =	 {David Garlan},
title =	 {Research directions in software architecture},
journal =	 {ACM Computing Surveys},
volume =	 27,
number =	 2,
pages =	 {257--261},
year =	 1995

}

@InProceedings{Garlan95a,

author =	 {David Garlan},
title =	 {What is style?},
booktitle =	 IWASS1,
editor =	 {D. Garlan},
year =	 1995,
address =	 {Seattle, WA},
note =	 {Published as CMU--CS--TR--95--151}

}

@inproceedings{GarlanNotkin:VDM91,

author =	 "D.~Garlan and D.~Notkin",
title =	 "{Formalizing Design Spaces: Implicit Invocation
                Mechanisms}",
booktitle =	 "{Proceedings of VDM~'91: Formal Software Development
                Methods}",
month =	 oct,
year =	 1991

}

@incollection{GarlanShaw:ASEKE93,

author =	 "D.~Garlan and M.~Shaw",
title =	 "{An Introduction to Software Architecture}",
booktitle =	 "{Advances in Software Engineering and Knowledge
                Engineering}",
editor =	 "V.~Ambriola and G.~Tortora",
publisher =	 World,
address =	 World-add,
volume =	 1,
year =	 1993

}

@inproceedings{GarlanWang:COORD99,

author =	 "D.~Garlan and Z.~Wang",
title =	 "{Acme-Based Software Architecture Interchange}",
booktitle =	 COORD99,
publisher =	 Springer,
series =	 LNCS,
number =	 1594,
month =	 apr,
year =	 1999,
pages =	 "340--354"

}

@inproceedings{Goedicke+:IWSSD6,

author =	 "M.~Goedicke and H.~Schumann and J.~Cramer",
title =	 "{On the Specification of Software Components}",
booktitle =	 IWSSD6,
organization = IEEE-CS,
month =	 oct,
year =	 1991

}

@inproceedings{Goedicke+:TAPSOFT91,

author =	 "M.~Goedicke and J.~Cramer and W.~Fey and
                M.~Grosse-Rhode",
title =	 "{Towards a Formally Based Component Description
                Language}",
booktitle =	 TAPSOFT91,
month =	 apr,
year =	 1991

}

@techreport{Goedicke:UD93,

author =	 "M.~Goedicke",
title =	 "{On the Structure of Software Description Languages:
                A Component Oriented View}",
institution =	 UDortmund,
address =	 UDortmund-add,
number =	 473,
year =	 1993

}

@techreport{GoedickeSchumann:UE94,

author =	 "M.~Goedicke and H.~Schumann",
title =	 "{Component-Oriented Software Development with D}",
institution =	 UEssen,
address =	 UEssen-add,
type =	 "Informatik Research Report",
number =	 "01--94",
month =	 aug,
year =	 1994

}

@TechReport{Goldman-Hammond-Kurland-Platcow92,

author =	 {H. G. Goldman and E. J. Hammond and M. Kurland and
                R. Platcow},
title =	 {Preliminary Proposal for a Software Architecture
                Policy},
institution =	 {The MITRE Corporation},
year =	 1992,
number =	 {WP 92B0000181},
month =	 may,
abstract =	 {This paper documents the early work in identifying
                inputs into a Request For Proposal (RFP) package for
                the capture, assessment, and validation of the
                software component of a system architecture. It
                reflects the preliminary result of an ongoing
                Software Center initiative. This paper suggests
                wording to be included in the RFP package,
                establishes a minimum level of architectural
                information to be provided by the offerors, and
                addresses items that impact architecture, such as
                security, user interface definition, databases, and
                the use of COTS/GOTS packages. Further, the use of
                thread analysis and software architecture
                prototyping is discussed.}

}

@InProceedings{Gordijn-Akkermans-vanVliet2000,

author =	 {J. Gordijn and J.M. Akkermans and J.C. van Vliet},
title =	 {Business Modelling is not Process Modelling},
booktitle =	 {Conceptual Modeling for E-Business and the Web},
pages =	 {40--51},
year =	 2000,
volume =	 1921,
series =	 lncs,
publisher =	 {Springer}

}

@InProceedings{Gordijn-deBruin-Akkermans2001,

author =	 {J. Gordijn and H. de Bruin and J.M. Akkermans},
title =	 {Scenario Methods for Viewpoint Integration in
                e-Business Requirements Engineering},
booktitle =	 {Proceedings of the 34th Hawaii International
                Conference On System Sciences},
year =	 2001,
publisher =	 {IEEE}

}

@Unpublished{Gordijn-vanVliet99,

author =	 {Jaap Gordijn and Hans van Vliet},
title =	 {On the interaction between business models and
                software architecture in electronic commerce},
note =	 {Addendum to the Proceedings, 7th European Software
                Engineering Conference/Foundations of Software
                Engineering, Toulouse, 1999}

}

@Unpublished{Gordijn-vanVliet99,

author =	 {Jaap Gordijn and Hans van Vliet},
title =	 {On the interaction between business models and
                software architecture in electronic commerce},
note =	 {Addendum to the Proceedings, 7th European Software
                Engineering Conference/Foundations of Software
                Engineering, Toulouse, 1999}

}

@Article{Goseva-Popstojanova+2003,

author = 	 {Katerina Goseva-Popstojanova, Ahmed Hassan, Ajith Guedem, Walid
                Abdelmoez, Diaa Eldin M. Nassar, Hany Ammar, Ali
                Mili},
title = 	 {Architectural-Level Risk Analysis Using UML},
journal = 	 IEEE-TSE,
year = 	 2003,
volume =	 29,
number =	 10,
pages =	 {946--960},
abstract =     {Risk assessment is an essential part in managing software
                development. Performing risk assessment during the
                early development phases enhances resource
                allocation decisions. In order to improve the
                software development process and the quality of
                software products, we need to be able to build risk
                analysis models based on data that can be collected
                early in the development process. These models will
                help identify the high-risk components and
                connectors of the product architecture, so that
                remedial actions may be taken in order to control
                and optimize the development process and improve the
                quality of the product. In this paper, we present a
                risk assessment methodology which can be used in the
                early phases of the software life cycle. We use the
                Unified Modeling Language (UML) and commercial
                modeling environment Rational Rose Real Time
                (RoseRT) to obtain UML model statistics. First, for
                each component and connector in software
                architecture, a dynamic heuristic risk factor is
                obtained and severity is assessed based on hazard
                analysis. Then, a Markov model is constructed to
                obtain scenarios risk factors. The risk factors of
                use cases and the overall system risk factor are
                estimated using the scenarios risk factors. Within
                our methodology, we also identify critical
                components and connectors that would require careful
                analysis, design, implementation, and more testing
                effort. The risk assessment methodology is applied
                on a pacemaker case study.}

}

@Book{Grabow83,

author =	 {Stephen Grabow},
title =	 {Christopher Alexander: The Search for a New Paradigm
                in Architecture},
publisher =	 {Oriel Press},
year =	 1983

}

@Book{Halse72,

author =	 {Albert O. Halse},
title =	 {Architectural Rendering},
publisher =	 {McGraw-Hill},
year =	 1972,
edition =	 {2nd}

}

@inproceedings{Han:CBSE99,

author =	 "J.~Han",
title =	 "{An Approach to Software Component Specification}",
booktitle =	 CBSE99,
month =	 may,
year =	 1999,
pages =	 "97--102"

}

@inproceedings{Harris+:ICSE17,

author =	 "D.R.~Harris and H.B.~Rubenstein and A.S.~Yeh",
title =	 "{Reverse Engineering to the Architectural Level}",
booktitle =	 ICSE17,
organization = ACM,
month =	 apr,
year =	 1995,
pages =	 "186--195"

}

@TechReport{Hayes-Roth-Erman94,

author =	 {F. Hayes-Roth and L. Erman},
title =	 {The {Joint Task Force Architecture Specification
                (JTFAS)}},
institution =	 {Teknowledge Federal Systems},
year =	 1994,
address =	 {Palo Alto, CA}

}

@Unpublished{Hilliard,

author =	 {Rich Hilliard},
title =	 {Comments on Kogut and Clements},
note =	 {Email}

}

@Misc{Hilliard-Emery96,

author =	 {Rich Hilliard and David E. Emery},
title =	 {Patterns : Design :: Blueprints : Architecture},
year =	 1996,
note =	 {Unpublished}

}

@Unpublished{Hilliard-Kurland-Litvintchouk-Rice-Schwarm96,

author =	 {Rich Hilliard and Michael J. Kurland and Steven
                D. Litvintchouk and Timothy B. Rice and Stephen
                C. Schwarm},
title =	 {Architecture Quality Assessment},
institution =	 {The MITRE Corporation},
note =	 {Current version available from the first author.}

}

@InProceedings{Hilliard-Kurland-Litvintchouk97,

author =	 {Rich Hilliard and Michael J. Kurland and Steven
                D. Litvintchouk},
title =	 Template:MITRE's Architecture Quality Assessment,
booktitle =	 {1997 MITRE Software Engineering and Economics
                Conference},
year =	 1997

}

@InProceedings{Hilliard-Rice-Schwarm96,

author =	 {Rich Hilliard and Timothy B. Rice and Stephen
                C. Schwarm},
title =	 {The Architectural Metaphor as a Foundation for
                Systems Engineering},
booktitle =	 {Proceedings of Sixth Annual International Symposium
                of the International Council on Systems Engineering},
year =	 1996

}

@InProceedings{Hilliard-Rice98,

author =	 {Rich Hilliard and Timothy B. Rice},
title =	 {Expressiveness in Architecture Description
                Languages},
booktitle =	 {Proceedings of the 3rd International Software
                Architecture Workshop},
pages =	 {65--68},
year =	 1998,
editor =	 {Jeff N. Magee and Dewayne E. Perry},
publisher =	 {ACM Press},
note =	 {1 and 2 November 1998, Orlando FL}

}

@Misc{Hilliard-Sovinsky97,

author =	 {Rich Hilliard and Vivian E. Sovinsky},
title =	 {Architecture Description Framework (ADF) Workbook},
howpublished = {MII},
institution =	 {The MITRE Corporation},
year =	 1997

}

@InProceedings{Hilliard2000,

author =	 {Rich Hilliard},
title =	 {Views as Modules},
year =	 2000,
booktitle =	 {Proceedings Fourth International Software
                Architecture Workshop (ISAW-4), 4 and 5 June 2000,
                Limerick, Ireland},
pages =	 {7--10},
editor =	 {Bob Balzer and Henk Obbink}

}

@InProceedings{Hilliard2000,

author =	 {Rich Hilliard},
title =	 {Views as Modules},
year =	 2000,
booktitle =	 {Proceedings Fourth International Software
                Architecture Workshop (ISAW-4), 4 and 5 June 2000,
                Limerick, Ireland},
pages =	 {7--10},
editor =	 {Bob Balzer and Henk Obbink}

}

@Unpublished{Hilliard2000a,

author =	 {Rich Hilliard},
title =	 {TOGAF paper},
howpublished = {},
month =	 {},
year =	 2000,
url =		 {}

}

@Unpublished{Hilliard2000a,

author =	 {Rich Hilliard},
title =	 {TOGAF paper},
howpublished = {},
month =	 {},
year =	 2000,
url =		 {}

}

@Unpublished{Hilliard2001,

author =	 {Rich Hilliard},
title =	 {{IEEE Std} 1471 and Beyond},
note =	 {Position paper for first SEI software architecture
                representation workshop},
month =	 dec,
year =	 2000,
url =		 {}

}

@Unpublished{Hilliard2001,

author =	 {Rich Hilliard},
title =	 {{IEEE Std} 1471 and Beyond},
note =	 {Position paper for first SEI software architecture
                representation workshop},
month =	 dec,
year =	 2000,
url =		 {}

}

@Unpublished{Hilliard2001a,

author =	 {Rich Hilliard},
title =	 {Three Models for the Description of Architectural
                Knowledge: Viewpoints, Styles, and Patterns},
note =	 {Submission to WICSA-2},
month =	 jan,
year =	 2001,

}

@Unpublished{Hilliard2001b,

author =	 {Rich Hilliard},
title =	 {Viewpoint Modeling},
year =	 2001,
note =	 {Position paper for First ICSE Workshop on Describing
                Software Architecture with UML
                (http://www.rational.com/\-events/ICSE2001/\-ICSEwkshp/\-HILLIARDViewpointModeling.pdf)}

}

@Unpublished{Hilliard2001b,

author =	 {Rich Hilliard},
title =	 {Viewpoint Modeling},
year =	 2001,
note =	 {Position paper for First ICSE Workshop on Describing
                Software Architecture with UML
                (http://www.rational.com/\-events/ICSE2001/\-ICSEwkshp/\-HILLIARDViewpointModeling.pdf)}

} @InProceedings{Hilliard2001c,

author = 	 {Rich Hilliard},
title = 	 {``Don't Ask, Don't Tell Inference: architectural
                views and their interfaces},
booktitle = 	 {tbd},
OPTcrossref =  {},
OPTpages = 	 {},
OPTyear = 	 {},
OPTeditor = 	 {},
OPTvolume = 	 {},
OPTnumber = 	 {},
OPTseries = 	 {},
OPTaddress = 	 {},
OPTmonth = 	 {},
OPTorganization = {},
OPTpublisher = {},
OPTnote = 	 {Submission to 2nd International Workshop on Living
                with Inconsistency},
OPTannote = 	 {}

} @InProceedings{Hilliard90,

author = 	 {Rich Hilliard},
title = 	 {The notion of `architecture' in model-based software

engineering},

booktitle =	 {Proceedings of the Workshop on Domain-Specific

Architectures},

address =	 {Hidden Valley, PA},
year =	 1990,
month =	 jul

} @Unpublished{Hilliard95,

author = 	 {Rich Hilliard},
title = 	 {Dimensions of Architectural Thinking},
URL = 	 {http://katanga.mitre.org/ose/arch/Dimensions.ps},
year =	 1995,
note =         {MII}

}

@InProceedings{Hilliard96,

author = 	 {Rich Hilliard},
title = 	 {Representing Software Systems Architectures or,

components, connections and (why not?) first-class constraints and views},

booktitle =	 {Joint Proceedings of the SIGSOFT '96 Workshops},
pulisher =     {ACM Press}, 
year =	 1996

}

@Booklet{Hilliard97,

title = 	 {The Architect's Job},
author =	 {Rich Hilliard},
month =	 jun,
year =	 1997,
note =	 {Briefing for the US Air Force.}

}

@Misc{Hilliard99,

author = 	 {Rich Hilliard},
title = 	 {Views and viewpoints in software systems architecture},
howpublished = {Position paper from the {\em First Working IFIP
               Conference on Software Architecture}, San Antonio}, 
year =	 1999

}

@Misc{Hilliard99,

author = 	 {Rich Hilliard},
title = 	 {Views and viewpoints in software systems architecture},
howpublished = {Position paper from the {\em First Working IFIP
               Conference on Software Architecture}, San Antonio}, 
year =	 1999

}

@InProceedings{Hilliard99a,

author = 	 {Rich Hilliard},
title = 	 {Using the {UML} for architectural description},
editor =	 {Robert France and Bernhard Rumpe},
pages =	 {32--48},
publisher =	 {Springer},
volume =	 1723,
year =	 1999,
booktitle = 	 {$\ll$UML$\gg$'99 The Unified Modeling Language,
                Second International Conference}, 
series =	 {Lecture Notes in Computer Science}

}

@InProceedings{Hilliard99a,

author = 	 {Rich Hilliard},
title = 	 {Using the {UML} for architectural description},
editor =	 {Robert France and Bernhard Rumpe},
pages =	 {32--48},
publisher =	 {Springer},
volume =	 1723,
year =	 1999,
booktitle = 	 {$\ll$UML$\gg$'99 The Unified Modeling Language,
                Second International Conference}, 
series =	 {Lecture Notes in Computer Science}

} @Misc{Hilliard99b,

author =	 {Rich Hilliard},
title =	 {Aspects, Concerns, Views, ...},
howpublished = {Position paper for OOPSLA'99 Workshop on
                Multi-Dimensional Separation of Concerns},
month =	 nov,
year =	 1999,
url = 	 {http://www.cs.ubc.ca/~murphy/multid-workshop-oopsla99/}

} @Misc{Hilliard99b,

author =	 {Rich Hilliard},
title =	 {Aspects, Concerns, Views, ...},
howpublished = {Position paper for OOPSLA'99 Workshop on
                Multi-Dimensional Separation of Concerns},
month =	 nov,
year =	 1999,
url = 	 {http://www.cs.ubc.ca/~murphy/multid-workshop-oopsla99/}

} @Misc{Hilliard99c,

author =	 {Rich Hilliard},
title =	 {Patterns of Practical Architecting},
howpublished = {Position paper for OOPSLA'99 Workshop on
                Patterns in Software Architecture},
month =	 nov,
year =	 1999,
url = 	 {http://www.eclipse.net/~tomo/pisa/oopsla99/}

} @Misc{Hilliard99c,

author =	 {Rich Hilliard},
title =	 {Patterns of Practical Architecting},
howpublished = {Position paper for OOPSLA'99 Workshop on
                Patterns in Software Architecture},
month =	 nov,
year =	 1999,
url = 	 {http://www.eclipse.net/~tomo/pisa/oopsla99/}

} @TechReport{Hilliard99d,

author = 	 {Rich Hilliard},
title = 	 {Building blocks for extensibility in the {UML}},
institution =  {Object Management Group},
year = 	 1999,
note = {Response to Object Management Group's Request for
                Information for Unified Modeling Language
                2.0. Available from OMG as: ad/99-12-12. See also:
                ad/99-12-13 and ad/99-12-14},
URL =          {http://cgi.omg.org/cgi-bin/doc?ad/99-12-12.pdf}

} @TechReport{Hilliard99d,

author = 	 {Rich Hilliard},
title = 	 {Building blocks for extensibility in the {UML}},
institution =  {Object Management Group},
year = 	 1999,
note = {Response to Object Management Group's Request for
                Information for Unified Modeling Language
                2.0. Available from OMG as: ad/99-12-12. See also:
                ad/99-12-13 and ad/99-12-14},
URL =          {http://cgi.omg.org/cgi-bin/doc?ad/99-12-12.pdf}

} @InCollection{Hilliard:2001x,

author = 	 {Rich Hilliard},
title = 	 {IEEE~1471 and Beyond},
booktitle = 	 {Workshop on Software Architecture Representation, 16-17 January 2001},
OPTcrossref =  {},
OPTpages = 	 {},
OPTpublisher = {Software Engineering Institute},
OPTyear = 	 {},
OPTeditor = 	 {},
OPTvolume = 	 {},
OPTnumber = 	 {},
OPTseries = 	 {},
OPTtype = 	 {},
OPTchapter = 	 {},
OPTaddress = 	 {},
OPTedition = 	 {},
url = 	 {http://www.sei.cmu.edu/publications/documents/01.reports/01sr010.html},
OPTnote = 	 {},
OPTannote = 	 {}

} @inproceedings{Hoek+:ISAW3,

author	= "A.~van~der~Hoek and D.M.~Heimbigner and A.L.~Wolf",
title		= "{Versioned Software Architecture}",
booktitle     = ISAW3,
month         = nov,
year          = 1998,
pages         = "73--76"}

@book{Hofmeister+:AW00,

author	= "C.~Hofmeister and R.L.~Nord and D.~Soni",
title		= "{Applied Software Architecture}",
publisher	= Addison,
address	= Addison-add,
year		= 2000}

@InProceedings{Hofmeister-Nord-Soni95,

author = 	 {C. Hofmeister and R. L. Nord and D. Soni},
title = 	 {Architectural descriptions of software systems},
booktitle = 	 IWASS1,
editor =	 {D. Garlan},
year =	 1995,
address =	 {Seattle, WA},
note =         {Published as CMU--CS--TR--95--151},
pages =	 {127--137},

} @InProceedings{Hofmeister-Nord-Soni99,

author =	 {C. Hofmeister and R. L. Nord and D. Soni},
title =	 {Describing software architectures with {UML}},
booktitle =	 wicsa1,
pages =	 {145--160},
year =	 1999,
editor =	 {Patrick Donohoe},
publisher =	 {Kluwer Academic Publishers}

} @Book{Hofmeister-Nord-Soni99a,

author =	 {C. Hofmeister and R. Nord and D. Soni},
title = 	 {Applied Software Architecture},
publisher = 	 {Addison-Wesley},
year = 	 1999

} @Book{Hofmeister-Nord-Soni99a,

author =	 {C. Hofmeister and R. Nord and D. Soni},
title = 	 {Applied Software Architecture},
publisher = 	 {Addison-Wesley},
year = 	 1999

} @TechReport{Horowitz,

author = 	 {Barry M. Horowitz},
title = 	 {The Importance of Architecture in {DOD} Software},
institution =  {The MITRE Corporation},
year = 	 1991,
number =	 {M 91-35},
month =	 jul

} @TechReport{ICAM,

author = 	 {SofTech},
title = 	 {{Integrated Computer-Aided Manufacturing (ICAM) Task

I -- Final Report}},

institution =  {Air Force Materials Laboratory},
year = 	 1978,
number =	 {AFML--TR--78--148}

} @Misc{IEEE-APG,

author = 	 {IEEE Architecture Planning Group},
title = 	 {Action Plan for Future Architectural Standards},
institution =  {IEEE Software Engineering Standards Committee},
year = 	 1996

} @Manual{IEEE1471:2000,

title = {ANSI/IEEE Std 1471--2000 Recommended Practice for Architectural Description

of Software-Intensive Systems},

year = 2000,
month = oct,
IEEE-standard-number = "IEEE Std 1471-2000",

}

@Proceedings{IWASS1995,

title = 	 IWASS1,
year = 	 1995,
editor =	 {D. Garlan},
month =	 {April 24--25},
address =	 {Seattle, WA},
note =         {Published as CMU--CS--TR--95--151}

}

@inproceedings{Inverardi+:COORD97,

author	= "P.~Inverardi and A.L.~Wolf and D.~Yankelevich",
title		= "{Checking Assumptions in Component Dynamics at the

Architectural Level}",

booktitle	= COORD97,
publisher	= Springer,
series	= LNCS,
number	= 1282,
month		= sep,
year		= 1997,
pages		= "46--63"}

@article{Inverardi+:TOSEM00,

author	= "P.~Inverardi and A.L.~Wolf and D.~Yankelevich",
title		= "{Static Checking of System Behaviors Using Derived

Component Assumptions}",

journal	= ACM-TOSEM,
volume	= 9,
number	= 3,
month		= jul,
year		= 2000,
pages		= "239--272"}

@InProceedings{Inverardi-Wolf-Yankelvich97,

author =	 {P. Inverardi and A. L. Wolf and D. Yankelevich},
title =	 {Checking Assumptions in Component Dynamics at the
                Architectural Level},
booktitle =	 {Second International Conference on Coordination
                Models and Languages (COORD '97)},
pages =	 {46--63},
year =	 1997,
number =	 1282,
series =	 {Lecture Notes in Computer Science},
address =	 {Berlin},
publisher =	 {Springer},
URL =		 {http://www.cs.colorado.edu/~serl/arch/Papers.html},
abstract =	 {A critical challenge faced by the developer of a
                software system is to understand whether the
                system's components correctly integrate. While type
                theory has provided substantial help in detecting
                and preventing errors in mismatched static
                properties, much work remains in the area of
                dynamics. In particular, components make assumptions
                about their behavioral interaction with other
                components, but currently we have only limited ways
                in which to state those assumptions and to analyze
                those assumptions for correctness. We have begun to
                formulate a method that addresses this problem. The
                method operates at the architectural level so that
                behavioral integration errors, such as deadlock, can
                be revealed early in development. For each
                component, a specification is given both of its own
                interaction behavior and of the assumptions that it
                makes about the interaction behavior of the external
                context in which it expects to operate. We have
                defined an algorithm that, given such specifications
                for a set of components, performs ``adequacy
                checks between the component context assumptions and
                the component interaction behaviors. A configuration
                of a system is possible if and only if a successful
                way of ``matching actual behaviors with
                assumptions can be found. In effect, we are
                extending the usual notion of type checking to
                include the checking of behavioral compatibility.}

} @Article{Inverardi-Wolf95,

author = 	 {Paola Inverardi and Alexander L. Wolf},
title = 	 {Formal specification and analysis of software
                architectures using the chemical abstract machine
                model}, 
journal = 	 {IEEE Transactions on Software Engineering},
year = 	 1995,
volume =	 21,
number =	 4,
month =	 apr,
pages =	 {373--386}

} @article{InverardiWolf:TSE95,

author	= "P.~Inverardi and A.L.~Wolf",
title		= "{Formal Specification and Analysis of Software
                Architectures using the Chemical Abstract Machine Model}",
journal	= IEEE-TSE,
volume	= 21,
number	= 4,
month		= apr,
year		= 1995,
pages		= "373--386"}

@inproceedings{InverardiYankelevich:IWSSD8,

author	= "P.~Inverardi and D.~Yankelevich",
title		= "{Relating CHAM Descriptions of Software Architectures}",
booktitle	= IWSSD8,
organization	= IEEE-CS,
month		= mar,
year		= 1996,
pages		= "66--74"}

@InProceedings{Issarny-Bidan-Saridakis98,

author = 	 {Val\'{e}rie Issarny and Christophe Bidan and Titos Saridakis},
title = 	 {Characterizing Coordination Architectures According
                to Their Non-Functional Execution Properties},
booktitle = 	 {Proceedings of the 31st Annual Hawaii International
                Conference on System Sciences}, 
pages =	 {275-283},
year =	 1998

} @InProceedings{Issarny-Bidan-Saridakis98,

author = 	 {Val\'{e}rie Issarny and Christophe Bidan and Titos Saridakis},
title = 	 {Characterizing Coordination Architectures According
                to Their Non-Functional Execution Properties},
booktitle = 	 {Proceedings of the 31st Annual Hawaii International
                Conference on System Sciences}, 
pages =	 {275-283},
year =	 1998

} @InProceedings{Issarny-Saridakis-Zarras98,

author = 	 {Val\'{e}rie Issarny and Titos Saridakis and Apostolos Zarras},
title = 	 {Multi-View Description of Software Architectures},
booktitle = 	 {Proceedings of the 3rd International Software
                Architecture Workshop},
pages =	 {81--84},
year =	 1998,
editor =	 {Jeff N. Magee and Dewayne E. Perry},
publisher =	 {ACM Press},
note =	 {1-- 2 November 1998, Orlando, FL USA}

} @InProceedings{Issarny-Saridakis-Zarras98,

author = 	 {Val\'{e}rie Issarny, Titos Saridakis, Apostolos Zarras},
title = 	 {Multi-View Description of Software Architectures},
booktitle = 	 {Proceedings of the 3rd International Software
                Architecture Workshop},
pages =	 {81--84},
year =	 1998,
editor =	 {Jeff N. Magee and Dewayne E. Perry},
publisher =	 {ACM Press},
note =	 {1-- 2 November 1998, Orlando, FL USA}

} @Article{Jacobson-Palmkvist-Dyrhage96,

author = 	 {Ivar Jacobson and Karin Palmkvist and Susanne Dyrhage},
title = 	 {Systems of Interconnected Systems},
journal =	 {ROAD},
year =	 1996,
month =	 {May--June}

} @Article{Kande-Crettaz-Strohmeier-Sendall2002,

author = 	 {Mohamed M. Kand\'{e} and Valentin Crettaz and Alfred Strohmeier and Shane Sendall},
title = 	 {Bridging the Gap between IEEE 1471, Architecture Description Languages and UML},
journal = 	 {Journal on Software and Systems Modeling},
year = 	 2002,
volume =	 1,
number =	 2,
pages =	 {113--129},
annote = 	 {}

} @PhdThesis{Kande2003,

author = 	 {Mohamed Mancona Kand\'{e}},
title = 	 {A Concern-oriented Approach to Software Architecture},
school = 	 {\'{E}cole Polytechnique F\'{e}d\'{e}ral de Lausanne},
year = 	 2003,
note = "These n. 2796",
annote =	 {-}

} @Article{Kazman-Abowd-Bass-Clements96,

author = 	 {Rick Kazman and Gregory Abowd and Len Bass and Paul

Clements},

title = 	 {Scenario-based analysis of software architecture},
journal =	 {IEEE Software},
year =	 1996,
pages =	 {47--55},
month =	 nov

} @InProceedings{Kazman-Bass-Abowd-Clements95,

author = 	 {R. Kazman and L. Bass and G. Abowd and P. Clements},
title = 	 {An architectural analysis case study: {Internet}

information systems },

booktitle =	 IWASS1,
year =	 1995,
address =	 {Seattle, WA},
month =	 apr

} @InProceedings{Kazman-Bass-Abowd-Webb94,

author = 	 {R. Kazman and L. Bass and G. Abowd and M. Webb},
title = 	 {SAAM: a method for analyzing the properties of

software architectures},

booktitle =	 {Proceedings 16th International Conference on

Software Engineering},

year =	 1994,
address =	 {Sorrento, Italy}

} @TechReport{Kazman-Bass94,

author = 	 {R. Kazman and L. Bass},
title = 	 {Toward Deriving Software Architectures From Quality

Attributes},

institution =  {Software Engineering Institute},
year = 	 1994,
number =	 {CMU/SEI-94-TR-10}

} @Unpublished{Kazman-Burth97,

author = 	 {Rick Kazman and Marcus Burth},
title = 	 {Assessing Architectural Complexity},
note = 	 {Submitted to ICSE 97},
url =          {http://www.cgl.uwaterloo.ca/\homedir rnkazman/SE-papers.html}

} @Unpublished{Kazman-Clements-Abowd-Bass96,

author = 	 {Rick Kazman and Paul Clements and Gregory Abowd and

Len Bass},

title = 	 {Classifying Architectural Elements as a Foundation

for Mechanism Matching},

note = 	 {Unpublished ms.},
url =          {http://www.cgl.uwaterloo.ca/\homedir rnkazman/SE-papers.html}

} @InProceedings{Kazman96,

author = 	 {Rick Kazman},
title = 	 {Tool support for architecture analysis and design},
pages =	 {94--97},
booktitle =	 {Proceedings Second International Software

Architecture Workshop},

year =	 1996

} @Misc{Kenney-Luckham93,

author =	 {John J. Kenney and David C. Luckham},
title =	 {Specifying and testing conformance to reference architectures},
year =	 1993,
month =	 jun

} @InProceedings{Klein-Kazman-Bass-Carriere-Barbacci-Lipson99,

author = 	 {M. Klein and R. Kazman and L. Bass and J. Carriere
                and M. Barbacci and H. Lipson}, 
title = 	 {Attribute-Based Architecture Styles},
booktitle = 	 wicsa1,  
pages =	 {225--243},
year =	 1999,
editor =	 {Patrick Donohoe},
publisher =	 {Kluwer Academic Publishers},
url = 	 {http://www.sei.cmu.edu/ata/abas.html}

} @TechReport{Klein-Kazman99,

author = 	 {Mark Klein and Rick Kazman},
title = 	 {Attribute-Based Architectural Styles},
institution =  {Software Engineering Institute, Carnegie Mellon University},
year = 	 1999,
type =	 {Technical Report},
number =	 {CMU/SEI-99-TR-022 (ESC-TR-99-022)},
month =	 oct

} @Misc{Kogut-Clements95,

author =	 {Paul Kogut and Paul Clements},
title =	 {Features of Architecture Representation Languages},
year =	 1995,
howpublished = {http://www.stars.reston.unisysgsg.com/arch/sei-feature-model-draft.ps},
URL = 	 {http://www.stars.reston.unisysgsg.com/arch/sei-feature-model-draft.ps}

} @Article{Koning-vanVliet2003,

author = 	 {Henk Koning and Hans van Vliet},
title = 	 {Real-life IT architecture design reports and their
                relation to IEEE Std 1471 stakeholders and concerns},
journal = 	 {submitted},
year = 	 {2003},
OPTvolume = 	 {},
OPTnumber = 	 {},
OPTpages = 	 {},
OPTmonth = 	 {},
OPTnote = 	 {},
annote = 	 {-}

} @inproceedings{Kozaczynski:CBSE99,

author	= "W.~Kozaczynski",
title		= "{Composite Nature of Component}",
booktitle	= CBSE99,
month		= may,
year		= 1999,
pages		= "73--77"}

@inproceedings{KramerMagee:CDS98,

author	= "J.~Kramer and J.~Magee",
title		= "{Analysing Dynamic Change in Software Architectures: A

Case Study}",

booktitle	= CDS98,
organization	= IEEE-CS,
month		= may,
year		= 1998,
pages		= "91--100"}

@inproceedings{KramerMagee:COORD97,

author	= "J.~Kramer and J.~Magee",
title		= "{Exposing the Skeleton in the Coordination Closet}",
booktitle	= COORD97,
publisher	= Springer,
series	= LNCS,
number	= 1282,
month		= sep,
year		= 1997,
pages		= "18--31"}

@InProceedings{Kruchten-Thompson94,

author = 	 {Philippe B. Kruchten and C. J. Thompson},
title = 	 {An object-oriented, distributed architecture for

large scale {Ada} systems},

booktitle =	 {Proceedings TRI--Ada '94},
year =	 1994,
address =	 {Baltimore, MD},
month =	 nov

} @InProceedings{Kruchten95,

author = 	 {Philippe B. Kruchten},
title = 	 {Mommy, where do architectures come from?},
booktitle =	 IWASS1,
year =	 1995

} @Article{Kruchten95a,

author = 	 {Philippe B. Kruchten},
title = 	 {The 4+1 view model of architecture},
journal =	 {IEEE Software},
year =	 1995,
volume =	 {28},
number =	 {11},
pages =	 {42--50},
month =	 nov

} @InProceedings{Kruchten96,

author = 	 {Philippe Kruchten},
title = 	 {Software architecture --- a rational metamodel},
booktitle =	 {Proceedings 2nd International Workshop on the

Architecture of Software Systems},

year =	 1996

} @InProceedings{Kruchten96,

author = 	 {Philippe Kruchten},
title = 	 {Software architecture --- a rational metamodel},
booktitle =	 {Proceedings 2nd International Workshop on the

Architecture of Software Systems},

year =	 1996

} @InProceedings{Kruchten99a,

author = 	 {Philippe B. Kruchten},
title = 	 {The Software Architect},
booktitle = 	 wicsa1,
year =	 1999,
editor =	 {Patrick Donohoe},
publisher =	 {Kluwer Academic Publishers},
pages = 	 {565--583},
note =	 {February 1999, San Antonio, TX, USA}

} @InProceedings{Kruchten99a,

author = 	 {Philippe B. Kruchten},
title = 	 {The Software Architect},
booktitle = 	 wicsa1,
year =	 1999,
editor =	 {Patrick Donohoe},
publisher =	 {Kluwer Academic Publishers},
pages = 	 {565--583},
note =	 {February 1999, San Antonio, TX, USA}

} @Book{Kruchten99b,

author =	 {Philippe Kruchten},
title =  	 {The Rational Unified Process: an introduction},
publisher = 	 {Addison-Wesley},
year = 	 1999

} @Book{Kruchten99b,

author =	 {Philippe Kruchten},
title =  	 {The Rational Unified Process: an introduction},
publisher = 	 {Addison-Wesley},
year = 	 1999

} @inproceedings{Kruchten:ISAW2,

author	= "P.~Kruchten",
title		= "{Software Architectur---A Rational Metamodel}",
booktitle     = ISAW2,
month         = oct,
year          = 1996,
pages         = "5--7"}

@article{Kruchten:Software95,

author	= "P.~Kruchten",
title		= "{The 4+1 View Model of Architecture}",
journal	= IEEE-Software,
volume	= 12,
number	= 6,
month		= nov,
year		= 1995,
pages		= "42--50"}

@Book{Kruft,

author = 	 {Hanno-Walter Kruft},
title = 	 {A history of architectural theory from {Vitruvius}

to the present},

publisher = 	 {Zwemmer, Princeton Architectural Press},
year = 	 1994

} @PhdThesis{Land:2003,

author = 	 {Rikard Land <rikard.land@mdh.se>},
title = 	 {An Architectural Approach to Software Evolution and Integration},
school = 	 {},
year = 	 {},
OPTtype = 	 {},
OPTaddress = 	 {},
OPTmonth = 	 {},
url = 	 {http://www.mrtc.mdh.se/publications/0590.pdf},
OPTannote = 	 {}

} @TechReport{Lane,

author = 	 {T. G. Lane},
title = 	 {Studying Software Architecture Through Design Spaces

and Rules},

institution =  {Software Engineering Institute},
year = 	 1990,
number =	 {CMU/SEI-90-TR-18}

} @InProceedings{Lawson-Rossak-Simpson94,

author = 	 {H. W. Lawson and W. Rossak and H. R. Simpson},
title = 	 {Working Group Report -- {CBS} architecture},
booktitle =	 {Proceedings of the 1994 tutorial and workshop on

systems engineering of computer-based systems},

year =	 1994,
publisher =	 {IEEE Computer Society Press},
address =	 {Los Alamitos, CA}

} @InProceedings{Lawson-Rossak-Simpson94,

author = 	 {H. W. Lawson and W. Rossak and H. R. Simpson},
title = 	 {Working Group Report -- {CBS} architecture},
booktitle =	 {Proceedings of the 1994 tutorial and workshop on

systems engineering of computer-based systems},

year =	 1994,
publisher =	 {IEEE Computer Society Press},
address =	 {Los Alamitos, CA}

} @inproceedings{LeMetayer:FSE4,

author	= "D.~Le~M\'{e}tayer",
title		= "{Software Architecture Styles as Graph Grammars}",
booktitle	= FSE4,
organization	= SIGSOFT,
month		= oct,
year		= 1996,
pages		= "15--23"}

@article{LeMetayer:TSE98,

author	= "D.~Le~M\'{e}tayer",
title		= "{Describing Software Architecture Styles Using Graph

Grammars}",

journal	= IEEE-TSE,
volume	= 24,
number	= 7,
month		= jul,
year		= 1998,
pages		= "521--533"}

@InProceedings{Levis-Perdu94,

author = 	 {A. H. Levis and D. M. Perdu},
title = 	 {A systems engineering approach to information

architecture design},

year =	 1994,
booktitle =	 {Proceedings 1994 IFAC Symposium on Integrated

Systems Engineering} } @article{Luckham+:TSE95,

author	= "D.C.~Luckham and J.J.~Kenney and L.M.~Augustin

and J.~Vera and D.~Bryan and W.~Mann",

title		= "{Specification and Analysis of System Architecture Using

Rapide}",

journal	= IEEE-TSE,
volume	= 21,
number	= 4,
month		= apr,
year		= 1995,
pages		= "336--355"}

@Article{Luckham-Kenney-Augustin-Vera-Bryan-Mann95,

author = 	 {David C. Luckham and John J. Kenney and Larry M. Augustin

and James Vera and Doug Bryan and Walter Mann},

title = 	 {Specification and analysis of system architecture

using {Rapide}},

journal =	 {IEEE Transactions on Software Engineering},
volume =       21,
number =       4,
month =        apr,
year =	 1995

} @Article{Luckham-Vera-Bryan-Augustin-Belz93,

author = 	 {David C. Luckham and James Vera and Doug Bryan and

Larry Augustin and Frank Belz},

title = 	 {Partial Orderings of Event Sets and Their

Application to Prototyping Concurrent, Timed Systems},

journal =	 {Journal of Systems and Software},
year =	 1993,
volume =	 21,
number =	 3,
pages =	 {253--265},
month =	 jun,
abstract = {Rapide is a concurrent, object-oriented language

specifically designed for prototyping large concurrent systems. One of the principle design goals has been to adopt a computation model in which the synchronization, concurrency, dataflow, and timing aspects of a prototype are explicitly represented and easily accessible both to the prototype itself and to the prototyper. This paper describes the partially ordered event set (poset) computation model, and the features of Rapide for using posets in reactive prototypes and for automatically checking posets. An example prototyping scenario illustrates uses of the poset computation model, with and without timing.},

keywords = {Rapide, partial orders, prototyping, concurrency,
           real-time, architecture, programming languages.}

} @TechReport{Luckham-Vera-Meldal95,

author = 	 {David C. Luckham and James Vera and Sigurd Meldal},
title = 	 {Three concepts of system architecture},
institution =  {Stanford University},
year = 	 1995,
number =	 {CSL-TR-95-674},
month =	 jul,
URL =	 {http://anna.stanford.edu:80/rapide/rapide.html}

} @Article{Luckham-Vera95,

author = 	 {David C. Luckham and James Vera},
title = 	 {An event-based architecture definition language},
journal =	 {IEEE Transactions on Software Engineering},
year =	 1995,
volume =	 21,
number =	 9,
pages =	 {717--734},
month =	 sep

} @article{LuckhamVera:TSE95,

author	= "D.C.~Luckham and J.~Vera",
title		= "{An Event-based Architecture Definition Language}",
journal	= IEEE-TSE,
volume	= 21,
number	= 9,
month		= sep,
year		= 1995,
pages		= "717--734"}

@Unpublished{Lung-Kalaichelvan96,

author = 	 {Chung-Horng Lung and Kalai Kalaichelvan},
title = 	 {Metrics for software architecture analysis: a case

study in telecommunications},

note = 	 {Submitted to ICSE'97}

} @inproceedings{Madhav:AdaEurope96,

author	= "N.~Madhav",
title		= "{Testing Ada 95 Programs for Conformance to Rapide

Architectures}",

booktitle	= "{Proceedings of Ada-Europe '96}",
publisher	= Springer,
series	= LNCS,
number	= 1088,
month		= jun,
year		= 1996,
pages		= "123--134"}

@inproceedings{Magee+:ESEC5,

author	= "J.~Magee and N.~Dulay and S.~Eisenbach and J.~Kramer",
title		= "{Distributed Software Architectures}",
booktitle	= ESEC5,
publisher	= Springer,
series	= LNCS,
number	= 989,
month		= sep,
year		= 1995,
pages		= "137--153"}

@inproceedings{Magee+:FTDCS97,

author	= "J.~Magee and J.~Kramer and D.~Giannakopoulou",
title		= "{Analysing the Behaviour of Distributed Software

Architectures: A Case Study}",

booktitle	= "Fifth IEEE Workshop on Future Trends of Distributed

Computing Systems",

month		= oct,
year		= 1997,
pages		= "240--247"}

@InProceedings{Magee-Kramer95,

author = 	 {Jeff Magee and Jeff Kramer},
title = 	 {Modelling distributed software architectures},
booktitle = 	 IWASS1,
editor =	 {David Garlan},
year =	 1995

} @inproceedings{MageeKramer:FSE4,

author	= "J.~Magee and J.~Kramer",
title		= "{Dynamic Structure in Software Architectures}",
booktitle	= FSE4,
organization	= SIGSOFT,
month		= oct,
year		= 1996,
pages		= "3--14"}

@Article{Maier-Emery-Hilliard2002,

author = 	 {Mark Maier and David Emery and Rich Hilliard},
title = 	 {Introducing IEEE~1471},
journal = 	 {IEEE Computer},
year = 	 {2001},
OPTvolume = 	 {},
OPTnumber = 	 {},
OPTpages = 	 {},
OPTmonth = 	 apr,
OPTnote = 	 {},
annote = 	 {-}

} @Article{Maier-Emery-Hilliard:2003,

author = 	 {Mark W. Maier and David Emery and Rich Hilliard},
title = 	 {{ANSI/IEEE} 1471 and Systems Engineering},
journal = 	 {INCOSE Journal},
year = 	 {(to appear)}

} @InProceedings{Maier2000,

author = 	 {Mark W. Maier},
title = 	 {Model Organization through Viewpoints and Views},
booktitle = 	 {Proceedings of International Council on Systems
                Engineering Mid-Atlantic Regional Conference},
pages =	 {6.2-1--9},
year =	 2000

} @InProceedings{Maier2000,

author = 	 {Mark W. Maier},
title = 	 {Model Organization through Viewpoints and Views},
booktitle = 	 {Proceedings of International Council on Systems
                Engineering Mid-Atlantic Regional Conference},
pages =	 {6.2-1--9},
year =	 2000

} @InProceedings{Maier96a,

author = 	 {Mark W. Maier},
title = 	 {System Architecture: An Emergent Discipline?},
volume =	 3,
pages =	 {231--246},
booktitle =	 {1996 IEEE Aerospace Applications Conference

Proceedings},

year =	 1996

} @InProceedings{Maier96b,

author = 	 {Mark W. Maier},
title = 	 {Architecting principles for systems-of-systems},
booktitle =	 {Proceedings of Sixth Annual International Symposium

of the International Council on Systems Engineering},

year =	 1996

} @Article{Makkuni,

author = 	 {Ranjit Makkuni},
title = 	 {A Gestural Representation of the Process of Composing Chinese Temples},
journal =	 {IEEE Computer Graphics and Applications},
year =	 1987,
volume =	 7,
number =	 12,
month =	 dec

} @inproceedings{McIlroy:NATO68,

author	= "M.D.~McIlroy",
title		= "{Mass Produced Software Components}",
booktitle	= "{Proceedings of the NATO Conferences on Software

Engineering (1968/1969)}",

editor	= "P.~Naur and B.~Randell and J.N.~Buxton",
publisher	= "Petrocelli/Charter",
address	= "New York",
year		= 1976,
pages		= "88--98"}

@InProceedings{Medvidovic-Rosenblum99,

author = 	 {Nenad Medvidovic and David S. Rosenblum},
title = 	 {Assessing the suitability of a standard design
                method for modeling software architectures},
booktitle = 	 wicsa1,
pages =	 {161--182},
year =	 1999,
editor =	 {Patrick Donohoe},
publisher =	 {Kluwer Academic Publishers}

} @TechReport{Medvidovic97,

author = 	 {Nenad Medvidovic},
title = 	 {A Classification and Comparison Framework for

Software Architecture Description Languages},

institution =  {Department of Information and Computer Science,

University of California, Irvine},

year = 	 1997,
number =	 {UCI-ICS-97-02},
month =	 feb,
URL =          {ftp://www.ics.uci.edu/pub/arch/papers/TR-UCI-ICS-97-02.ps.gz}

} @inproceedings{Medvidovic:ESEC6,

author	= "N.~Medvidovic",
title		= "{A Framework for Classifying and Comparing Architecture

Description Languages}",

booktitle	= ESEC6,
publisher	= Springer,
series	= LNCS,
number	= 1301,
year		= 1997,
pages		= "60--76"}

@InProceedings{Melton-Garlan97,

author = 	 {Ralph Melton and David Garlan},
title = 	 {Architectural Unification},
booktitle =	 {Proceedings of CASCON '97},
year =	 1997,
month =	 nov

} @inproceedings{MendoncaKramer:IWPC98,

author	= "N.C.~Mendonca and J.~Kramer",
title		= "{Developing an Approach for the Recovery of Distributed

Software Architectures}",

booktitle     = IWPC98,
month         = jun,
year          = 1998,
pages         = "28--36"}

@InProceedings{Meszaros95,

author = 	 {Gerald Meszaros},
title = 	 {Software architecture in {BNR}},
booktitle =	 IWASS1,
year =	 1995

} @InProceedings{Meszaros97,

author = 	 {Gerard Meszaros},
title = 	 {Archi-patterns: a process pattern language for defining architectures},
booktitle = 	 {PLoP'97},
year =	 1997

} @Unpublished{Monroe-Garlan-Wile97,

author = 	 {R. Monroe and D. Garlan and D. Wile},
title = 	 Template:Acme StrawManual,
note =         {Available from the ACME Web site at CMU.}

} @Article{Monroe-Kompanek-Melton-Garlan97,

author = 	 {Robert T. Monroe and Andrew Kompanek and Ralph

Melton and David Garlan},

title = 	 {Architectural Styles, Design Patterns, and Objects},
journal =	 {IEEE Software},
year =	 1997,
pages =	 {43--52},
month =	 jan,
abstract =     {Software system builders are increasingly recognizing

the importance of exploiting design knowledge in the engineering of new systems. One way to do this is to define an architectural style for a collection of related systems. The style determines a coherent vocabulary of system design elements and rules for their composition. By structuring the design space for a family of related systems a style can, in principle, drastically simplify the process of building a system, reduce costs of implementation through reusable infrastructure, and improve system integrity through style-specific analyses and checks.

                Like architectural style, object-oriented design

patterns attempt to capture and exploit design knowledge to ease the process of designing software systems and reusing proven designs. There are, however, significant differences in the roles and capabilities of architectural styles and object-oriented design patterns, as there are between architectural design and object-oriented design. In this paper we illustrate the relationship between software architecture and object-oriented design, as well as the relationship between architectural styles and design patterns. We begin by defining our terms and then proceed to compare and contrast the various approaches with examples.},

URL = {http://www.cs.cmu.edu/afs/cs/project/able/ftp/ObjPatternsArch-ieee97.ps}

} @article{Moriconi+:TSE95,

author	= "M.~Moriconi and X.~Qian and R.A.~Riemenschneider",
title		= "{Correct Architecture Refinement}",
journal	= IEEE-TSE,
volume	= 21,
number	= 4,
month		= apr,
year		= 1995,
pages		= "356--372"}

@InProceedings{Moriconi-Qian94,

author = 	 {Mark Moriconi and Xiaolei Qian},
title = 	 {Correctness and composition of software architectures},
booktitle =	 {Proceedings of ACM SIGSOFT '94: Symposium on

Foundations of Software Engineering},

year =	 1994,
address =	 {New Orleans, LA},
month =	 dec

} @inproceedings{Naumovich+:ESEC6,

author	= "G.~Naumovich and G.S.~Avrunin and L.A.~Clarke

and L.J.~Osterweil",

title		= "{Applying Static Analysis to Software Architectures}",
booktitle	= ESEC6,
publisher	= Springer,
series	= LNCS,
number	= 1301,
year		= 1997,
pages		= "77--93"}

@Misc{Nord-Hofmeister-Soni99,

author =	 {R. L. Nord and C. Hofmeister and D. Soni},
title =	 {Preparing for change in the architecture design of
                large software systems},
howpublished = {Position paper from the {\em First Working IFIP
                Conference on Software Architecture}, 22--24
                February 1999: San Antonio},
year =	 1999

} @Unpublished{Ogush-Coleman-Beringer2000,

author = 	 {M. A. Ogush and D. Coleman and D. Beringer},
title = 	 {A template for documenting software and firmware
                architectures},
note = 	 {Draft version 1.3},
month =	 jan,
year =	 2000

} @inproceedings{Oreizy+:ICSE98,

author	= "P.~Oreizy and N.~Medvidovic and R.N.~Taylor",
title		= "{Architecture-Based Runtime Software Evolution}",
booktitle	= ICSE98,
organization	= ACM,
month		= apr,
year		= 1998,
pages		= "177--186"}

@Book{POSA96,

author =	 {Frank Buschmann and Regine Meunier and Hans Rohnert
                and Peter Sommerlad and Michael Stal}, 
title = 	 {Pattern-oriented software architecture: a system of patterns},
publisher = 	 {Wiley},
year = 	 1996

} @Article{Perry-Wolf92,

author = 	 {Dewayne E. Perry and Alexander L. Wolf},
title = 	 {Foundations for the study of Software Architecture},
journal =	 {ACM SIGSOFT Sofware Engineering Notes},
year =	 1992,
volume =	 17,
number =	 4,
month =	 oct,
annote =	 {Published version of their underground classic

``Software Architectures} } @article{PerryWolf:SEN92,

author	= "D.E.~Perry and A.L.~Wolf",
title		= "{Foundations for the Study of Software Architecture}",
journal	= SEN,
volume	= 17,
number	= 4,
month		= oct,
year		= 1992,
pages		= "40--52"}

@TechReport{Peterson-Stanley94,

author = 	 {A. S. Peterson and J. L. Stanley},
title = 	 {Mapping a Domain Model and Architecture to a Generic

Design},

institution =  {Software Engineering Institute},
year = 	 1994,
number =	 {CMU/SEI--94--TR--8}

} @Article{Pollak-Rissman94,

author = 	 {W. Pollak and M. Rissman},
title = 	 {Structural models and patterned architectures},
journal =	 {IEEE Computer},
year =	 1994,
pages =	 {67--68},
month =	 aug

} @article{Prieto-DiazNeighbors:JSS86,

author	= "R.~Prieto-Diaz and J.M.~Neighbors",
title		= "{Module Interconnection Languages}",
journal	= JSS,
volume	= 6,
number	= 4,
month		= nov,
year		= 1986,
pages		= "307--334"}

@Book{Rechtin-Maier96,

author = 	 {Eberhard Rechtin and Mark Maier},
title = 	 {The art of systems architecting},
publisher = 	 {CRC Press},
year = 	 1996

} @Book{Rechtin91,

author = 	 {Eberhardt Rechtin},
title = 	 {Systems architecting: creating and building complex

systems},

publisher = 	 {Prentice Hall},
year = 	 1991

} @inproceedings{RichardsonWolf:ISAW2,

author	= "D.J.~Richardson and A.L.~Wolf",
title		= "{Software Testing at the Architectural Level}",
booktitle     = ISAW2,
month         = oct,
year          = 1996,
pages         = "68--71"}

@Misc{Robbins-Medvidovic-Redmiles-Rosenblum,

author       = {Jason E. Robbins and Nenad Medvidovic and David
                F. Redmiles and David S. Rosenblum},
title        = {Integrating architecture description languages with
                a standard design method},
note         = {Presented at the Second EDCS Cross Cluster Meeting
                in Austin, Texas.}

} @techreport{Rosetti:UA97,

author	= "A.~Rosetti",
title		= "{Generazione di Test Cases da Specifiche Formali della

Architettura Software}",

institution	= "Dipartimento di Matematica Pura ed Applicata",
address	= "L'Aquila, Italy",
number	= "Tesi di Laurea",
month		= mar,
year		= 1997}

@Article{Ross-Goodenough-Irvine75,

author = 	 {Douglas T. Ross and John B. Goodenough and C. A. Irvine},
title = 	 {Software engineering: process, principles, and goals},
journal =	 {IEEE Computer},
year =	 1975,
volume =       8,
number =       5,
pages =	 {17--27},
month =	 may

} @Article{Rossak-Kirova-Jololian-Lawson-Zemel97,

author = 	 {Wilhelm Rossak and Vassilka Kirova and Leon Jololian

and Harold Lawson and Tamar Zemel },

title = 	 {A Generic Model for Software Architectures},
journal =	 {IEEE Software},
year =	 1997,
volume =	 14,
number =	 4,
pages =	 {84--92},
month =	 {July--August}

} @Book{Roth93,

author = 	 {Leland M. Roth},
title = 	 {Understanding Architecture},
publisher = 	 {Harper Collins},
year = 	 1993

} @PhdThesis{Rowe2000,

author = 	 {David Rowe},
title = 	 {An Ontological Model of Computer Based Systems and Architectural Change},
school = 	 {University of Technology, Sydney},
year = 	 2000,
annote =	 {-}

} @InProceedings{Royce89,

author = 	 {Walker E. Royce},
title = 	 {Reliable, reusable {Ada} components for constructing

large, distributed multi-task networks: {Network Architecture Services (NAS)}},

booktitle =	 {TRI-Ada Proceedings},
year =	 1989,
address =	 {Pittsburgh},
month =	 oct

} @InProceedings{Royce90,

author = 	 {Walker E. Royce},
title = 	 {{TRW}'s {Ada} process model for incremental

development of large software systems},

booktitle =	 {Proceedings of the 12th International Conference on

Software Engineering},

year =	 1990,
address =	 {Nice, France},
month =	 {March 26--30}

} @Book{Ruskin,

author = 	 {John Ruskin},
title = 	 {The seven lamps of architecture},
publisher = 	 {J. Wiley},
year = 	 1849

} @TechReport{SARA2002,

author = 	 {The SARA Working Group},
title = 	 {Software Architecture Review and Assessment (SARA) Report},
institution =  {The SARA Working Group},
year = 	 2002,
number =	 {version 1.0},
annote = 	 {-}

} @TechReport{SBIS,

author = 	 {Timothy B. Rice and others},
title = 	 {Sustaining Base Information Services ({SBIS}) Software

Architecture},

institution =  {The MITRE Corporation},
year = 	 1994,
number =	 {W114-HU-161},
address =	 {Ft. Huachuca, AZ},
month =	 sep

} @InProceedings{Saridakis-Issarny99,

author = 	 {Titos Saridakis and Valérie Issarny},
title = 	 {Developing Dependable Systems Using Software Architecture},
booktitle = 	 wicsa1,
year =	 1999,
editor =	 {Patrick Donohoe},
publisher =	 {Kluwer Academic Publishers},
note =	 {February 1999, San Antonio, TX, USA}

} @InProceedings{Saridakis-Issarny99,

author = 	 {Titos Saridakis and Valérie Issarny},
title = 	 {Developing Dependable Systems Using Software Architecture},
booktitle = 	 wicsa1,
year =	 1999,
editor =	 {Patrick Donohoe},
publisher =	 {Kluwer Academic Publishers},
note =	 {February 1999, San Antonio, TX, USA}

} @TechReport{Saunders-Horowitz-Mleziva92,

author = 	 {Thomas F. Saunders and Barry Horowitz and Matt L. Mleziva},
title = 	 {New Process for Acquiring Software Architecture},
institution =  {The MITRE Corporation},
year = 	 1992,
number =	 {M 92B0000126},
URL =          {http://info.mitre.org/edm/corp/general/m092b126/m092b126.html}

} @inproceedings{Schwanke+:IWSSD8,

author	= "R.W.~Schwanke and V.A.~Strack and T.~Werthmann-Auzinger",
title		= "{Industrial Software Architecture with Gestalt}",
booktitle	= IWSSD8,
organization	= IEEE-CS,
month		= mar,
year		= 1996,
pages		= "176--180"}

@article{Shaw+:TSE95,

author	= "M.~Shaw and R.~DeLine and D.V.~Klein and

T.L.~Ross and D.M.~Young and G.~Zelesnik",

title		= "{Abstractions for Software Architecture and

Tools to Support Them}",

journal	= IEEE-TSE,
volume	= 21,
number	= 4,
month		= apr,
year		= 1995,
pages		= "314--335"}

@Unpublished{Shaw-Clements96,

author = 	 {Mary Shaw and Paul Clements},
title = 	 {How Should Patterns Influence Architecture
                Description Languages?},
note = 	 {Working paper for DARPA EDCS community},
month =	 jul,
year =	 1996

} @InProceedings{Shaw-Clements97,

author = 	 {Mary Shaw and Paul Clements},
title =        {A Field Guide to Boxology: Preliminary Classification

of Architectural Styles for Software Systems},

booktitle = 	 {Proc. COMPSAC97, 1st Int'l Computer Software and Applications Conference},
year =	 1997

} @TechReport{Shaw-Garlan94,

author = 	 {Mary Shaw and David Garlan},
title = 	 {Characteristics of higher-level languages for

software architecture},

institution =  {Carnegie Mellon University},
year = 	 1994,
number =	 {CMU/SEI--94--TR--23},
month =	 dec

} @Book{Shaw-Garlan96,

author = 	 {Mary Shaw and David Garlan},
title = 	 {Software Architecture: Perspectives on an emerging discipline},
publisher = 	 {Prentice Hall},
year = 	 1996

} @InCollection{Shaw-Garlan96a,

author = 	 {Mary Shaw and David Garlan},
title = 	 {Formulations and formalisms in software architecture},
booktitle =	 {Computer Science Today: Recent Trends and Development},
publisher =	 Springer,
year =	 1996,
pages =	 {307--323},
editor =	 {Jan van Leeuwen},
volume =	 1000,
series =	 {Lecture Notes in Computer Science}

} @Article{Shaw94,

author = 	 {Mary Shaw},
title = 	 {Comparing architectural design styles},
journal =	 {IEEE Software},
year =	 1994,
pages =	 {27--41},
month =	 nov

} @TechReport{Shaw94a,

author = 	 {Mary Shaw},
title = 	 {Procedure Calls Are the Assembly Language of

Software Interconnection: Connectors Deserve First-Class Status},

institution =  {Software Engineering Institute},
year = 	 1994,
number =	 {CMU/SEI--94--TR--2}

} @Article{Shaw95,

author = 	 {Mary Shaw},
title = 	 {Comparing architectural design styles},
journal =	 {IEEE Software},
year =	 1995,
volume =	 28,
number =	 11,
pages =	 {27--14},
month =	 nov

} @InProceedings{Shaw95a,

author = 	 {Mary Shaw},
title = 	 {Patterns for Software Architectures },
booktitle = 	 {Pattern Languages of Program Design: First Annual
                Conference on the Pattern Languages of Programming},
pages =	 {453-462},
year =	 1995,
editor =	 {James Coplien and Douglas Schmidt},
volume =	 1,
publisher =	 {Addison-Wesley}

} @InProceedings{Shaw96,

author = 	 {Mary Shaw},
title = 	 {Some Patterns for Software Architechture},
booktitle = 	 {Pattern Languages of Program Design: Second Annual
                Conference on Pattern Languages of Programming,
                September 1995},
pages =	 {255--269},
year =	 1996,
editor =	 {John Vlissides and James Coplien and Norman Kerth},
volume =	 2,
publisher =	 {Addison-Wesley}

} @article{Shaw:Software95,

author	= "M.~Shaw",
title		= "{Comparing Architectural Design Styles}",
journal	= IEEE-Software,
volume	= 12,
number	= 6,
month		= nov,
year		= 1995,
pages		= "27--41"}

@inproceedings{ShawClements:COMPSAC97,

author	= "M.~Shaw and P.~Clements",
title		= "{A Field Guide to Boxology: Preliminary Classification

of Architectural Styles for Software Systems}",

booktitle     = COMPSAC97,
month         = aug,
year          = 1997,
pages         = "6--13"}

@book{ShawGarlan:PH96,

author	= "M.~Shaw and D.~Garlan",
title		= "{Software Architecture: Perspectives on an Emerging

Discipline}",

publisher	= Prentice,
address	= Prentice-add,
year		= 1996}

@InProceedings{Smolander-Hoikka-Isokallio-Kataikko-Makela2002,

author = 	 {Kari Smolander and Kimmo Hoikka and Jari Isokallio
                and Mika Kataikko and Teemu M\"{a}kel\"{a}},
title = 	 {What is Included in Software Architecture? A Case
                Study in Three Software Organizations},
booktitle =	 {Ninth Annual IEEE International Conference and
                Workshop on the Engineering of Computer-Based
                Systems (ECBS 2002)},
pages =	 {131--139},
year =	 2002,
abstract =     {Software architecture is conventionally concerned with
                the structures at a high abstraction level
                describing the mainconstituents of a software
                system. However, there seems to be no common
                agreement of what these structures exactly are. This
                paper acts as an attempt to understand how the
                viewpoints from which we see the structures are
                selected. The rationale of having different
                viewpoints is reflected and a framework of the
                relationship between software architecture design
                and information systems development (ISD) is
                presented. It is noted that the selection of
                architectural viewpoints is based on the prevalent
                architectural practices in an organization and on
                the requirements from the project at hand. Examples
                of viewpoint selection are shown in the case study
                on the experiences from three different telecom-area
                software organizations. They end up using different
                sets of viewpoints in their software process,
                because of the differences in their resources,
                business practices, and technology.} 

} @InProceedings{Smolander-Paivarinta2002,

author = 	 {Kari Smolander and ?? P\"{a}iv\"{a}rinta},
title = 	 {Practical Rationale for Describing Software
                Architecture, Beyond Programming-in-The-Large},
booktitle =	 {Proceedings of 3rd Working IEEE/IFIP Conference on
                Software Architecture (WICSA3)}, 
pages =	 {113--125},
year =	 2002,
editor =	 {Jan Bosch},
annote = 	 {-}

} @InProceedings{Smolaner2002,

author = 	 {Kari Smolander},
title = 	 {Four Metaphors of Architecture in Software
                Organizations: Finding Out the Meaning of
                Architecture in Practice},
booktitle =	 {2002 International Symposium on Empirical Software Engineering (ISESE'02)},
pages =	 {211--222},
year =	 2002,
abstract =     {Current literature, research, and practice provide
                ambiguous meanings for the concept of architecture
                in the context of software and systems
                development. This qualitative and grounded theory
                based study delves into the practice of architecture
                design and description in three software-producing
                organizations. Nineteen architects, designers, and
                managers are interviewed and the general meanings of
                architecture in practical real-life situations are
                distilled and analyzed. The ambiguity of the concept
                of architecture receives its
                explanation. Architecture emerges as a plastic
                concept including diverging and simultaneous
                connotations for different stakeholders. The
                research process produces four general metaphors for
                architecture, "architecture as blueprint",
                "architecture as literature", "architecture as
                language ", and "architecture as decision". These
                metaphors and the research process are presented and
                discussed in detail.}

} @inproceedings{Soni+:ICSE17,

author	= "D.~Soni and R.L.~Nord and C.~Hofmeister",
title		= "{Software Architecture In Industrial Applications}",
booktitle	= ICSE17,
organization	= ACM,
month		= apr,
year		= 1995,
pages		= "196--207"}

@InProceedings{Soni-Nord-Hofmeister95,

author = 	 {D. Soni and R. L. Nord and C. Hofmeister},
title = 	 {Software Architecture in industrial applications},
booktitle = 	 {Proceedings of the 17th International Conference on
                Software Engineering},
year =	 1995,
address =	 {Seattle, Washington}

} @Article{Sowa-Zachman92,

author = 	 {J. F. Sowa and J. A. Zachman},
title = 	 {Extending and formalising the framework for

information systems architecture},

journal =	 {IBM Systems Journal},
year =	 1992,
volume =	 31,
number =	 3,
pages  =       {590--616}

} @InProceedings{Spitznagel-Garlan98,

author = 	 {Bridget Spitznagel and David Garlan},
title = 	 {Architecture-based performance analysis},
booktitle = 	 {Proceedings of the 10th International Conference on
                Software Engineering and Knowledge Engineering},
editor =	 {Yi Deng and Mark Gerken},
year =	 1998,
organization = {Knowledge Systems Institute},
pages =	 {146--151}

} @techreport{Stafford+:CU-CS-845-97,

author	= "J.A.~Stafford and D.J.~Richardson and A.L.~Wolf",
title		= "{Chaining: A Software Architecture Dependence

Analysis Technique}",

institution	= CU-CS,
address	= CU-add,
number 	= "CU-CS-845-97",
month		= sep,
year 		= 1997}

@techreport{Stafford+:CU-CS-858-98,

author	= "J.A.~Stafford and D.J.~Richardson and A.L.~Wolf",
title		= "{Aladdin: A Tool for Architecture-Level Dependence

Analysis of Software Systems}",

institution	= CU-CS,
address	= CU-add,
number 	= "CU-CS-858-98",
month		= apr,
year 		= 1998}

@TechReport{Stafford-Richardson-Wolf97,

author =	 {J.A. Stafford and D.J. Richardson and A.L. Wolf},
title =	 {Chaining: A Software Architecture Dependence
                Analysis Technique},
institution =	 {Department of Computer Science, University of
                Colorado},
year =	 1997,
type =	 {Technical Report},
number =	 {CU--CS--845--97},
month =	 sep,
abstract =	 {The emergence of formal architecture description
                languages provides an opportunity to perform
                analyses at high levels of abstraction. Research has
                primarily focused on developing techniques such as
                algebraic and transition-system analysis to detect
                component mismatches or global behavioral
                incorrectness. In this paper, we describe chaining,
                a technique similar in concept and application to
                program slicing, in which the goal is to reduce the
                portions of an architecture that must be examined by
                an architect for some purpose, such as testing or
                debugging. In chaining, links represent the
                dependence relationships that exist in an
                architectural specification. Links connect elements
                of the specification that are directly related,
                producing a chain of dependencies that can be
                followed during analysis. We illustrate the utility
                of chaining by showing how the technique can be used
                to answer various questions one might pose of a
                Rapide architecture specification.},
URL =          {http://www.cs.colorado.edu/~serl/arch/Papers.html#CU-CS-845-97}

} @TechReport{Stafford-Wolf2000,

author = 	 {Judith A. Stafford and Alexander L. Wolf},
title = 	 {Architecture-Level Dependence Analysis for Software Systems},
institution =  {Department of Computer Science, University of Colorado},
year = 	 2000,
type =	 {Technical Report},
number =	 {CU-CS-913-00},
address =	 {Boulder, Colorado},
month =	 dec,
abstract = {The emergence of formal software architecture
                description languages provides an opportunity to
                perform analyses at high levels of abstraction, as
                well as early in the development process.  Previous
                research has primarily focused on developing
                techniques such as algebraic and transition-system
                analysis to detect component mismatches or global
                behavioral incorrectness.  In this paper we motivate
                the utility and describe the challenges in
                developing a different kind of analysis for use at
                the architectural level, namely dependence analysis.
                Various kinds of dependence analyses have been used
                widely at the implementation level to aid program
                optimization, anomaly checking, program
                understanding, testing, and debugging.  However, the
                languages used for architectural description offer
                quite different features than the languages for
                which traditional dependence analysis techniques
                have been developed. We describe our initial
                approach to architecture-level dependence analysis
                and illustrate that approach through a prototype
                tool we have built, called Aladdin, to automatically
                perform the analysis.}  

} @TechReport{Stafford-Wolf99,

author = 	 {Judith A. Stafford and Alexander L. Wolf},
title = 	 {Architecture-Based Software Engineering},
institution =  {Department of Computer Science, University of Colorado},
year = 	 1999,
type =	 {Technical Report},
number =	 {CU-CS-891-99},
address =	 {Boulder, Colorado},
month =	 nov,
abstract = 	 {This paper provides an overview of the major issues
                and trends in architecture-based software
                engineering.  While all software systems can be
                described in terms of components and
                interconnections, such descriptions are not always
                documented.  Explicit description of software
                architecture provides a foundation for understanding
                and reasoning about both the functionality and
                quality of software systems very early in the
                development process as well as at a high level of
                abstraction.  In this paper, we discuss the
                formalization of architectural specification,
                including a review of several languages developed
                especially for architectural description, and follow
                this with a discussion of architectural analysis
                techniques that can be applied to architectures
                described in these languages.  Additionally, we
                discuss several other emerging concepts in software
                architecture that are having an influence on the
                general utility of the field.} 

} @inproceedings{StaffordWolf:ISAW3,

author	= "J.A.~Stafford and A.L.~Wolf",
title		= "{Architecture-Level Dependence Analysis in Support

of Software Maintenance}",

booktitle     = ISAW3,
month         = nov,
year          = 1998,
pages         = "129--132"}

@book{Szyperski:AW98,

author	= "C.~Szyperski",
title		= "{Component Software}",
publisher	= Addison,
address	= Addison-add,
year		= 1998}

@Manual{TAFIM,

title = 	 {Technical Architecture Framework for Information Management (TAFIM)},
organization = {Defense Information Systems Agency},
edition =	 {Version 2.0},
year =	 1995

} @Misc{TOGAF,

title =	 Template:The Open Group Architectural Framework (TOGAF) version XXX,
author =       Template:The Open Group,
howpublished = {http://www.opengroup.org/public/arch/},
year =	 2001,
URL = 	 {http://www.opengroup.org/public/arch/}

} @Misc{TOGAF5,

title =	 Template:The Open Group Architectural Framework (TOGAF) version 5,
author =       Template:The Open Group,
howpublished = {http://www.opengroup.org/public/arch/},
year =	 1999,
URL = 	 {http://www.opengroup.org/public/arch/}

} @Article{TSESA,

author = 	 {D. Garlan and D. E. Perry},
title = 	 {Introduction to the Special Issue on Software Architecture},
journal =	 {IEEE Transactions on Software Engineering},
year =	 1995,
volume =	 21,
number =	 4,
month =	 apr

} @article{Taylor+:TSE96,

author	= "R.N.~Taylor and N.~Medvidovic and K.M.~Anderson and

J.E.~Whitehead, Jr. and J.E.~Robbins and K.A.~Nies and P.~Oreizy and D.L.~Dubrow",

title		= "{A Component- and Message-Based Architectural Style

for GUI Software}",

journal	= IEEE-TSE,
volume	= 22,
number	= 6,
month		= jun,
year		= 1996,
pages		= "390--406"}

@InProceedings{Taylor-Medvidovic-Anderson-Whitehead-Robbins95,

author = 	 {R. N. Taylor and N. Medvidovic and K. M. Anderson

and E. J. Whitehead Jr. and J. E. Robbins},

title = 	 {A Component- and Message-Based Architectural Style

for GUI Software},

booktitle =	 {Proceedings of the Seventeenth International

Conference on Software Engineering},

year =	 1995

} @inproceedings{Tichy:ICSE4,

author	= "W.~Tichy",
title		= "{Software Development Control Based on Module

Interconnection}",

booktitle	= ICSE4,
organization	= IEEE,
month		= sep,
year		= 1979,
pages		= "29--41"}

@InProceedings{Tracz,

author = 	 {Will Tracz},
title = 	 {Test and analysis of software architectures},
booktitle =	 {Proceedings of the International Symposium on

Software Testing and Analysis},

year =	 1996,
publisher =	 {ACM Press},
abstract =	 {Some DoD programs now require prospective

contractors to demonstrate the superiority of their software architectures for new weapons systems. This acquisition policy provides new software engineering challenges that focus heavily on the test and analysis of software architectures in order to determine the ``best architecture in terms of its implementability, affordability, extendability, scalability, adaptability, and maintainability -- not overlooking whether or not it will meet the functional requirements of the system.} } @Unpublished{Vestal93,

author =       {Steve Vestal},
title = 	 {A cursory overview and comparison of four

architecture description languages},

year = 	 1993,
URL = 	 {http://www.stars.reston.unisysgsg.com/arch/four\_adl.ps}, 
institution =  {Honeywell Technology Center},
note =         {Unpublished}

} @manual{Vestal:PM97,

author	= "S.~Vestal",
title		= "{MetaH Programmer's Manual}",
organization	= "Honeywell, Inc.",
address	= "Minneapolis, MN",
year		= 1997}

@manual{Vestal:PM98,

author	= "S.~Vestal",
title		= "{MetaH Programmer's Manual Version 1.27}",
organization	= "Honeywell, Inc.",
address	= "Minneapolis, MN",
year		= 1998}

@book{Vidal+:ACM96,

editor	= "L.~Vidal and A.~Finkelstein and G.~Spanoudakis

and A.L.~Wolf",

title		= "{Joint Proceedings of the SIGSOFT~'96 Workshops}",
publisher	= ACM-press,
address	= ACM-press-add,
year		= 1996}

@InProceedings{Wermelinger-Fiadeiro98b,

author = 	 {M. Wermelinger and J. Fiadeiro},
title = 	 {Towards an Algebra of Architectural Connectors: a
                Case Study on Synchronisation for Mobility}, 
booktitle = 	 {Proc. 9th International Workshop on Software
                Specification and Design},
pages =	 {135--142},
year =	 1998,
publisher =	 {IEEE Computer Society Press}

} @inproceedings{Wermelinger:CDS98,

author	= "M.~Wermelinger",
title		= "{Towards a Chemical Model for Software Architecture 

Reconfiguration}",

booktitle	= CDS98,
organization	= IEEE-CS,
month		= may,
year		= 1998,
pages		= "111--118"}

@Book{Witt-Baker-Merrit94,

author = 	 {B. I. Witt and T. Baker and E. W. Merrit},
title = 	 {Software architecture and design -- principles,

models and methods},

publisher = 	 vanNos,
year = 	 1994,
address =	 vanNos-add

} @InProceedings{Woodside2001,

author = 	 {C. M. Woodside},
title = 	 {Software Resource Architecture and Performance
                Evaluation of Software Architectures}, 
booktitle = 	 {Proceedings of the 34th Hawaii International
                Conference on System Sciences},
year =	 2001

} @Article{Woodside95,

author = 	 {C.M. Woodside},
title = 	 {A Three-View Model for Performance Engineering of Concurrent Software},
journal = 	 {Transactions on Software Engineering},
year = 	 1995,
volume =	 21,
number =	 9,
pages =	 {754--767},
month =	 sep

} @Article{Youngs99,

author = 	 {R. Youngs and D. Redmond-Pyle and P. Spaas and E. Kahan},
title = 	 {A standard for architecture description},
journal = 	 {IBM Systems Journal},
year = 	 1999,
volume =	 38,
number =	 1,
url =          {http://www.almaden.ibm.com/journal/sj/381/youngs.html}

} @Article{Zachman,

author = 	 {J. A. Zachman},
title = 	 {A framework for information systems architecture},
journal =	 {IBM Systems Journal},
year =	 1987,
volume =	 26,
number =	 3,
pages =	 {276--292}

} @article{ZaremskiWing:TOSEM97,

author	= "A.M.~Zaremski and J.M.~Wing",
title		= "{Specification Matching of Software Components}",
journal	= ACM-TOSEM,
volume	= 6,
number	= 4,
month		= oct,
year		= 1997,
pages		= "333--369"}

@TechReport{vanDerHoek-Heimbigner-Wolf99,

author = 	 {André van der Hoek and Dennis Heimbigner and Alexander L. Wolf},
title = 	 {Capturing Architectural Configurability: Variants,
                Options, and Evolution}, 
institution =  {Department of Computer Science, University of Colorado},
year = 	 1999,
type =	 {Technical Report},
number =	 {CU-CS-895-99},
address =	 {Boulder, Colorado},
month =	 dec,
abstract = 	 {Although meant to be relatively stable, the
                architecture of a software system does, at times,
                change.  This simple yet important observation
                immediately raises the question of how changes to an
                architecture should be captured.  Current
                architecture description languages are not
                well-suited for this purpose, but existing
                techniques from the discipline of configuration
                management can be adapted to provide a solution.  In
                particular, we propose a novel representation,
                called configurable software architecture, that
                extends the traditional notion of software
                architecture with the concepts of variants, options,
                and evolution.  We discuss the details of the
                representation, present an environment that allows
                the specification of configurable software
                architectures, and highlight a few of the
                opportunities that we believe arise once
                architectural configurability can be precisely
                captured.} 

}

Personal tools