You'll be able to see what interfaces with what by looking at these diagrams.
1273 items found
Legacy systems must be modified to integrate a new application package. Use these tables to define, track and prioritize the changes to each legacy system and system component.
This matrix will help you determine which systems and their components will be replaced, changed or impacted by the new application package.
A necessary step in both selecting and implementing a package is detailing the technical requirements required to run the application. Identify the hardware/software environment, interfacing systems, operational and backup procedures, and other key technical requirements.
This matrix will help you define the changes you'll have to make to the existing hardware/software environment so that the application package will work properly.
Specify what your application package testing environment should consist of and how it should be configured.
Before deploying your new application to users, you must thoroughly test its installation in the production environment. Document your installation test procedures and verify that the package passed all tests.
Part of the application package evaluation process is to assess the need for third-party vendor support. This simple template profiles third-party vendors who can provide support to your application package.
Assess the scope, impact ranking and criticality of each business change required to implement a particular application package.
Implementing a custom application requires a comprehensive strategy. This guide will aid you in developing and administering that strategy.