{"id":11915,"date":"2023-04-03T22:59:24","date_gmt":"2023-04-03T22:59:24","guid":{"rendered":"https:\/\/www.goodacademic.com\/blog\/questions\/final-project-milestone-two-conceptual-design-section-iii-and-design-revision-section-iii\/"},"modified":"2023-04-03T22:59:24","modified_gmt":"2023-04-03T22:59:24","slug":"final-project-milestone-two-conceptual-design-section-iii-and-design-revision-section-iii","status":"publish","type":"questions","link":"https:\/\/www.goodacademic.com\/blog\/questions\/final-project-milestone-two-conceptual-design-section-iii-and-design-revision-section-iii\/","title":{"rendered":"Final Project Milestone Two: Conceptual Design (Section III) and Design Revision (Section III)"},"content":{"rendered":"

Overview<\/u><\/b>: Database design is an integral step in the overall development of a database solution; a bad design can lead to many issues and problems with queries and potential expansion for any database. Getting the database design right is the first and most important step in <\/span>creating a successful database. <\/span><\/p>\n

<\/div>\n
Prompt<\/u><\/b>: In Milestone One, you read the final project scenario and then gathered the business requirements based on the goals, objectives, and user and business needs. <\/span><\/div>\n

<\/span><\/div>\n
For this milestone, you will frame the entity-relationship model (ERM) and define the entities and attributes for the business. Your next steps will <\/span>be to normalize your entities, define primary and foreign keys, and finally, draft an initial entity-relationship diagram (ERD).<\/span><\/div>\n

<\/span><\/div>\n
Specifically, the following critical elements must be addressed in the file “IT 235 Milestone Two Guidelines And Rubric.pdf”<\/span><\/div>\n

<\/span><\/div>\n
II<\/b>. Conceptual Design: Using your analysis of the provided scenario, address the following in order to determine an appropriate entity-relationship model (ERM) that will inform your final design:
\n<\/span><\/div>\n
A<\/b>. Assess various ERMs for their design applicability to your database design.
\n<\/span><\/div>\n
Hint: In this section, define the process you have used, and note several considerations you have made in your choice of
\n<\/span><\/div>\n
specific entities and attributes. Be sure to list the various entities and attributes that are of interest based on the scenario.
\n<\/span><\/div>\n
Some entities and attributes may not ultimately be included in your initial or final design and ERD.
\n<\/span><\/div>\n
B<\/b>. Determine the appropriate ERM and explain your choice.
\n<\/span><\/div>\n
Hint: Describe the appropriateness, reason, or basis for why certain entities and attributes would be included in your design
\n<\/span><\/div>\n
and others would be left out.
\n<\/span><\/div>\n
C<\/b>. Identify the data sets for the database, including all entities and attributes.<\/span><\/div>\n

<\/span><\/div>\n
III<\/b>. Design Revision: During this stage, you will draft your entity-relationship diagram (ERD), addressing the following elements:
\n<\/span><\/div>\n
A<\/b>. Construct your ERD, utilizing your identified entities and attributes.
\n<\/span><\/div>\n
B<\/b>. Determine appropriate primary and foreign keys for each entity and note them on your ERD.
\n<\/span><\/div>\n
C<\/b>. Determine table relationships and note them on your ERD.
\n<\/span><\/div>\n
D<\/b>. Determine appropriate data types and sizes for each attribute and note them on your ERD.
\n<\/span><\/div>\n
E<\/b>. Complete the normalization process utilizing dependency diagrams in order to prove tables are in third normal form (3NF), and
\n<\/span><\/div>\n
adjust your ERD if necessary.<\/span><\/div>\n
Hint: For each entity and table, complete dependency diagrams proving the table is in 3NF. If a table is in 3NF, only one
\n<\/span><\/div>\n
diagram is needed; if it is not in 3NF, progress through the normalization process, breaking up tables as necessary.
\n<\/span><\/div>\n
Additionally, revise your ERD based on the results of your normalization process. <\/span><\/div>\n

<\/span><\/div>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"

Overview: Database design is an integral step in the overall development of a database solution; a bad design can lead to many issues and problems with queries and potential expansion for any database. Getting the database design right is the first and most important step in creating a successful database.  Prompt: In Milestone One, you read the […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":[],"disciplines":[211],"paper_types":[],"tagged":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/questions\/11915"}],"collection":[{"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/questions"}],"about":[{"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/types\/questions"}],"author":[{"embeddable":true,"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/comments?post=11915"}],"version-history":[{"count":0,"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/questions\/11915\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/media?parent=11915"}],"wp:term":[{"taxonomy":"disciplines","embeddable":true,"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/disciplines?post=11915"},{"taxonomy":"paper_types","embeddable":true,"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/paper_types?post=11915"},{"taxonomy":"tagged","embeddable":true,"href":"https:\/\/www.goodacademic.com\/blog\/wp-json\/wp\/v2\/tagged?post=11915"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}