2DATABASE DESIGN AND IMPLEMENTATION
Project Description:
Library Database Design Requirements:
The database can be considered as the set of data associated to a specific purpose or subject. The
database is either installed in a computer or in a cloud. The relational database system is the most popular
database type. The relational database is based on implementing relation among the entities stored in the
database. Prior to design the database, the designer must design the whole database. Without a good design it
is not possible to implement a fully functioning and scalable database. The database design include the entity
relationship diagram, relationships, attributes, constraints and many other things.
The fundamental steps for designing a complete database are as following.
i. Determining the database implementation purpose
ii. Identifying the entities required to support the purpose
iii. To recognize the attributes that can be the basic structure of the entities
iv. To understand the constraints that will be applied to the attributes
v. Recognizing the relationships among the tables
vi. Making the database entities in 3rd Normal form
vii. Adding data to the entities so that it can be meaningful
Determining the Database Purpose: The database is prepared for storing the data and activities done
in the library. The database will be storing the details of the members, books and rents mainly. However, the
other process associated with the library will need to be recorded. Taken as an example, a member can search
books of a specific writer. Therefore, storing the information of each author and which books they have
written is important. The library also impose fines when the books are not returned on time. Therefore the
database will also store the fine related information. It is essential to complete the planning part before start
implementing the database in Oracle. It is because, planning can seem to be time consuming but if not planned
properly a complex database can take ten times more time to be completed without planning.
Determining the Tables: This is considered to be one of the trickiest parts in the whole database
design process. This part is extremely tricky as the outcome of the database does not provide any assumptions
regarding the structure of it. The structure has to be done from scratch without having no idea of what can be
the outcome, up to a certain point. This process needs to be done by an extremely skilled and experienced
person. It is essential that database structure can prevent storing same data twice. However, for meeting the
purpose few data will be used various time but this repetitive data must be restricted only one in the whole
table. All the columns of the table must be related to the purpose of the database. Taken as an example, if the

+13062052269

info@desklib.com