Re: Booch's book feels too philosophical rather than practical?
- From: "arnuld" <arnuld3@xxxxxxxxx>
- Date: 20 Jan 2007 09:24:36 -0800
I suggest you read Booch as if it was a novel. Don't try to understand
or absorb it. Then read "Designing Object-Oriented C++ Applications
using the Booch Method" by Martin and "Object-Oriented Design
Heuristics" by Riel. These two books really opened my eyes. Then read
Booch's book again and see what you think.
i dont have Booch, i have an illiegal pdf copy. book is too expensive,
nearly 2.5 times expensives than Rumbaugh's :-( if i need to purchase
then i will choose Rumbaugh. BTW, the other 2 books you mentioned, of
Reil & Robert Martin, are not available in India.
A couple of other book suggestions, not strictly OO: "The Pragmatic
Programmer" by Hunt & Thomas" and "Refactoring: Improving the Design of
Existing Code" by Fowler.
these 2, also, are not available in India. BUT these are available:
"OBJECT ORIENTED SOFTWARE ENGINEERING" by IVAR JACOBSON
"UNIFIED MODELING LANGUAGE USER GUIDE" by BOOCH / RUMBAUGH /
JACOBSON
"UNIFIED SOFTWARE DEVELOPMENT PROCESS" by JACOBSON / BOOCH /
RUMBAUGH
"UML DISTILLED" by MARTIN FOWLER / KENDALL SCOTT
"FUNDAMENTALS OF OBJECT ORIENTED DESIGN IN UML" by MEILIR PAGE JONES
"APPLYING UML & PATTERNS" by CRAIG LARMAN
"EXECUTABLE UML - FOUNDATION FOR MODEL DRIVEN ARCHITECURE" by MELLOR /
BALCER
"OBJECT ORIENTED MODELING & DESIGN WITH UML" by MICHAEL BLAHA / JAMES
RUMBAUGH
Read the post below as well:
http://groups.google.com/group/comp.software.patterns/browse_thread/threa
d/d6e77220da9d415c/2d3fa888f4ec1652?tvc=2&q=group%3A*software.patterns*+a
uthor%3Adaniel#2d3fa888f4ec1652
"out of my head", the problem explained by OP (Frank O'Haram in that
thread) really looks like Ph. D. thesis to me, disconnected from the
real world.
You don't have to intuit OO in order to take advantage of it:
what does that mean? ::
You don't have to intuit OO in order to "take advantage of" it:
OR
You don't have to intuit OO in order to "understand" it:
In procedural code, we are taught to move duplicated blocks of code into
a function. Those for whom procedural is "intuitive" are special in that
they can spot duplication before it's in the code and create that
function up front.
People who intuit OO can spot duplicated decision code before typing it.
However, like the beginner procedural person, you don't have to "get it"
in order to take advantage of it after the fact.
i don't see any difference between these 2 explanations. may be because
of my newbie-ness.
.
- Follow-Ups:
- Re: Booch's book feels too philosophical rather than practical?
- From: Daniel T.
- Re: Booch's book feels too philosophical rather than practical?
- References:
- Prev by Date: Re: Simples Rules make creating Big Balls of Mud impossible.
- Next by Date: Re: Booch's book feels too philosophical rather than practical?
- Previous by thread: Re: Booch's book feels too philosophical rather than practical?
- Next by thread: Re: Booch's book feels too philosophical rather than practical?
- Index(es):
Relevant Pages
|
