1.1.9+Evaluate+Different+Methods+of+providing+user+documentation

Certain products, especially software and files have a copyright seal, disabling certain forms of distribution. [|__http://creativecommons.org/__] Authenticity as user documentation allows the creator to ensure legally that their work can only be redistributed under their control. Unfortunately, it is difficult to know whether these rules are being followed.
 * Authenticity**

Manual
People who do not know how to use a product can refer to the manual. [|__http://manuals.info.apple.com/en/iphone_user_guide.pdf__] These can be very useful for some people who like having a structured collection of information and help. Sometimes, a simple Google search may be faster though.

FAQ
Internet tradition.

Examples of F.A.Q taken from [|__http://www.raspberrypi.org/faqs__]

readme.txt
README files are commonly included with software and detail many things from installation instructions to operating instructions.

= Warranty = “ A guarantee given to the purchaser by a company stating that a product is reliable and free from known defects and that the seller will, without charge, repair or replace defective parts within a given time limit and under certain conditions” - www.thefreedictionary.com/warranty

= Guarantee = Is similar to a warranty, as it assures the consumer that the product will be able to perform it’s functionality. However it tends to be more open ended as you may be able to return your product if it does not satisfy your needs, instead of only being able to return it in case of malfunction.

Warranty and Guarantee both assure that the client will not be buying a faulty product and that if infact it is faulty it will be replaced/repaired free of charge. This is very important as it protects the consumer from being swindled.

=System Requirements:=

To be used efficiently, all computer software needs certain hardware components or other software resources to be present on a computer. These prerequisites are known as (computer) system requirements and are often used as a guideline as opposed to an absolute rule. Most software defines two sets of system requirements: minimum and recommended. With increasing demand for higher processing power and resources in newer versions of software, system requirements tend to increase over time. Although, there is a certain problem with system requirements as a lot of them might not be entirely accurate, and a lot of times some of it may be incorrect, stating that a certain computer can run a program when it actually can't, and they are never specific on how fast the computer can actually run that specific program or in what settings, just that it can run it or not.



=Installation Guides:=

This documentation provides you with step by step instructions on how to install the specific product, such as a piece of software, helping you through it, making sure you install it correctly and quite possibly helping you through any errors that may come up during installation. This is very useful as its some quick and readily available help on how to correctly install and get your product running, although it’s efficiency all depends on how good and understandable the guide is for it’s users

Troubleshooting Guide
Definition: Troubleshooting is a form of problem solving, often applied to repair failed products or processes. It is a logical, systematic search for the source of a problem so that it can be solved.

Troubleshooting guides can be very helpful and help the user. It quickly finds the problem and presents a number of solutions to help solve the problem.

One disadvantage is that these may not contain the user’s specific problem thus not presenting a viable solution.



Access Codes
These usually come with software are used to verify the copy’s authenticity making it possible to install the software. Access codes can be any form of alphabetic or numerical code.