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.
I am a consulting manager, responsible for user and
technical documentation. I am trying to identify a more
(okay, so *more* presupposes that we actually do it
now, which isn't really the case) effective way to
measure the quality and functionality of our
documentation (primarily software doc). One of the
methods I'm looking into is function points.
Our company recently purchased the LBMS Methodology,
and I am responsible for developing a documentation
template, including guidelines and techniques. As a
result of this task, I am working closely with our chief
methodologist. We have discussed using function points
(although we assume that we would have to assign
arbitrary values) since that has worked well on application
development projects in the past.
Has anyone used function points to measure the quality
of documentation, and do you have any advice for
getting started? I am interested in any other metrics (for
measuring quality only). I would appreciate any comments,
suggestions, or recommendations you could give me.
Levi, Ray & Shoup, Inc.
217-793-3800, x. 713
Lrsmail!Lrsspfld!Lrs!Mayberry -at- Attmail -dot- com