Part 1

Music Nepal need to design a product for Storing and selling. This product central idea is to
design a database that represents all the information that a music store needs to provide.
There is a lot of attributes on the database. The information for music need singing artists, their
uniquely identifying name, age, birth place and their style famous for singing. The product
should store the artist, recorded year, unique song, title, category of music. (e.g. classical, jazz,
pop, rock) and it’s market price for each song. Each song is also classified into specific group
according to major instrument, for example Guitar based, Drum base, Flute solo etc. This
product also keeps information about buyers like customer unique name, address, total money
spends for records, name of singer and group of song that the customer listens. For the data
Security and better user database is divide into some table. Information of artist a separate
table is design with information about the artist. the information of products and buyers in
another table is design. so, I have made database design using Visio. There were Three tables
altogether. the table data has done by 1NF as all the attributes has divided into table. All the
entity has unique name which is used as primary key to references to other table, category of
music every attributes are single value. In 2NF there should not be in any partial dependency .
Partial dependency means that a nonprime attribute is functionally dependent on part of a
candidate key.  if attribute B is functionally dependent on A, but is not functionally dependent
on a proper subset of A, then B is considered fully functional dependent on A. Hence, in a 2NF
table, all non-key attributes cannot be dependent on a subset of the primary key. Note that if
the primary key is not a composite key, all non-key attributes are always fully functional
dependent on the primary key. A table that is in 1st normal form and contains only a single key
as the primary key is automatically in 2nd normal form. Third normal form (3NF) is the third
step in normalizing a database and it builds on the first and second normal forms, 1NF and 2NF.
the attributes in a table are determined only by the candidate keys of that relation and not by
any non-prime attributes. Fourth normal form (4NF) is a level of database normalization where
there are no non-trivial multivalued dependencies other than a candidate key. It builds on the
first three normal forms (1NF, 2NF and 3NF) and the Boyce-Codd Normal Form (BCNF). It states
that, in addition to a database meeting the requirements of BCNF, it must not contain more
than one multivalued dependency.

Entities 1NF 2NF 3NF 4NF

Nick Name Nick Name Nick Name Nick Name Nick Name
Name Name Name Name Name
Age Age Age Age Age
Address Address Address Address Address
Birthplace Birthplace Birthplace Birthplace Birthplace
Singing style Singing style Singing style Singing style Singing style
Record Year

Artist Id Id Id Id

Song Title Artist Artist Artist Artist

Music Category Song Title Song Title Song Title Song Title
Marked Prize Music Category Music Category Music Category Music Category
Songs Group Marked Prize Marked Prize Marked Prize Marked Prize
Customers Record Year Record Year Record Year Record Year
Unique Name
Address Songs Group Songs Group Songs Group Songs Group
Total Money
Spend
Group of Song
Name of artist