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 can tell you from personal experience that this sort of information is
critical, especially where the software does not present a consistent
interface. You'll be doing a service to your users, who will appreciate the
verification. Also, you've identified and recorded for your developers
something they can improve in the software's next release.
Also, if I were using your procedures, I would much prefer your second
sample, where you name the specific fields. The first verges on being
redundant (it seems to me that "enabled" *almost* equals "editable") It's
almost a circular definition.
