How do you get from use cases to code? More specifically, how do you get from use cases to code using a combination of OOAD techniques from Jacobson, Booch, and Rumbaugh?
I've been answering this question for people in a variety of ways, including onsite training workshops, multimedia CDROM tutorials, magazine articles, and EMAIL postings to OTUG, the Object Technology User's Group, since about 1992. Yep, that's about 3 years BEFORE the advent of UML. About a year and a half ago, I met Kendall Scott, who was looking for his next project after winning every award in sight with UML Distilled, and we decided it was time to answer the question in book form. As the book has taken shape, I've been "debugging" it during every UML training workshop that I've taught over the last 6 months, and I think we've pretty much got "the truth, the whole truth, and nothing but the truth" in it now. It's clear, it's concise, and it's easy to read and follow. In spots, it's even funny.
The book focuses on the practical aspects of driving a project from use cases to code in a traceable manner, and omits any and all theory that is extraneous to that goal. It comes complete with Top 10 lists at the back of every chapter, and "Analysis Paralysis Alerts" to warn you when you're about to fall into a modeling trap that your schedule probably doesn't allow for.
If you're having trouble weeding through the myriad of details that comprise the UML, and you don't want to learn three different ways to express every modeling concept, but just want somebody to tell you what you really need to know in the simplest and most straightforward manner, we think you'll like this book.
Doug Rosenberg, ICONIX President