This is about domain knowledge.
1. How much domain knowledge should a user have while using a software? For example, if it is a banking application, will domain knowledge help the user in finishing tasks? 2. How much of these domain knowledge should go into a user manual? Will users benefit if the business context or logic is described in detail in a manual? Or will the user more interested in finishing a task, rather than reading the context and other things? 3. Do you think that the future is bright for "specialist" technical communicators, rather than "generalists"? ______________________________________________ ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or HTML and publish to the Web, Help systems or printed manuals. Download Free Trial. www.doctohelp.comhttp://www.techcommpros.com/componentone/ Interactive 3D Documentation Parts catalogs, animated instructions, and more. www.i3deverywhere.com _______________________________________________ Technical Communication Professionals Post a message to the list: email t...@techcommpros.com. Subscribe, unsubscribe, archives, account options, list info: http://techcommpros.com/mailman/listinfo/tcp_techcommpros.com Subscribe (email): send a blank message to tcp-subscr...@techcommpros.com Unsubscribe (email): send a blank message to tcp-unsubscr...@techcommpros.com Need help? Contact listad...@techcommpros.com Get the TCP whole experience! http://www.techcommpros.com
