Another question that is coming up is:
How can (or should) code metrics be presented to management ?
My view is that in all cases the metrics are something that can help make decisions around focus and prioritization. Management should be made aware of the metrics and what they mean to allow them to decide where to focus resources. If management is more levels away from the code then the Maintainability index can serve as a good, simple, metric.
Sometimes you may ship code that has low maintainability or very high complexity etc. and management would make this decision based on risk, time and resources and perhaps other factors. Metrics helps them make that decision with quantitative data.
Some possible options:
One option is to present the metrics in terms of risk and mitigation. For example:
I'd be very interested in hearing other approaches people have taken in presenting metrics or code analysis in general to management.