I am in the process of creating a new database and moving old data into it. I would like to create Business Objects for the new system and looking at the old system, it looks like the objects are based on the tables in the old database. Is this the correct way to create business objects?
+1
A:
If the old database was properly normalized you will find that many tables do correspond to business objects. However...
Your decision about what constitutes a business object should not be restricted to that. You need to study the scenario and decide what the business is interested in. You understanding of the business will be the main determinator.
Vincent Ramdhanie
2010-03-01 17:03:21
The database looks like it was normalised properly, but it certainly wasn't created correctly :o) Thanks for the information.
Ardman
2010-03-01 17:21:51
+2
A:
A properly normalized database will look nothing like a proper object-oriented design. The needs of a database are very different from the needs of a software application.
You should design your application according to the requirements for how it is to be used. What sorts of things is the application supposed to do? What objects will be required to support those needs? And what are the natural relationships between them?
A single business object may be stored across a dozen database tables, or a single table may store data for a dozen objects. It really depends on the specifics of the system you are working with.
Jeffrey L Whitledge
2010-03-01 17:11:32