Return to NI Tools Network Software Requirements
Requirement | Additional Resources |
Installation | |
Application is shipped with an installer appropriate for the target operating system(s). | Building and Distributing Applications |
Installer includes and/or documents any software dependencies. | |
Users are notified If any additional software is needed to use the application. | |
The package includes a EULA which complies with the “Restrictions” and “Application Deployment” sections of the NI Software License Agreement. | |
Users can uninstall the application. | |
There is a documented or intuitive update process. | |
Activation (if applicable) | |
[Recommended] The application utilizes the NI License Manager (NILM) 3rdParty SDK for licensing. |
NI License Manager Third-Party SDK |
Users can evaluate the application immediately upon downloading the software. | Note: users should not be required to request a license to evaluate the software. |
Users are reminded of the remaining trial period. | |
Users are prompted to activate the application when the trial period expires. | |
Users can activate the product with appropriate credentials. | |
Tutorials and Demonstrations | |
Product provides examples and/or tutorials to demonstrate typical customer use cases. | |
Examples and tutorials are intuitive and any required steps are documented. Tutorials include explanations to describe what is demonstrated or accomplished by following the tutorial in order to serve as a learning aid for customers. | |
[Recommended] Simulation mode is available in case it’s a hardware-dependent software. | |
File Structure | |
Files and folders follow a recommended naming convention (combination of company and/or product names) to ensure name-spacing and avoid conflicts with other add-ons or code. | |
Documentation | |
Application contains a help document accessible from within the product. | |
Documentation describes any installation steps outside of running the installer (if applicable). | |
Third-party and NI software dependencies are documented (if applicable). | |
Hardware system requirements are documented (if applicable). | |
Supported operating systems are documented. | |
Documentation describes any required communication ports and firewall settings (if applicable). | |
Product directs users to a support channel for technical support. | Free products may specify "not supported" or direct users to a community/forum/and so on. All paid products must provide support contact information. |
User Experience | |
Works on all operating systems that are listed as supported (Windows x64, Windows x86, Mac, Linux, RT, and so on). | |
The application runs when opened and can be closed any time. Special considerations or exceptions should be documented. |
|
Users can modify port settings required for communication (if applicable). | - |
The user interface for applications and dialogs are visible to the user. User interface is intuitive. |
Specify in the hardware requirements if a specific resolution is required for an application, and consider support for multiple resolutions by creating a resizable user interface.
|
User is provided with feedback during long operations (that is, progress bar, busy cursor, and so on). | |
It is clear to the user when administrator rights are required for execution. | |
No crashes or unexpected errors are reported. | |
There are no apparent memory leaks or undocumented spikes in CPU or memory usage. | |
Stand-alone applications do not override common keyboard shortcuts (such as copy/paste). | |
Other | |
Product does not include any malicious software (malware, viruses, and so on). | |
Product complies with LabVIEW Tools Network Style Guide. The product name should comply with any NI trademarks, e.g. Product Name for LabVIEW by Company/Product Name for USRP by Company. | NI Tools Network Style Guide |
Product and accompanying documentation are localized in English. |