Modeling of Architectures with UML

  • Thomas Weigert
  • David Garlan
  • John Knapman
  • Birger Møller-Pedersen
  • Bran Selic
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1939)


A critical level of abstraction in the modeling of a large, complex system is its architecture. At an architectural level one models the principal system elements and their interaction. Architectural models are typically used to provide an intellectually tractable, birds-eye view of a system and to permit design-time reasoning about system-level concerns such as performance, reliability, portability, and conformance to external standards and architectural styles.

In practice most architectural descriptions are informal documents. They are usually centered on box-and-line diagrams, with explanatory prose. Visual conventions are idiosyncratic, and usually project specific. As a result, architectural descriptions are only vaguely understood by developers, they cannot be analyzed for consistency or completeness, they are only hypothetically related to implementations, their properties cannot be enforced as a system evolves, and they cannot be supported by tools to help software architects with their tasks.

There exist several architecture description languages, but we are interested in the use of UML. We aim to identify requirements on architectural modeling and how different modeling concepts of UML meet these requirements. This paper is not intended as a critique of the UML but as a discussion of approaches to modeling architectures that have been tried, more or less successfully.


Interaction Point Architectural Modeling Architectural Element Architecture Description Language Enterprise Application Integration 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 2.
    J. Rumbaugh, I. Jacobson and G. Booch, Unified Modeling Language Reference Manual, Addison Wesley, 1999, p. 150.Google Scholar
  2. 3.
    B. Selic, UML-RT: A Profile for Modeling Complex Real-Time Architectures, Technical Report, ObjecTime Ltd., 1999.Google Scholar
  3. 6.
    D. Garlan, R. Monroe, D. Wile, ACME Reference Guide. Available from the URL
  4. 7.
    N. Medvidocic and R. Taylor, “A Framework for Classifying and Comparing Architecture Description Languages”, Proc. 6th European Software Engineering Conference, 1997.Google Scholar
  5. 8.
    C. Bock and J. Odell, “A Foundation for Composition”, Journal Of Object-Oriented Programming, Vol 7, No 6, 1994.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2000

Authors and Affiliations

  • Thomas Weigert
    • 1
  • David Garlan
    • 2
  • John Knapman
    • 3
  • Birger Møller-Pedersen
    • 4
  • Bran Selic
    • 5
  1. 1.MotorolaILUSA
  2. 2.Carnegie Mellon UniversityPAU.S.A
  3. 3.IBMWinchesterU.K.
  4. 4.Ericsson ASBillingstadNorway
  5. 5.Rational Software Inc.KanataCanada

Personalised recommendations