Skip to main content
SpringerLink
Log in

Introducing UML: Object-Oriented Analysis and Design

  • Chapter
UML Applied: A .NET Perspective

Abstract

In UML, the L is for language, one of the definitions of which is “any means of communicating,” according to the Merriam-Webster Dictionary. That is the single overriding purpose of UML, or the Unified Modeling Language: to provide a comprehensive notation for communicating the requirements, architecture, implementation, deployment, and states of a system.

TIP For those who are impatient... If you already understand objects, you don’t need convincing that UML is a great thing, and you just want to start learning the UML notation right away, skip ahead to Chapter 2.

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

Access this chapter

Log in via an institution
eBook
USD 16.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 49.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. Grady Booch, Object-Oriented Analysis and Design with Applications, Second Edition ( Addison-Wesley, 1994 ). This is the classic work on GOAD, and a must-read.

    Google Scholar 

  2. Steve McConnell, Code Complete: A Practical Handbook of Software Construction (Microsoft Press, 1993), pp. 81-93, 116-130, 150. McConnell provides far more information on code design than I can cover here.

    Google Scholar 

  3. See http://www.mpimet.mpg.de/ for pictures and the history of this vessel.

  4. Steve McConnell, Software Project Survival Guide (Microsoft Press, 1997), p. 29

    Google Scholar 

  5. Kent Beck, Extreme Programming Explained: Embrace Change (Addison Wesley, 1999), pp. 21-25

    Google Scholar 

  6. In December 2002, Rational became a division of IBM Corporation.

    Google Scholar 

  7. Martin Fowler and Kendall Scott, UML Distilled, Second Edition (Addison-Wesley, 1999), pp. 13-38

    Google Scholar 

  8. Murray R. Cantor, Object-Oriented Project Management with UML (John Wiley & Sons, 1998), pp. 98-103

    Google Scholar 

  9. Putnam P. Texel and Charles B. Williams, Use Cases Combined with Booch/OMT/UML: Process and Products (Prentice Hall, 1997), pp. 3-9ff.

    Google Scholar 

  10. Ivar Jacoboson, Grady Booch, and James Rumbaugh, The Unified Software Development Process (Addison-Wesley, 1999 )

    Google Scholar 

  11. Scott W. Ambler, Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process (John Wiley & Sons, 2002 )

    Google Scholar 

  12. Klutz Press Editors, Draw the Marvel Comics Super Heroes (Klutz Press, 1995), pp. 20-32

    Google Scholar 

  13. Scott Adams, The Dilbert Principle (HarperBusiness, 1997), p. 324

    Google Scholar 

Download references

Authors
  1. Martin L. Shoemaker
    View author publications

    You can also search for this author in PubMed Google Scholar

Rights and permissions

Reprints and permissions

Copyright information

© 2004 Martin L. Shoemaker

About this chapter

Cite this chapter

Shoemaker, M.L. (2004). Introducing UML: Object-Oriented Analysis and Design. In: UML Applied: A .NET Perspective. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-0712-2_1

Download citation

  • DOI: https://doi.org/10.1007/978-1-4302-0712-2_1

  • Publisher Name: Apress, Berkeley, CA

  • Print ISBN: 978-1-59059-087-4

  • Online ISBN: 978-1-4302-0712-2

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics

Search

Navigation