Description:
Documents the specific library names containing the application source code and executable components. If multiple staging environments are used, the libraries are separated by Development, QC testing, User Acceptance testing, Pre-production Staging and Production. All development and support analysts need to know where specific system components, data, test routines/scripts, files and databases are stored via library name or physical storage device address or identity. It is like knowing the location of a filing cabinet that contains a specific type of information you need to find or use.
Provides understanding of libraries which may need to be accessed in order to correct a problem.
Provides information such as:
- A brief description of the Library Environment
- The file name of the Unit Test Library
- The file name of the Acceptance Test Library
- The file name of the Pre-Production Staging Library
- The file name of the Production Environment
How is it used?
All development and support analysts need to know where specific system components, data, text routines, files and databases are stored. Library name, physical storage device address or identity. It is like knowing the location of a filing cabinet that contains a specific type of information you need to find or use.
Why is it important?
(1) Contains a list of all library environments, their characteristicsused and usage for the applciation.
(2) Provides understanding of libraries which may need to be accessed in order to correct a problem.
(3) Provides information such as:
- A brief description of the Library Environment
- The file name of the Unit Test Library
- The file name of the Acceptance Test Library
- The file name of the Production Staging Library
- The file name of the Production Environment









IT Support Services Comments