Installation Flow and Options Template
An Installation Flow and Options document explains any user input required while running the installation of a legacy setup and testing of the prepackaged setup.
- An experienced end user of the software should provide this information. If there is someone within your organization who has ownership of the application, they can provide these details.
- If you need to gather the options yourself, you should run the legacy installation and note every piece of user input required during the installation.
Note: An application migration project will usually include this type of document also.
|
Description |
| Corporate Standards |
Corporate standards for product installation directories, such as: C:\Program Files\CompanyName\ProductName |
| Shortcut Standards |
Standards for shortcut locations (such as a Product Name folder inside the All Programs folder of the Start menu). |
| Add or Remove Programs Support Information |
Standards for the Add or Remove Programs support information settings. |
| Installation Type |
Whether installations will be performed silently, or with a full user interface, or at some intermediate level. |
| Server Locations |
Documentation of server locations for the finished installation packages. |
| Distribution Method |
Documentation of the intended distribution method (Active Directory, SMS, Marimba, and so forth). |
| Roles and Responsibilities |
Definition of different roles and responsibilities in the application-migration process.
Note: This manual occasionally refers to an application owner, a sophisticated user of an application who can verify that it functions correctly.
|
| Status Reports |
Guidelines for status reports. |
| Application Owner Information |
Application owner contact information (for questions, returns, and escalations). |
| Application Owner |
Application Owner name and Business unit |
| Owner Contacts |
Application owner Telephonic number or E-mail |
| Support Contacts |
Helpdesk phone or URl |
Application General Information
| Application Name |
Name of the application |
| Version |
Full in format XX.XX.XXXX |
| Vendor Setup Type |
The format of the original installation(MSI,legacy,Raw files, CD,File downloaded, internal) |
| Source |
The medium used to install the program |
| Application Function |
The function and the use of application |
Application Type
| Application Type |
Application architecture(standalone, clientserver,hardware driver web, other. |
| 32-bit Application |
16-bit,32-bit,or 64-bit application |
Manufacturer Information
| Manufacturer |
The vendor company name |
| Manufacturer Contact |
Vendor phone or Email |
Application Usage
| Business Criticality |
The importance of the application |
| Number of Target Users |
Estimated number of users for the Application |
| Number of Target Devices |
Estimated number of devices for the Application |
Application Dependencies
| Hardware Dependency |
Additional hardware required for the run the program |
| Software Dependency |
Additional software required for the run the program |
Installation Instructions
| Installation |
Step by step |
| Instructions |
Instructions |
| Serial Number |
Serial number |
| Additional Configuration |
Additional files to be add or delete,additional programs to run |
Outputpackage
| Output Files |
Type of output files created(MSI,MST,MSP) |
| Complexity |
Package complexity(Easy,Medium,Difficult) |
Testing Procedures
| Application Functionality |
Testing step by step instructions |
| Testing Results Tested By |
Name of the test engineer |
| Validation Results |
Unresolved validation errors |
| Conflicts |
Unresolved conflicts |
| Comments |
Comments... |
|
Very well explained. Goood
Very well explained. Goood Job !!
Additional Items
If packaging and support for the application are segregated in your organization, you might also consider additional items such as licensing and approvals, and items related to distribution of the application. Including distribution info helps eliminate delays in deploying the application once packaging and end user acceptance testing is complete. Examples include:
- requested date
- target PC list
- pilot plan
- phased distribution plan
- communication plan
- backout plan if the production install fails
It is helpful to meet with the support person to complete the documentation and to run through an install prior to beginning packaging so that the packaging team and the support person are on the same page as to the install and requirements of the app support group and of the packaging processes in use. It also give the opportunity to review organizational guidelines and policies that may apply, such as change management requirements.
Yep!..Good Add-in
Yes,mocarski good Add-in information for
- requested date
- target PC list
- pilot plan
- phased distribution plan
- communication plan
- backout plan if the production install fails
But, Basically given information is enough
the extra information depends on the situations,or on the application demand.
Thanks...mocarski
Cheers Tillu
conflicts
is there any tool other then conflict manager , as i am using wise standard edition 7.
check the link
http://ewall.org/index.php?module=ContentExpress&f...