I am a strong proponent of use cases, yet as I pointed out in my last column,1 I find that use cases are often misused. In this column I would like to address the configuration of the use case process, which I find to be equally misunderstood and misused.
An international corporation I am working with is developing a distributed, multi-currency, and multi-lingual, core financial system. In many ways the project exemplifies the best current practices for OO software development.