Skip to main content
  • 4228 Accesses

Abstract

During coding, it’s likely that you’ll have made a few changes to the design, so the code will now be slightly out of sync with the design diagrams. A depressingly common reaction at this stage is to deem the design documentation obsolete, throw it away, and continue all subsequent development work without doing any more design work.

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 59.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 74.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 99.99
Price excludes VAT (USA)
  • Durable hardcover 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.

Rights and permissions

Reprints and permissions

Copyright information

© 2007 Doug Rosenberg and Matt Stephens

About this chapter

Cite this chapter

(2007). Code Review and Model Update. In: Use Case Driven Object Modeling with UML. Apress. https://doi.org/10.1007/978-1-4302-0369-8_11

Download citation

Publish with us

Policies and ethics