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.
Re: FW: The Technical Writer vs. Agile Development Methodologies
Subject:Re: FW: The Technical Writer vs. Agile Development Methodologies From:Tony Markos <ajmarkos -at- yahoo -dot- com> To:Dan Goldstein <DGoldstein -at- riverainmedical -dot- com>, TECHWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 1 Feb 2006 11:30:39 -0800 (PST)
--- Dan Goldstein <DGoldstein -at- riverainmedical -dot- com>
wrote:
Hi Tony,
What does "the UML techniques strongly retard a focus
on the essential" mean?
Thanks,
Dan
Dan:
UML techniques all employ what is commonly referred to
as a force, artificial approach to system partitioning
("chunking" to us TWs). Basically, with these
techniques, we FIRST draw boxes or ovals or some other
entity, and THEN we try to figure out how they all
interrelate (interconnect). This is an age-old
analyis mistake (we should have matured beyond this
mentality back in the 80's, but we did not).
When we play the old "connect-the-boxes" game, what we
are doing is putting our limited understanding down on
paper, and then trying to force reality to fit this
flawed understanding. In other words, we derail the
all important discovery phase of analysis (analysis
is, in the main, a discovery process).
Tom DeMarco wrote that a model based upon the old
"connect-the- boxes" approach is a lie: It looks like
we did a proper discovery phase, but we did not.
And if our discovery phase has been derailed, we lack
a comprehensive, integrated understanding of the whole
which greatly retards our ability to identify the
essential.
Tony Markos
Focused On The Essential Like A Laser
-----Original Message-----
From: Tony Markos
Gene:
I disagree with that article. The goal is not to
create simple models - it is to create essential
models. I worked on a large-scale Agile Development
project where the simple models where but Post It
notes stuck to the bosses door. Simple - yes, but the
lack of rigor in this approach resulted in a large
number of essential requirements being missed
until much latter in the development process - and
requiring
a 1000 X more time to fix.
The article also specifically espouses use of UML
modeling techniques. Sorry to say it, but the UML
techniques strongly retard a focus on the essential.
__________________________________________________
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