I think what you are missing is that if the classes are designed properly, there is no need to determine at this early stage what database it will be implemented on. That comes later. What I need to focus on right now is the basic responsibiltities of the actors in the system and their attributes. It isn't until later I will begin molding the object model to the data model, the data model would get created after the object model. But in order to model the business as closely as possible into an object model, there are certain pre-stages that need to be dealt with.

If you want to get generic, you could design the object model on a piece of paper without even knowing what you're going to be implementing it on. It is kindof like an SRS, but it maps the business model with all the responsisblitites and attributes about all the systems actors.

Remember, think in general terms. Then when the object model is well under way, you can get more specific and start modeling the design on that particular implementation. I think a use case scenario can be applied to any object model, can't it?

Thanks for the advise,
Greg