The initial entities identified to be managed by the database include: (1) Piano-Teacher, (2) Piano-Student; (3) Piano-Level level 1 through 10 - indicating standard reached by a student); (4) Piano-Lesson {individual}; (5) Theory-Lesson {class}; and (6) Lesson- Payment. The kinds of information the academy wishes the database to capture is not just to manage actual timetables of teachers and students, but also to be able to measurably answer questions new students/parents ask, such as how long will it take before I can pass my Piano Level 1? How much will cost to get to Piano Level 37 etc. Consider what attributes the various entities named will require to answer the questions posed as part of your #4 task - testing the database. For this case, it will serve you well to read and consider the whole case (including the testing questions) before beginning to Conceptualise or build your database. Develop an ERD to conceptualise how the entities within the case/scenario relate to one another, so that a database can be built from that ERD. You will need to: 1. Build the conceptual database: a. Build an ERD that captures the conceptual database/model " include entities, relationships, and PK/FK attributes. " you may use crows-foot or UML class diagram annotation, but be consistent