Entity relationship diagrams (ERDs) represent the data portion of a cloud-based database. This is why ERDs are often used as a tool to communicate how information is stored in a database. Being able to describe what goes into a specific database (entities, attributes, and relationships) ensures that you end up creating a cloud database that actually supports organizational operations. You want to avoid creating a database that stores irrelevant data.
For the purposes of this assignment, imagine that you are a solutions architect at a start-up organization, Your Online Database Architecture for Education (YODAE). To provide some context, YODAE is an educational technology company that is quickly growing and scaling its services. Its cloud solutions are used by teachers, educators, and administrators in the K–12 education industry. In order to implement a cloud-based system that meets YODAE’s clients’ needs (in this case, schools), you will design the cloud database.
For this activity, you will create an ERD that will represent student-information and teacher-information data. To successfully complete this activity, you will need to:
Review the : Review the business case document to gain a better understanding of YODAE, and of how your cloud solution will meet its organizational needs and operations.
Create an Entity Relationship Diagram: As part of the design of the cloud-based database, create an ERD to show the architecture of the cloud database system. To create your ERD, refer to that already includes some components of your diagram. You must add to this diagram by including the following components:
· All of the appropriate entities: What are the entities that need to be included in the ERD that are described in the business scenario?
· All of the appropriate attributes: What are at least five attributes for each entity?
· Necessary relationships: How will the relationships between the entities be accurately presented in the diagram?
Explain Your ERD: Write 2 to 5 paragraphs about how your diagram meets the needs of YODAE and its clients. You are required to provide a brief explanation about the entities, attributes, and relationships depicted in your diagram.
Guidelines for Submission
Upload a file that contains your ERD. You may use Lucidchart, Visio, or another software application of your choice to create your diagram. The file you upload should either be in a .doc or .pdf format. Do not submit the Lucidchart or Visio file that you created. Select All of the elements of the ERD from within the application you used to create it, and copy and paste into a Word or PDF document prior to submitting it for assessment.
YODAE ERD Example
For the entity relationship diagram (ERD) example, note that each entity (table) can have more attributes added to it, but the ones shown below must be included as they are for use later in this project. Your diagram should have a one-to-many relationship shown in crow’s foot notation with the relationship line above. (For more information about this notation, go to Crow’s Foot Notation.)