InstallAware Consulting Services Project Scope Form

Transcription

1 InstallAware Consulting Services Project Scope Form Please fill all the document's sections in order to provide a full description of your installation project's features and functionality. Use a single copy of this document along with its following sections, to exclusively describe a single installation project. In case you need to describe additional projects use a different copy of this document with each project. Product name Product version Manufacturer Default target directory 1 - User Account Control (UAC) A setup package typically modifies the target system, therefore the package must be executed with full administrative privileges on those systems where UAC is enabled. InstallAware fully complies with UAC requirements and directly handles the process elevation if needed. Check the desired UAC elevation level (select one): Always Elevate (requireadministrator) Elevate Administrators Only (highestavailable) Never Elevate (asinvoker) RequireAdministrator - The application runs for administrators only and requires full administrative rights. This option will always show the UAC dialog prompt. Non-admin users are forced to enter Admin credentials to elevate the process. This option guarantees maximum privileges for the installer. highestavailable - The application runs with the highest privileges the current user can obtain. This option will show the UAC dialog prompt only if the installer is executed by an admin. If the installer is executed under a non admin user context, the installer will run without elevated privileges. asinvoker - The application runs with the same access token as the parent process. This option will not show the UAC dialog prompt even if the installer gets started by an admin and due to this setup is forced to run without any admin level privileges. Page 1/14

2 2 - Application Requirements Specify the minimum hardware and software requirements for your software to be verified before your application is allowed to install. Minum OS Minum memory (RAM) Minimum resolution 64 bit system List other additional application requirements and notes here (leave blank if this does not apply). Page 2/14

3 3 - Application Runtimes List all application runtimes to be included with your installer. For each third party runtime package, specify the exact version you want to include and the command line parameters necessary to execute a silent installation of the package (leave blank if this does not apply). You may also request command line parameter discovery, but this will increase your cost. Page 3/14

4 3a - Application Runtime notes Specify here any additional notes that may be necessary to successfully install Application Runtimes listed in section 3, such as the conditional installation of a specific package version depending on the target operating system (leave blank if this does not apply). Page 4/14

5 4 Setup interview Specify the desired sequence of your setup dialogs. 4a Check this if want to include the following setup dialogs (default dialogs/sequence). 1. Prerequisites Dialog, displayed before proceeding with prerequisites installation (if required), and also before proceeding with the un-installation of a different version of your product (if present). This dialog doesn't get displayed if these prerequisites do not apply. 2. Prerequisites progress Dialog, displayed only during prerequisite installation, or during the un-installation of an older version of your product. 3. Welcome Dialog 4. License Check Dialog, displays the EULA of your product. 5. ReadMe Information Dialog, displays the late breaking Read-me notes for your product. 6. User Registration Dialog, collects User Name and User Company data. 7. Setup Type Dialog, used to collect product features installation options such as; Least required features, Some features and All features. 8. Custom Setup Dialog, used to select individual features. This dialog gets displayed only when the Some features option has been selected in the Setup Type Dialog. 9. Destination Directory Dialog, used to select the target installation directory of the installed product. 10. Start Menu Dialog, used to select if your application installation mode is to be PER- MACHINE or PER-USER. This dialog also collects information about the STARTMENU folder used to create the shortcuts of your application. 11. Start Installation Dialog, a final confirmation displayed before starting the actual installation process for your product. 12. Installation progress Dialog, displayed during product installation process. 13. Finish Dialog, displayed once the installation process has been completed. This dialog reports the SUCCESS state of the installation process. The following dialogs are shown during setup maintenance. Maintenance Dialog, displayed when the maintenance process is started. Maintenance is used to Change installed features, Repair installed features, or un-install your product. Custom Setup Dialog, used to select individual product features to add or Remove. Start Installation Dialog, displayed before committing the selected product maintenance actions to disk. Finish Dialog, displayed when the maintenance process has been completed. The dialog reports the SUCCESS state of the maintenance process. Report here if any of the previous setup dialogs have to be excluded by indicating the respective dialog number (leave blank if this does not apply). Page 5/14

6 Specify here if any additional custom dialogs are to be included along with the default sequence indicated on the previous page. Use a separate document file to illustrate the aspects of each custom dialog, along with a detailed description of the dialog's logic/functionality and where the dialog is to be sequenced within the setup interview. For example, if a custom dialog is used to validate a license number, specify the exact logic required to validate the given number. Please list here the name of each document file that describes each custom dialog and remember to attach your documents when you are sending us this master specification document (leave blank if this does not apply). Page 6/14

7 4b Check this only if you want to use a completely custom setup dialog sequence in place of the default sequence described in section 4a above. List your custom dialogs here. Use a separate document to illustrate the aspects of each custom dialog, along with a detailed description of each dialog's logic/functionality, and where to sequence the dialog in your setup interview. For example, if a custom dialog is used to validate a license key, specify the exact logic required to validate the given key. Please list here the name of each document that describes each custom dialog and remember to include your documents when sending us this master specification document (leave blank if this does not apply). Page 7/14

8 5 Application Files Please list all of the files to be installed on the target machine in this section. For each file, specify the file source path, and the target directory where it is to be installed on end-user systems. For example; Myfile.exe -> $TARGETDIR$\myfolder Alternatively, you may specify a source folder (optionally including sub-folders) in place of individually listing every single single file. For example; MyFolder -> $TARGETDIR$\myfolder In the above example, the contents of MyFolder are to be copied to the end-user selected target folder (sub-foders included if any). Please note that the default location of the TARGETDIR variable is selected during the setup interview process, inside the Destination Directory Dialog. Page 8/14

9 Page 9/14

10 5a Application File notes Specify here any additional operations that may be necessary for your Application files listed above, such as the conditional installation of a file based on the target operating system, file associations, access permissions to be granted to a target folder, and so on (leave blank if this does not apply). Page 10/14

11 5b Application shortcuts Specify here the shortcuts required to launch your application or its components. For each shortcut, specify the shortcut name and the shortcut target's location on the end-user system. Indicate whether the shortcuts should be pinned to the Start Menu or the Taskbar. For example; My shortcut -> Application Start Menu Folder -> $TARGETDIR$\myfolder\myfile.exe or My shortcut -> Desktop -> $TARGETDIR$\myfolder\myfile.exe Page 11/14

12 6 Target system modifications Specify here any other installation actions required for your product, such as system registry entries, environment variables, and so on (leave blank if this does not apply). Also indicate if any actions involving system registry entries and/or environment variables are based on data collected during the setup interview or the state of the target system. Page 12/14

13 6 Additional setup actions Specify here any additional custom actions that should be undertaken on the target system (leave blank if this does not apply). Page 13/14

14 NOTES! InstallAware automatically detects whether a different version of your application is already installed on the target system. However this works by default only for setup packages created using InstallAware. It is also possible to detect your application when it has been installed by third party setup software, so simply let us know whether you'd like us to handle these cases for you as well. InstallAware automatically handles the un-installation of all installed files, therefore, it is not necessary to manually specify any operations in order to build a correctly working uninstaller. When deploying an update for a different version of a product/application, by default a full installation will always be run after the differing application version has been uninstalled automatically. This default Windows Installer Engine behavior may be modified - for example, by building patches instead of full installers, or by preserving data regarding already installed components and the state of the existing installation. Simply let us know what you'd like to do. Copyright(C) 2016 InstallAware Software. All rights reserved. Page 14/14