I am used to specifying requirements using the traditional "It must be possible" type of requirement list. Recently I have started working with business use cases to supplement the high level business requirement statements to get to the detail needed. I find these help greatly to focus the mind but do not always find it easy to sell this technique to stakeholders more used to the other type of document. The stakeholders feel these use cases can start to document a possible solution (which I do agree with to an extent) where before we would look for the analysts and designers to be offering a solution that will allow the requirements to be met. We are moving from a traditional mainframe to a JAVA based environment and developers using that technology do seem to expect the use case documents. Has anyone else come across the same resistance or could I be defining my use cases incorrectly