I suppose the answer is either "none of the above" or "all of the above" but I'm not sure which.
Originally posted by Darya Akbari:
Isn't the overall goal to describe an OO Software Development Process?
Originally posted by Dave Wood:
I'll throw out a few things that will be there...
- a chapter on analysis...how to work though a problem from requirements to an initial object model
- a chapter on writing use cases
- lots of discussion of fundamental OO concepts like encapsulation, polymorphism, coupling, cohesion, etc.
- use of UML throughout, but not complete UML diagram coverage...class diagrams will be very well covered, along with package diagrams, sequence diagrams, object diagrams, and possible one or two others
- high-level discussion of topics like design patterns, frameworks, refactoring, anti-patterns, etc.
- discussion of object-to-relational mapping
- use of Java for most examples that involve code...some bits of C++ and C# are also thrown in here and there
- and much much more!!! (how's that for marketing spin?!)
Hope that helps a bit.
PS: I can't make any promises, but if people have OO topics that they feel very strongly should be included in a book like this, I'm open to suggestions.
Originally posted by Daniel Rhoades:
UML distilled is a good book, but it's more of an overview, not really how to use UML on every day projects...
Originally posted by Bert Bates:
... our philosophy is that we'd rather be late but get it right, than be on time with the wrong topics!