Skip to main content

How Can a Subsystem Be Both a Package and a Classifier?

  • 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:

  • 1182 Accesses

Abstract

The UML specifies that a subsystem is both a package and a classifier. This paper explores what that could possibly mean and explains why that was the right choice. It points out a key to the use of the concept in CASE tools, mentions the historical precedent for that key, and challenges CASE tools to support the flexibility that architects and designers need. Along the way, the paper reviews a method for discovering a good partition of a system into subsystems, describes a scheme for using UML to build a model of a system, and suggests some changes to the UML.

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. Oxford English Dictionary (Second Edition), Oxford University Press, Oxford (1994)

    Google Scholar 

  2. Information Processing—Open Distributed Processing—Reference Model—Foundations, X.902 | IS 10746-2. International Organization for Standardization, Geneva (1995) http://enterprise.shl.com/RM-ODP/

  3. Myers, G. J.: Reliable Software through Composite Design. Van Nostrand Reinhold, New York (1975)

    Google Scholar 

  4. Cox, B. J., Novobilski, A. J.: Object-oriented Programming—An Evolutionary Approach. Addison-Wesley, Menlo Park, California (1986)

    Google Scholar 

  5. Wirfs-Brock, R., Wilkerson, B., Wiener, L.: Designing Object-Oriented Software. Prentice Hall, Englewood Cliffs (1990)

    Google Scholar 

  6. Shaw, M., Garlan, D.: Software Architecture—Perspectives on an Emerging Discipline. Prentice-Hall, Englewood Cliffs (1996)

    Google Scholar 

  7. Object Management Group, OMG Unified Modeling Language Specification—Version 1.3. Object Management Group, Framingham, Massachusetts (1999) http://www.omg.org/cgi-bin/doc?ad/99-06-08

  8. Reenskaug, W., Reenskaug, T., Lehne, O. A.: Working With Objects: The OOram Software Engineering Method. Prentice Hall, Englewood Cliffs (1995)

    Google Scholar 

  9. Selic, B., Gullekson, G., Ward, P.T.: Real-Time Object-Oriented Modeling. John Wiley & Sons (1994)

    Google Scholar 

  10. Khoshafian, S. N., Copeland, G.P.: Object Identity, OOPSLA’ 86 Proceedings, in SIGPLAN Notices 21,11 (1986) 406–416.

    Article  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

Miller, J., Wirfs-Brock, R. (1999). How Can a Subsystem Be Both a Package and a Classifier?. 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_41

Download citation

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

  • 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