TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
You are correct in stating that very rarely do
diagrams alone do the job - text is most often
necessary. But text needs to be properly structured
(organized). And this structuring is an analysis
activity. And, especially for systems of any
complexity, analysis needs to be rigorous - that is
model (diagram) based. This is true whether the final
deliverable contains diagrams or not.
> Text and diagrams are typically complementary
> approaches. Very rarely does
> diagramming alone work, except in Sergio Aragones'
> "marginal thinking"
> On 12/13/05, Dick Margulis <margulisd -at- comcast -dot- net>
> > Tony Markos wrote:
> > > Dick:
> > >
> > > Your right. Ed Yourdon, James Robertson, the
> > > amigos (the guys who invented the UML), the
> > > requirements engineering profession, and the
> heads of
> > > all systems engineering departments at all the
> > > universities are all wrong: Using text is the
> way to
> > > document a multidimensional system (of manual
> > > automated interacting procedures).
> > >
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l