Company Certificate
1
Collage Certificate
2
Acknowledgment
It gives us great pleasure and deep satisfaction to present this report of our
project work as a part of BCA course arranged to gain a piece of practical
knowledge in system development
We took this opportunity to express our sincere gratitude to several people with
whose help and encouragement, we have been able to complete this project
rather successfully.
We express a deep sense of gratitude to our internal project guide Prof. for her
guidance, valuable suggestions, and continuous encouragement without which
the project would not have been a success.
We also thank our Professor, Prof. Nikunj patel, and all other faculties of college
because their constructive suggestions, valuable inspiration, and motivation
encourage us throughout the project.
3
INDEX
Sr. No. Topic Page No.
1. Introduction ........................................................................ 05
2. Company Profile ................................................................ 06
3. Project Profile..................................................................... 07-16
3.1 Existing System ................................................. 07
3.2 Proposed System ................................................ 08
3.3 Development Tools And Technology ................. 09
3.4 Modules.............................................................. 13
3.5 Process Of Modules ........................................... 14-16
3.5.1 Admin ................................................... 14
3.5.2 Seller ..................................................... 15
3.5.3 Buyer .....................................................16
4. UML Diagrams................................................................... 17-34
4.1 Use Case Diagram .............................................. 18-21
4.1.1 Admin ................................................... 19
4.1.2 Seller ..................................................... 20
4.1.3 Buyer .....................................................21
4.2 Class Diagram .................................................... 22
4.3 Activity Diagram ................................................ 24-28
4.3.1 Admin ................................................... 26
4.3.2 Seller ..................................................... 27
4.3.3 Buyer .....................................................28
4.4 Sequence Diagram ............................................. 29-34
4.4.1 Admin .................................................. 32
4.4.2 Seller .................................................... 33
4.4.3 Buyer ....................................................34
5. Entity Relationship Diagram .............................................. 35
6. Data Dictionary .................................................................. 37-43
4
1.1 Introduction
Online Tiffin Service System is a web-based application that allows the
administrator to handle all the activities online quickly and safely. Using
Interactive GUI anyone can quickly learn to use the complete system. This
system will give power and flexibility to the administrator to manage the entire
system from a single online portal.
In the Online Tiffin Service System, we use PHP and MySQL Database.
This project keeps the records of Tiffin’s orders. This project has three modules
i.e. admin, buyer, and seller.
5
Company Profile
6
Project Profile
3.1 Existing System
● It is offline.
● Requires more man resources.
● Work is done manually.
● Takes a lot of time.
● Customers have to visit the place for ordering.
● Less convenient.
● Limited-time period.
7
3.2 Purposed System
● Requires less man resource
● Takes less time
● User friendly
● More convenient for people as they don't have to go anywhere
● Order can be placed at any time and from anywhere
● Also identifies the past data record of the customer
● Demo available at starting for the ease of customer
8
3.3 Development Tools And Technology
Frontend Language : HTML , CSS , JavaScript
Backend Language : PHP
Database : MySql
Other Tools : VS Code , XAMPP
9
3.4 Modules
● Admin
● Seller
● Buyer
10
3.5 Process Of Modules
1 . Admin
● Login
● Manage Account
● Manage Category
● Manage Customer listing
● Manage Seller Listing
● Manage Order Listing
● Manage Bills
● Manage Reports
● Manage Complains
● Logout
11
2. Sellers
● Login
● Manage Account
● Manage Menu
● Manage Orders
● Manage Delivery
● View Reviews
● Manage Complains
● Manage Reports
● Logout
12
3. Buyer
● Login
● Manage Account
● Manage Orders
● Give Reviews
● Logout
13
UML Diagram
● Use Case Diagram
● Class Diagram
● Activity Diagram
● Sequence Diagram
14
7.1 Use Case Diagram
Name Symbol Use
Actor Actors are the users of a system.
When one system is the actor of
another system, label the actor system
with the actor stereotype.
Use Case Draw use cases using ovals. Label the
ovals with verbs that represent the
system's functions.
Relationships <<include> Illustrate relationships between an
- -------> actor and a use case with a simple
line. For relationships among use
<--------
cases, use arrows labeled either "uses"
<<extend>> or "extends." A "uses" relationship
indicates that one use case is needed
by another in order to perform a task.
An "extends" relationship indicates
alternative options under a certain use
case
System Boundary Draw your system's boundaries using
a rectangle that contains use cases.
Place actors outside the system's
boundaries.
15
Admin Use Case :
16
Seller Use Case :
17
Buyer Use Case :
18
7.2 Class Diagram
Name Symbol Use
Classes and interfaces in UML show
architecture and features of the
Upper Section
Class designed system.
Middle Section
Lower Section
Dependency relationship is a
relationship in which one element, the
Dependency client, uses or depends on another
element, the supplier.
Generalization is a relationship in
which one model element (the child)
is based on another model element
Generalization (the parent).ns under a certain use
case
Association is a relationship between
two classifiers, such as classes or use
cases, that describes the reasons for
Association the relationship and the rules that
govern the relationship.
Aggregation is a special type of
association in which objects are
Aggregation assembled or configured together to
create a more complex object. An
aggregation describes a group of
objects and how you interact with
them.
Composition Composition represents whole-part
relationships and is a form of
aggregation
19
20
7.3 Activity Diagram
A small filled circle followed by
an arrow represents the initial
Start Node / action state or the start point for
Initial Node any activity diagram. For an
activity diagram using
swimlanes, make sure the start
point is placed in the top left
corner of the first column.
An action state represents the
non-interruptible action of
Action Box objects. You can draw an action
state in SmartDraw using a
rectangle with rounded corners.
Shows the directional flow, or
control flow, of the activity. An
incoming arrow starts a step of
Control Flow an activity; once the step is
completed, the flow continues
with the outgoing arrow.
Represents a decision and
always has at least two paths
branching out with condition
Decision-Box / text to allow users to view
Condition options. This symbol represents
the branching or merging of
various flows with the symbol
acting as a frame or container.
Parallel Activity In Sequence activity at same
time.
21
Join Node Combines two concurrent
activities and re-introduces them
to a flow where only one
activity occurs at a time.
Represented with a thick
vertical or horizontal line.
Fork Splits a single activity flow into
two concurrent activities.
Symbolized with multiple
arrowed lines from a join.
Final State / Marks the end state of an
End Node activity and represents the
completion of all flows of a
process.
22
Admin Side Activity :
23
Seller Side Activity :
24
Buyer Side Activity :
25
7.4 Sequence Diagram
Name Symbol Use
Represents a class or object
in UML. The object symbol
demonstrates how an object
Object symbol will behave in the context of
the system. Class attributes
should not be listed in this
shape.
Represents the time needed
for an object to complete a
Activation box task. The longer the task will
take, the longer the activation
box becomes.
Shows entities that interact
with or are external to the
Actor system.
Represents the passage of
time as it extends downward.
This dashed vertical line
Lifeline shows the sequential events
that occur to an object during
the charted process. Lifelines
may begin with a labeled
rectangle shape or an actor
symbol.
Used in UML 2.0 notation to
contain interactive elements
of the diagram. Also known
Package as a frame, this rectangular
shape has a small inner
rectangle for labeling the
diagram.
26
Option loop Used to model if/then
scenarios, i.e., a
circumstance that will only
occur under certain
conditions.
Alternative Symbolizes a choice (that is
usually mutually exclusive)
between two or more
message sequences. To
represent alternatives, use
the labeled rectangle shape
with a dashed line inside.
Synchronous Represented by a solid line
message with a solid arrowhead. This
symbol is used when a
sender must wait for a
response to a message
before it continues. The
diagram should show both
the call and the reply.
Asynchronous Represented by a solid line
message with a lined arrowhead.
Asynchronous messages
don't require a response
before the sender continues.
Only the call should be
included in the diagram.
Asynchronous Represented by a dashed
return line with a lined arrowhead.
Asynchronous Represented by a dashed
create line with a lined arrowhead.
This message creates a new
object.
27
Reply message Represented by a dashed
line with a lined arrowhead,
these messages are replies
to calls.
Delete message Represented by a solid line
with a solid arrowhead,
followed by an X. This
message destroys an object.
28
Admin Sequence
29
Seller Sequence
30
Buyer Sequence
31
E-R Diagram
Name Symbol Description
Entity An entity may be any object,
Or class, person or place. In the
Strong Entity ER diagram, an entity can be
represented as rectangles.
Attribute The attribute is used to
describe the property of an
entity. Eclipse is used to
represent an attribute.
Multi-Valued An attribute can have more
Attribute than one value. These
attributes are known as a
multivalued attribute. The
double oval is used to
represent a multivalued
attribute.
Key Attribute The key attribute is used to
represent the main
characteristics of an entity. It
represents a primary key.
The key attribute is
represented by an ellipse
with the text underlined.
Composite An attribute composed of
Attribute many other attributes is
known as a composite
attribute. The composite
attribute is represented by an
ellipse, and those ellipses are
connected with an ellipse.
Relationship A relationship is used to
describe the relation between
entities. Diamond or
rhombus is used to represent
the relationship.
32
33
Data Dictionary
List of the table in Data Dictionary :
● User
● Role
● Categories
● Items
● Carts
● Orders
● Reviews
● Promo codes
● Complains
34
Table name: User
Sr No. Field Data type(size) Constraints Description
1 user_id int(5) Primary Key It is used to store user_id.
2 email varchar(50) Not Null It is used to store email.
3 password varchar(25) Not Null It is used to store passwords.
4 phone number int(10) Not Null It is used to store phone numbers.
5 address varchar(60) Not Null It is used to store addresses.
6 city varchar(11) Not Null It is used to store city names.
7 state varchar(11) Not Null It is used to store the state.
8 photo varchar(50) Not Null It is used to store photos.
9 create date time_stamp(6) Not Null It is used to store dates.
Table name: Role
Sr No. Field Data type(size) Constraints Description
1 user_id int(5) Foreign Key It is used to store user_id.
2 role type varchar(10) Not Null It is used to store role_type.
3 role id Int(5) Primary Key It is used to store role_id.
35
Table name: Category
Sr No. Field Data type(size) Constraints Description
1 user_id Int(5) Foreign Key It is used to store user_id.
2 role id Int(5) Foreign Key It is used to store role_id.
3 category_id Int(5) Primary Key It is used to store category_id.
4 seller_id Int(5) Foreign Key It is used to store seller_id.
5 name varchar(30) Not Null It is used to store names.
Table name: Item
Sr No. Field Data type(size) Constraint Description
1 user_id Int(5) Foreign Key It is used to store user_id.
2 role id Int(5) Foreign Key It is used to store role_id.
3 category_id Int(5) Foreign Key It is used to store category_id.
4 Title varchar(20) Not Null It is used to store titles.
5 seller_id Int(5) Foreign Key It is used to store seller_id.
6 content varchar(50) Not Null It is used to store content.
7 picture varchar(50) Not Null It is used to store pictures.
8 price int(5) Not Null It is used to store prices.
9 description varchar(100) Not Null It is used to store descriptions.
10 availability_time time(6) Not Null It is used to store availability_time.
36
Table name: Cart
Sr No. Field Data type(size) Constraints Description
1 user_id int(5) Foreign Key It is used to store user_id.
2 seller_id int(5) Primary Key It is used to store seller_id.
3 role id int(5) Foreign Key It is used to store role_id.
4 item_id int(5) Foreign Key It is used to store item_id.
5 Price int(5) Not Null It is used to store prices.
Table name: Order
Sr No. Field Data type Constraint Description
1 user_id int(5) Foreign Key It is used to store user_id.
2 address varchar(50) Not Null It is used to store addresses.
3 seller_id int(5) Foreign Key It is used to store seller_id.
4 order_id int(5) Primary Key It is used to store order_id.
5 item_id int(5) Foreign Key It is used to store item_id.
6 order_date date Not Null It is used to store order_date.
7 order_status boolean Not Null It is used to store order_status.
8 promo_applied boolean Not Null It is used to store promo_applied.
9 total_price int(5) Not Null It is used to store total_price.
37
Table name: Reviews
Sr No. Field Data type(size) Constraints Description
1 user_id int(5) Foreign Key It is used to store user_id.
2 seller_id int(5) Not Null It is used to store seller_id.
3 review int(5) Not Null It is used to store reviews
4 review_date date Not Null It is used to store review data.
5 rating int(5) Not Null It is used to store rating
Table name: Promo Code
Sr No. Field Data type(size) Constraints Description
1 user_id int(5) Foreign Key It is used to store user_id.
2 seller_id int(5) Foreign Key It is used to store seller_id.
3 Promo code varchar(20) Not Null It is used to store promo codes.
4 discount int(3) Not Null It is used to store discounts.
5 discount_type varchar(30) Not Null It is used to store a type of
discount.
6 status boolean Not Null It is used to store status.
38
Table name: Complaints
Sr No. Field Data type(size) Constraints Description
1 user_id int(5) Foreign Key It is used to store user_id.
2 seller_id int(5) Foreign Key It is used to store seller_id.
3 description varchar(100) Not Null It is used to store descriptions.
4 date date Not Null It is used to store data.
5 status boolean Not Null It is used to store status.
39
