Hi,
i
just want ask the expert for this : Entity
Relationship Modeling Examples
Please
reply my email. Thanks
This
example explains the requirements for databases—music, and
shows it’s Entity Relationship diagram:
-
The music database
is designed to store details of a music collection, including the
albums in the collection, the artists who made them, the tracks on
the albums, and when each track was last played. -
-The
Music Database -
The music database
stores details of a personal music library, and could be used to
manage your MP3, CD, or vinyl collection. Because this database
is for a personal collection, it’s relatively simple and stores
only the relationships between artists, albums, and tracks.
I
first draw up a clear list of requirements for our database:
-
The
collection consists of albums. -
An
album is made by exactly one artist. -
An
artist makes one or more albums. -
An
album contains one or more tracks -
Artists,
albums, and tracks each have a name. -
Each
track is on exactly one album. -
Each
track has a time length, measured in seconds. -
When
a track is played, the date and time the playback began (to the
nearest second) should be recorded; this is used for reporting when
a track was last played, as well as the number of times music by an
artist, from an album, or a track has been played.
It
is notice that ER diagram consists of only one-to-many
relationships: one artist can make many albums, one album can contain
many tracks, and one track can be played many times. Conversely, each
play is associated with one track, a track is on one album, and an
album is by one artist. The attributes are straightforward: artists,
albums, and tracks have names, as well as identifiers to uniquely
identify each entity. The track entity has a time attribute to store
the duration, and the played entity has a timestamp to store when the
track was played.
The
only strong entity in the database is Artist,
which has an artist_id attribute
that uniquely identifies it. Each Album entity
is uniquely identified by its album_id combined
with the artist_id of
the corresponding Artist entity.
A Track entity
is similarly uniquely identified by its track_id combined
with the related album_id and artist_id attributes.
The Played entity
is uniquely identified by a combination of its played time,
and the related track_id, album_id,
and artist_id attributes.
Could
you please develop the database consider
adding the following features:
-
Support
for compilations or various-artists albums, where each track may be
by a different artist and may then have its own associated
album-like details such as a recording date and time. Under this
model, the album would be a strong entity, with many-to-many
relationships between artists and albums. -
Playlists,
a user-controlled collection of tracks. For example, you might
create a playlist of your favorite tracks from an artist. -
Source
details, such as when you bought an album, what media it came on,
how much you paid, and so on. -
Album
details, such as when and where it was recorded, the producer and
label, the band members or sidemen who played on the album, and even
its artwork. -
Smarter
track management, such as modeling that allows the same track to
appear on many albums.
The post Entity Relationship Modeling appeared first on My Assignment Online.