Good book to show how to break down domain

[Sharpitect]

I downloaded the Zicom Mentor and worked through it. I feel I have a good understanding of what EA can do. I am absolutely amazed at what all it will do. My problem is - I'm still a little squishy on what must be some of the basics.

For example, I assume I start documenting my problem domain with use cases but how many? Should there be just 1 use case and all other diagrams relate back to it?

Can anybody recommend a good "modern" book that tells me how to break down my problem domain and into what kinds of diagrams and how many.

Also being a one man shop, I am responsible for the whole project. So on any given day, I have ideas for screen layouts, classes, work flows, as well as existing databases I need to import and document. Is there a book out there that shows me how to start in so many trenches and still successful work back to the beginning?

Any help is greatly appreciated.

Clay

[potterm]

Clay,

I would recommend Use Case Driven Object Modelling, by Doug Rosenberg and Kendall Scott.  It's very well written (almost entertaining in parts) and has lots of hints and tips.  It's also a manageable size (not so long that you never finish it!).

What's more, EA supports the ICONIX process that the book describes, including the robustness diagram notations.

Hope that helps,
Martin.

[Sharpitect]

Thanks, looks exactly like the book I'm looking for.