(Enter summary)
Abstract: The software architecture of most systems is described informally and diagrammatically by means of
boxes and lines. In order for these descriptions to be meaningful at all, the diagrams are understood by
interpreting the boxes and lines in specific, conventionalized ways. The imprecision of these interpretations
has a number of limitations. In this paper we consider these conventionalized interpretations as
architectural styles and provide a formal framework for their uniform definition. In... (Update)
Context of citations to this paper: More
.... patterns and their constraints comprise architectural styles, which are targeted at families of systems with shared characteristics [1,25]. Styles are therefore reusable software architectural idioms. There are many architectural styles currently in use: client server, pipe...
.... The advantages of creating explicit software architecture models and architectural descriptions have been identified by many [AAG95, SG96, BCK98] Communication among stakeholders Architectural description, as a common highlevel abstraction and common vocabulary, can...
Cited by: More
Toward Compos i t i on O f S t y l e - Con f orman t - So Tware Arch (2004)
(Correct)
Sensor Data Fusion for Context-Aware Computing Using.. - Wu (2003)
(Correct)
The Wright Architectural Specification Language - Allen, Garlan (1996)
(Correct)
Similar documents (at the sentence level):
65.8%: Formalizing Style to Understand Descriptions of Software.. - Abowd, Allen, Garlan (1995)
(Correct)
51.5%: Using Style to Understand Descriptions of Software Architecture - Abowd, Allen, Garlan (1993)
(Correct)
Active bibliography (related documents): More All
0.3: The Architectural Metaphor as a Foundation for Systems.. - Hilliard, II, Rice.. (1996)
(Correct)
0.3: Common Facilities RFI Response Imagery Facilities - Zahavi
(Correct)
0.2: Medither - an Event Space for Context-Aware Multimedia.. - Boll, Westermann (2003)
(Correct)
Similar documents based on text: More All
0.4: Distilling Software Architectural Primitives from.. - Mehta, Medvidovic (2002)
(Correct)
0.3: Rule-Based Systems Formalized Within a Software.. - Gamble Stiger Plant (1999)
(Correct)
0.0: Head-Driven Lexical Representation of Idioms in HPSG - Erbach (1992)
(Correct)
Related documents from co-citation: More All
28: Foundations for the study of software architecture
- Perry, Wolf - 1992
22: Specification and Analysis of System Architecture Using Rapide
- Luckham, Kenney et al. - 1995
21: Software Architecture: Perspectives on an Emerging Discipline (context) - Mary, Garlan - 1996
BibTeX entry: (Update)
G. Abowd, R. Allen, and D. Garlan. Formalizing style to understand descriptions of software architecture. ACM Transactions on Software Engineering and Methodology, 1995. http://citeseer.ist.psu.edu/abowd95formalizing.html More
@article{ abowd95formalizing,
author = "Gregory D. Abowd and Robert Allen and David Garlan",
title = "Formalizing style to understand descriptions of software architecture",
journal = "ACM Transactions on Software Engineering and Methodology",
volume = "4",
number = "4",
pages = "319--364",
year = "1995",
url = "citeseer.ist.psu.edu/abowd95formalizing.html" }
Citations (may not include all citations):
616
Notation: A Reference Manual (context) - Spivey, The - 1989
427
the criteria to be used in decomposing systems into modules (context) - Parnas - 1972
338
Foundations for the study of software architecture
- Perry, Wolf - 1992
213
An introduction to software architecture (context) - Garlan, Shaw - 1993
181
Connecting tools using message passing in the Field Environm.. (context) - Reiss - 1990
177
Formalizing architectural connection (context) - Allen, Garlan - 1994
121
A formal approach to software architectures
- Allen, Garlan - 1992
60
Formalizing design spaces: Implicit invocation mechanisms (context) - Garlan, Notkin - 1991
29
The domain-specific software architecture program (context) - Mettala, Graham - 1992
21
Adding implicit invocation to traditional programming langua.. (context) - Garlan, Scott - 1993
20
A formal model for module interconnection languages (context) - Rice, Seidman - 1994
15
Formal specifications as reusable frameworks (context) - Garlan, Delisle - 1990
9
Event-based concepts and language for system architecture
- Luckham, Vera - 1992
9
A reference model for computer assisted software engineering.. (context) - Earl - 1990
6
Tutorial on software design techniques (context) - Freeman - 1976
6
Towards formalized software architectures
- Allen, Garlan - 1992
3
Proceedings of the Workshop on Domain-Specific Software Arch.. (context) - the, Domain et al. - 1990
3
The importance of architecture in DOD software (context) - Horowitz - 1991
The graph only includes citing articles where the year of publication is known.
Documents on the same site (http://nenya.ms.mff.cuni.cz/thegroup/rel_work/r.html): More
Three Concepts of System Architecture - Luckham, Vera, Meldal (1995)
(Correct)
Acme: An Architecture Description Interchange Language - Garlan (1997)
(Correct)
The Polylith Software Bus - Purtilo (1991)
(Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC