INTRODUCTION

This research is an analysis of Recycle4Change (R4C), which is a social enterprise affiliated with TOMRA Cleanaway Victoria (TCV) with the objective of participating in the Victorian Government Container Deposit Scheme. The outcomes of R4C are to cut the amount of garbage and send it to landfills, generate new jobs, enhance waterways, and strengthen Columbia’s circular economy (Burke, 2024). This project is planned for achieving the purpose of stabilizing which has been set for social entrepreneurship, as well as to create conditions for further education and employment of people of all ages, including those with imprisonment or women with children who can work only part-time.

The necessities of integrating an existing business model into the R4C project includes customer registration, bins, collection and dispatch of truck fleets, payments and billing, donations and charity, maps, notice-boards and announcements, reports and analyses, user control and role play, compatibility and growth. 

In this task 1, an initial conceptual data model is introduced in order to illustrate the business by giving the fundamentals; the various elements needed within the business, the specifics of these elements, the connection between these elements and the degree of constraint between entities in terms of multiplicity and cardinality to be included in order to reach an effective system configuration.

Similarly in regard to Task 2 an ER-Diagram, which is basically a conceptual model, is transformed to a more precise and strict Third Normal Form (3NF) detailed logical model. This complete defines the entity, characteristics of the entity, keys of the entity and relationship applicable to it, and possibly constraints in the model. 

As for Task 3, to create the mindset of the UI for the user interface to design the broad architecture of the system to cater for data needs, and to know how their is supposed to interact with the database agenda. They copy the kind of tasks typical for some kind of work, such as bin management or client registration.

TASK 1

Conceptual Data Design Model

In the development of a database system, the process starts with conceptual data model design. It provides a coarse-grained view of the organization focusing on general concepts, their dependencies and data quality with the special technical details (Gharaibeh et al., 2017).

On this model, all entities, properties, relationships, business rules relevant for data requirements specification, and other details are defined, but implementation-specific aspects are excluded; thus, stakeholders easily understand this model and can relay data requirements information with understanding. It helps in formation of the subsequent levels of the database creation, so as to arrive at a workable and efficient database system.



Figure 1: Conceptual Data Model

Task 2

 Logical (Relational) Design Model

A conceptual design is attempted to be created to follow the Third Normal Form (3NF) and then proceed to a more detailed structure. It reduces the records duplication and identifies associations between these tables by arranging data in several tables. To achieve database design and organization for data to be stored, retrieved, shared and to ensure data consistency critical aspects entail designing of tables, attributes, primary keys, foreign keys and building of associations.


Figure 2: Relational Model Design 

ENTITIES AND ATTRIBUTES

Entities define the main parts of a system while characteristics of the specific entity are called attributes. This scene is divided into eight entities: Customer, BinOrder, Truck, Container Drop ID, Donation, Billing, Notification, and BinCollection; and most of these entities require some characteristics for identification purposes.

Table 1: Table of Primary Key

Table 2: Customer

Table 3: Bin

Table 4: BinCollection

Table 5Truck

Table 6: BillingAndPayment

Table 7: Donation

Table 8:Notification

Table 9:Container Drop off
 

Relationship and Cardinalities

The relationships and cardinalities in this database model are appropriate to attain various operations of a business process. The bin orders and billing records have a one to many relationship with the customers, allowing many bin orders and billing records under one customer and the customer had a one to many relationship for notification so the customer can receive any number of notifications but is still under one specific customer (Jiang et al., 2019).

Bin orders are closely related to delivery trucks through the use of a many-to-one relationship since each delivery truck may haul numerous bin orders. In addition, trucks also mediate a one-to-many relationship with bin ordering and bin collection events signifying their participation in multiple delivery and collection. One can store receipts on multiple bin collection events on a container drop location, while many donations can be assigned to a single customer and the system is effective for order processing and customer management.

Assumption and Business Rule

The following assumptions and rules of business were developed when designing the R4C database to make the system effective: The recycling management software can barely runs efficiently without strict compliance to these key principles.
Customers are classified into one of the three groups namely: Individual, Commercial, and Residential. Thus, by categorization of the services, interactions with various types of consumers are simplified and made individualized.

• Billing and Payment alternatives: Scam systems on the other hand provide a number of variants of payment like cash on delivery, bank transfer, direct debit and the like. Other customer types are paid after 5 business days from bin pickup, but the ‘Individuals’ are paid on the time of item collection.

• Donation & Charity: Consumer can decide to give portion of their money spent to the charity of R4C’s choice. For any donations equal to or exceeding $2, a Donation Tax Receipt is issued.

• Maps and Notifications: Its feature is that the system has mapping modules for ‘Individual’ customers to locate a nearby collection center and get up-to-date information on the latter’s working conditions (Bogdanova et al., 2019). Customers receive notification of upcoming collection visits, change of service etc.

• User Roles and Access Control: To enhance security and privacy of the data the following user roles are developed administrator, driver, customer care representative and the customer. Due to access control systems there is granted at various levels according to the employment opportunities for the authorized workers.

• Integration and Scalability: The software is designed, with a view of making it expand due to the increasing clientele offering various operations. For raising total operating efficiency, it fosters integration with other functional applications and systems including accounting and route optimization. These presumptions and regulations make recycling management firm and adaptable when linked to business objectives and the database design of the R4C.

TASK 3

Sample Dummy Input Screen (Mock-up)
This section showcases the Dummy screenshots of the Input Screens under various tab pages.



Figure 3: (User Role) Login Account 



Figure 4: Create new Account (Individual, Commercial, and Residential)



Figure 5: Container Drop-off



Figure 6: Bin Order




Figure 7: Payment


Figure 8: Order Place Screen


Figure 9:  Screen Notification 


a. Data Completeness: R4C database design aims at including all the information which has to be incorporated either company or by case study standards. The design approach adopted in the work involved an understanding of the case study and extraction of the main entities, attributes, relationships and constraints and their transformation into a conceptual data model. During this entire process of analysing and identifying all the primary data objects and their attributes, their record was kept continuously (Fischer et al., 2018).

The above-mentioned model laid the foundation for the future logical model design, which aimed at eliminating anomalies and redundancies but retaining the integrity of the data. However, to facilitate the achievement of this goal, the design approach had to entail comprehensive knowledge of R4C case study business needs to cater for its activities such as client registration, invoicing, as well as general management of truck fleet and reporting. 

b. Design Iterations: The sample input screens in the conceptual and logical review of the systems database design. This iterative process proved to be helpful in setting the models in comparison with the user interface and usability. The basic entities stayed intact but for some mandatory user input constraints of the attributes. For example, when developing the user interface, two fields within the Notification entity, namely “NotificationType” and “Content,” to record various content notifications (Börner et al., 2019). These changes increased user engagement and helped to implement automatic notification. Furthermore, to meet user experience, relationships were also adjusted and data flow was designed as naturally as possible. The iteration model was used to refine the design so that it would closely meet the user interface and utilities of the system developed to be an improved version of R4C system.
 

Top Humanities Samples

References

Bogdanova, D. and Snoeck, M., 2019. CaMeLOT: An educational framework for conceptual data modelling. Information and software technology, 110, pp.92-107.
Börner, K., Bueckle, A. and Ginda, M., 2019. Data visualization literacy: Definitions, conceptual frameworks, exercises, and assessments. Proceedings of the National Academy of Sciences, 116(6), pp.1857-1864.
Burke, L. and Grodach, C., 2024. Planning inclusive circular cities. Planning News, 50(2), pp.25-27.
Fischer, P.M., Deshmukh, M., Koch, A., Mischke, R., Martelo Gomez, A., Schreiber, A. and Gerndt, A., 2018. Enabling a conceptual data model and workflow integration environment for concurrent launch vehicle analysis.
Gharaibeh, A., Salahuddin, M.A., Hussini, S.J., Khreishah, A., Khalil, I., Guizani, M. and Al-Fuqaha, A., 2017. Smart cities: A survey on data management, security, and enabling technologies. IEEE Communications Surveys & Tutorials, 19(4), pp.2456-2501.
Jiang, Y., Wang, C., Wang, Y. and Gao, L., 2019. A cross-chain solution to integrating multiple blockchains for IoT data management. Sensors, 19(9), p.2042.
Shafagh, H., Burkhalter, L., Hithnawi, A. and Duquennoy, S., 2017, November. Towards blockchain-based auditable storage and sharing of IoT data. In Proceedings of the 2017 on cloud computing security workshop (pp. 45-50).
Sudmanns, M., Tiede, D., Lang, S., Bergstedt, H., Trost, G., Augustin, H., Baraldi, A. and Blaschke, T., 2020. Big Earth data: disruptive changes in Earth observation data management and analysis International Journal of Digital Earth, 13(7), pp.832-850.