"Documentation – Client" Profile

 Description This Facet provides a list of user documentation that a Client application should provide.
 URI http://opcfoundation.org/UA-Profile/Client/Documentation

This page lists the conformance units of the selected profile with their name and description.
Conformance units that are inherited via included Profiles are not listed by default. Use the following radio buttons to change this default behaviour.






Miscellaneous
Include  Name Opt.  Description  From Profile  Test Cases
Documentation Client – Supported Profiles The documentation includes a description of the profiles supported by the product. This description includes any software certificates that describes the level of Certification testing the product has passed.   Open
Documentation Client – Multiple Languages The documentation is available in multiple languages. The results of this ConformanceUnit include the list of supported languages.   Open
Documentation Client – Users Guide The application includes documentation that describes the available functionality provided by the application. For client applications this includes any operator restrictions or general functionality that the client application makes use of.   Open
Documentation Client – On-line The documentation provided by the application is available in electronic format as part of the application. The electronic documentation could be a WEB page, installed document or CD/DVD, but in all cases it can be accessed from the application or from a link installed with the application.   Open
Documentation Client – Installation The application includes installation instructions that are sufficient to easily install the application. This includes descriptions of any and all possible configuration items. Instructions for loading or configuring security related items such as Application Instance Certificates.   Open
Documentation Client – Trouble Shooting Guide The application includes documentation that describes typical problems a user may encounter and actions that the user could perform to resolve the problem. It could also describe tips, tricks or other actions that could help a user diagnose or fix a problem. It could also describe tools or other items that can be used in diagnosing or repairing problems. The actual Trouble Shooting Guide can be part of other documentation, but should be complete enough to provide useful information to a novice user.   Open