Food Wastage Management System
Component Diagram Description – Food Wastage Management
System
Problem Statement:
To identify and organize the major software components of the Food Wastage Management
System and define their interfaces, dependencies, and responsibilities. This diagram aims to
demonstrate how the system is logically divided into modules and how those modules
interact.
Description:
The component diagram illustrates the modular architecture of the Food Wastage
Management System, capturing the structure and relationships among the system's core
components. It highlights the interaction between user interfaces, controllers, services, and
data storage components.
The system is composed of distinct interfaces for each user role: Donor, Admin, Receiver,
and Delivery Person. These interfaces communicate with corresponding controllers such as
UserController, ReceiverController, AdminController, and DeliveryController. The controllers
handle business logic and interact with specialized services like FoodDonationService,
DonationRequestService, DeliveryService, and ReportService.
All service components connect to a shared Database, ensuring data consistency and
persistence. Additionally, a NotificationService component interacts with the external Email
Server to send real-time updates to users.
This component-based architecture promotes modularity, reusability, and separation of
concerns, supporting future scalability and maintainability.
Deployment Diagram Description – Food Wastage Management
System
Problem Statement:
To map the software components of the Food Wastage Management System onto physical
hardware nodes and illustrate the system's execution environment, including
communication paths and external services.
Description:
The deployment diagram represents the physical architecture of the Food Wastage
Management System, detailing how software artifacts are deployed across various nodes in
the system’s infrastructure.
The system operates across four primary nodes:
1. Web Client – Hosts the user’s browser, which accesses the system through a web
interface using HTTP/HTTPS.
2. Web Server – Contains both frontend (HTML, JavaScript) and backend (PHP)
application logic. It includes application controllers, services, and the
NotificationService.
3. Database Server – Hosts the MySQL database used to store user profiles, donation
data, requests, deliveries, and reports.
4. Mail Server – Responsible for sending system-generated email notifications using
SMTP.
The web server communicates with the Database Server over a secure MySQL connection
and with the Mail Server via SMTP to dispatch emails. End users (Donors, Admins, Receivers,
and Delivery Personnel) access the system remotely through standard web browsers.
This diagram ensures a clear understanding of the system’s runtime behavior, deployment
configuration, and network interactions, and supports decisions related to infrastructure,
scalability, and security.
Component diagram:
Deployment diagram
