In this paper we have made an attempt to identify the dependent objects (closure) that are determined with help
of the implementation mapping table. The guidelines are framed to transform transient objects to persistent objects
(persistent constructor) and vice-versa (persistent loader). Thus we have attempted to keep the object in the valid
state protecting the persistent closure. Persistent constructor/loader in case of implementation of inheritance/multiple
inheritances in the host program along with their mappings are to be addressed.