Testing Applications for Compatibility with Windows 2000

Many large organizations have hundreds or even thousands of applications. If this is the case in your organization, compiling the list of applications can be extremely time-consuming.

You might want to compile the following information about each application:

• Application name and version.

• Vendor name.

• Current status (for example, in production, under development, no longer used).

• Number of users and their business units.

• Priority or importance to your organization.

• Current operating systems where the application is used.
  Include whether the application is client-based or server-based and which components reside on the client and on the server.

• Web site addresses (URLs) for Web applications.

• Requirements for installation (for example, security settings and installation directories).

• Development utility or technology (if developed internally).

• Contact names and phone numbers (internal and vendors).

If you find multiple contacts for the same vendor, try to consolidate them where possible.

If one of your goals is to consolidate applications or to better plan your testing efforts, you might prioritize applications by using Table A.21.

Table A.21 Prioritize Your Applications

Table A.22 includes a number of tests that you can use to begin planning a testing strategy. Extend this list with additional issues that are appropriate for your organization. To track the results of your testing, record in the table whether the test passed, failed, is in progress, or unknown. You might also want to include the name of the person who is responsible for testing the application and the date that testing was completed or is due to be completed.

Table A.22 Plan and Track Your Testing Strategy