A database of 16th-century European music records what pieces are located in which books, and where. A single book will contain many pages. A given musical piece can cover several lines of multiple pages. The Entity-Relationship diagram below shows an attempt to model this situation. (a) This model doesn't allow storing the order or co-ordinates for lines of music on a page, meaning that retrieving all the lines for a given piece will jumble them up. How could this be fixed? (b) Some books are published in tablebook format. These are designed to be placed on a flat table, with multiple performers standing around the book. An example is given below: To add this to our model, we need to resolve two concerns. Firstly, there are multiple instrument or voice parts to a piece. Secondly, the page has regions, each with lines going in different directions. Add these aspects to the model. [8] (c) List the tables, primary and foreign keys for a relational implementation of your modified model. [7] (d) Give a query to list pieces with the total number of lines of music that they occupy. (e) Assess the suitability of this data structure for a relational model, and compare with ONE other database model from the course (XML-based tree database, document database or Linked data graph database)