Abstract is missing.
- A comedy of errors: the London Ambulance Service case studyAnthony Finkelstein, John Dowell. 2-5 [doi]
- A Case Study in Architectural Modelling: The AEGIS SystemRobert Allen, David Garlan. 6 [doi]
- Message from the Chairs7-8 [doi]
- Message from the Chairs9-15 [doi]
- A Survey of Architecture Description LanguagesPaul C. Clements. 16-25 [doi]
- Tool Specification with GTSLWolfgang Emmerich. 26-35 [doi]
- ACME/PRIME: Requirements Acquisition for Process-Driven SystemsMark Feblowitz, Sol J. Greenspan, Howard B. Reubenstein, Robert Walford. 36-45 [doi]
- A Mathematical Toolbox for the Software ArchitecJosé Luiz Fiadeiro, Tom Maibaum. 46-55 [doi]
- Towards a formal specification method for graphical user interfaces using modularized graph grammarsMichael Goedicke, Bettina Eva Sucrow. 56-65 [doi]
- Relating CHAM Descriptions of Software ArchitecturesPaola Inverardi, Daniel Yankelevich. 66-74 [doi]
- Specification and Verification of Real-Time Properties Using LOTOS and SQTLAbderrahmane Lakas, Gordon S. Blair, Amanda G. Chetwynd. 75-84 [doi]
- Requirements Elicitation Driven by Interviews: The Use of ViewpointsJulio Cesar Sampaio do Prado Leite, Ana Paula Pinho Gilvaz. 85-94 [doi]
- Formalizing System StructureMatthias Radestock, Susan Eisenbach. 95-104 [doi]
- A Framework for Heterogeneous Concurrency Control Policies in Distributed ApplicationsAntónio Rito Silva, João Pereira 0002, Pedro Sousa. 105-114 [doi]
- Visual Presentation of Software Specifications and DesignsGruia-Catalin Roman, Delbert Hart, Charles Calkins. 115-124 [doi]
- How Modeling Methods Affect the Process of Architectural Design Decisions: A Comparative StudyTetsuo Tamai. 125-135 [doi]
- Learning from InconsistencySteve Easterbrook. 136-140 [doi]
- Software Package Requirements and ProcurementAnthony Finkelsteiin, George Spanoudakis, Mark Ryan 0001. 141-145 [doi]
- Supporting the Selection of Software RequirementsJoachim Karlsson, Kevin Ryan. 146-149 [doi]
- Concern-driven design for a specification language supporting component-based software engineerinWojtek Kozaczynski, Jim Q. Ning. 150-154 [doi]
- A "Coming and Going" Approach to Specification Construction: A ScenarioNicole Lévy, Jeanine Souquières. 155-158 [doi]
- A computational mechanism for parallel problem decomposition during requirements engineeringNeil A. M. Maiden, Alistair G. Sutcliffe. 159-163 [doi]
- To Be and Not to Be: On Managing Inconsistency in Software DevelopmentBashar Nuseibeh. 164-169 [doi]
- Assuring Accuracy and Impartiality in Software Design Methodology ComparisonLeon J. Osterweil, Xiping Song. 170-171 [doi]
- Design Decision TreesAlexander Ran, Juha Kuusela. 172-175 [doi]
- Industrial software architecture with GestaltRobert W. Schwanke, Veronika A. Strack, Thomas Werthmann-Auzinger. 176-180 [doi]
- Truth vs Knowledge: The Difference Between What a Component Does and What We Know It DoesMary Shaw. 181-185 [doi]
- PDP: Programming A Programmable Design ProcessStanley M. Sutton Jr., Leon J. Osterweil. 186-190 [doi]