Best Practice Implementation › How to Perform the Best Practice Implementation › BPI Software Inventory Lifecycle

BPI Software Inventory Lifecycle

The Best Practice Implementation sets up a seven-environment mapping structure, by default. This structure includes the Development (DEV), Quality Assurance (QAS), Production (PRD), Emergency (EMER), Unclaimed (UNCLMED), Archive (ARCHIVE), and Administrator (ADMIN) environments. Your site may not need all seven environments, or you may need more than seven. However, this represents an active development lifecycle that is appropriate for most sites.

The lifecycle defines the movement of your software inventory through a set of data set libraries. These lifecycles are defined in the Defaults table (C1DEFLTS). A data set naming convention supports the lifecycle structure.The Best Practice Implementation sets up the following lifecycles or maps:

• Standard Map— For regular development activities.The Standard Map is where most activity will take place. The Standard Map starts with the DEV environment, at entry stage, stage 1. From DEV Stage 1, source will be promoted to DEV Stage 2, then to QAS stage 2, and finally PRD stage 2. Stage one for both the Quality Assurance and Production environments are skipped. DEV stage 2 maps to QAS stage 2, and QAS stage 2 maps to PRD stage 2.
• Emergency Map— For emergency fixes. The Emergency environment maps also to PRD stage 2.
• Unclaimed Map— For unclaimed or unclassified elements. The Unclaimed environment has an entry stage of 2. This environment does not map to any other environment.
• Archive Map— For archived elements. The Archive environment has an entry stage of 2. This environment does not map to any other environment.
• Administrator Map— For the CA Endevor SCM Administrator activities. The Administrator environment has an entry stage of 1. This environment does not map to any other environment.

The following graphic shows how the BPI environments are mapped: