Skip to main content

Abstract

How often have we seen a well-thought-out design degrade because we lose control over the way our code evolves? One common reason for that is badly managed dependencies. In Chapter 12 we looked at how Architecture Explorer and the dependency diagram can be used to visualize code dependencies and to help us detect problem areas in our codebase. It would be better, though, if instead of having a tool to help us find issues in our code, we had one that would help us prevent the problems in the first place.

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

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Joachim Rossberg and Mathias Olausson

About this chapter

Cite this chapter

Rossberg, J., Olausson, M. (2012). Using Layer Diagrams. In: Pro Application Lifecycle Management with Visual Studio 2012. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-4345-8_13

Download citation

Publish with us

Policies and ethics