Own words no plagarism

Step 1: Read and understand the Scenario and Business needs presented below. Define and document the ENTITIES, and RELATIONSHIPS, required to address the business needs. The nouns in the scenario below will give the ENTITIES that you will need. Finally, the verbs will describe the RELATIONSHIPS.Scenario and Business Need The Pythagoras Math Academy is in need to develop a database to keep track and control of his students, teachers, and classes offered. Teachers are able to teach multiple courses. But they are required to be certified on the course they are teaching. For example, only a group of teachers are certified to teach Algebra, and other Geometry. Students can take multiple courses. Courses are taught by teachers with the proper certification and have multiple certs as needed.  Courses are taught in one of the classrooms at one of the School’s several sites.Each classroom is optimized to serve the needs for a course (for example some courses might require computer labs and whiteboards). The school needs to keep track of the math courses delivered in each of the sites.Step 2: For this project, you are required to use MS Visio or ERD PLUS to produce the deliverables.If you are using MS Visio follow the steps below:

  • Reference the Course Project Ph2 VIDEO.mp4, for a short demonstration and tutorial of this tool, and project overview/ expectations.
  • Open MS Visio
  • Click on the Software Database Template in the main window
  • Select the Database Model Diagram Template to open a new file.
  • Save the File and ensure to have in your file name PROJECT2_LastName_FistInitial.

If you are using ERD PLUS.

  • Watch the recorded short tutorial for this tool. Reference the attached video as follows: Course Project Ph2 VIDEO.mp4.
  • From the ERP PLUS main interface, select DOCUMENTS –> NEW DIAGRAM (NAME YOUR DIAGRAM) –>ER DIAGRAM –> CREATE
  • Reference demonstration video for how to navigate tool, how to create entities, add attributes, relationships, and Cordiality. Demonstration video attached as follows: Course Project Ph2 VIDEO.mp4

Step 3: Define and Database ENTITIES

  • Add an entity for each Table you identified in the Scenario and Business Need.
  • You will use the MS Visio tool, or the ERD PLUS open source offering to complete this step.

Step 4: ADD the required ENTITY ATTRIBUTES  

  • Add the required Attributes for each Entity that you feel would help to define each Entity as needed.
  • Select one of the attributes to be PRIMARY KEY (PK)

Step 5: Define RELATIONSHIPS

  • Use the Crow’s Feet Notation.
  • Reference recorded demonstrations on how to use these notations, for MS Visio and ERD PLUS. Reference attached video as follows: Course Project Ph2 VIDEO.mp4
  • Drag and drop (draw) relationships between the entities you defined.
  • Connect the ends to the two entities for each relation.
  • Defined the Primary Key for the parent entity.

Step 6: Define CARDINALITY RELATIONSHIPSet the cardinality for each of your relationships defined in Step 5.  For MS Visio: select a relationship line in the drawing area that is connecting two entities. In the Database Properties window, select the miscellaneous category. Select the cardinality for the selected relationship.Step 7: Upload your Work 

  • Save the File and ensure to have in your file name PROJECT2_LastName_FistInitial. 

***The submission is a Word document with the ER Model diagram copied.  Do not send any type of image.  The submission must be the image copied into a Word document.  Please include a cover sheet with your full name, the class and  the university spelled correctly.  Please include any details necessary to describe the results. Rubric:

  • 10 points: ER Model (MS Visio OR ERD PLUS)
  • 10 points: Entities: Minimum of Three entities are represented
  • 10 points: Attributes: Minimum of Two attributes for each Entity. Most would require more than two attributes, and I am only requiring two per entity.
  • 10 points: Relationships: Minimum Three relationships are presented.
  • 10 points: Cardinality is defined and specific for each relationship with Crow’s foot notation.
Tags: No tags