Re: Object Oriented Analysis Is An Oxymoron

[TechComm Dood <techcommdood -at- gmail -dot- com>]

> While Use Cases and OOA data models can be useful, OOA
> functional modeling techniques (Use Cases, Activity
> Diagrams) lack rigor.  Only a Data Flow Diagram makes
> "holes" in our understanding of the logoc of a system
> glaringly obvious.  The output of OOA is going to be
> disjointed.  This is why I say that Object Oriented
> Analysis is an Oxymoron.

I would argue that your output is only as disjointed as the effort
used to produce it. I've been involved with OOA efforts in one form or
another for many years and I can honestly say from my experience that
in the heavy majority of cases flaws were produced by the efforts and
not by the processes.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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.