Ubiquitous Dishonorability
While reading the delightful “Object-Oriented Analysis and Design with Applications“, Grady Booch et al extol the virtues of object-oriented analysis over the venerable, but passe, structured analysis approach to front end system composition. As they assert below, one of the benefits of OOA is that it’s easier and more natural to avoid mixing concrete design details with abstract analysis results.
Out of curiosity (which killed the cat), I scrolled down to see what note [4] meant:
WTF? Do they mean “because that’s the way the boss sez it must be done!” and “because that’s the way we’ve always done it!” aren’t honorable reasons for maintaining the status quo? If so, then dishonorable behavior runs rampant within the halls of most software shops the world over. But you already knew that, no?
Leave a reply to Mark Cancel reply
Why am I here?
WTF?
Meh!
D'oh!
My BTC Address
Bulldozer00's Blog 
That’s how it is here. After 7 1/2 years, I’m taking most of my OOA,OOP,OOD books home,and anything else that smells like book learnin’, which in our redneck shop is not appreciated…
I’m sorry, but not surprised, to hear that Mark. In my company, we’ve informally transitioned over to OOA & OOD for the most part, but it’s been a change that’s bubbled up from the bottom. Since it’s been informal progress, we have a mixture of structured analysis/design and OOAD projects going on.