MCSP-23
TITLE OF THE PROJECT
Bake Connect: A Unified Platform for Homemade Bakers and Customers
BY
Brief
JINSHA. S
ENROLLMENT NO: 2350959207
UNDER GUIDANCE OF
SYNOPSIS
1. Title of the Project
CAKE ORDER MANAGEMENT SYSTEM
2. Introduction & Objectives
The Cake Orders Management System is an innovative platform designed
to simplify and enhance the process of managing homemade cake orders.
With the growing trend of home-baked goods, many small-scale vendors face
challenges in efficiently handling customer requests, managing inventory,
and ensuring timely deliveries. On the other hand, customers often find it
difficult to explore options, check availability, and place orders seamlessly.
This system bridges the gap between vendors and customers by providing
an intuitive and user-friendly web-based platform. Vendors can efficiently
manage their inventory, display available cakes with detailed descriptions,
and track orders in real-time. Customers can browse a variety of cakes,
customize their preferences (such as flavor, size, and decorations), and place
orders conveniently.
The project leverages modern technologies to create a scalable, secure,
responsive application. It ensures smooth communication between the
parties involved and eliminates manual errors, improving customer
satisfaction and vendor efficiency.
Objectives
1. Automate the Ordering Process: Develop a streamlined system
to enable customers to place orders easily and track them in real-
time.
2. Inventory Management: Provide a feature for vendors to add,
update, and manage their cake inventory based on availability
and demand.
3. Customization Options: Allow customers to customize their
orders, such as selecting flavors, sizes, and decorations, while
ensuring accurate communication with vendors.
4. User Authentication: Ensure secure login and role-based access
for vendors and customers to protect sensitive data.
5. Order Status Tracking: Enable vendors to update the status of
orders (e.g., Confirmed, In Progress, Delivered) and notify
customers through the system.
6. Feedback and Ratings: Include a feedback mechanism for
customers to review their experience, helping vendors improve
service quality.
7. Reporting and Analytics: Provide vendors with sales and
inventory reports to analyse performance and make data-driven
decisions.
8. Responsive Design: Ensure the platform is accessible and usable
across various devices, including desktops, tablets, and
smartphones.
9. Notifications: Integrate notification systems (e.g., email, SMS,
or in-app) to keep users updated about order confirmations and
delivery statuses.
10. Future Scalability: Design the system with scalability in mind,
allowing for the addition of new features, such as delivery
tracking or integration with payment gateways.
3. Project Category
Web-based Application
4. Tools and Platforms used
4.1 Hardware Specification:
Server-Side Processor: 11th Gen Intel(R) Core(TM) i3-1115G4 @ 3.00GHz 2.90 GHz
RAM: 8.00 GB
Hard Disk Space: 100MB minimum
Client Side
Processor: 11th Gen Intel(R) Core (TM) i3-1115G4 @ 3.00GHz 2.90 GHz Processor or higher
RAM: 8MB or 64MB
4.2 Software Specification:
Server-Side Platform: Windows- NT/2000/2003
Software support: .NET Framework 4.0
Client-Side Platform: Win 98/XP
Software support: Internet Explorer 6 or higher
Tools/Languages Script Languages used: JavaScript Programming
Language: C# (C Sharp)
Front End: [Link] 4.5
Back End: SQL Server 2021
Developer Tool: Visual Studio 2022
5. Problem Definition
The study phase is the most important step for a problem solution. This is the first
stage. The whole success of the solution depends upon this phase. The deeper we learn
about the problem, the more perfect the coming phases will be to the end to find the
goal. The existing system that uses manual operations is very tiresome and time-
consuming. The paperwork is tedious and very clumsy, and it is difficult to handle in
time. Data inconsistencies and corruption are due to a lack of manual updating. The
traditional method of paper works faces not only the head-aching data works but their
security aspect also becomes a challenge. When works are transformed into a
computerized form makes the operations very easy and smooth running of the system.
The current system works manually. Earlier there was a computerized system, but now
everything has come to chaos. So it requires upgradation of the hardware and software
infrastructure which is to be maintained regularly against security threats and data loss.
Now the new system proposed has to absorb all the previous data including the paper
form data they kept in the recent time in the current system. The use and ease of
automatic systems in the good old days thrust them to move fast to the installation of
new software systems. The new system proposed helps to manage all level operations
very easily, the inquiry, time scheduling, time calculations, and periodic work
reminders all are achieved very smoothly. The present system uses a paper system as
the old software system got collapsed. The new system requires new features like
security, periodic operations, and some other tools. There are two types of logins -
administrator and operator. The users are allowed to log in using their username and
password allotted.
5.2 Project Planning and Scheduling
Without planning it is difficult to measure progress. As plans are crystallized, crises
should begin to disappear. A project manager must plan the life cycle of the project
and delegate authority for its implementation. Project planning involves plotting
project activities against a time frame.
Gantt chart
A Gantt chart is a project technique that can be used for several purposes, including
scheduling and resource planning. A Gantt chart is a bar chart, with each bar
representing an activity. A Gantt chart provides a graphical illustration of a schedule
that helps to plan, coordinate, and track specific tasks in a project. A Gantt chart is
constructed with a horizontal axis representing the total period of the project, broken
down into increments (for example, days, weeks, or months), and a vertical axis
representing the tasks that make up the project. Horizontal bars of varying lengths
represent the sequences, timing, and period for each task. Gantt charts give a clear
illustration of project status, but one problem with them is that they don’t indicate task
dependencies. The Gantt chart for “CAKE ORDER MANAGEMENT SYSTEM” is
given below:
1. User Request and approval
2. Requirement Study
3. Initial Investigation
4. Feasibility Study
5. Requirement Specification and Approval
6. Detailed Investigation
7. Selection of a prototype
8. Physical Design
9. Logical Design (coding)
10. Testing
11. Implementation
12. User Training
PERT Chart
A Program Evaluation and Review Technique (PERT) chart is a project management
tool used to schedule, organize, and coordinate tasks within a project PERT chart is a
scheduling technique or device that also shows graphically which tasks must be
completed before others are begun. The direction of the arrows on the lines indicates
the sequence of tasks. The PERT chart is sometimes preferred over the Gantt chart,
another popular scheduling technique because it clearly illustrates task dependencies.
The PERT chart we were able to plan the execution of the project ‘CAKE ORDER
MANAGEMENT SYSTEM’. With the help of CAKE ORDER MANAGEMENT
SYSTEM 7 the PERT chart we identified the project's critical path; this critical path
allows us to consider alternative approaches to cope with a potential problem. With
this chart's help, we could monitor and control the project. The project was started on
9th OCT 2024. The project PERT chart is shown below. The various activities
performed are represented by respective IDs which are given below.
PERT CHART
6 Scopes of the Solution
The scope of the Cake Orders Management System includes creating a web-based
application that facilitates the management of homemade cake orders. Key features
encompass user registration, customer browsing and customization of cake orders,
order tracking, inventory management, and automated notifications. The system will
also provide an admin interface to manage orders, and users, and generate reports.
Non-functional aspects include performance, scalability, and a user-friendly experience
across various devices. Security and compliance with regulations will be ensured.
Constraints include time, budget, and technology stack limitations, with assumptions
made about user requirements and resource availability.
7 Analysis
7.1 Dataflow Diagram
LEVEL 0
LEVEL 1
LEVEL 1
ER DIAGRAM
8 Database Design
