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.
Standardization of the document is part of quality only so far as it
agrees with your standarization requirements. If you have a style guide,
you should follow it. That could be part of your quality metrics.
However, it doesn't mean that the document is worthwhile for your
end-users. It just says that you are following a standard look and feel,
using specific formatting, etc.
If you want, you can define your entire quality effort in that way.
Scott
punit shrivastava wrote:
> Hey Guys,
> Very helpful views. Thanks for that.
> But just one doubt which I would like to get cleared.
>
> When we talk of quality standard of document, is it just about usability
> factor for end user?
>
> What about the formatting and look and feel factor of documentation?
> Shouldn't such factors also be considered while defining Quality of a
> document?
>
> thanks
> Punit
>
> On Thu, Apr 23, 2009 at 3:12 AM, Chinell, David F (GE EntSol, Security) <
> David -dot- Chinell -at- ge -dot- com> wrote:
>
>
>> I like to think of delivering value to the reader.
>>
>> One expression of value is this:
>>
>> Value = Quality / Cost
>>
>> However, due to the difficulty of defining meaningful "quality"
>> measures, I started thinking of utility. Like this:
>>
>> Value = Utility / Cost
>>
>> Utility depends on the reader's purpose -- one can only say whether or
>> not something is useful in the context of a purpose.
>>
>> So in the end I come back to agreeing with John, that you have to
>> determine whether or not the reader achieves the result determined by
>> the purpose.
>>
>> Bear
>>
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. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-