A persistent object is associated with a specific server storage mechanism, which actually contains the object. The persistence of an object within the San Francisco framework, along with the location of the object and its container, is transparent to the application developer. The persistent object is created through an object factory, which resides on the same server as the storage mechanism that contains the object. An object factory can create both persistent and transient objects, as well as delete persistent objects from the storage mechanism. San Francisco provides methods for creating transient copies of persistent objects, along with methods for promoting transient copies to persistent objects.
Referential persistence is supported through the concept of ownership.
5.7.1.2 Application Development Process IBM San Francisco provides a complete roadmap for application development including requirements mapping, analysis and design. Initial requirements collection results in application scenarios, which are mapped to existing San Francisco framework scenarios to determine the requirement coverage by the framework, including the extensions of the framework and the changes to the framework. The analysis phase of the application roadmap includes defining any required user interfaces or business logic. Application scenarios or use cases are detailed, possibly uncovering additional scenarios. These class categories are compared to the existing San Francisco framework, identifying required extensions to the San Francisco class model.