1.   The modules to be entered can contain modules known and unknown to LIFESPAN, subject to the conditions specified below, but all modules must be at development versions.

2.   Users may only add development versions.

3.   There is no restriction on the number of development versions of modules which can be entered into LIFESPAN in this manner.

4.   Both he and the developer signed off the test record and he allowed all the modules in the package with development versions to be given a fully approved status.

5.   It is recommended that this is an approved version, although a development version may be used if necessary.

6.   During this stage, development versions of modified modules may be entered into the LIFESPAN system.

7.   Once a DC is granted active status, the user responsible for the DC may enter as many development versions of the module as may be desired.

8.   Here LIFESPAN automatically raises a DC when module names are reserved to allow initial development versions to be entered.

9.   Intermediate development versions introduced to the database by latest selection are not referenced by any package and therefore can not be sent offline in this fashion.

10.   If the latest version of the module is a development version then the package must contain it as Latest.