Database System Design and Development Report

The report provides an in-depth analysis of the database system design and development process, highlighting key considerations such as system and user requirements, data type validity, normalization concepts, effectiveness testing strategies, and performance monitoring. The report also emphasizes the importance of regular updates to ensure optimal system performance.

Database Design &
Development

TABLE OF CONTENTS
INTRODUCTION...........................................................................................................................1
PART 1............................................................................................................................................1
Producing user and system requirements...............................................................................1
Fully functional system for Tesco..........................................................................................2
Clear statements of system and user requirements.................................................................4
Effectiveness of design in relation to user and system requirements.....................................5
PART 2............................................................................................................................................8
Evaluating the effectiveness of database system in relation with user and system requirements:
base tables:..............................................................................................................................9
Improvement suggestions for the developed database of Tesco: ........................................11
PART 3..........................................................................................................................................12
TASK 4 .........................................................................................................................................16
Technical and user documentation for Tesco ......................................................................16
CONCLUSION .............................................................................................................................22
REFERENCES:.............................................................................................................................23

INTRODUCTION
Designing of database is considered as involvement of all the factors that are necessary to
achieve all the objectives. After a successful designing of the database, implementation phase
takes place when the designed database is being analysed on actual and real applications. It also
helps in analysing and checking the reliability of the database (Harrington, 2016). The report is
about analysing the system as well as user requirements of Tesco. Also, the report will involve a
fully functional database system for Tesco that can help the firm to replace all the manual
processing of operations and functions. Also, it includes testing of the database system. A
technical and user documentation of the database designed and implemented for Tesco has also
been included in the report.
PART 1
Producing user and system requirements
A variety of operations and processes in Tesco are being done manually, because of
which the management has to face some issues while analysing their market position and
competitive advantage. It is because in case of manual processing, there are chances of data
getting lost. So, Tesco has decided to make involvement of a proper and developed database so
that they may not have to face any issue regarding analysing their market position. As they are
implementing a database, sot here must be some user as well as system requirements so that the
firm can be easily able to cope with the different challenges of the market place. User
requirements here can be considered as the fact that Tesco needs a database that should be
friendly and reliable enough so that employees can easily able to access and use the database. It
should be user friendly and less complicated so that the employees and management of Tesco
may not have to face any further issue with the database. System requirements can be classified
as the fact that the systems in which the database has to be implemented should have all
software's up to date so that the database cannot throw any extra load on the system (Elmasri
and Navathe, 2016). Also, along with the software, hardware installed also should be up to date
and have an efficient amount of RAM so that while operating different processes and operations,
Tesco may not have to face any issue or complexity such as hanging of system etc.
1

Fully functional system for Tesco
The relational database system for Tesco is designed in a way that it not only facilitates
the easy data handling for Tesco but also makes it easy for the customers to interact with
organisation via easy user interface. The designed database system consist of different sections
such as customers, sales related data, product description and suppliers details. For sustaining the
effectiveness of the database system the system is provided with features such as data
normalisation and data validation. It is one of the most common practices that unknowingly users
can put invalid data in certain fields of the database tables. For instance in the contact number
attribute user can feed invalid number or alphabets. This can create error in output or even can
mislead the administrator leading huge losses. To avoid such instances data validation is used.
Data validation is a defined set of rules ensures the validity of the data stored in the databases
system. They enhance the consistency and functionality of the system (Coronel and Morris,
2016).
2

Data validation techniques:
For validating data designers defines the input data requirements so that any error due to
invalid data can be avoided. Data validation can be achieved by various techniques.
 The most common technique is the restricted data type. Designers can fix the data type
which must be followed during data processing. For instance if a rule is fixed during table
design that name attribute must be sequence of characters it cannot be numerical values
then user will not be able to mislead system by feeding inappropriate values to the
column. In the designed database system along with data type restriction property of requirement
is also used. Due to this property if users of Tesco will try to leave any attribute empty
then database system will generate an error message. This technique is useful in avoiding
null values. For security reasons if it is essential for organisation to fill the name and
contact details properly then users will not be able to enter null values in the columns.
Along with data validation designed database system is also able to decompose tables. This
approach eliminates the redundancy. Thus, with normalisation techniques only useful and
sensible data is stored. It will be helpful for Tesco as it will make system fast as well as more
efficient. Without normalisation database will consume additional memory and system will
become slow as well as full of repeated useless entries (Bhogal and Choksi, 2015). Designed
tables follows following normalisation rules.
First normalised form (1NF): According to this rule table attribute cannot hold multiple values.
For example for a single employee code user cannot feed two different names. It can feed only
one name for one id.
Second normalised form (2NF): The developed system is in 1NF form and it does not have any
kind of partial dependency thus it is also said to have 2NF.
Third normalised form (3NF): The designed tables are 2NF are does not follow transitive
dependency thus they follow the third normalisation rule.
3

Clear statements of system and user requirements
User and system requirements of Tesco for an efficient designing and implementation of
database are discussed as under :
User requirements
User requirements at the time of designing and implementation of database are as
following :
 The database should be reliable enough so that it can be quite easy for Tesco to
understand its processing.
 The database should not throw any load to the system.
 The database should be compatible with various operating systems, which means that
there should be no sort of restriction on using the database on any specific operating
system (Mukherjee and et.al., 2016). The database designed should be suitable enough to
be run on any operating system. It means it should be compatible and reliable enough.
4

System requirements
System requirements of the database that has been designed and to be implemented in
Tesco are as following :
 Software of the system should be up to date so that the database may not throw any sort
of load to the system.
 Also, appropriate hardware's must be installed with a huge capacity because this helps in
excluding any issue of load on system. Therefore, it helps in preventing the system to
hang.
Effectiveness of design in relation to user and system requirements
Tesco has requires database system for making data handling process easy. This system
will allow the organisation to establish a better management system for its human resources.
With increasing growth the amount data to be handled is also increases. The huge amount of data
cannot be handled manually. Database system will allow users to perform multitasking with a
single centralised system. All management related functional records such as data related to
customers, employees, products and suppliers can be maintained by a single system. Tesco can
also provide security to its data from vulnerable cyber attacks. Database system is capable of
providing features like speed, accuracy, reliability and enhanced functionality. The redundancy
and validity of data are major concern for user during data handling (Pejathaya, Talluri and
Bhide, 2017).
Database system provides the effective solution to Tesco by addressing these basic
aspects. Database system is also capable to store the data safely for long time along with security
features to protect unauthorised access. With this system organisation will be able to maintain
long term relation with their customers and can analyse its own performance in different years or
with comparison to its competitors. Another significant advantage of database system is that it
allows organisation to access the records and data from any location. Thus authorised multiple
access increases the flexibility of the work and makes the operational activities very convenient.
In relation to the system requirements also database is designed as per mark. It meets all
functional and operational requirements which are necessary for Tesco to achieve its
organisational goals. The effectiveness of database in regards with system requirements can be
assessed with the help of requirement tracing. The requirement traceability creates and
5

understands the bidirectional path among goals of Tesco, its operational requirements and
performance. Requirements of Tesco are traced before as well as post development of the
database. For instance before development of database it is necessary to analyse that which type
of data will be handle by the database, its storage capacity, its features, possible threats and
improvement strategies for future advancement of technologies.
After the development and implementation of database also requirements of Tesco are
analysed. For instance as most of the organisations are shifting towards digital transaction. Thus,
in future if Tesco also want to upgrade its database system then their must be possibility for this.
If database is implemented by the organisation then users must have access to integrate the
system with advanced devices and technologies. Database system must be capable of integration
with other devices. The user interface of the database must be easy and as per the requirement of
users. It is designed in a way that it facilitate the management process. It is also essential that
requirements of organisation are documented and could be tested and implemented (Mukherjee
and et.al., 2016). The quality and appearance of database is also a matter of concern. It must be
suitable to the users.
The characteristics such as background colour, font size and interaction with outside
environment are also considered as an essential criterion for effectiveness. If database is not user
friendly then it may not prove much effective in its operational activities also because user may
not be able to utilize all its features. The developed database system must also be able to support
variety of operating systems instead of relying on any single operating system. The database
must handle the data effectively so that excessive load of data handling may not affect the
routine activities of the organisation.
6

Validation user interface form:
7

PART 2
Evaluating the effectiveness of database system in relation with user and system requirements:
There are different methodologies for evaluating the effectiveness of designed database
system. Tesco must have proper documentation of the purpose and requirement of its database.
This documentation will not only make designing process easy and accurate but will also
evaluate the effectiveness of system correctly. Organisation must have clarity about what type of
customer details is required by the organisation. In accordance to the requirement database is
designed. The effectiveness is measured by testing data and plans which are similar to real time
so that efficiency and accuracy can be evaluated. The database transactional activities like
consistency, isolation, atomicity and durability are essential for evaluation of effectiveness.
The factors like hardware, software, installation accessories and capabilities of
virtualisation are also considered (Jukic, Vrbsky and Nestorov, 2016). The developed system
must be integrated with the networking components of Tesco. For evaluation of transaction
process of database transaction processing performance council (TPC) benchmarks can serve as
effective tools. These benchmarks make repeated queries and data modifications in concurrent
pattern so that all parameters of system can be monitored and performance can be evaluated. The
database must be in support with cloud storage. Tesco is multinational organisation thus cloud
storage is one of the necessity for the organisation.
The effectiveness of database system can be evaluated by monitoring the status of in-
memory management of data. If the designed database system process the data in memory then,
performance can meet the speed standards. The effective database system also keeps track and
monitoring of all activities regularly. This approach will play significant role in detecting the
vulnerable threats. The database must be supporting to back up the records and tables.
Organisation must regularly back up its data.
8

Database tables:
9

Queries:
10

In the designed database system it is possible for the users to categorise the various
records. The records of customers, suppliers and other stakeholders can be accessed any time.
Each record consist of basic details like id, name and certain specific details as per the
requirement. For instance it is possible for the user to access the complete details of any supplier
by using its id only. User can modify, update, insert or delete the data as per the requirement.
The data normalisation allows user to avoid the unnecessary iterations of the data. For evaluating
the effectiveness of the database system testing tools can be used. Under evaluation of
effectiveness various parameters such as data validity, integrity are tested. Tesco also ensure that
database system is accessible and supports all types of platforms like mobile devices, desktop
versions and web application as well. For organising the details and feedback of customers user
may require the web interaction along with database (Setiaji and Wibowo, 2016). Similarly, as
most of the target audience of Tesco uses mobile devices to interact with organisation the
database must also support the mobile technology.
Improvement suggestions for the developed database of Tesco:
Tesco can improve the effectiveness of the database system by following suggestions:
 For future development of database Tesco must ensure that sufficient memory, disk space
and CPU cores are available. Thus, database administrator of Tesco must always monitor
11

the memory statistics and CPU ready time along with time delay in performing
operational activities.
 Monitoring strategies for regulating only authorised access is essential. Organisation
must monitor all activity log details so that any kind of security breach can be noticed on
time and losses can be prevented.
 Instead of storing customer's information across different systems Tesco can use a single
view of customer's details. This approach will prevent the fragmentation and duplicate
information. With the implementation of single customer view organisation can clean,
merge and match all customer records into a single record (Jukic, Vrbsky and Nestorov,
2016).
 Tesco must make proper and regular use of quality standards. Organisation must ensure
that these standards are followed. It will be also beneficial for the organisation to
continuously review the documentation and process of designed database (Elmasri and
Navathe, 2016). This approach will help organisation to always maintain an eye on
performance and requirements. It will make organisation to quickly identify the
marketing needs and to modify the data handling process according to the advancements.
 Appropriate selection of data types and procedures for database can increase its
functionality and performance. The accurate data storage in fields can increase the data
integrity.
PART 3
Effectiveness of testing: The effectiveness of the database is tested at each and every layers of
database. During database testing all functionalities of database are tested to ensure that designed
database of Tesco is providing desired results in terms of data integrity, performance speed,
analysis of triggering and procedures related to functioning. Data base testing mainly includes
following techniques:
Black box testing:
This functional testing test the functionality of incoming and outgoing data of designed
database. It ensures that functionality is not compromised in design. It does not give detailed
description of the programs which are required to be tested. This testing is performed at the
initial stages of database development and is less costly. The most common black box testing
techniques are equivalence partitioning, boundary value analysis and error guessing techniques.
12

In equivalence partitioning input values of system are divided into groups and output is tested. In
boundary value analysis database is tested by feeding extreme values to the database so that data
validity can be tested (Bhogal and Choksi, 2015). On the other hand in error guess technique
error prone segments are detected at priority and are tested.
White box testing:
In contrary to the black box testing, white box testing requires the detailed knowledge of
internal structure and code of the database. It tests the syntax and can be accomplished with
programming knowledge only. This database testing utilizes flowcharts and data-flow diagrams.
This type of testing prohibits the communication between different modules. White box testing
uses triggers and supporting logical concepts for testing. It validates database integrity and
schema.
Non functional testing: In these testing procedures the various parameter such as load, stress,
record fetching time, response time are tested. In this testing various transactions are performed
to test the response time of the designed database. It also analyses the system failure by creating
situations in which system gets failed. This testing approach helps Tesco to determine the risk
factors in prior to actual system failure.
13

Test the customer information:
14

Test log and test plan:
Before executing the database testing test plan gives a systematic outline for testing the
database. It will highlight the aims, resources, schedule, deliverable and estimation related to
database testing.
Purpose and scope: The data base testing is required to test the validity and effectiveness of the
database system designed for the Tesco. It must meet speed, accuracy, huge data flow
management which is regular practice for Tesco.
Test approach and environment: The functionality tests will ensure that data modifications
operations such as insertion, deletion are performed accurately. It also ensures that data
integrity, functionality and reliability are maintained throughout the operation. The testing also
aims at achieving data validity and to eliminate the data redundancy. The appropriate testing
strategies such as white box testing, black box and functionality testing can be chosen for
achieving the database testing.
Test schedule, activities and risk assessment: The testing is accomplished in order to meet the
requirements of Tesco. To confirm the accuracy the test is accomplished by using different type
of test data which can generate test results under various possible real time situations. It also
15

gives analysis of possible risks which may emerge in case of system failure. The results are
documented so that they required changes can be implemented in order to meet the actual
specifications of the system and organisation.
Test data choice: For critically evaluating the effectiveness of the designed database system of
Tesco data which can be used for testing must be chosen wisely. The suitable test data quantity
can be limited by factors such as cost, quality and time. The designed database is tested with
both positive and negative test data. Positive test data is used so that database can generated
expected results while negative test data is used to test the response of database in unfavourable
conditions like system failure or invalid data (Setiaji and Wibowo, 2016). In testing following
test data can be used: Invalid and boundary condition test data: It can be used to test the accuracy and
boundary conditions of the database system. Correct and Incorrect test data: These sets of test data test that database responds
according to the requirement and it confirms its behaviour for inappropriate data inputs. Huge and lengthy data: This type of test data evaluates the load testing, fetching time
during great traffic and system failures.
 Blank and corrupt data: This type of test data evaluates the behaviour of database when
certain attributes are feed with null values or corrupt data which may consist of bugs.
The implementation of different test data types in testing provides the best analysis of
performance of designed database system.
TASK 4
Technical and user documentation for Tesco
Technical documentation: The designed database system of Tesco has following technical
documentation.
Database overview- As Tesco operates in many countries and produces variety of products so
it requires a huge and large database for storing data related to customers, products, markets,
etc. so that strategies can be developed accordingly.
16

System architecture- It refers to the model of database that is required in Tesco. The database
model of Tesco is relational database (Piec, Pallez and Pasquali, 2016). In this data is stored
in tabular format which makes it easy to access it. This database is designed in several phases.
The first one start with designing of logical database in which tables are created. It reflects the
relationship between products. In second stage a mediator is determined in that will be
responsible for performing all operations and request of user. Also, in order to handle and
manage the user request, server will be installed. It processes the user request to provide useful
information or data. In this anther element is clients. They have right to perform operations like
modify, insert or delete in database. Relational database also consist a back up process that
works is case of system failure.
Quality assurance procedures for database: In this various procedures are developed to
improve the performance of database. It is the responsibility of designers to ensure this. For this
they set guidelines that define the standards of quality. The designer at tesco develop new data
set to measure quality. In this different profiling tools are used. They analyse relationship
between table and content. Tesco is growing rapidly so an effective database is required to
manage data. Besides this, in database semantic management system is also included.
Developers should take this into consideration that data is checked regularly to ensure its
validity and reliability (Mohankumar and Kumar, 2016). This is done by using sets of rules that
are designed.
User documentation:
System information- An effective and systematic database system is required in tesco to
evaluate data and information of customers, markets, products, etc. this will help them to
develop strategies and evaluate their performance. With this they can manage and control their
operations (Yu and et.al 2016). The requirements of system will be internet for both user and
tesco. In company internet browser can be installed to run system. Along with this, the
configuration of system is described below :-
Login window: After installing, login window will appear, in this the person has to enter
username, password and other details for verification.
17

TABS: in database there will be different tabs that will contain information and data. These are
as follows :-
Employees: In this tab all data and information of all employees will be displayed. By using
this employees can access the database. In this manager will monitor the activities in order to
ensure security of database.
Customers- This section can be used by tesco in which all information related to customers will
be stored. The records will contain information like name, address, products purchased, contact
no, etc.
Feedback and suggestion: It is very important for tesco to solve customer problems and issues
properly. For this in system a separate section will be there (El-Halees and Kehail, 2017). It
will consist of a systematic procedure through which feedback are provided. Also, it will store
those feedbacks so that it can be used in the future. With this tesco can enhance customer
satisfaction and retain them.
Sales review customer wise: this section will be used by tesco to analyse the market position in
different countries. This will be done by comparing sales. Also, accordingly sales target can be
set by reviewing the entire market condition.
Sales review product wise: It is similar to sales review customer wise but in this section sales is
reviewed according to the product categories (Zhang, Wang and HU, 2017 ). With this tesco
can measure which product sales is maximum and in which market. So that strategies can be
developed to increase sales of other goods. It will also have a feature of maintaining records of
product wise sales.
Performance evaluation- this section will provide a graphical representation of sales in
different years. This will help tesco to evaluate their performance that whether they have
achieved set goals or not. Also, tesco can evaluate their marketing strategies and take actions to
improve it.
Settings: It is the main section of system that can be only accessed by database manager. In this
he or she can do various changes in the settings of database. It also contains privacy
18

Assessment of future improvements: there are several measures that can be taken into
consideration by tesco. This will help them to maintain efficiency of database system. Theses are
as follows :-
 Database manager can timely update software of system so that its efficiency can be
maintained. By this speed of database will be improved. Also, it will help in effective
working.
 In database security is a major cause of concern. Therefore, manager must monitor all the
activities of system (Yu and et.al 2016). Also, access must be provided to only
employees of tesco or person who are having specific. For maintaining security anti virus
and firewall must be installed in systems. This will help in preventing the virus attacks.
 Moreover, tesco can develop an IT team that will monitor threats and crimes related to
cyber security. Also, this team will take necessary action to prevent data theft and
managing database. TASK 4◦ Technical and user documentation for tesco
◦ Technical documentation: The designed database system of Tesco has following
technical documentation.
 Database overview- As Tesco operates in many countries and produces variety of
products so it requires a huge and large database for storing data related to customers,
products, markets, etc. so that strategies can be developed accordingly. System architecture- It refers to the model of database that is required in Tesco. The
database model of Tesco is relational database (Piec, Pallez and Pasquali, 2016). In
this data is stored in tabular format which makes it easy to access it. This database is
designed in several phases. The first one start with designing of logical database in
which tables are created. It reflects the relationship between products. In second stage a
mediator is determined in that will be responsible for performing all operations and
request of user. Also, in order to handle and manage the user request, server will be
installed. It processes the user request to provide useful information or data. In this
anther element is clients. They have right to perform operations like modify, insert or
delete in database. Relational database also consist a back up process that works is case
19

of system failure.
 Quality assurance procedures for database: In this various procedures are developed to
improve the performance of database. It is the responsibility of designers to ensure this.
For this they set guidelines that define the standards of quality. The designer at tesco
develop new data set to measure quality. In this different profiling tools are used. They
analyse relationship between table and content. Tesco is growing rapidly so an effective
database is required to manage data. Besides this, in database semantic management
system is also included. Developers should take this into consideration that data is
checked regularly to ensure its validity and reliability (Mohankumar and Kumar, 2016).
This is done by using sets of rules that are designed.
User documentation: System information- An effective and systematic database system is required in tesco
to evaluate data and information of customers, markets, products, etc. this will help
them to develop strategies and evaluate their performance. With this they can manage
and control their operations (Yu and et.al 2016). The requirements of system will be
internet for both user and tesco. In company internet browser can be installed to run
system. Along with this, the configuration of system is described below :- Login window: After installing, login window will appear, in this the person has to enter
username, password and other details for verification. TABS: in database there will be different tabs that will contain information and data.
These are as follows :- Employees: In this tab all data and information of all employees will be displayed. By
using these employees can access the database. In this manager will monitor the
activities in order to ensure security of database. Customers- This section can be used by tesco in which all information related to
customers will be stored. The records will contain information like name, address,
products purchased, contact no, etc.
20

 Feedback and suggestion: It is very important for tesco to solve customer problems and
issues properly. For this in system a separate section will be there (El-Halees and
Kehail, 2017). It will consist of a systematic procedure through which feedback are
provided. Also, it will store those feedbacks so that it can be used in the future. With this
tesco can enhance customer satisfaction and retain them.
 Sales review customer wise: this section will be used by tesco to analyse the market
position in different countries. This will be done by comparing sales. Also, accordingly
sales target can be set by reviewing the entire market condition.
 Sales review product wise: It is similar to sales review customer wise but in this section
sales is reviewed according to the product categories (Zhang, Wang and HU, 2017 ).
With this tesco can measure which product sales is maximum and in which market. So
that strategies can be developed to increase sales of other goods. It will also have a
feature of maintaining records of product wise sales. Performance evaluation- this section will provide a graphical representation of sales in
different years. This will help tesco to evaluate their performance that whether they have
achieved set goals or not. Also, tesco can evaluate their marketing strategies and take
actions to improve it.
 Settings: It is the main section of system that can be only accessed by database manager.
In this he or she can do various changes in the settings of database. It also contains
privacy
Assessment of future improvements: there are several measures that can be taken into
consideration by tesco. This will help them to maintain efficiency of database system. Theses are
as follows :-
 Database manager can timely update software of system so that its efficiency can be
maintained. By this speed of database will be improved. Also, it will help in effective
working.
21

 In database security is a major cause of concern. Therefore, manager must monitor all the
activities of system (Yu and et.al 2016). Also, access must be provided to only
employees of tesco or person who are having specific. For maintaining security anti virus
and firewall must be installed in systems. This will help in preventing the virus attacks.
 Moreover, tesco can develop IT teams that will monitor threats and crimes related to
cyber security. Also, this team will take necessary action to prevent data theft and
managing database.
 Tesco must back up all the data so that in case of system failure, data can be retrieved.
Also, data can be regularly back up so there is not loss to tesco.
 Tesco can develop strategies on how to cope up with advancements with technology. It
will help in increasing their performance for long term. Along with this, it will lead to
minimise the risk of cyber threats.
 Tesco must back up all the data so that in case of system failure, data can be retrieved.
Also, data can be regularly back up so there is not loss to tesco.
 Tesco can develop strategies on how to cope up with advancements with technology. It
will help in increasing their performance for long term. Along with this, it will lead to
minimise the risk of cyber threats.
CONCLUSION
From the report it can be concluded that database design and development is an integral
part of the organisational success. Data base is a mandatory tool for managing various
operational activities of the organisation. The report has described the system and user
requirement of Tesco for development of its database system. It has also explained the concepts
like validity of data type and normalisation concept in regards with the implemented data base
system. The report has focused on effectiveness of database system and its testing strategies. It
can be also concluded from the report that for achieving the benefits of database system
organisation must monitor its performance and it should be updated regularly. Thus, it can be
conclude that database systems can make it easy for the organisation to achieve targets by
enhancing accuracy, speed, functionality and reliability.
22

REFERENCES:
Books and journals :
Bhogal, J. and Choksi, I., 2015, March. Handling big data using NoSQL. In Advanced
Information Networking and Applications Workshops (WAINA), 2015 IEEE 29th
International Conference on (pp. 393-398). IEEE.
Coronel, C. and Morris, S., 2016. Database systems: design, implementation, & management.
Cengage Learning.
El-Halees, A.M. and Kehail, E.O., 2017. Integrate Database Design Techniques with Agile
Applications.
Elmasri, R. and Navathe, S., 2016. Fundamentals of database systems. London: Pearson.
Harrington, J.L., 2016. Relational database design and implementation. Morgan Kaufmann.
Jukic, N., Vrbsky, S. and Nestorov, S., 2016. Database systems: Introduction to databases and
data warehouses. Prospect Press.
Mohankumar, M. and Kumar, M.A., 2016. Green Database Design Model in Software
Development Life Cycle Phase. Indian Journal of Science and Technology.9(30).
Mukherjee, N., Ganesh, A., and et.al., 2016. Core in-memory space and object management
architecture in a traditional RDBMS supporting DW and OLTP applications. U.S. Patent
9,430,390.
Pejathaya, K., Talluri, G. and Bhide, A.S., Tata Consultancy Services Ltd, 2017. Foreign key
identification in database management systems. U.S. Patent 9,552,379.
Piec, J., Pallez, M. and Pasquali, M., 2016. The Luxembourg database of trichothecene type B F.
graminearum and F. culmorum producers. Bioinformation. 12(1). p.1.
Setiaji, B. and Wibowo, F.W., 2016. Chatbot using knowledge in database. In 7th International
Conference on Intelligent Systems, Modelling and Simulation.
Yu, J. and et.al 2016. PMDBase: a database for studying microsatellite DNA and marker
development in plants. Nucleic acids research. 45(D1). pp.D1046-D1053.
Zhang, X.D., Wang, D.H. and HU, J.H., 2017. Design and development of information
management system based on network database for hyperbaric oxygen therapy. Chinese
Medical Equipment Journal. 38(9). pp.39-43.
23