Consider that if there was enough detail in the problem statement that could be "extracted", there would be no need for database design. An "extract utility" would be run that automagically generates the DDL.
Many (most?) problem statements are somewhat nebulous. Someone who knows the business need and how to design database structures (db designer/dba) often meets with the "users" to iron out specifics and then the informaton leads to the first iteration of the database model.
Where to start is probably making Sure you have a good understanding of the "target" - before implementing anything.
Ok friends. Thank you so much.
The database is looks very simple but lengthy.
English + Urdu
Product In (hope this and..
Sale Product (..this are two main tasks that company does)
Profit and Loss
Packing List (just send a copy of sale order (without rates etc, to packing, print)
Customer A/C (stock out and payment)
Customer Reminder (SMS sending, I will do it)
These are the tasks that our database will do, given to me to create database application.
I found following entities:
and their detail like ID, Name, Address etc...
Now I have to make dataflow diagrams then tables???? then normalize them???
Last edited by Hyder Rana; 09-01-12 at 06:52.
Reason: add dataflow diagrams