Implementing a custom application requires a comprehensive strategy. This guide will aid you in developing and administering that strategy.
10 items found
Know the technical foundation on which you will be setting up your application package -- do a gap assessment of the existing and new technical environment.
You'll be able to see what interfaces with what by looking at these diagrams.
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.
Map the transformation of the data elements from source system tables to data warehouse target tables.
What is the best way to get data from the legacy system(s) into the new system? Design your conversion routines to organize the process.
Don't retire the legacy system without backing it up and knowing how to restore it if necessary.
IT system storage is a major part of your e-business strategy. How do you keep track of how much space you are using for production, testing and development, and how much you'll have left for future projects? Start with this matrix.
Got a question? Refer to the manual. This comprehensive template will help you create a useful--we'd even say indispensible--user manual for your new software system. Don't leave home without it.