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.
Subject:Use Case references From:Michael Collier <michacol -at- SBSERVICES -dot- COM> Date:Tue, 27 Aug 1996 14:26:06 -0400
Do any of you who have worked on software development projects have any
ideas on numbering conventions for use cases and other artifacts*?
In the scheme I'm developing, an Order use case would be numbered
ORuc01; its corresponding interaction graph would be numbered ORig01,
etc. These numbers are for cataloging purposes; in common usage, in
response to an inquiry the inquirer would be advised, "well, in the order
subsystem, there's a use case having to do with..."
If you've had to do this, please contact me so we can compare notes.
michacol -at- sbservices -dot- com
SOFTBANK Services Group
*a geeky term for design documentation
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-