posted 22 years ago
I disagree on part of that.
There is no need to change the use cases. They are solid.
The domain model is *NOT A SOFTWARE DESIGN DIAGRAM* it is a tool to show relationships between *ideas* or *concepts* in a system. There is absolutely nothing wrong with adding or modifying relationships between these concepts to match the use cases.
In my submission, I asserted that the domain model is not in sync with the use cases. I took appropriate action.