> In Sean's use of names, wouldn't that get confusing in the case of multiple > people with different roles? Uma (the network admin) and John (the user) > could be ambiguous without their titles. I can see where actors could help > solidify some concepts, but I don't think they would be the best in all > situations. Could be. That's why the scenarios drop the name and role. And remember, I am talking about requirements documents and not manuals....a whole other beast. The purpose in using names, however, is to try to make realistic scenarios beyond "The user will do X."
******************************************** Sean Hower - communications specialist http://www.seanhower.com _____________________________________________________________ Create your own web site for FREE at http://www.freehomepage.com _______________________________________________ Are you a Help Authoring Trainer or Consultant? Let clients find you at www.HAT.Matrix.com, the searchable HAT database based on Char James-Tanny's HAT Comparison Matrix. Contact [EMAIL PROTECTED] for details. Interested in Interactive 3D Documentation? Get the scoop at http://www.doc-u-motion.com -- your 3D documentation community. _______________________________________________ Technical Communication Professionals To post a message to the list, send an email to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com or, via email, send a blank message [EMAIL PROTECTED] Visit the TCP site at http://www.techcommpros.com To find out more about the list, including archives and your account options, visit http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com If you need assistance with the list, write to [EMAIL PROTECTED]
