Tutorial: describing software architecture with UML

ABSTRACT

The presence of a solid architectural vision is a key discriminator in the success or failure of a software project. This tutorial examines what software architecture is and what it is not. It discusses and illustrates how to describe architecture through a set of design viewpoints and views and how to express these views in the UML, in the spirit of the new IEEE Standard 1471:2000:Recommended practice for architectural description. The tutorial shows of how architectures drive the development process and how to capture architectural design patterns using the UML. It is illustrated by several widely applicable architectural patterns in different domain.

REFERENCES

• 1: James Rumbaugh , Ivar Jacobson , Grady Booch, The Unified Modeling Language reference manual, Addison-Wesley Longman Ltd., Essex, UK, 1998
• 2: IEEE Std. 1471:2000. Recommended Practice for Architectural Description, IEEE, New York, October 2000.
• 3: Philippe Kruchten, The 4+1 View Model of Architecture, IEEE Software, v.12 n.6, p.42-50, November 1995 [doi>10.1109/52.469759]
• 4: Rational Unified Process (RUP), Rational Software, Cupertino, Ca., 2000
• 5: W. Kozaczynski, Architecture Description Standard (ADS), Rational Software, Cupertino, 1999
• 6: W. Kozaczynski, Reusable Asset Specification (RAS), Rational Software, Cupertino, 2000
• 7: Bran Selic , Garth Gullekson , Paul T. Ward, Real-time object-oriented modeling, John Wiley & Sons, Inc., New York, NY, 1994

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.11 Software Architectures
            Subjects: Domain-specific architectures

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.3 Coding Tools and Techniques
          Subjects: Structured programming
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications

          Nouns: UML

General Terms:
Design, Languages, Performance