Document control procedures

["Christopher.Shade" <Christopher -dot- Shade -at- PSCMAIL -dot- PS -dot- NET>]

especially William,

some thoughts on directory structure...  i recently worked in the QA
group at a client site.  the project development approach, which I
found very odd, consisted of three groups:  QA, Coding and Systems
Management.  the QA group was responsible for everything but coding
and systems management, and included the writing of all docs except
for the design.  these three groups practiced a very chaotic approach
to managing docs.  i implemented a formal directory structure, topped
by a directory named PROJECTS, and bestowed access to all three
groups.  it has been successful as a preliminary approach.  in the
PROJECTS directory, i established the following directories:

  SUBDIRECTORY   CONTAINS
  ------------   --------
  DESIGN         Design Document
  FUTURE         Requirements for next release
  GENERAL        General files such as memos
  GRAPHICS       Graphics that are shared among the docs
  GENERAL        General files such as memos
  ONLINE         Files related to on-line help
  OVERVIEW       Any overview documentation
  PROJPLAN       Project Plan
  REQMTS         Requirements Document
  STDS           Standards specific to this project
  TEST           All test docs and subdirectories
  TRAINING       All training docs and subdirectories
  USERMAN        User Manual

just food for thought.  best of luck!

--christopher shade, denver