Table of Contents

Introduction......................................................................................................................................... 2
SQL Code Names.................................................................................................................................... 3
SQL Query and View Query......................................................................................................................... 4
Security and Privacy Policies............................................................................................................ 7
Query View...................................................................................................................................... 8
Poster........................................................................................................................................... 16
Conclusion..................................................................................................................................... 17
References.................................................................................................................................... 18
Introduction

The automation of operations at Global Waste Management to enhance different categories of waste, resources, and customer services as a huge
reform agenda to instigate efficiency and scale economies. As the organisation extended it reach across Australia, a centralized folder and paper
based system made way for more systematic and transperent approach with the need for a centralised comprehensive database system with the
capability to reduce errors and improve decision making. This project includes the development and deployment of an enhanced structured
storage solution, which can enable the significant activities like customer and order, personnel, vehicle, and locality-based dump management.
About the structure of Databases, the company must interconnect Customers, Orders, Vehicles, and Personnel with help of schemas and
structures, so all flows would align with company’s operation. Complex SQL queries were implemented to obtain effective data access to
generate customer order patterns, vehicle usage, and business intelligence reports to support organizational resource management and decision-
making. In addition, security and privacy were key drivers, with features using Role-Based Access Control (RBAC), data encryption, data
protection in accordance with the Privacy Act 1988 and other legislation. Policies were supplemented by audit trail to track data base activities,
accredited access for administrative users, and data backup methods to enhance availability and reliability respectively. For data protection,
privacy, data minimization and Retention policies whereby only requisite information is collected and retained as well as implementation of
policies on records deletion by the system. This technique minimizes the risks that are common like SQL injection, and the application uses
effects like parameterized queries and attained statements to counter such actions. Besides identifying useful relationships between tables,
several issues were encountered during the project, such as guaranteeing the data integrity, testing query performance for accuracy for highly
complex queries with high volume of data, and addressing future growth of the application. Some decisions were made for easier development :
clean data in the beginning of the project, consistent data, users will not perform unauthorized actions, and structuring of the infrastructure that
would support major database loads. As for the system’s design decisions, they followed the principles of flexibility so that the system could one
day accommodate new necessities such as the inclusion of smart technologies or a possibility to monitor performance in the cloud environment .
This means this automated database solution provides not only for the current operational issues, but it also provides a future-proof solution for
Global Waste Management to finally embark on its journey of proper digitalization for more sustainable growth and development of sustainable
waste management solutions. This approach by deliberate and systematic planning and development suggests that this project is indeed a worthy
demonstration of how database automation can transform conventional ways of maintaining tradition, and applying a workable, reliable, and
adaptive model in support of an organization’s needs of today and tomorrow. In synthesizing technical development with organizational
purposes, the project demonstrates a sound understanding of database administration, business processes and management, security and privacy
in contemporary information systems that would serve as a theoretical foundation for Global Waste Management’s effective functioning in the
future.
SQL Code Names

1. Create Database for Waste Management System

2. Create Table for Customer Entity
3. Create Table for Orders Entity
4. Create Table for Personnel Entity
5. Create Table for Vehicle Entity
6. Insert Data into Customer Table
7. Insert Data into Orders Table
8. Join Tables for Customer Orders
9. Data Analysis Query - Customer Order Trends
10.Data Analysis Query - Vehicle Utilization
11.Query for Locality-Based Dump Management
12.Grant Permissions for User Access
13.Revoke Permissions for Security
14.Complex Dashboard Query for Business Intelligence
15.Final Query for Overall Analysis Across Entities
SQL Query and View Query
The query has been created in MySQL Workbench. Here, the SQLCode starts with:

1. Create Database
CREATE DATABASE WasteManagement;

2. Create Customer Table

CREATE TABLE Customer (
CustomerID INT PRIMARY KEY,
CustomerName VARCHAR(100),
Address VARCHAR(255),
PhoneNumber VARCHAR(15)
);

3. Create Orders Table

CREATE TABLE Orders (

OrderID INT PRIMARY KEY,
CustomerID INT,
OrderDate DATE,
Category VARCHAR(50),
Quantity INT,
VehicleID INT,
FOREIGN KEY (CustomerID) REFERENCES Customer(CustomerID),
FOREIGN KEY (VehicleID) REFERENCES Vehicle(VehicleID)
);

4. Create Personnel Table

CREATE TABLE Personnel (

PersonnelID INT PRIMARY KEY,
Name VARCHAR(100),
Role VARCHAR(50),
PhoneNumber VARCHAR(15),
AssignedVehicleID INT,
FOREIGN KEY (AssignedVehicleID) REFERENCES Vehicle(VehicleID)
);

5. Create Vehicle Table

CREATE TABLE Vehicle (

 VehicleID INT PRIMARY KEY,
VehicleType VARCHAR(50),
Capacity INT,
AssignedDriverID INT,
FOREIGN KEY (AssignedDriverID) REFERENCES Personnel(PersonnelID)
);

6. Insert Data into Customer Table

INSERT INTO Customer (CustomerID, CustomerName, Address, PhoneNumber)

VALUES
(1, 'John Doe', '123 Main St', '123-456-7890'),
(2, 'Jane Smith', '456 Maple Rd', '987-654-3210');

7. Insert Data into Orders Table

Copy code

INSERT INTO Orders (OrderID, CustomerID, OrderDate, Category, Quantity, VehicleID)

VALUES

(1, 1, '2024-12-01', 'Mixed Rubbish', 5, 101),

(2, 2, '2024-12-02', 'Concrete', 10, 102);

8. Join Tables for Customer Orders

SELECT
Customer.CustomerName,
Orders.OrderDate,
Orders.Category,
Orders.Quantity
FROM
Customer
JOIN
Orders ON Customer.CustomerID = Orders.CustomerID;

9. Data Analysis Query - Customer Order Trends

SELECT
CustomerName,
COUNT(OrderID) AS TotalOrders
FROM
Orders
JOIN
Customer ON Orders.CustomerID = Customer.CustomerID
GROUP BY
CustomerName
HAVING
COUNT(OrderID) > 1;

10. Data Analysis Query - Vehicle Utilization

SELECT
VehicleID,
COUNT(OrderID) AS TotalTrips
FROM
Orders
GROUP BY
VehicleID
ORDER BY
TotalTrips DESC;

11. Query for Locality-based Dump Management

SELECT
DumpID, Location, Capacity
FROM
Dump
WHERE
Locality = 'XYZ';

12. Grant Permissions for User Access

GRANT SELECT, INSERT, UPDATE ON WasteManagement.* TO 'user'@'localhost' IDENTIFIED BY

'password';

13. Revoke Permissions for Security

REVOKE INSERT ON WasteManagement.* FROM 'user'@'localhost';

14. Complex Dashboard Query for Business Intelligence

SELECT
Orders.Category,
SUM(Orders.Quantity) AS TotalQuantity,
COUNT(DISTINCT CustomerID) AS UniqueCustomers
FROM
Orders
GROUP BY
Orders.Category
ORDER BY
TotalQuantity DESC;

15. Final Query for Overall Analysis

SELECT
Customer.CustomerName,
Orders.OrderDate,
Orders.Category,
Vehicle.VehicleType,
Personnel.Name AS DriverName
FROM
Orders
JOIN
Customer ON Orders.CustomerID = Customer.CustomerID
JOIN
Vehicle ON Orders.VehicleID = Vehicle.VehicleID
JOIN
Personnel ON Vehicle.AssignedDriverID = Personnel.PersonnelID
ORDER BY
Orders.OrderDate;
Security and Privacy Policies

The automated waste management system for Global Waste Management focuses on security and privacy to protect personal identifiable
information and stability. The security policies emphasize on the principle of ‘need to access,’ meaning that admin, personnel and customers are
allowed to access resources according to their responsibilities in the firm. For instance, administrators have all the accesses while drivers,
specifically customers only have access to the functions meant for their roles.(Connolly & Begg, 2019)

To safeguard the data in transit and at storage, the system uses data encryption. Customer information and login credentials are also stored safely
with an encrypted algorithm, and all form of communication is protected by SSL/TLS. Also, user authentication is improved with stronger
passwords and multiple factors gaining access into the system.

This means that daily, weekly and monthly database backup is done to ensure that in case of any system failure or a cyber-progression, no data is
lost. These backups are encrypted and then the backed up data is kept securely for easy recovery in case of disaster recovery. Database auditing
is the process of capturing information about events that affect a database and audit logs record the user activities such as login the activities,
changes on data and executing queries among others which facilitates quick identification of any alterations.(Elmasri & Navathe, 2020).

Privacy policies are aligned with legal requirements, for example, the Privacy Act of Australia which guarantees that customer data is obtained,
handled, and stored in a lawful manner. Data minimization principles are implemented, gather solely the necessary information, and regularly
erase documents to meet them.

By using parameterized queries as well as prepared statements, the system is armed against such threats as SQL injection. A schedule update of
security authorities and vulnerability reviews are conducted in order to maintain the database system secure from these contemporary threats.
(Australian Government, 1988)

Altogether these policies ensure the confidentiality, integrity and availability of data as well as creating confidence among the stakeholders due
to protection of the privacy of individuals.
Query View
Waste Management System
Customer Entity

Orders Entity
Personnel Entity

Vehicle Entity
Customer Table

Orders Table
Customer Orders

Customer Order Trends

Vehicle Utilization
Locality-Based Dump Management
User Access

Revoke Permissions for Security

Complex Dashboard Query for Business Intelligence

Final
Poster
Conclusion
When designing the Global Waste Management system in the form of an automated database, a number of
decisions, difficulties and presumptions could be determined.

Key Design Decisions: The system requirements initially considered focused only on the key processes of the waste
management solution to provide efficient customer management, orders tracking, personnel management, and
vehicle management. To have a smooth integration of data, the database uses relationship to associated tables like
customer’s table, orders table, personnel table and more to the vehicle’s table. A mechanism of the role-based
access control was given priority with an aim of protecting data and avoiding intrusion by unauthorized persons.
Further, new types of queries that concerned business intelligence: tendencies of customer orders and
performance of vehicles were created.

Challenges: Another difficulty, was to provide data integrity while defining the relational scheme among the tables.
This was compounded with the fact that it involved the planning of the foreign key constraints and the sequence of
table creation. The third implementation issue was the simulation of realistic scenarios, like working with the
locality-based dump management and further expand scalability. To further test these complex queries for
performance and accuracy we identified several round of refining to meet operational demands. Lastly, the
development of privacies that met legal and ethical requirements to give its own mission to the prevention of
protecting customer and personnel data.

Assumptions: Some of the assumptions made for the purpose of this project included the following: Coming from
structured datasets, it was assumed that the data was preprocessed as much as possible with minimal cleaning
and standardization required. That means that when designing the system, its authors assumed that proposed
levels of automation could be supported by existing network infrastructure such as cloud-based performance
monitoring. In addition, considerations were made with respect of the effectiveness of users in using secure
authentication measures and frequency at which users update their access details.
References
 Connolly, T., & Begg, C. (2019). Database systems: A practical approach to design, implementation, and
management (6th ed.). Pearson Education.

 Elmasri, R., & Navathe, S. B. (2020). Fundamentals of database systems (7th ed.). Pearson.

 MySQL. (n.d.). MySQL Workbench. Oracle. Retrieved December 6, 2024, from

https://www.mysql.com/products/workbench/

 Australian Government. (1988). Privacy Act 1988. Federal Register of Legislation. Retrieved December 6,
2024, from https://www.legislation.gov.au/Details/C2023C00194

 W3Schools. (n.d.). SQL tutorial. Retrieved December 6, 2024, from https://www.w3schools.com/sql/

 Oracle. (n.d.). SQL best practices for database management. Retrieved December 6, 2024, from
https://www.oracle.com/

 ISO/IEC. (2017). ISO/IEC 27001: Information security management systems requirements. International
Organization for Standardization.