SDD of Bakery Managment System
SDD of Bakery Managment System
for
By
Revision History
Document Approval
The following Software Requirement Specification (SRS) has been accepted and approved by the
following:
Table of Contents
1. Introduction
1.1. Purpose
1.2. Scope
1.3. Overview
1.4. Reference Material
1.5. Definitions and Acronyms
2. System Overview
3. System Architecture
3.1. Architectural Design
3.2. Decomposition Description
3.3. Design Rationale
4. Data Design
4.1. Data Description
4.2. Data Dictionary
5. Component Design
6. Human Interface Design
6.1. Overview of User Interface
6.2. Screen Images
6.3. Screen Objects and Actions
7. Requirements Matrix
8. Appendices
1. Introduction
1.1 Purpose
This document provides a detailed design for the Bakery Product Management System. It includes
architectural designs, component descriptions, user interface layouts, and database structures to meet
the requirements outlined in the SRS. This system focuses on improving bakery operations by
managing products, inventory, orders, and financial reports.
1.2 Scope
The system will provide the following functionalities:
1. Product Management : Add, edit, delete, and automatically expire products.
2. Order Management : Process orders (online and offline).
3. Inventory Tracking : Manage raw material and finished goods stock.
4. Financial Reporting : Generate sales and profit reports.
5. Role-Based Access : Secure user roles with access controls for admins and employees.
1.3 Overview
This SDD includes:
1. System Architecture: A 3-tier architecture with ReactJS, Django Rest Framework, and SQL.
2. Component Design: Frontend, backend, and database modules.
3. Human Interface Design: Mock screen layouts for user interaction.
4. Data Design: Relational database structure and flow.
2. System Overview
• Centralized Database: The BPMS is a central hub for all product information. This includes:
• Selling prices
• Expiration dates
• Inventory Tracking:
• Real-time updates on stock levels: Automatic adjustments for sales, purchases, and
wastage.
• Low stock alerts: Notifications to prevent stockouts and ensure timely replenishment.
• FIFO (First-In, First-Out) tracking: Helps manage inventory efficiently and minimize
spoilage.
• Batch Management: Track individual batches of products with their own production dates
and expiration times. This allows for better control over quality and reduces the risk of
expired goods.
2. Automated Product Expiration
• Expiration Date Tracking: The BPMS automatically tracks the expiration dates of all
products.
• Expired products
• Potential spoilage
• Reduced Wastage: Timely alerts help prevent the sale of expired goods, minimizing losses
and maintaining customer trust.
3. Analytics and Reporting
• Sales Analysis:
• Inventory Reports:
• Cost Analysis:
• Point of Sale (POS) Integration: Seamlessly integrate with existing POS systems.
• Increased Efficiency: Streamlined inventory management, reduced manual data entry, and
automated tasks.
• Reduced Costs: Minimized wastage, optimized production, and improved cost control.
• Improved Profitability: Increased sales, reduced costs, and improved overall business
performance.
3. System Architecture
Frontend Components :
- Product Catalog: Displays product details and actions (add/edit/delete).
- AdminDashboard: Provides a comprehensive view of system status (e.g., inventory, sales).
Backend Services :
Database :
- Structured tables with indexing and foreign key relationships.
4. Data Design
5. Component Design
Frontend
- Components :
- ProductCatalog: Displays product list, forms for adding/editing products.
- OrderForm: Manages order placement.
- Actions :
- Add, Edit, Delete buttons trigger modals or forms.
- Real-time stock status alerts.
Backend
- Services :
- ProductService: Implements logic for CRUD operations.
- OrderService: Processes order requests and maintains statuses.
- Endpoints :
- /api/products/ (GET, POST, PUT, DELETE).
- /api/orders/ (POST, GET).
Database
- Design : Normalized structure with indexed tables.
- Key Relationships :
- Products → Orders (one-to-many).
7. Requirements Matrix
8. Appendices
Level 0_DFD
LEVEL 1_ADMIN
LEVEL 2_USER
UML DIAGRAM