Skip to main content

Structuring UML Design Deliverables

  • Conference paper

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

Abstract

The idea of using Unified Modeling Language (UML) appeals to people, but actually using it can be challenging. Many would like to use UML for software development, but do not know how to structure design models and what the relationships between various UML diagrams are. This paper introduces a structure for design deliverables that can be used for software development with UML. The structure is based on a pattern of four deliverables describing classifier relationships, interactions, responsibilities and state machines. The pattern can be applied to different levels of abstraction and to different views on a software product. The paper also discusses practical considerations for documenting software design in the project repository as well as cases in which UML may not be the most appropriate notation to use. The conference presentation with speaker notes is available at this address: www.navision.com (click services).

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

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.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

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Cockburn, A.: Using Goal-Based Use Cases, Journal of Object Oriented Programming (November 1997), also available at http://members.aol.com/acockburn/papers/usecases.htm

  2. Coleman, D., et al.: Object-Oriented Development: The Fusion Method. Prentice Hall, Inc., Englewood Cliffs (1994)

    Google Scholar 

  3. Hruby, P.: The Object-Oriented Model for a Development Process. In: OOPSLA 1997, also available at http://www.navision.com/services/default.asp

  4. Rational Objectory Process 4.1, demo version, available at http://www.rational.com

  5. UML Notation Guide, version 1.1, Rational, September 1 1997, also at http://www.rational.com/uml

  6. Shlaer, S., Mellor, S.J.: Object Lifecycles: Modeling the World in States. Prentice Hall, Inc., Englewood Cliffs (1992)

    MATH  Google Scholar 

  7. Thibault, E.: What is BNF Notation?, available at http://cuiwww.unige.ch/db-research/Enseignement/analyseinfo/AboutBNF.html

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

Hruby, P. (1999). Structuring UML Design Deliverables. In: Bézivin, J., Muller, PA. (eds) The Unified Modeling Language. «UML»’98: Beyond the Notation. UML 1998. Lecture Notes in Computer Science, vol 1618. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-48480-6_22

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-48480-6_22

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-66252-5

  • Online ISBN: 978-3-540-48480-6

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics