Long before the tables are created and data is moved or inserted into them, the
ID: 3842598 • Letter: L
Question
Long before the tables are created and data is moved or inserted into them, the database designer created the logical and physical models of the database. In this unit you will examine the process of relational database design and modeling and understand and use normalization techniques to create a UML (Unified Modeling Language) diagram of a database.
From the readings, web resources and videos this week, what have you learned about the process of relational database design and modeling and use normalization techniques to create a UML (Unified Modeling Language) diagram of a database. Be specific on the “do’s and don’ts of the process that database designers need to look for. Please identify positive and negative issues with UML diagrams.
Supervises LIBRARIAN 0 EMP NO (PK) NAM ADDRESS AGE CHECK OU requests RECORD NO (PK) CARD NO (PK) OUTDATE NAME DUE DATE ADDRESS RETURN DATE CONTACT WARN DATE WARNINGNO MESSAGE PUBLISH PUB NO (PK) NAME ADDRESS SBN NO published by AUTHOR CATEGORY PUBLICATION DATE AUDIO BOOKS HARDCOPY BOOKS COPY NO COPY NO READER NUMBER PAGES LENGTH SUPPLIEl SUPP NO (PK) NAME ADDRESS CONTACT IS MEDIA NO (PK) NAME DATE OF REQUISITION DATE OF DISPOSAL REFERENCE ONLY VIDEOS DEO NO NAME COPY NO VOLUME LEAD ACTOR SSUE DATE DIRECTOR CATEGORY TYPE LENGTH DATE LEAD ARTICLEExplanation / Answer
Answer :
Process of relational database design :
The process of relational database design mainly follows the below steps.
step 1: Define the purpose of database that you are constructing.
step 2: Gather data,organize in tables and specify the required constraints.
step 3: Create proper relationships among the tables.
step 4: Refine and normalize the design.
step 5: Create UML diagrams based on the normalized data for better understanding.
DO's :
1)Identify the crux part of the requirement to design database
2)Keep the design as simple as possible
3)Give proper naming convention to the UML diagram
DONT's :
1)Improper analysis of the data leads to incorrect design
2)Shouldn't neglet the depencies properly which leads to redundancy of data
UML positive issues:
1) UML shows the relational database in an interactive way
2) One can easily understand the design properly
3) Coding becomes easy with UML diagram
UML negative issues:
1) The UML diagram might become overcomplicated at times which can be confusing and frustrating for developers.
2) UML gives more priority to design, which can be problematic for some developers.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.