UML Work-3
UML Work-3
Paix-Travail-Patrie Peace-Work-Fatherland
BP 13 Yaounde(Cameroun) PB 13 Yaounde(Cameroun)
UML
THEME :
Class : BA2A
Group : 13
Members
SIAPI JEAN
NAELLA ORIANE
Mr.MESSIO
ACADEMIC YEAR
2024/2025
SUMMARY
SUMMARY ......................................................................................................................................................2
INTRODUCTION ............................................................................................................................................. 3
I. OVERVIEW .................................................................................................................................................. 4
Conclusion ................................................................................................................................................... 28
INTRODUCTION
The Food Sale System (FSS) is a robust software solution designed to simplify and
automate food store operations. This system efficiently handles inventory management, orders,
deliveries, customer engagement, and feedback collection. Key features include reward
tracking, trash management for expired products, and a communication platform for customer
feedback (Tchat).
I. OVERVIEW
The Food Sale System is a software solution designed to optimize food store operations.
It includes features like inventory tracking, order processing, billing, and generating reports.
The system aims to reduce manual errors, streamline processes, and improve customer service.
The Use Case Diagram represents the interactions between the actors (users) and the
system. It highlights the functionalities the system provides and who accesses them.
II.1. Actors:
Track Inventory, Generate reports, and Manage deliveries: Managers track stock levels and
reorder items.
Supplier Interaction: Managers communicate with suppliers to replenish inventory.
Generate Reports: Managers generate sales and inventory reports.
Manage Users: Admin adds or removes users like cashiers, managers, or visitors.
System Configuration: Admin updates system settings or permissions.
Update delivery status and Manage delivery details: Delivery Man.
Send Feedback: customer share feedback via Tchat, which is reviewed by the Admin.
Calculate Rewards: System tracks customer purchases and compute loyalty points.
Manage Trash: Admin identifies expired products and moves them to the trash.
The Activity Diagram illustrates workflows for major processes in FSS. It shows the
sequence of actions and decision points.
III.2. SCENARIOS
1. Order placement .
2. Make Payment.
3. Creating an account.
4. Restocking products by store manager.
5. Managing expired products.
6. Collecting customer feedback(Tchat).
7. Reward Management.
8. Delivery Management.
9. Supply Products
The Sequence Diagram details the interactions between system components and users
for specific processes.
IV.1. SCENARIOS
1. Order Placement.
2. Make Payment.
3. Generates bills.
4. Supply Products.
5. Inventory Replenishment.
6. Managing Expired Products.
7. Reward Calculation and Redemption.
8. Customer Feedback (Tchat).
9. Delivery Assignment.
IV.1.2.Generates Bills
V. CLASS DIAGRAM
V.1. Classes:
1. Visitor:
Attributes: visitorID,browseingHistory .
Methods: browseProducts(), registerAccount(), makeResearch().
2. Customer:
Attributes: customerID, name, email, phone, locationID.
Methods: browseProducts(), placeOrder(), viewOrderHistory(), updateProfile(), makePayment(),
addProductBasket(), makeComment(), trackOrder().
3. Product:
Attributes: productID, name, price, quantity, description, expiredDate.
Methods: updateStock(), getDetails(), checkAvailability().
4. Order:
Attributes: orderID, orderDate, customerID, totalAmount, basketID, status.
Methods: calculateTotal(), generateInvoice(), updateStatus(), getOrderDetails().
5. Inventory:
Attributes: inventoryID, productID, stockLevel, reorderLevel.
Methods: checkStock(), updateStock(), addProductToInventory(), getLowStockProducts().
6. Supplier:
Attributes: supplierID, name, contactDetails.
7. Store Manager:
Attributes: managerID, name.
Methods: manageInventory(), generateReport(), assignDeliveryMan(), contactSupplier().
8. Payment:
Attributes: paymentID, orderID, amount, paymentMethod.
Methods: processPayment().
9. Admin:
Attributes: adminID, username, password, email.
Methods: managesUsers(), configureSystem(), auditLogs(),trackCars(), makePayment() .
10. Location:
Attributes: locationID, latitude, longitude, address.
Methods: getCoordinates(), setAddress().
11. Notification:
Attribute: notificationID, type, message.
Method: sendNotification(), markAsread().
12. Promotion:
Attributes: promotionID, description, discountPercentage.
Methods: applyPromotion(), validatePromotion().
13. Cars:
Attributes:carID, model, plateNumber.
16. Category:
Attributes: categoryID, productID, name, description.
Methods: addCategory(), removeCategory(), getCategoryDetails().
17. Baskets:
Attributes: basketID, customerID, items, totalPrice.
Methods: addProduct(), removeProduct(), calculateTotal(), checkout().
18. Trash:
Attributes: trashID, productList, disposalDate.
Methods: addExpiredProduct(), generateWasteReport().
19. Reward:
Attributes: rewardID, points, custumerID.
Methods: trackPurchases(), calculateMonthlyReports(), redeemReward.
20. Tchat:
VI.PACKAGE DIAGRAM
The Package Diagram groups classes into logical components to depict the structure of
the software system. It illustrates dependencies among these packages, ensuring modularity,
reusabilty, and scalability.
The FSS can be divided into the following packages:
f. Reward
g. Promotion
h. Trash
i. Inventory
4. Utility Package
Description:
Provides auxiliary features to support other packages.
Classes:
a. Notification
b. Tchat
5. Payment Package
Description:
Handles financial transactions in the system. This package isolates payment
functionalities, ensuring modularity and maintainability.
Classes:
a. Payment
It models the interactions between classes and their relationships, focusing on the flow
of messages within a specific use case. For this system, we are going to work on the
communication diagram for the “Place Order and Payment Process” use case. This includes
classes such as Customer, Order, Product, Payment, and related entities.
VII.1. Authentication
It represents the states and transitions of an object throughout its lifecycle in response
to events.
1. Manual Errors :
Inventory mismatches due to human error. Billing inaccuracies during rush
hours.Inefficient tracking of stock and expired products.
2. Time-Consuming Processes:
Manual inventory tracking and reordering. Generating sales or inventory reports takes
time.
3. Customer Dissatisfaction:
Long waiting times during checkout. Lack of real-time product availability updates.
4. Communication Gaps:
Poor coordination with suppliers leading to overstocking or understocking.
5. Inefficient Resource Management:
Difficulty in tracking employee performance or assigning tasks efficiently.
6.Customer Retention Issues:
Lack of loyalty programs reduces customer engagement.
5. Spoiled Product Management:
Difficulty in identifying and removing expired items.
6. Inefficient Delivery Management:
Poor allocation tracking of deliveries and vehicules.
1. Automation:
Real-time inventory updates after sales. Automated billing ensures accurate and quick
checkout. Track stock and product expiration dates.
2. Efficiency:
Faster order processing and reduced waiting times. Streamlined communication with
suppliers for timely restocking.
3. Improved Decision-Making:
Sales and inventory reports help managers forecast demand. Alerts for low stock levels
to prevent shortages.
4. Enhanced Customer Experience:
Quick checkout process with minimal errors.Easy-to-navigate product browsing and
order placement.
5. Scalability:
Can handle large inventories and multiple store locations.
6. Trash Management:
Handles expired products systematically.
7. Reward System:
Rewards loyal customers based on purchase history.
8. Customer Feedback (Tchat):
Allows real-time communication between customers and the system.
9. Optimized delivery Tracking :
Assigns delivery men and vehicles to track order fulfillment.
Conclusion
The Food Store Management System addresses critical challenges like inventory
mismatches, slow processes, and poor customer experiences through automation and
efficiency. Its applicability spans supermarkets, restaurants, and online food platforms, making
it a versatile solution for food-related businesses. By integrating core functionalities like
inventory tracking, order processing, and supplier coordination, FSMS ensures streamlined
operations, cost savings, and enhanced customer satisfaction.
TABLE OF CONTENTS
SUMMARY ......................................................................................................................................................2
INTRODUCTION ............................................................................................................................................. 3
I. OVERVIEW .................................................................................................................................................. 4
Conclusion ................................................................................................................................................... 28