Skip to main content
  • 4336 Accesses

Abstract

Once you’ve finished robustness analysis, and you’ve held a preliminary design review, it’s time to begin the detailed design effort. By this time, your use case text should be complete, correct, detailed, and explicit. In short, your use cases should be in a state where you can create a detailed design from them.

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.

References

  1. See Refactoring: Improving the Design of Existing Code by Martin Fowler (Addison-Wesley, 2000).

    Google Scholar 

  2. Rebecca Wirfs-Brock and Alan McKean, Object Design: Roles, Responsibilities and Collaborations (New York: Addison-Wesley, 2003), p. 132

    Google Scholar 

Download references

Rights and permissions

Reprints and permissions

Copyright information

© 2007 Doug Rosenberg and Matt Stephens

About this chapter

Cite this chapter

(2007). Sequence Diagrams. In: Use Case Driven Object Modeling with UML. Apress. https://doi.org/10.1007/978-1-4302-0369-8_8

Download citation

Publish with us

Policies and ethics