Skip to main content

Using the UML for Architectural Description

  • Conference paper
  • First Online:
«UML»’99 — The Unified Modeling Language (UML 1999)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 1723))

Included in the following conference series:

Abstract

There is much interest in using the Unified Modeling Language (UML) for architectural description — those techniques by which architects sketch, capture, model, document and analyze architectural knowledge and decisions about software-intensive systems. IEEE P1471, the Recommended Practice for Architectural Description, represents an emerging consensus for specifying the content of an architectural description for a software-intensive system. Like the UML, IEEE P1471 does not prescribe a particular architectural method or life cycle, but may be used within a variety of such processes. In this paper, I provide an overview of IEEE P1471, describe its conceptual framework, and investigate the issues of applying the UML to meet the requirements of IEEE P1471.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. OMG Analysis and Design Platform Task Force. White paper on the profile mechanism (version 1.0). OMG Document ad/99-04-07, April 1999.

    Google Scholar 

  2. D. Bell and L. J. LaPadula. Secure computer systems: unified exposition and Multics interpretation. Technical Report MTR-2297, The MITRE Corporation, Bedford, MA, 1976.

    Google Scholar 

  3. Christophe Bidan and Valérie Issarny. Dealing with multi-policy security in large open distributed systems. In Proceedings of the 5th European Symposium on Research in Computer Security, number 1485 in Lecture Notes in Computer Science, pages 51–66, Belgium, September 1998. Springer-Verlag.

    Google Scholar 

  4. Grady Booch, James Rumbaugh, and Ivar Jacobson. The Unified Modeling Language User Guide. Addison-Wesley, 1999.

    Google Scholar 

  5. Alexander Egyed. Integrating architectural views in uml. Technical Report USC/CSE-99-TR-514, Center for Software Engineering, University of Southern California, Los Angeles, CA, 1999.

    Google Scholar 

  6. David E. Emery, Rich Hilliard, and Timothy B. Rice. Experiences applying a practical architectural method. In Alfred Strohmeier, editor, Reliable Software Technologies-Ada-Europe’ 96, number 1088 in Lecture Notes in Computer Science. Springer, 1996.

    Google Scholar 

  7. A. Finkelstein, J. Kramer, B. Nuseibeh, L. Finkelstein, and M. Goedicke. Viewpoints: a framework for integrating multiple perspectives in system development. International Journal of Software Engineering and Knowledge Engineering, 2(1):31–57, March 1992.

    Article  Google Scholar 

  8. A. Finkelstein and I Sommerville. The viewpoints FAQ. Software Engineering Journal, 11(1):2–4, 1996. Also available from ftp://cs.ucl.ac.uk/acwf/papers/viewfaq.ps.gz.

    Article  Google Scholar 

  9. Cristina Gacek, Ahmed Abd-Allah, Bradford Clark, and Barry W. Boehm. On the definition of software system architecture. In Proceedings of the First International Workshop on Architectures for Software Systems, Seattle, WA, 1995.

    Google Scholar 

  10. David Garlan, Robert T. Monroe, and David Wile. Acme: An architecture description interchange language. In Proceedings of CASCON’ 97, pages 169–183, November 1997.

    Google Scholar 

  11. Rich Hilliard. Views and viewpoints in software systems architecture. Position paper from the First Working IFIP Conference on Software Architecture, San Antonio, 1999.

    Google Scholar 

  12. Rich Hilliard, Michael J. Kurland, and Steven D. Litvintchouk. MITRE’s Architecture Quality Assessment. In 1997 MITRE Software Engineering and Economics Conference, 1997.

    Google Scholar 

  13. Rich Hilliard and Timothy B. Rice. Expressiveness in architecture description languages. In Jeff N. Magee and Dewayne E. Perry, editors, Proceedings of the 3rd International Software Architecture Workshop, pages 65–68. ACM Press, 1997. 1 and 2 November 1998, Orlando FL.

    Google Scholar 

  14. C. Hofmeister, R. L. Nord, and D. Soni. Architectural descriptions of software systems. In D. Garlan, editor, Proceedings of the First International Workshop on Architectures for Software Systems, pages 127–137, Seattle, WA, 1995. Published as CMU-CS-TR-95-151.

    Google Scholar 

  15. C. Hofmeister, R. L. Nord, and D. Soni. Describing software architectures with UML. In Patrick Donohoe, editor, Proceedings of the First Working IFIP Conference on Software Architecture, pages 145–160. Kluwer Academic Publishers, 1999.

    Google Scholar 

  16. IEEE Architecture Working Group. IEEE P1471/D5.0 Information Technology—Draft Recommended Practice for Architectural Description, August 1999. Available by request from http://www.pithecanthropus.com/~awg/.

  17. International Organization for Standardization. ISO/IEC 10746 1-4 Open Distributed Processing — Reference Model — Parts 1–4, July 1995. ITU Recommendation X.901-904.

    Google Scholar 

  18. Gregor Kiczales, John Lamping, Anurag Mendhekar, Chris Maeda, Cristina Lopes, Jean-Marc Loingtier, and John Irwin. Aspect-oriented programming. Xerox Palo Alto Research Center, 1997.

    Google Scholar 

  19. Philippe B. Kruchten. The 4+1 view model of architecture. IEEE Software, 28(11):42–50, November 1995.

    Article  Google Scholar 

  20. David C. Luckham, John J. Kenney, Larry M. Augustin, James Vera, Doug Bryan, and Walter Mann. Specification and analysis of system architecture using Rapide. IEEE Transactions on Software Engineering, 21(4), April 1995.

    Google Scholar 

  21. Nenad Medvidovic and David S. Rosenblum. Assessing the suitability of a standard design method for modeling software architectures. In Patrick Donohoe, editor, Proceedings of the First Working IFIP Conference on Software Architecture, pages 161–182. Kluwer Academic Publishers, 1999.

    Google Scholar 

  22. Object Management Group. Unified Modeling Language — Semantics (version 1.1), September 1997. OMG ad/97-08-04.

    Google Scholar 

  23. Object Management Group. Unified Modeling Language — Summary (version 1.1), September 1997. OMG ad/97-08-03.

    Google Scholar 

  24. Eberhard Rechtin and Mark Maier. The art of systems architecting. CRC Press, 1996.

    Google Scholar 

  25. Mary Shaw and David Garlan. Software Architecture: Perspectives on an emerging discipline. Prentice Hall, 1996.

    Google Scholar 

  26. D. Soni, R. L. Nord, and C. Hofmeister. Software architecture in industrial applications. In Proceedings of the 17th International Conference on Software Engineering, Seattle, Washington, 1995.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 1999 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Hilliard, R. (1999). Using the UML for Architectural Description. In: France, R., Rumpe, B. (eds) «UML»’99 — The Unified Modeling Language. UML 1999. Lecture Notes in Computer Science, vol 1723. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-46852-8_4

Download citation

  • DOI: https://doi.org/10.1007/3-540-46852-8_4

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-66712-4

  • Online ISBN: 978-3-540-46852-3

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics