If you're building a big system with lots of modules, and you need to structure your code, have system-wide design constraints, or if you want to share some common aspects between parts of your system, presenting the solution from a development viewpoint should benefit you, along with software developers and testers.
A package diagram of the development view can be handy to show where different modules in your system are located, what their dependencies are, and other related modules (for example, residing in the same software layer). It doesn't need to be a UML diagram – even boxes and lines would do. If you plan for a module to be replaceable, this kind of diagram can show you what other software packages can be affected.
Tactics to increase reuse in your system, such as creating your own runtime framework for components, or tactics for increasing the coherence of your systems, such as a common approach to authentication, logging, internationalization...
