|
From: Frank V. C. <fr...@co...> - 2001-02-04 22:27:23
|
Ok, now that the contract is slowing down I have time to breathe again. I have re-awoken the persistent framework model (having trashed one or two of them) by going back to the fundemental use cases and analysis steps for discussion. There are two (2) things that are evident immediatley when thinking about a framework abstraction for OO persist: 1. Applications work with objects 2. Modeling the mapping of objects to persistent store is not the requirement of the application, but one of a modeler. To that end I have attached some simple diagrams (2 use case and 1 analaysis class) which should be self explanatory. But, heh, if you DO have questions or comments I would appreciate it. The hardest part will be defining the element types in terms that all persist (from flat file to relational) can relate to without slanting the implementation to a specific terminology. Sorry for the heavy attachment. -- Frank V. Castellucci http://corelinux.sourceforge.net OOA/OOD/C++ Standards and Guidelines for Linux |