Database Testing: Anomaly Checks, BI Reports, and Real-Life Scenarios

Verified

Added on  2023/04/24

|4
|638
|448
Report
AI Summary
This report details the testing of a database, focusing on anomaly detection, data integrity, and real-life scenario implementation. The database was tested for multivalued attributes, partial and transitive dependencies, and the proper handling of date values. The report also covers the generation of Business Intelligence (BI) reports using Power BI, specifically focusing on customer purchase analysis and monthly sales trends. While the database effectively stores relevant data and supports BI reporting, some real-life scenarios, such as automated ownership updates upon purchase, were identified as potential areas for improvement through the use of check constraints and triggers. The report concludes with a bibliography of relevant sources, highlighting the importance of database design and implementation for effective management information systems.
Document Page
Running head: DATABASE
Database
Name of the Student
Name of the University
Author’s note:
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
1DATABASE
The database has been tested based on the various parameters that has been discussed in
the test plan. The first thing that has been tested is the database anomalies. The anomalies makes
the database more complex to manage. Each table of the database has been tested to see whether
there is any multivalued attribute, partial dependency or transitive dependency. Multiple values
for a foreign key has been added to the tables to test the database. Everything went fine with the
normalization. The purchase of many cars by same buyer has been checked by entering multiple
data rows in the sales invoice table for each customer. The same has been tested to see whether
same seller can sell many cars. This test also went well. The database stores only the relevant
data. Taken as an example, the database accepts only date value for attributes that refers to buy
or selling date. The ownership dates also accept only date value. The primary keys and their
foreign keys have the same data type and data range.
Another things that has been tested in the database is that whether it supports the real life
situations. Taken as an example, the ownership detail has two date related attributes such as
from-date to to-date. As per the real life scenario, the to-date must be bigger than the from-date.
This situation has not been implemented in the database. However, this could have been
implemented using the check constraint which would have checked whether the from-date is
shorter than to-date. Another real-life scenario is, ownership of the car changes when a purchase
is made. This function is left for manually entering by the end-user such as receptionist.
However, this could be implemented using trigger function.
Purpose of database is to provide in-depth date about business operations. These
information are used for assisting the management to make decisions. The BI or Business
Intelligence reports allow the management to fetch data in a more convincing way by showing
the data in graph or pivot table. For this reason, the database has been tested to see whether it can
Document Page
2DATABASE
create BI reports. The BI reports has been generated using the Power BI which is a Microsoft
open source product. Two fundamental BI report has been created using the Power BI. These
reports are purchase made by a customer and sales for each moth. The reports shows exact
amount of purchase made by each customer using bar chart. This allows the management to have
proper idea of most loyal and spending customers. The next report shows the sales for each
month using pi-chart. The pi-chart is great for identifying the most valued parts, in this case
months.
No scripts has been created for automating the DML functions. As said before, the DML
function could be automated for changing the ownership when a purchase is made. This would
have been achieved by defining a trigger that take sell date as input and insert it as from date to
the ownership table.
Document Page
3DATABASE
Bibliography:
Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education
India.
Zheng, Y., & Bai, Q. (2018, February). Design and Implementation of Database Centralized
Access Control and Audit System. In 2018 International Conference on Computer
Science, Electronics and Communication Engineering (CSECE 2018). Atlantis Press.
chevron_up_icon
1 out of 4
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]