Chapter 3

Technical Background

Clucash is a system designed to help users efficiently manage and declutter their homes by providing structured options for item utilization, such as selling or auctioning. It streamlines the process of listing, organizing, and purchasing items, ensuring a seamless experience for all users involved.

This chapter introduces the individuals responsible for developing Clucash and presents various diagrams that illustrate the flow of both the current and proposed systems. Each diagram is accompanied by a narrative to provide a clear understanding of system interactions, user roles, and data flow. These visual representations help in analyzing and improving the overall efficiency of Clucash.

Figure 3.1 Organizational Structure

In Figure 3.1, the organizational structure of a retail business typically features a hierarchy with the shop owner at the top, the one responsible for strategic decision-making and overall management. Below the owner, there are two roles: the logistics and salesman. The logistics oversees inventory management and supply chain operations, while the salesman supervises the sales in the shop and interacts directly with customers to provide assistance and process transactions.

Figure 3.2 Floor Plan

Figure 3.2 illustrates the system's deployment at the clients' location. The system is installed on dedicated workstations for the Shop Owner, Logistics, and Cashier. Users receive training, followed by a pilot test to address issues before full deployment.

Figure 3.3 Activity Diagram of the Current System

Figure 3.3 shows the workflow of managing surplus items in the Surplus Retail Store system, involving the Seller, Shop Owner, Logistics, Salesman, and Buyer. The Seller lists surplus items for the Shop Owner, who selects and purchases them. Logistics manages pricing and inventory updates. The Salesman assists with order processing, and the Buyer selects and buys items. This workflow ensures smooth coordination of pricing, inventory, and sales.

Figure 3.4 Context Level Data Flow Diagram of the Current System

Figure 3.4 illustrates the interactions of the Surplus Retail Store with the Buyer, Shop Owner, Seller, Logistics, and Salesman. The system manages item exchanges, payments, order tracking, pricing, and receipts. The Buyer purchases from the Shop Owner, who sources inventory from the Seller. Logistics handles pricing, while the Salesman facilitates order fulfillment. These interactions ensure efficient purchasing, inventory management, and sales tracking.

Figure 3.5 Level 0 Data Flow Diagram of the Current System

Figure 3.4 illustrates the flow of surplus item management in the retail system, showing how items move from sellers to buyers through various processes. Sellers add items to inventory, which are then organized into a catalog for shop owners to view and purchase. Once an order is placed, the system processes payments, updates inventory, and generates order records. Logistics sets item prices, ensuring accurate pricing before items are made available for sale. Buyers then select and purchase items, with sales being recorded and receipts issued. Throughout the process, data stores track inventory, orders, and transactions, ensuring smooth and efficient retail operations.

Figure 3.6 Clucash’s System Architecture

Figure 3.6 illustrates the middleware architecture, where a user submits a purchase request, which is processed through a messaging system to ensure seamless communication. The integration layer manages interactions between various components, facilitating data exchange and system coordination. The API gateway acts as a security checkpoint, routing requests to the appropriate purchase service while ensuring efficient handling of user inputs. The server communicates with the database to store transaction details, ensuring data consistency and retrieval when needed. Once the purchase is confirmed, a receipt is generated and sent to the store, finalizing the transaction.

Figure 3.7 Activity Diagram of the Proposed System

Figure 3.7 illustrates the activity diagram of the proposed system. The Clucash Admin approves supplier and shop accounts, ensuring only verified users can participate. The Supplier adds, declutters, and sorts items before the Shop Owner places an order. If the Shop Owner selects more items, the process repeats; otherwise, the order is finalized, and inventory is updated. Logistics sets prices before the Buyer places an order. Once confirmed, orders are processed, and transactions are completed, ensuring smooth inventory management and sales flow.

Figure 3.8 Context Level Data Flow Diagram of the Proposed System

Figure 3.8 shows the Clucash System and its external entities, starting with the Clucash Admin, who oversees the platform by approving supplier and shop accounts to ensure legitimacy. Buyers interact with the system by placing orders, while Suppliers provide item details and pricing information. Shop Owners manage inventory, update product listings, and handle payment transactions. Logistics is responsible for setting item prices and ensuring smooth inventory movement. The Cashier processes transactions and generates receipts for completed orders.

Figure 3.9 Level 0 Data Flow Diagram of the Proposed System

Figure 3.9 illustrates the flow of surplus item management within the system, highlighting interactions between the Clucash Admin, Seller, Shop Owner, Logistics, Buyer, and Salesman. The process begins with the Clucash Admin approving supplier and shop accounts, ensuring only verified users can participate. The Seller lists items, which the Shop Owner reviews and purchases. Logistics sets item prices to maintain accurate cost tracking. Buyers select and purchase items, while the Cashier facilitates order fulfillment. Transactions are recorded, and receipts are issued to confirm purchases.

Figure 3.10 Entity-Relationship Diagram of the Proposed System

Figure 3.10 illustrates the entity-relationships diagram in the system for the application Clucash. Suppliers add items to the closet, which connects to the inventory and catalog. Shop owners can purchase these items and transfer them to their shop inventory for sale. Buyers browse and purchase items, the Cashier processes the order within the system. This flow ensures smooth tracking, organization, and transactions.

Figure 3.11 Project Organization

Figure 3.11 illustrates the project's organizational structure, ensuring clear roles and responsibilities. At the top, the Project Manager oversees the entire operation, coordinating tasks and ensuring smooth execution. The Researcher gathers relevant information, while the Documenter records essential details. The Developer is responsible for implementing technical aspects based on the research and documentation. This structure promotes efficient collaboration, streamlined workflows, and effective project management.