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.
Subject:RE: Object Oriented Analysis Is An Oxymoron From:"Ronica Roth" <rroth -at- globusandcosmos -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 20 Aug 2004 11:30:18 -0600
I tried three times to respond to the original post, and I just
couldn't. I could go on for days, and I don't have days. I love OOAD,
and I love UML, and I believe in how both--along with some other
methodology elements--help develop good software with good
documentation.
I applaud everyone (I'm not even done reading them all) who defended the
importance of understanding the HOW in developing good user doco. Maybe
not for everyone, but it helps me.
I am going to assume someone also made the point the technical
communicators also often are tasked with helping developers create
technical documentation. At least, those of us who enjoy tech detail and
design often sign up for that work.
And now I'll point to my original discussion that lead to his comment. I
said that I am a BUSINESS ANALYST and was looking for
BA/requirements-management lists. Half my job is TW, the other half is
to, in a Joint Application Development (JAD) environment, facilitate a
team of business owners, SMEs, and tech staff to gather requirements for
products developed via object-oriented technology. My role begins at
project definition and extends all the way through design, testing, and
deployment. I am an expert in OOAD methods.
How did I get that job? Because years ago I was a TW and my company
adopted JAD and OOAD. A key role is that of documentor (because that
frees up BA to facilitate while decisions are captured). I was really,
really good at that because I quickly picked up the principals of UML
and OOAD (and because I'm a reporter who used to cover Congress and I
can listen to hours of arguing yet capture only the important
decisions). Eventually, I was so good at helping with facilitation and
analysis that I was made a BA. When the downsizing came, I could perform
both facilitation and documentation.
Now I have helped bring OOAD and JAD principles, with UML as a modeling
language, to my new company.
Ronica Roth
Business Analyst/Technical Writer
Group Voyagers Inc.
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.
