All GUIs contain a Help menu with commands to see the project name, web site, how/where to get help, version, date, licence and copyright (or where to find this information), location of entry point into user doc. |
|
|
0.2 |
0.4 |
0.6 |
0.8 |
0.9 |
1.0 |
1.0 |
All mandatory third-party dependencies or external references are currently available. |
|
|
|
0.1 |
0.3 |
0.5 |
0.8 |
1.0 |
1.0 |
All optional third-party dependencies or external references are currently available. |
|
|
|
|
|
|
0.2 |
0.3 |
0.4 |
All other content distributed as an archive contains a README.TXT with project name, web site, nature, how /where to get help, version, and date. |
|
0.2 |
0.2 |
0.4 |
0.6 |
0.8 |
0.9 |
1.0 |
1.0 |
All source and binary distributions contain a README.TXT with project name, web site, how/where to get help, version, date, licence and copyright (or where to find this information), location of entry point into user doc. |
|
|
0.2 |
0.4 |
0.6 |
0.8 |
0.9 |
1.0 |
1.0 |
Binary distributions have instructions for installing the product. |
|
|
|
0.1 |
0.2 |
0.4 |
0.7 |
1.0 |
1.0 |
Binary distributions list all third-party dependencies and external references that are not bundled, along with (as appropriate) web addresses, suitable versions, licences and whether these are mandatory or optional. |
|
|
|
|
|
|
0.2 |
0.4 |
0.5 |
Dependency management is used to automatically download dependencies (e.g. ANT, Ivy, Maven or custom solution). |
|
|
|
|
|
|
0.1 |
0.3 |
0.5 |
Installers allow user to select where to install software. |
|
|
|
|
0.2 |
0.4 |
0.6 |
0.8 |
1.0 |
Tests are provided (or silently performed) to verify the install has succeeded or service/product is fully available. |
|
|
|
0.1 |
0.2 |
0.4 |
0.6 |
0.8 |
0.8 |
Uninstallers exist, and uninstall every file or warns user of any files that were not removed and where these are. |
|
|
|
|
|
|
0.4 |
0.6 |
0.6 |
Web site has instructions for installing or accessing the product. |
|
|
0.1 |
0.3 |
0.5 |
0.7 |
0.9 |
1.0 |
1.0 |
Web site lists all third-party dependencies and external references that are not bundled, along with (as appropriate) web addresses, suitable versions, licences and whether these are mandatory or optional. |
|
|
|
|
|
0.1 |
0.3 |
0.5 |
0.6 |
When an archive (e.g. TAR.GZ or ZIP) is unpacked, it creates a single directory with the files within. It does not spread its contents all over the current directory. |
|
|
0.1 |
0.2 |
0.3 |
0.5 |
0.7 |
0.8 |
0.8 |
When software is installed, or when a product or service has multiple facets, its contents are organised into sub-directories (e.g. docs for documentation, libs for dependent libraries) or IRL hierarchies (/about, /support, etc.) as appropriate. |
|
|
0.2 |
0.4 |
0.6 |
0.8 |
0.9 |
1.0 |
1.0 |