Re: Object Oriented Analysis Is An Oxymoron
How would you write a functional description or theory of
operation if you don't understand how the system works?
For a "theory of operation", that understanding is indeed
necessary. For a functional description -- what it does
rather than how it works -- it is largely irrelevant. In
fact, in some cases knowing too much about the internals
makes getting that sort of description harder.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ROBOHELP X5: Featuring Word 2003 support, Content Management, Multi-Author
support, PDF and XML support and much more!
TRY IT TODAY at http://www.macromedia.com/go/techwrl
WEBWORKS FINALDRAFT: New! Document review system for Word and FrameMaker
authors. Automatic browser-based drafts with unlimited reviewers. Full
online discussions -- no Web server needed! http://www.webworks.com/techwr-l
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit
http://www.raycomm.com/techwhirl/ for more resources and info.
Follow-Ups:
- Re: Object Oriented Analysis Is An Oxymoron, Gene Kim-Eng
- Re: Object Oriented Analysis Is An Oxymoron, John Posada
References:
Object Oriented Analysis Is An Oxymoron: From: Tony Markos
Re: Object Oriented Analysis Is An Oxymoron: From: Gene Kim-Eng
Previous by Author:
Re: filesystem or file system?
Next by Author:
Re: Object Oriented Analysis Is An Oxymoron
Previous by Thread:
Re: Object Oriented Analysis Is An Oxymoron
Next by Thread:
Re: Object Oriented Analysis Is An Oxymoron
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads