10 Commandments of Creating Database fro

Hello,

There rules of how to best design an implement a database a solution, but on the structure, not on the content, you have to know what kind of information you will need to store, so you can design the database structure accordingly, applying the rules that exist for database relations. If you search the techrepublic site for database you'll find some very good articles on this subject, one of them is this one:

-https://www.techrepublic.com/download_item.jhtml?id=dr00820010820adm01.htm&src=bc

But there are several other articles and downloads.

Hope this helps.

Good question. The important thing is that a developer should be able to verify (and prove to the end-user) that the database created satisfies every specified business condition (and then some unsaid things from the "wish list" also).

Ideally the developer should be able to do this before actually beginning the development. This is akin to a building plan. The buyer sees the plan and the architect ecplains the important points.

Developers have evolved many methods to address these points and convert the requirements into workable programs and databases - once the requirements have been understood, agreed and signed off.

By this process, the end-user will have the confidence that the developer can and will develop the right solution. Whats important is t agree on whats to be delivarabled.

This is equally true of a packaged product. The feature list should be well understood by the seller and the user must know what he is getting and how to make it work.

End of mail.