Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

+ - Documentation Naming Conventions 1

Submitted by
realsilly
realsilly writes "I am a requirements analyst, and I often find myself in companies where they either have an extremely rigid naming convention and structure for storing documents or there is no structure in place at all. I find myself in the latter of the two situations, where I'm trying to come up with an easy to use and implement naming convention that will be followed by those who don't name things formally. I am avoiding using numbers and dates within document names and in many cases, I have much of my early documentation on internal wiki pages. I'm looking for some best practices ideas from the Slashdot community."
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Documentation Naming Conventions

Comments Filter:
  • I'm active duty military, and worked this problem recently for a ~2000 person operation. In the end, we had a fairly complex set of rules laid out in a 2 page instruction, but also provided a tool (an html file that used text input and javascript) that simplified the process. There was a checkbox for "Is this a draft?", "Is this a template?", a dropdown for classification and another for originating unit. There was only 1 mandatory text field, and that was for Base Document. Each input field had a brief des

: is not an identifier

Working...