28 Mar work on the Logical Modeling Design and to speci
work on the Logical Modeling Design and to specify the entries, columns and their relationship. Use an entity-relationship ER diagram to visualize the database.
Your schema should include some attributes that make it possible to include some transactions that involve aggregate functions. For example, a school schema would allow for queries to calculate enrollment in each section of the average enrollment in courses for a given department, or the total courses being taught by each instructor, etc. This should also make interesting constraints and triggers possible. Review this basic example of a requirements document and Conceptual Data Model.
Turn your ER diagram into a normalized relational database design for the (subset of the) domain (i.e. a set of tables, each with appropriate attributes, a primary key, and appropriate foreign keys. The database should be based on the ER diagram, but one-to-one and one-to-many relationships may be implemented by appropriate attirbutes in the "one" entity, rather than as separate tables. You relational database must be at least in 3NF. Remember to determine the cardinality of the relationships. You may want to decide on cardinality when you are creating an Entity–relationship diagram ERD relationship table.
see sample below
Running Head: Conceptual Modeling Design 1
Conceptual Modeling Design 4
Conceptual Modeling Design
Student’s Name:
Tutor’s name:
Date:
The entities to be used include the following:
· Artist.
· Manager
· Producer
· Event
· Album
· Organizers
· Label
· Release
Relationships
The manager manages all the activities that the artist should take part in including signing the artist, managing the artist’s resources, advising the artist etc. The producer deals with the music production part, together with the organizers, they organize events that the artist will perform at. The producer together with the manager oversea the recording and the release of albums.
Each of the entities will have various attributes as follows:
· Under the manager the primary key will be the manager’s ID, other attributes will include the manager’s name, address, and the phone number.
· Under the artist the PK will be the artist’s ID while the other attributes will be the name, address, genre of music, and the phone number.
· The producer’s section will include the name, address, phone number, the salary, and the producer’s ID.
· The event will have attributes such as the type of event, the amount to be charged per person, and the reference number of the event.
· The label will include the record label’s name, the amount they charge, the serial number of the record label.
· The release entity will attribute such as the release date, and the venue of the release.
ERD Blueprint.
The ERD shows the relationship between the various entities involved in the music production.
Organizers
Event
Producer
Artist
Album
Label
Release
Manager
Reference.
D’Angelo, A. (2016). Development of the reliability-risk modeling framework for ranking conceptual designs. Volume 14: Emerging Technologies; Materials: Genetics to Structures; Safety Engineering and Risk Analysis. https://doi.org/10.1115/imece2016-66791
Embley, D. W., & Thalheim, B. (2012). Handbook of conceptual modeling: Theory, practice, and research challenges. Springer Science & Business Media.
Mok, W. Y., & Embley, D. W. (1996). Transforming conceptual models to object-oriented database designs: Practicalities, properties, and peculiarities. Conceptual Modeling — ER '96, 309-324. https://doi.org/10.1007/bfb001993
