I read both of the articles on OOP. They are very comprehensive and detailed, a lot of good work went
into them. Here is my situation: I am using the Codebook framework, which I have modified, VFP 5.0 and
XCase for a data modeling tool. Why shouldn't I concentrate on the the data model before any kind of object model is produced? Don't I need to see if all of the business requirements can be handled by the data model before anything else? I need a very good reason to start designing an object model first.
I started designing an object model for my insurance module recently. I did this during the design of the SRS (Software Requirements Spec.) But I ran into alot of problems designing methods for those classes, because all of the methods rely on some other form of performing
function to achieve the results the objects needs. One good example is a claim needing to get the information required and sent itself to the insurance company. This is a method. But it relies on getting data from other tables. Doesn't that require a data model. Also, when
designing classes, these classes have attributes. The customer class, for example has attributes like name, address, city, etc. Are these properties of the class, and if so does the data in the controls on the
form go directly into the attributes, then to the table? How would buffering work? I need a solid example of a good object model before I can even begin desiging an object model. Savvanah Brentnall replied back to my e-mail and advised me to go with the object model first before the data model. She states this is because when you design the object model, you will design it too closely to the data model, not looking at the how the business functions. I want more than anything to design an object model for my module in the purest OOP sense, but have no direction in accomplishing it. Thanks for any help.