# in dhis question you need to draw an e r diagram on your answer sheet for the follow 5187903

In dhis question, you need to draw an E-R diagram (on your answer sheet) for the following data modeling problem: Assume that we are designing a database for a TV company to store the that the company produced. A TV series is a television program that consists that usu data about the TV series of many episodes ally share common main characters and often a common story line. The data we need to store includes information about TV series and their episodes, actors, first need to track the following information for TVSeries, Episode, Actor, and Director. and directors. In specific, we For TVSeries, you need to track its SeriesNo, SeriesTitle, and Release Date. A TV series can be identified by its Series No. For Episode, you need to track its EpisodeNo, Episode Title, and length. An episode can be identified by its EpisodeNo . For Actors, you need to track its ActoriD, Name, Gender, and Email. An actor can be identified by its ActoriD For Directors, you need to track its DirectorID, Name, and Email. A director can be identified by its DirectorlD. In addition to track the above information, you also need to track the relationships among TVSeries, Episode, Actor, and Director. In specific, you need to consider the following relationship in your design: First,each TV series consists of many episodes, but each episode belongs to only one TV Second, actors are contracted to play in a TV series. An actor can play in many TV series and each TV series can have multiple actors. Last, directors are responsible for directing a whole TV series. A director can direct many TV series, and a given TV series can have only one director Further notes The instruction above only provides information about maximum cardinalities. You carn assume that the minimum cardinality of any entity in any relationship is one (but you still need to draw minimum cardinalities in the diagram) You just need to draw data models, and thus do not need to specify datatypes, foreign keys, and other constraints needed for table design. Your data models just need to have entities, their attributes and identifiers, and the relationships among them (including maximum/minimum cardinalities).