Mechanism to support orphaned and partially configured objects

1. A machine implemented method residing as executable instructions in a non-transitory computer-readable storage medium for execution on a processor, comprising:

receiving, by the processor, a definition for an object, the definition permits configuration details of the object to be delayed and defined at a subsequent point in time, identifying a plurality of different processing contexts provided for the object in the definition, wherein some of the contexts include selective configuration details for fully deploying the object with some of the configuration details within a project and presenting the object to a first user within a first one of the processing contexts as a high-level object lacking the configuration details and at the same time presenting the object to a second user within a second one of the processing contexts as a fully-deployed object having the configuration details;

integrating, by the processor, the object into the project to which the object is associated when the configuration details are still undefined for the object; and

permitting, by the processor, other objects of the project to reference the object and process with dependencies to the object even when the configuration details remain undefined when these other objects process within the project.

2. The method of claim 1 , wherein receiving further includes iteratively interacting, via the processor, with a particular user to receive the definition for the object that lacks the configuration details.

3. The method of claim 1 , wherein receiving further includes identifying a security limitation provided for the object in the definition, wherein the security limitation when satisfied permits selective configuration details to be deployed for the object having some of the configuration details within the project.

4. The method of claim 3 , wherein identifying further includes recognizing the security limitation as an identity for a requesting resource that requests access to the object during the lifecycle of the project.

5. A machine implemented method residing as executable instructions in a non-transitory computer-readable storage medium for execution on a processor, comprising:

loading, by the processor, first objects within a project processing environment for a project;

permitting, by the processor, a second object to load for the project within the project processing environment, wherein the second object lacks a complete definition for that second object and wherein some of the first objects reference or include a dependency to the second object, allowing a first version of the second object to be subsequently defined with a first version of the complete definition supplied by a first user and allowing a second version of the second object to be subsequently defined with a second version of the complete definition supplied by a second user, wherein the first user uses the first version of the second object to simulate actions of some of the first objects as the first user believes the second user is going to use those first objects, and wherein the second user uses the second version of the second object to simulate other actions of other first objects as the second user believes the first user is going to use those other first objects; and

processing, by the processor, the first objects within the project processing environment for the project while the second object lacks the complete definition.

6. The method of claim 5 further comprising, allowing, by the processor, a third object to load for the project within the project processing environment, wherein the third object includes annotations to the first objects or the second object, the annotations define details for moving the first objects or the second object to a different processing environment.

7. The method of claim 6 , wherein allowing further includes identifying within the annotations additional details for moving the first objects or the second object to a different project.

8. The method of claim 5 , wherein loading further includes identifying at least one first object having an annotation to the second object, wherein the second object once it eventually acquires the complete definition provides details for migrating that first object to a different version, a different processing environment, and/or a different project.

9. The method of claim 5 , wherein permitting further includes iteratively during a lifecycle for the project receiving the complete definition in a piecemeal fashion as details are provided by resources and while the project develops.

10. The method of claim 5 , wherein permitting further includes subsequently receiving the complete details for the second object, wherein the complete details provide alternative configurations for the second object so as to permit the second object to simulate different aspects of the project and different aspects of the second object within a different project.