Database Management Systems: Design & Applications

This assignment delves into the core concepts of Database Management Systems (DBMS). Students are tasked with analyzing various DBMS models, exploring their strengths and weaknesses, and evaluating the suitability of different systems for diverse applications. Case studies and examples from diverse fields like healthcare, bioinformatics, and energy management illustrate the practical relevance of DBMS. Understanding normalization principles and the database life cycle are also crucial aspects of this assignment.

DATABASE
MANAGEMENT
SYSTEMS

TABLE OF CONTENTS
INTRODUCTION...........................................................................................................................1
TASK 1 DATABASES AND DATA MANAGEMENT SYSTEMS.............................................1
1.1 Key issues and Application of databases..........................................................................1
1.2 Features and Advantages of DBMS.................................................................................4
TASK 2 DATABASE DESIGN TECHNIQUES............................................................................5
2.1 Database Developmental Methodology...........................................................................5
2.2 Entity- Relationship Modelling and Normalization.........................................................8
TASK 3 DATABASE DESIGN....................................................................................................10
Overview..............................................................................................................................10
3.1 Database Development Cycle.........................................................................................10
3.2 Fully Functional Database..............................................................................................17
3.3 Effectiveness of the Database Solution and improvement methods..............................32
3.4 Supporting user and Technical Documentation.............................................................33
CONCLUSION..............................................................................................................................35
REFERENCES..............................................................................................................................32

ILLUSTRATION INDEX
Illustration 1: waterfall model..........................................................................................................6
Illustration 2: Database life-cycle....................................................................................................7

INTRODUCTION
A database management system also called as DBMS is known as the first manufactured
database followed by its management. DBMS is an internal system software. There is a
systematic way by which users can create, edit, update or delete the data. DBMS provides them
this way. This system can be divided into four parts i.e. the Users, DBMS, Database and the
Database application. The users can be of many type like administrators, developers and the end
users. DBMS application can be personal, regulatory, operational and internal as well (Chen and
Hu, 2011). Database applications are being used almost everywhere, some very common
examples are computerised system in libraries, reservations at airport, ATMs etc. Database is
the overall contribution of the logical data. Some functions are that it supplies data
independence, gives recovery services and various beneficial services. It provides minimum
duplicates of data and it is very easy to recover the data in DBMS but is quite costly to use and it
deals with a lot of complexity. Shoengallric Art Gallery is an art gallery, established in 2010 in
China. This report explains how database management helps the art gallery to recover fast.
TASK 1 DATABASES AND DATA MANAGEMENT SYSTEMS
1.1 Key issues and Application of databases
There are a various number of database applications worldwide being used by the people.
Some of the applications are being discussed below: Telecom: All the calls made, the overall network usage, details of the customer, these all
are being tracked by a database (Chen and Hu, 2011). It is very difficult to maintain the
large amount of data without the database system. In database system, data keeps
updating every millisecond. Industry: No matter whether it is a warehouse, retailer centre, distributor centre or any
manufacturing unit, databases are required to keep the record for every entry of in as well
as of out. A very common example of this can be online shopping sites, when the product
is being out for the delivery, the buyer can track where it is and when it will be delivered.
Although it gives an approx., but most of the times, it gives the appropriate schedule. Banking System: Daily debit and credit transactions, storing the customer's information,
Chalan details, new account openers etc. all the record of these activities are maintained
by the database management system.
1

 Education Sector: Every schools and colleges use the database management systems for
storing the student's details, teacher's details, course details, exams details etc. All the
details of students, exams, teachers, course etc. constitutes lot much amount of data
which is impossible for any person to keep in mind for a long time (Chen and Hu, 2011).
So, a database management system makes a difference here by storing this much large
amount of data.
 Online shopping: All the online websites as Flipkart, Amazon, Jabong etc. keeps a
record of the card details one saves while billing online. If the information like address
etc. are stored once, the next time it automatically shows the previous details. This is
called the database management system.
The managers at Shoengalleric Art Gallery can also use some of these applications for the
betterment of the business. They can use database system for the online demand of their art
pieces (Voulodimos and et.al, 2010). They can open an online portal where they can send their
antiques online. Their customers will be able to track the product from time to time and this can
go good for their business as people from other states will also be able to buy that online and can
time to time track the product and also can cancel it if want to. Also, the Art Gallery can keep
record of their employees, staff, customers etc. Usage of the database management system can
help Shoengalleric Art Gallery to grow faster.
Key issues of Databases
There are various issues also while dealing with databases. Some key issues and
challenges are discussed as under: Data distribution issues: This deals with availability of data is much higher than the cost
of remote access. It is lower than the availability of data. It provides more proper access
to data as well as higher security. Replication Issues: The more we increase the number of duplicates, the more increase in
costs for updates and signalling takes place. There are mobile hosts which can move
anywhere and anytime. Transactional Models: The ACID i.e. atomic, consistent, isolated, durable properties are
being satisfied by all the transactions (Chen and Hu, 2011). Concurrent transactions that
are performed should be serialised. Mobile transactions are a part of distributed
transactions in which some transactions are performed in fixed hosts while others in
2

mobile computers. When the mobile computers are disconnected, ACID properties are
hard to impose on them. Query processing: When mobility is being considered, Query processing gets affected. It
is very common as nowadays, various latest apps have been developed as we can easily
search e.g. “gas stations near me”, theatres near me etc. on any search engine. Even on
Google also and it replies back and that too within a few milliseconds. Caching: These techniques for query processing dramatically reduces communication
costs. It is quite difficult to apply these techniques in mobile context. Fault Tolerance: Even with some internal faults, the capability of performing function
efficiently, is called Fault tolerance. Faults can be either transient or permanent. There
are some features by which mobile computing environment can be characterised by and
these are limited availability of resources, high flexibility, low bandwidth and repetition
in disconnection.
 Location based services: To find out the location of some mobile users is not as easy. It
is quite challenging. There are some techniques such as GPS etc. but there are some other
methods also which include Cell of Origin, Time of arrival and Angle of arrival and
enhanced and observed time difference. GPS is also a very developed technology. GPS
stands for Global Positioning System (Chen and Hu, 2011). GPS can also be accessed in
mobile phones as if someone feels troubled in some weird place and does not know the
location, or he/she has to travel somewhere else. GPS can be operated in those phones in
which GPS receiver chip has been integrated. There are some issues also with it e.g. it
somehow interferes the user’s privacy as if someone don't want to let other knows their
location, but for that they can turn off their GPS also.
As obvious, the database management system has some issues, so Shoengalleric Art Gallery
also have to bear some, if they are using database management system. It can affect them in a
way that if they do not enable their location services on the internet, people won't be able to get
the exact location when they search for it (Voulodimos and et.al, 2010). Also, if they will not
register themselves on the internet, google or any other website will be unable to deliver the
results about it which becomes as a barrier for their popularity in the market. The staff there
should know how to deal with Fault tolerance because many times some faults have been done
by any staff member or any member of the gallery and that fault can be transient or it can be
3

permanent also. So, they should know the techniques to deal with it so that it does not affect the
name of the Art Gallery.
1.2 Features and Advantages of DBMS
Some well-known features of DBMS are that it manages the data effectively, it is user
friendly and it provides full security of the shared as well as the stored data. As the
communication and sharing of information in the Shoengalleric Art Gallery is poor, database
management system can help them to come out of it as it provides full security of the shared data
as well as the data in their storage (Chen and Hu, 2011). This will improve conditions in
Shoengalleric Art gallery as the employees there can communicate well about various issues and
they will be sure of the security of the data as well. DBMS also provides information that is free
of errors. In computers, usually users generate backup for their data on a regularly basis but it
can be very hectic and time consuming if the data is large. So, DBMS has created recovery sub
systems by which data backup and restore can automatically happen when required. If someday
this problem happens at Shoengalleric Art Gallery, the gallery will face no sort of loss because
DBMS can easily restore the data (Färber and Dees, 2012).
Another important fact that DBMS provides is the restriction of the unauthorized access.
It becomes a very important factor for all the organisations as no one can steal the information by
this means and this refers to high security. The developing cost as well as the maintenance is low
in DBMS. Although the initial cost of setting of database management system is high, but the
cost of development and maintenance is much lower than the initialization. The manager of
Shoengalleric Art Gallery should set up the database system for their gallery so that they will not
go into further losses and by means of DBMS, they can recover well. Only the initial cost is
quite high, after that the development, fixing and maintaining is not as high as the initial so it
will not be that tough for the gallery. It is just one-time fixation (Voulodimos and et.al, 2010).
The gallery will automatically recover soon and will become a boom in the market. Some other
characteristics of DBMS are:1. Real World Entity: To design the architecture, real world entities are being used by the
user. Taking an example, in a school database, students are entities and their age act as
attributes.
4

2. Relation based Tables: The database system permits the entities and relations to form
tables. It becomes very easy for the user to understand the architecture just by looking at
the tables.3. Separation of data and application: Data is quite different from its database system.
This is an entity which is always active whereas data is always passive (Färber and Dees,
2012). The data about data is called as Metadata. It is also stored by DBMS because it
eases its process.4. Less redundancy: When any of the attributes is having redundancy, it splits its relation
i.e. it starts following normalisation. Normalisation is a method in which data redundancy
can be reduced.
5. Stability: Every relation remains stable at a stage called stability. If it is unstable, there
are some techniques which can detect it.
TASK 2 DATABASE DESIGN TECHNIQUES
2.1 Database Developmental Methodology
As in a very large firm, a huge team has coordinated groups that are focusing on their
work simultaneously on database design, the comparative database lifespan is called the
relational database system. Partitioning of all the development processes into different parts such
as phases, steps whose only forte is the development. It can be termed as Adrienne Watt. The
process of database development consists of many processes which are discussed as below:
 SDLC - Waterfall
5

Waterfall model is termed as the easiest model in the database design techniques and is
mostly used in many software processes. As in fig, the waterfall model is partitioned into a few
components (Voulodimos and et.al, 2010). The outcome of one component is the input of the
other component and similarly the process goes on till component maintenance.1. Requirement analysis - Development of all the necessities of the system takes place.2. System Design – All the necessary specifications are kept in mind so that the system
design can be prepared easily.3. Implementation – The inputs from the system design are evolved into small parts called
units and that units become cohesive in the next phase (Färber and Dees, 2012). It refers
to unit testing.4. Testing – From the implementation phase, all the evolved units are taken in a system
after their testing. Faults and failures are also being tested later on.5. Deployment – After the functioning process, the product is being placed for the
customers in the market.
6
Illustration 1: waterfall model
(Source: Färber and Dees, 2012)

6. Maintenance – If the client has some issues, patches for the product start releasing and
modified versions are also being produced. To provide the new and modified changes in
the market, maintenance is being done.
Database Life Cycle
Database Life Cycle can also be said as DBLC. It is a combination of technical and
business approach which helps in the betterment of development of the database, delivery and
the management (Voulodimos and et.al, 2010). Database Life cycle includes database making
and the resource allocation, which helps in managing the database schema and data. It also does
backup and recovery tasks. The life-cycle tasks have been performed by the database
administrators and the application developers. One can create tables, appoints primary and
foreign keys and creates views and indexes and other database entities (Färber and Dees, 2012).
It regularly takes and tests backups, safeguarding the data. Its scale up is very good as it
increases the size of database as required. To perform the maintenance tasks, it can be stopped as
well as restarted if the user wants. The user can disable the database whenever it wants to as well
as deleting databases is also easy because it is good to free up the facilities when not required.
7
Illustration 2: Database life-cycle
(Source: Lee and Lin, 2015)

 Requirements gathering: For Requirements Gathering, establishing requirement are must.
It includes consultation and the agreement along with the users. The data administrator
has a key role in this process. Understanding of requirements with the users is necessary.
 Analysis: Data Analysis starts with the data requirements and produces a conceptual data
model. The main forte of data analysis is to acquire an exact formatted description of the
data that users are comfortable with. Some examples of its properties are like in school
database system, course number, course title, roll number of students etc.
2.2 Entity- Relationship Modelling and Normalization
The graphical representation of entities and their relationships with each other is called
Entity-Relationship. Real world objects, that can be easily identified are called Entities. Taking
example of a school database, students, classes, teachers etc. are considered as the entities of the
database. Similar types of entities are collected in an entity set. By means of some properties,
entities are represented as attributes. The attributes can be simple, composite, derived, single
value attributes and multi value attributes. In an entity set, there are some keys. Super key
constitutes an attribute set that identifies an entity in an entity set. Candidate key is also a super
key that is minimal. There is an entity model relationship which is usually the systematic
analysis of defining and describing the importance to process in the business area. Business
processes are not defined under this. It only represents a graphical schema of business entity
relationship. Conceptual data model is the ER model that is on highest level but it consists the
least granular detail which has established the overall scope of everything what is to be included
in the entity relation model. Logical data model is another model which does not requires an ER
model that is conceptual. It is specially when it only has the production of distinct information
system. Physical data model is another model that can be developed from a logical ER model.
Each physical ER model must have satisfied the required details. The ER model is basically used
to design the new modifications to the relational database. The candidate keys can be more than
one in an entity set. Primary key is a type of Candidate key which uniquely identifies the set.
Normalization can be described as under :
Normalization can be termed as a method in which something can be returned back to its normal
state. It decomposes the relations into small relations. Use of normalization eliminates the
useless data. It also ensures data dependencies. Ensuring data dependencies satisfies all integrity
8

constraints. Elimination of useless data prevents insert, delete and update analomy. Various
forms of normalization are described as under :
(Source : Chen and Hu, 2011)
1. First Normal Form (1NF) – According to this, the two simultaneous rows does not
contain any repetition of data. That means every column should have a unique value. No
value in the table should be repeated. The table should be organised into rows and each
row should have a particular and unique primary key. This form has an advantage that it
helps in increasing the data redundancy.
2. Second Normal Form (2NF) – In this form, on any primary key there should not be any
partial dependency. If even any one column relies on concatenated key, then the table
fails to be in second normal form.
9
Illustration 3: Normalization

3. Third Normal Form (3NF) – In this form, every attribute that is non prime attribute of the
table should rely on the primary key. A non prime attribute cannot be termed as another
non prime attribute. From the table, transitive function dependency should be eliminated
and it has some advantages also that copied data amount is minimised and data integrity
can be achieved.
4. Boyce and Codd Normal Form (BCNF) – This form is an upper and higher version of the
third normal form. It is an higher form because it deals with a particular type of analomy
that 3NF can not handle. BCNF is a 3NF table which does not have overlapping
candidate keys but for a table to be in BCNF, it must satisfy some conditions as R should
be in 3rd normal form.
TASK 3 DATABASE DESIGN
Overview
Designing a database of an art gallery i.e. Shoengalleric Art gallery, established in China
in 2010. From that time, it is enlarging in various cities of China. Art on various subjects is
present there in the gallery. The Shoengalleric art gallery is having a staff of at least 500
members. It deals with art, its culture. The main forte of this gallery is to present the art culture
to people so that they can know the importance of it.
Business rules approaches in software development are concentrated in finding ways and
facilities that would support automatic propagation of business changes from business
environment to software systems. This would help to bridge the gap between business and
technology, as aligning information systems and business operation is one of the fundamental
problems in all organizations. To reach that goal, it has to be clear how business rules should be
dealt with, as a special kind of software requirements, in each phase of the software development
lifecycle. Accordingly, at least the following aspects have to be considered in this process: rules
identification, business rules specification, rules implementation and rules management. A
business rules implementation strategy assumes identifying both the place and the way of how to
implement a business rule.
3.1 Database Development Cycle
Company business rules
10

 Term — The focus on business, in that there's no reference to information systems or
concepts of information systems - focuses exclusively on how business people think.
 Fact — People involved in the business (as "customers") communicate vocabulary and
business rules to computer professionals (as "suppliers"), in the form of system
requirements specifications.
 Derivation — Database design should be influenced on the meaning that business people
and business analysts give to certain objects or terms from the business vocabulary. And
discussions regarding these aspects might be endless. If we consider a very simple e-
commerce application
 Constraint — Constraint is a generic term related to table columns which limits data
values in order to preserve database integrity. Integrity of the relational model restrictions
are structural and behavioural
Database Design
Entity Name:
Customer, Supplier, Product, Stock, Order, Payment
Normalization:
Database Normalization is a technique of organizing the data in the database. Normalization is a
systematic approach of decomposing tables to eliminate data redundancy and undesirable
characteristics like Insertion, Update and Deletion Anomalies. It is a multi-step process that puts
data into tabular form by removing duplicated data from the relation tables.
Normalization is used for mainly two purposes,
 Eliminating redundant (useless) data.
 Ensuring data dependencies make sense i.e. data is logically stored.
Normalization rule are divided into following normal form.
 First Normal Form - values cannot be repeated in this form.
 Second Normal Form – non prime number is not dependent.
 Third Normal Form – upper form of second normal form.
 BCNF – upper form of 3NF and containes 3rd Normal Form tables only.
First normal form (1NF)
As per the rule of first normal form, an attribute (column) of a table cannot hold multiple values.
It should hold only atomic values.
11

data (Cust Last Name, Cust First Name, Cust Address, Cust State, Cust Zip, Cust email, Cust
Phone, Supp Last Name, Supp First Name, Supp Address, Supp State, Supp Zip, Supp email,
Supp Phone, Prod Name, Unit Price, Expire Date, Prod Type, Description, Stock Date,
Description, Prod ID, Quantity, Reorder Level, Order Date, Description, Prod ID, Quantity,
Total Price, Description, Payment date, Amount, Due, Paymenttype, Note)
Second normal form (2NF)
A table is said to be in 2NF if both the following conditions hold:
 Table is in 1NF (First normal form)
 No non-prime attribute is dependent on the proper subset of any candidate key of table.
Customer (Cust ID, Cust Last Name, Cust First Name, Cust Address, Cust State, Cust Zip, Cust
email, Cust Phone, Supp LastName, Supp FirstName, Supp Address, Supp State, Supp Zip, Supp
email, Supp Phone)
Product (ProdID, Prod Name, Unit Price, Expire Date, Prod Type, Description, Stock Date,
Description, Prod ID, Quantity, ReorderLevel)
Order (OrderID, OrderDate, Description, ProdID, Quantity, TotalPrice, Description,
Paymentdate, Amount, Due, Paymenttype, Note)
Third Normal form (3NF)
A table design is said to be in 3NF if both the following conditions hold:
 Table must be in 2NF
 Transitive functional dependency of non-prime attribute on any super key should be
removed.
 An attribute that is not part of any candidate key is known as non-prime attribute.
In other words 3NF can be explained like this: A table is in 3NF if it is in 2NF and for each
functional dependency X-> Y at least one of the following conditions hold:
 X is a super key of table
 Y is a prime attribute of table
Customer (CustID, CustLastName, CustFirstName, CustAddress,CustState,
CustZip,Custemail,CustPhone)
Employee (EmpID, EmpLastName, EmpFirstName, EmpAddress, EmpState, EmpZip,
Empemail, EmpPhone)
12

Supplier (SuppID, SuppLastName, SuppFirstName, SuppAddress, SuppState, SuppZip,
Suppemail, SuppPhone)
Product (ProdID, ProdName, UnitPrice, ExpireDate, ProdType, Description, Stock, SuppID)
Stock (StockID, StockDate, Description, ProdID, Quantity, ReorderLevel)
Order (OrderID, OrderDate, Description, ProdID, Quantity, TotalPrice, CustID)
Payment (PaymentID, Description, Paymentdate, Amount, Due, Paymenttype, Note)
Use Case Diagram
Data dictionary
Table Name : Customer
Field Name Data Type Size Primary Key Or
Foreign key
Comments
13

CustID Number 10 Primary Key
CustLastName Varchar2 100
CustFirstName Varchar2 100
CustAddress Varchar2 150
CustState Varchar2 30
CustZip Varchar2 30
Custemail Varchar2 30
CustPhone Varchar2 30
Table Name : Customer
Field Name Data Type Size Primary Key Or
Foreign key
Comments
EmpID Number 10 Primary Key
EmpLastName Varchar2 100
EmpFirstName Varchar2 100
EmpAddress Varchar2 150
EmpState Varchar2 30
EmpZip Varchar2 30
Empemail Varchar2 30
EmpPhone Varchar2 30
Table Name : Product
Field Name Data Type Size Primary Key Or
Foreign key
Comments
ProdID Number 10 Primary Key
ProdName Varchar2 100
UnitPrice Number 12,2
ExpireDate Date
ProdType Varchar2 2
Description Varchar2 150
Stock Number 10
SuppID Number 10 Foreign key
14

Table Name : Supplier
Field Name Data Type Size Primary Key Or
Foreign key
Comments
SuppID Number 10 Primary Key
SuppLastName Varchar2 100
SuppFirstName Varchar2 100
SuppAddress Varchar2 150
SuppState Varchar2 30
SuppZip Varchar2 30
Suppemail Varchar2 30
SuppPhone Varchar2 30
Table Name : Order
Field Name Data Type Size Primary Key Or
Foreign key
Comments
OrderID Number 10 Primary Key
OrderDate Date
Description Varchar2 150
ProdID Number 10 Foreign key
Quantity Number 10
TotalPrice Number 12,2
CustID Number 10 Foreign key
Table Name : Stock
Field Name Data Type Size Primary Key Or
Foreign key
Comments
StockID Number 10 Primary Key
StockDate Date
Description Varchar2 150
ProdID Number 10 Foreign key
Quantity Number 10
ReorderLevel Number 10
15

Table Name : Payment
Field Name Data Type Size Primary Key Or
Foreign key
Comments
PaymentID Number 10 Primary Key
Description Varchar2 150
Paymentdate Date
Amount Number 10
Due Number 10
Paymentatype Varchar2 30
Note Varchar2 200
OrderID Number 10
Entity Relationship Diagram
16

3.2 Fully Functional Database
Implementation
Table creation
17

18

19

20

21

Insert Data
22

23

Constraints:
Primary Key
 CustID
 EmpID
 SuppID
 ProdID
 StockID
 OrderID
 PaymentID
Foreign Key:
 Product (SuppID)
 Stock (ProdID)
 Order (ProdID)
 Order (CustID)
Assumptions:
 Make sure to include an overview of all the requirements to start your business
 Outline all of your products, your inventory and packaging
 Understanding of the current market and your competition
 Customer service and customer acquisition
 Consider all the development requirements
 Budget planning, break-even analysis, projected profit and loss
 Products and services offered by your business
Forms
24

25

26

27

Reports
28

29

Queries
SELECT Customer.CustLastName, Customer.CustAddress, Customer.CustPhone
FROM Customer;
30

SELECT Payment.Paymentdate, Avg(Payment.Amount) AS AvgOfAmount,
Payment.Paymentatype
FROM Payment
GROUP BY Payment.Paymentdate, Payment.Paymentatype;
SELECT Product.ProdName, Product.UnitPrice, Stock.Quantity, Stock.ProdID
FROM Product INNER JOIN Stock ON Product.ProdID = Stock.ProdID
WHERE (((Stock.ProdID)=1 Or (Stock.ProdID)=2));
SELECT Stock.ProdID, Stock.StockDate, Sum(Stock.Quantity) AS SumOfQuantity
FROM Stock
GROUP BY Stock.ProdID, Stock.StockDate, Stock.ProdID;
SELECT Supplier.SuppLastName, Supplier.SuppPhone, Product.ProdName, Product.ProdType,
Stock.Quantity
FROM (Supplier INNER JOIN Product ON Supplier.SuppID = Product.SuppID) INNER JOIN
Stock ON Product.ProdID = Stock.ProdID;
3.3 Effectiveness of the Database Solution and improvement methods
 For the construction industries, Database solutions act as leading developers
which are organised specially according to the estimating environment. Databases
can be modified by inserting tables, by writing SQL queries etc. Enterprise
applications generates a particular volume of data which is always large and it is
ever growing. All the companies are undergoing some sort of pressure so that
costs can be controlled without oblation of the growth and the economy. The SQL
queries and servers helps in providing security that too is built-in, and also it
provides the availability and scale to keep the critical workloads in the business.
In a complete database management solution, whatever an organisation needs,
SQL server provides it all without any delay. It makes less the total cost of
ownership and takes the most of the value from it. It is a very rapid and creative
solution in any business that helps the organisation giving flexible deployment
options, protection of data and the overall performance from the server to the
drive.
 By combining price and the performance, companies offers a truly integrated
platform. It consists leading infrastructures of the market such as Biz talk server,
31

System centre etc. Enterprises can grow very fast with strategies and consultation.
Critical business insight handles the enterprise. Shoengalleric art gallery
integrates their systems with art intelligence departments who supply them the
goods. The employees at art gallery has a scale to check continously the feedback
of the products. Their solutions department has some very important work. They
handles the storing and protection of the information about the products as each
art piece costs high and is made incredibly. Every single art piece is so costly that
if it is being damaged, it will make a huge loss of the art gallery. So they have to
deal with the pieces very carefully and if some damage happens to any art piece,
it results in their loss of pay. The database of the Shoengalleric art gallery
includes the details of the art pieces, staff members, their suppliers and the regular
customers. They have made an online portal in which the people who are not able
to visit the shops can order online. This will be very helpful for the customers
who are in other cities or areas. They have created the database using SQL in
which every entry is entered automatically on a particular order. Their online
portal is so beneficial for the one's who are not able to come to stores. Many
people who live in the far areas or other cities who are interested in buying these
art pieces can order online. The employees at the Shoengalleric Art Gallery who
are in a specialised department has assigned the work of taking feedback from the
people. After every delivery of an art piece, they take the feedback from the
customers and if it has not delivered or been damaged while going for the
delivery, the art gallery takes it all upto itself. The gallery takes all the
responsibility and delivers a new one within a few days because there are unique
art pieces and it takes time to prepare it again. The loss goes into gallery itself but
for the satisfaction of customers, it takes it all by itself.
3.4 Supporting user and Technical Documentation
 How a product or service is operating comes under technical documentation e.g.
technical specifications, API documents etc. User documentation is a product or
service documentation which is given to the end users, the users that actually uses
that products. It is also important to check that Shoengalleric art gallery is
operating under the technical documentation, who is handling the documents, the
32

number of entries which include the number of art pieces sold and their buyers.
Because any leakage of data will lead to circumstances that will affect the
company's policies. It leads the company to affect a lot.It will also include the
contact details of the customers so that when new pieces will come, they will
inform their regular customers about the new art collection because some people
are very fond of it. Some people think art as their god. User documentations
include FAQs ( Frequently asked questions), Video tutorials, customer support
portals etc. They help the customers if any customer has some doubts about any
products, FAQs are there and are already answered. They are actually those
questions which comes in mind of every single customer. Videos are there on
their corporate website.
 As Shoengalleric Art Gallery has an online portal in which they have uploaded
the details of the gallery. They have also included videos and previous order
details which will help any new customer to know about the art gallery well.
Technical documentation is used for documentation with reference to a product. It
can include different documents which are related to the products data and
information related to the product. Users for support are also very necessary in a
workplace. In Shoengalleric art gallery, there is a separate department which is
handling the documentation of support area. The gallery has employees who keep
the data information secure and free from any privacy leak or any similar thing.
Directions have been given to them which guides them in planning and operating.
Instructions are given to them regularly in order to protect the work from any
mistakes. Operating manual is already being provided to the employees. It include
all the details how they have to manage the art pieces, old or new, how to handle
the brand new pieces. They have the art to manipulate the customers because their
focus is to sell the old art pieces first. For that, they have techniques and strategies
to manipulate the customer for buying the art piece. Every single art piece is so
costly that if it is being damaged, it will make a huge loss of the art gallery. So
they have to deal with the pieces very carefully and if some damage happens to
any art piece, it results in their loss of pay.
Defining backup strategies
33

The Shoengalleric art gallery can also adopt some back up strategies which can help them
in restoring their files if lost or misplaced due to some reason. Back up is considered as a way of
backing up the files in case of a data loss event. The data loss may be happened due to any
reason. Back up strategies act as a better defence against this. Some back up strategies they are
discussed as under :
Incremental Backup
As the full backups are so lengthy and consumes a huge amount of time, incremental
backup acts as a defence. It minimises the amount of time the system takes for completing a
backup. The data that has been changed from the last back up is the data that is backed up by
these incremental backups (Vijaykumar and Saravanakumar, 2011). The Shoengalleric art
gallery can adopt it for restoring of data but it has a disadvantage that it takes a huge amount of
time. So, it is better that Shoengalleric art gallery applies some other strategy.
Differential Backup
This way is quite similar to that of an incremental backup, it also starts with a full
backup. The difference between the both is that an incremental back up contains the data that has
modified since the last backup whereas the differential back up contains all the data from the last
full back up (Domínguez and Jaime, 2010).
Synthetic Full Backup
It is a variation of the incremental backup. The difference is that the backup server
of this backup server actually produces the full backups. As it is different from the both, it has
some advantage, that is it reduces the restoring times. The Shoengalleric Art gallery can adopt
this strategy if in case they face any data loss activity.
CONCLUSION
It should be clear from this paper that modern commercial database systems are grounded
both in academic research and in the experiences of developing industrial-strength products for
high-end customers. The task of writing and maintaining a high-performance, fully functional
relational DBMS from scratch is an enormous investment of time and energy. Many of the
lessons of relational DBMS's; however has translated over to new domains. Web services,
network-attached storage, text and e-mail repositories, notification services and network
monitors can all benefit from DBMS research and experience. Data-intensive services are at the
34

core of computing today and knowledge of database system design is a skill that is broadly
applicable, both inside and outside the halls of the main database shops. These new directions
raise a number of research problems in database management as well, and point the way to new
interactions between the database community and other areas of computing.
35

REFERENCES
Books and Journal
Chen, C. and Hu, G., 2011. Smart energy management system for optimal microgrid economic
operation. IET renewable power generation. 5(3). pp. 258-267.
Chen, Z., Cafarella, M., Chen, J., Prevo, D. and Zhuang, J., 2013. Senbazuru: a prototype
spreadsheet database management system. Proceedings of the VLDB Endowment. 6(12).
pp. 1202-1205.
Chock, M., Cardenas, A.F. and Klinger, A., 1984. Database structure and manipulation
capabilities of a picture database management system (PICDMS). IEEE Transactions on
Pattern Analysis and Machine Intelligence, (4), pp.484-492.
Domínguez, C. and Jaime, A., 2010. Database design learning: A project-based approach
organized through a course management system. Computers & Education. 55(3). pp.
1312-1320.
Färber, F. and Dees, J., 2012. The SAP HANA Database--An Architecture Overview. IEEE Data
Eng. Bull. 35(1). pp. 28-33.
Färber, F. and et.al., 2012. SAP HANA database: data management for modern business
applications. ACM Sigmod Record. 40(4). pp. 45-51.
Gelogo, Y. E. and Lee, S., 2012. Database management system as a cloud service. International
Journal of Future Generation Communication and Networking. 5(2). pp. 71-76.
Hennekens, S.M. and Schaminée, J.H., 2001. TURBOVEG, a comprehensive data base
management system for vegetation data. Journal of vegetation Science, 12(4), pp.589-
591.
Hudson, S.E. and King, R., 1989. Cactis: A self-adaptive, concurrent implementation of an
object-oriented database management system. ACM Transactions on Database Systems
(TODS), 14(3), pp.291-321.
Lee, H. and Lin, M., 2015. How I do it: a practical database management system to assist clinical
research teams with data collection, organization, and reporting. Academic
radiology. 22(4). pp. 527-533.
Lee, W. and Markley, J. L., 2012. PACSY, a relational database management system for protein
structure and chemical shift analysis. Journal of biomolecular NMR. 54(2). pp. 169-179.
Reddy, T. and et.al., 2014. The Genomes OnLine Database (GOLD) v. 5: a metadata
management system based on a four level (meta) genome project classification. Nucleic
acids research. 43(D1). pp. D1099-D1106.
Stachour, P.D. and Thuraisingham, B., 1990. Design of LDV: A multilevel secure relational
database management system. IEEE Transactions on Knowledge and Data
Engineering, 2(2), pp.190-209.
Tie, S. F. and Tan, C. W., 2013. A review of energy sources and energy management system in
electric vehicles. Renewable and Sustainable Energy Reviews. 20. pp. 82-102.
36

Vijaykumar, S. and Saravanakumar, S.G., 2011. Future robotics database management system
along with cloud tps. International Journal on Cloud Computing: Services and
Architecture. 1(3). pp. 103-114.
Voulodimos, A.S. And et.al., 2010. A complete farm management system based on animal
identification using RFID technology. Computers and Electronics in Agriculture. 70(2).
pp. 380-388.
Online
Database Management System, 2012. [Online].Available
through:<http://www.ddegjust.ac.in/studymaterial/mca-3/ms-11.pdf>.[Accessed on 3rd
July 2017].
Silberschatz, 2005. Database System Concepts. [Pdf].Available
through:<https://www.cse.iitb.ac.in/~sudarsha/db-book/slide-dir/ch1.pdf>.[Accessed on
3rd July 2017].
37