TutorTermTell Us What Is StuckGet in Touch

What goes in a database design document?

Typically the requirements, the ER model, the relational schema with keys and constraints, the normalization reasoning, and sample queries showing the design answers the required questions. The normalization reasoning is the part most often thin.

This comes up on Database Design Coursework, where it is answered in the context of the work itself.

Get My Free QuoteBrowse all questions

More on computer science & it

See all
What goes in a testing strategy document?What if I cannot finish everything?What if my method is not better than the baseline?What is data leakage?What is the difference between the OSI and TCP/IP models?What makes a good requirement?What makes a good security policy?When can I use causal language?When should I add an index?When should I use TCP rather than UDP?Which data structure should I use?Which evaluation metric should I use?Which framework should I map to?Which language should I learn first?Which UML diagrams do I actually need?Why does my O(n log n) solution run slower than an O(n squared) one?Why does TCP use a three-way handshake?Why is my query returning too many rows?Will you fix my code?Will you write or fix my code?
Not what you asked?

Ask us the actual question

Send the draft, the rubric or the score report with it. You get a real answer and a price before you commit to anything.

Get My Free Quote[email protected]