SIMULATE PERSONALIZATIOZ USING DOCUMENNT ORIENTED

DATABASE

T.PRABAVATHI 20MA32

MASTER OF TECHNOLOGY

Branch : INFORMATION TECHNOLOGY

FEB 2021

DEPARTMENT OF INFORMATION TECHNOLOGY

PSG COLLEGE OF TECHNOLOGY

(Autonomous Institution)
 CONTENTS
CHAPTER PAGE
NO

1. Introduction……………………………………………………………………. 4

1.1 What is Nosql……………………………………………………………… 4

1.2 Types of Nosql………………………………………………………….… 5

1.3 Proposed System………………………………………………………...… 5

1.4 What is document oriented database…………………………………….... 5

1.5 How document oriented database works………………………………… 6

1.6 Advantage of document oriented database………………………………. 6

1.7 Disadvantage of document oriented database……………………………. 7

2. System Requirements..………………………………………………………... 8

2.1 Hardware Requirements………………………………………….….…….. 8

2.2 Software Requirements……………………………………………………. 8

2.2.1 MongoDb………………..…………………………………………………. 8

3. System Design…………………………………………………………….......... 11

3.1 Entity Relationship database………………………………………………. 11

3.2 Database Scheme…………………………………………………………… 11

3.3 Table Content………………………………………………………………. 11

4. Implementation and Result…………………………………………………… 12

4.1 Front end designs…………………………………………………………… 16

6. Conclusion…………………………………………………………................... 17
 ABSTRACT
An Personalization using document database is a distributed application that will be developed
to maintain the details of personal details working in any organization. It would maintain the
information about the personal details like resume, so that the human resource of the organization
can easily know the details of all its persons. It would be simple to understand and can be used by
anyone who is not even familiar with legacy personal system. It would be user friendly and just
ask the user to follow step by step operations by giving him few options. It would be fast and can
perform many operations of a company. This software package would be developed using the
powerful coding tools of MongoDb database at backend. For further enhancement or
development of the package, the user’s feedback will be considered.
 CHAPTER 1
INTRODUCTION

Indexing is a way to optimize the performance of a database by minimizing the number

of disk accesses required when a query is processed. It is a data structure technique which is
used to quickly locate and access the data in a database.

Indexes are created using a few database columns.

• The first column is the Search key that contains a copy of the primary key or candidate
key of the table. These values are stored in sorted order so that the corresponding data can
be accessed.
Note: The data may or may not be stored in sorted order.
• The second column is the Data Reference or Pointer which contains a set of pointers
holding the address of the disk block where that particular key value can be found.

1.1 WHAT IS NOSQL?

Nosql Database is a non-relational Data Management System, that does not require a fixed
schema. It avoids joins, and is easy to scale. The major purpose of using a Nosql database is for
distributed data stores with humongous data storage needs. Nosql is used for Big data and real-
time web apps. For example, companies like Twitter, Facebook and Google collect terabytes of
user data every single day.Nosql database stands for "Not Only SQL" or "Not SQL." Though a
better term would be "NoREL", Nosql caught on. Carl Strozz introduced the Nosql concept in
1998.Nosql Databases are mainly categorized into four types: Key-value pair, Column-oriented,
Graph-based and Document-oriented. Every category has its unique attributes and limitations.
None of the above-specified database is better to solve all the problems. Users should select the
database based on their product needs.

1.2 TYPES OF NOSQL DATABASES:

• Key-value Pair Based

• Column-oriented Graph
• Graphs based
• Document-oriented

1.3 PROPOSED SYSTEM:

Manual handling of personal information poses a number of challenges. The use of
paper work in handling some of these processes could lead to human error, papers may end up in
the wrong hands and not forgetting the fact that this is time consuming.An Personalization using
document database is a distributed application that will be developed to maintain the details of
personal details working in any organization. It would maintain the information about the
personal details like resume, so that the human resource of the organization can easily know the
details of all its persons. The project is aimed at setting up an personal information system, the
educational background and the work experience in order to help monitor the performance

1.4 WHAT IS A DOCUMNET -ORIENTED DATABASE?

Document store database (also known as a document-oriented database, aggregate database,

or simply document store or document database) is a database that uses a document-oriented

model to store data.Document store databases store each record and its associated data within a
single document. Each document contains semi-structured data that can be queried against using
various query and analytics tools of the DBMS.A document-oriented database is a specific kind
of database that works on the principle of dealing with 'documents’ rather than strictly defined
tables of information.The document-oriented database plays an important role is aggregating data
from documents and getting them into a searchable, organized form.

1.5 HOW DO DOCUMENT DATABASE WORK?

A document database is a type of non relational database that is designed to store and query data
as JSON-like documents. Document databases make it easier for developers to store and query
data in a database by using the same document-model format they use in their application code.
The flexible, semi structured, and hierarchical nature of documents and document databases
allows them to evolve with applications’ needs. The document model works well with use cases
such as catalogs, user profiles, and content management systems where each document is unique
and evolves over time. Document databases enable flexible indexing, powerful queries, and
analytics over collections of documents.

The idea behind document databases is that you can store any sort of information in a document.
That means you can mix and match whatever sort of data you want without really having to
worry about the database not being able to parse it. Of course, in practice, most document
databases still tend to use some form of schema with a file format and some kind of
predetermined structure.

Compared to an SQL database which is both tubular and relational, document store doesn’t have
the same foibles and restrictions that SQL does. This means it’s much easier to work with the
information at hand, and queries can be much easier to carry out. Ironically, the same sort of
actions you can perform in an SQL database, you can also perform in a document-store such as
deleting, adding, and querying.

As alluded to earlier, each document needs some sort of key, which is provided to it through a
unique ID. When the unique ID is provided in any process, the information in the document itself
is read and dealt with directly, rather than being taken out on a column by column basis.

One thing to be aware of when it comes to document databases (and NoSQL databases as a
whole), is that they tend to be slightly less secure than SQL databases. As such, you really need
to take into account database security, and one way to do that is using SAST. SAST, or Static
Application Security Testing, looks directly at source code to find vulnerabilities. You can also
run DAST, which is a dynamic version, and that can similarly help with avoiding NoSQL
injections.

1.6 ADVANTAGE OF DOCUMENT DATABASE:

⚫ Probably the biggest benefit of document-store is that everything is available in a single

database, rather than having information spread across several linked databases. As such you
get better performance compared to an SQL database as long as you don’t use relational
processes. Interlinking documents can add a lot of complexity and become frustrating to use,
and references don’t really work well in document-store.

⚫ Unlike in conventional databases where a field exists for each piece of information, even if
there's nothing in it, a document-store is more flexible. In fact, there’s no need for
consistency in the documents, and you can essentially store massive amounts of data with
relatively no issues.

⚫ Similarly, since it’s more flexible, integrating new data isn’t problematic at all. Compared to
a relational database where any new type of information must be added to all datasets,
document-store only requires you to do it in a few.

1.7 DISADVANTAGE OF DOCUMENT DATABASE:

⚫ While the majority of document-store databases have been around for a while now, there still
isn’t much documentation outside of small niches and the database’s own wiki or forums.
This is compounded by the fact that there are so many document-store databases to pick
from, sometimes it can be hard to find specific information without deep dives.

⚫ Along with that, there is the possibility of a loss of data, either due to an incorrect
configuration because of a lack of familiarity, or because of the use of a single node. Another
issue is that document-stores are not really made for running multiple, complex operations or
complex queries.

⚫ Compared to SQL which is relatively well established and isn’t going to see much change,
NoSQL can be difficult to keep up with if you don’t have the passion or interest.
 CHAPTER 2

SYSTEM REQUIREMENT

Performance requirements There is no restriction on the number of the users to be added

to the database.

2.1 HARDWARE REQUIREMENTS

HARDWARE SPECIFICATIONS:

• OS: Windows 10 pro

• Processor Generation: 10th Gen

• RAM: 8 GB

• RAM Type: DDR4

• Capacity: 1 TB

• Others: Network interface card, mouse, keyboard, and monitor.

2.2 SOFTWARE REQUIRMENTS

2.2.1 MONGODB

MongoDB is a document-oriented NoSQL database used for high volume data storage.
Instead of using tables and rows as in the traditional relational databases, MongoDB makes use
of collections and documents. Documents consist of key-value pairs which are the basic unit of
data in MongoDB. Collections contain sets of documents and function which is the equivalent of
relational database tables. MongoDB is a database which came into light around
2.2.2 MongoDB Features

1. Each database contains collections which in turn contains documents. Each

document can be different with a varying number of fields. The size and content
of each document can be different from each other.
2. The document structure is more in line with how developers construct their classes
and objects in their respective programming languages. Developers will often say
that their classes are not rows and columns but have a clear structure with key-
value pairs.
3. The rows (or documents as called in MongoDB) doesn't need to have a schema
defined beforehand. Instead, the fields can be created on the fly.
4. The data model available within MongoDB allows you to represent hierarchical
relationships, to store arrays, and other more complex structures more easily.
 CHAPTER 3

SYSTEM DESIGN

3.1 ENTITY RELATIONSHIP MODEL

3.2 DATABASE SCHEME

Personal(id,name,phone-no,address,date-of-birth)

School(name,percentage,year-of-passing)

College(name,percentage,year-of-passing)

Area-of-intrest(projects, subject-name)

Projects(project-title,year)

Sport-acitivity(sport-name,awards)
3.3 Table content

Person

Name Phone no Address Date of birth

prabavathi 987969576 Kaveri nagar trichy 17 july 1998

gokul 979705876 vellore 28 may 1998

School

School name Year of passing Percentage

Jospeh trichy 2016 91%

Srv chennai 2016 96%

College

College name Year of passing percentage

Psg college of technology 2020 80%

Psg college of technology 2020 90%

Project

Project name year

Breast cancer prediction IoT

Leukemia cell classification Machine learning

Sport activity

Name of sport awards

Tennis 1

Football 2

Area of interest

Subject name project

database Employee management system

java Bus reservation system

 CHAPTER 4

IMPLEMENTATION AND RESULT

Table 1:personal

Find()

Table 2 :school
Table 3:college

Table 4:sports

Table 5:are of interest

Table 6:project

Update()

Table 7:extra activities

 CONCLUSION

The application has been completed successfully and was also tested successfully by taking “test
cases”.And easy to get the command and update the commands .It would be simple to
understand and can be used by anyone who is not even familiar with legacy personal system. It
would be user friendly and just ask the user to follow step by step operations by giving him few
options. It would be fast and can perform many operations of a company.