Answer & Explanation:Please review the Requirement of designing a Database :you will need to design the database
schema, showing in detail all the relations, data types, relationships, and
constraints to be used in the database. You must draw schema diagrams using Microsoft Visio or similar. After the design phase
is over The draft must include at least the description
of your company, business rules, and an ERD: consists the following sections:
Title Page
that includes:
Title of the project
Course name
Course number
Name of the student
Description
that includes:
Screen shot from Blackboard confirming your topic
Description of the company (1 paragraph)
Business requirements for the database (1 paragraph)
Business requirements will explain why
your company needs a database, what kind of data you are planning to store in
the database, and how your company is going to utilize this data.
Business Rules:
Each business rule must follow the format
Each business rule must describe a relationship in
both directions
Each entity and each relationship used in the
database must be described in this section
Each entity and each relationship described in this
section must be presented on the ERD
Entities that
includes:
Entity’s name
Entity’s description
List of attributes
Data type of each attribute (numeric, text, or
date)
Sample data for each attribute
Constraints (PRIMARY KEY, FOREIGN KEY, UNIQUE, NULL
where applicable)
Each entity must be described in the
section. You must have a minimum of 4 entities. The total number of entities
recommended is 4-5.
Relationships
that includes:
A copy of a specific business rule from the
Business Rules section for each relationship described here.
Relationship’s type: 1:1, 1:M, M:N. Use business
rules to justify your decision.
Relationship strength: strong or weak. Use business
rules to justify your decision.
Optionality for both sides of each relationship:
mandatory or optional. Use business rules to justify your decision.
Each relationship must
be described in the section. Each M:N relationship must be resolved and
described.
Crow’s Foot
Entity Relationship Diagram:
ERD must be consistent with business rules and
descriptions
ERD must show all entities and their attributes,
relationships, connectivities, constraints, optionality and cardinalities
Tables and attributes names must follow naming
conventions used in class
Each relationship must be properly labeled If a composite primary or foreign key is used on ERD, explain your reasoning.Please review the files bellow attach for the topic
topic_and_des.rar
Unformatted Attachment Preview
…
Purchase answer to see full
attachment
