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.
> Yes, my experience is the same as Jim's -- this is
> a commonly-used term in software engineering. The
> development life cycle describes how you create a
> product -- from formulating the idea to maintaining
> the completed product -- including milestones,
> procedures, scheduling guidelines, etc.
There is a practical reason for your involvement
in the cycle. It is much easier to document as
you are involved and as the process proceeds.
You have the developer/programmer
at your physical location to sit down and
explain what that this person's code does and how
the user is to interface with the system.
I have several programming buds and of
course my resident Dilbert. Most programmers
are shall we say reticient to document
what they have done. Let's face it, this
is a conscience effort to keep their code
secret unto themselves or unconcience because
they do code not human words. Some programmers
are more comfortable speaking to machines.
They are on the machine and assembly level.
{SDC}
Yes, some people call this verticle development.
With it's roots firmly established by industrial
engineers later applied to software development.
Fredrick Taylor was the refiner of this
process. 1 d or 2 d's I forget.
The training folks call it ISD. Here I go again
but you will find clues and jumps the site in the
sig. if you are interested in learning more.
Check under the feature on modular instruction
for the tech. writing and ISD design jumps.
Mager.
Performance systems are referred to as
horizontal. Cutting across several system
"silos" like accounting, programming, marketing,
management for a cooperative effort <grin,
theory more than practice. Silos are also
known as sacred cows /grin>
I will be adding even more as time goes along.
Have tons of URLs stored up like a squirrel
and more features to add such as a full-
blown proposal for a career development multimedia
systems and other projects I have completed
from HRD (unique blending of Industrial Engineering,
Performance Systems, Tech Writing, other related
disciplines, Instructional Design and Training).
Even tho. my masters says HRD often confused w/
the typical Human Resources Management and Generalist.
Although I have work experience and classical training
in HR I chose to specialize in the human-computer/technology
interface. It blends my two main passions: working with
people and playing with my fav. geeky gadgets and software.
Hope this helps.
Look for descriptors:
ISD
EPSS
HRIS
EPSS
SDC
P.S. I have a particular personal distaste of buzz and
acronyms myself but this is technical writing
life, yes? <sigh> But it does look rosy for the
decoders of buzz into human language. <VBG>
~~~~~~~~~~~~~
Best Regards,
Pat Gantt, M.S. HRD
Personal email ~ pagantt -at- worldnet -dot- att -dot- net
The University of Tennessee Alum
Technical and Vocational Studies Guide
~ The Mining Company ~
Biz Mail ~ votech -dot- guide -at- miningco -dot- com http://votech.miningco.com
[humor = (intelligence + personality)]
GO VOLS! Don't ask Peyton who!
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html