>Well for example sql server and access comes with northwind and pubs databases which are in themselves models of a business. Oracle sells not only a database product but business solutions (financials, hr, general ledger, etc..) that they've created from their own product. What I'm looking for is cookie-cutter ER diagrams of the most common of business data. This would help alot when a programmer like myself doesn't have the business experience in a field like Human Resources. I could look at the diagram and get a sense of whats going on and program accordingly. Likewise if I am designing my database I can measure my design with what has been done previously. If I were to create my own accounting software (yeah, like we need another one...) why should I design the tables from scratch?

Johnny;

I think your basic question is a very good one. Looking at a “Classic Design” would help the developer to better comprehend how a specific element of business functions. In reality a business will have unique requirements and differ from an academic approach.

Business expressed as tables in a database seems like a very good idea. Perhaps someone has done this. This would save reading and becoming familiar with many differing data models and how a business runs.

I tend to create applications for those businesses and disciplines I am familiar with. Most models fall into a category I believe and share some commonality. Without understanding the finer points of an applications requirements (the why of it all) you may be entering a “black hole”.

It is one thing to be a developer and another to solve a business need. Developers write code and to be successful you create solutions.

Tom