21.   First, all new module names are reserved.

22.   When a module name is first entered into LIFESPAN, it is checked to ensure that the same name has not already been chosen for another module.

23.   Restrictions may be placed on module names for particular environments by using a development discipline.

24.   It is recommended that module names should be reserved for all software as it is being created.

25.   By reserving the module names at an early stage, their unique identity is immediately assured and module headers can be added when convenient.

26.   The source modules can then be entered into LIFESPAN as soon as they have module headers, by including their module names into a package module header.

27.   It is recommended that skeleton headers be mass-produced, specifying only the module name, issue number and type, and those modules be entered into LIFESPAN.

28.   Reserve module names for the package and the new modules which it is to contain.

29.   Unlike Design Changes, SPRs and SSRs are related to specific versions of a module and not to a module name.

30.   Distribution, however, takes place via module names.