Before running the database model

Question

What do you do before running a database model diagram? I mean how you formulate requirements, specifications, etc. Use cases are one thing, but something else? Any best practice or rule of thumb? As a self-taught student, I want to see how this happens in the hands of professionals?

Answer 1

Make sure you have a complete list of requirements from your client. Do your best to fully understand these requirements, it will really help in your design if you do. If you define requirements, it might be easier, because you already have an idea of ​​what you need to do. Understanding your goal is the most important part.

If there is an obvious part of your database that will be most important (for example, an application in the online application system), I usually start from there and process one part at a time.

Personally, I like to draw rough pictures (which ever makes sense to you, it doesn't have to be an official ERD) of what, in my opinion, will look like in the database, and revise it to finer levels of detail.

Answer 2

. , . , , , , -. .

, , , . , , (, , , , ).

Answer 3

. . - .

, ER (Entity-Relationship) RDM ( ) .

ER , , . ER , . , , .

RDM , - . RDM ER-, , ER.

In turn, its simple assembly of the table creates a script from the RDM diagram. You will need to add some physical features, such as indexes, to get good performance without breaking your hair.