Experiment No-1

Objective: Draw the E-R Diagram for online shopping system with proper cardinality and
participation of entities.

In this diagram, there are five entities: Customer, Products, Order, Vendors and Payment.

• The Customer entity represents the people who use the online shopping system to buy products.
Each customer has a unique Customer ID, and can place many Orders.
• The Product entity represents the items that are available for purchase on the website. Each
product has a unique Product ID, and can be included in many Orders.
• The Order entity represents a single purchase made by a customer. Each order has a unique Order
ID, and includes one or more Products. Each order is placed by one and only one Customer.
• The Payment entity represents a payment made by a customer for a particular order. Each
payment has a unique Payment ID, and is made for one and only one Order.
• The Vendors entity represents the people who supply products to the website. Any Vendor can
supply one or more than one product and similarly one single product can be supplied by one or
more Vendors.
The diagram also shows the relationships between these entities, indicated by the lines connecting them:

• The Customer entity has a one-to-many relationship with the Order entity, as each customer can
place many orders, but each order is placed by one and only one customer.
• The Product entity has a many-to-many relationship with the Order entity, as each order can
include many products, and each product can be included in many orders.
• The Order entity has a one-to-one relationship with the Payment entity, as each order is paid for by
one and only one payment, and each payment is made for one and only one order.
• The Vendors entity has a many-to-many relationship with the Products entity, as each product can
be supplied by many vendors, and each vendors can supply many products.

Table 1:Customer Table 2:Order

ID Name Address Mobile No. ID Amount Date

C001 Himanshu Prayagraj 7080621973 OD001 1200 02-03-2023
C002 Avnish Lucknow 9118460032 OD002 900 01-04-2023
OD003 2200 04-04-2023

Table 3:Payment Table 4:Vendors

ID Amount Payment Method ID Vendor Name Address
PM001 1200 COD V001 Manish Prayagraj
PM002 900 UPI
V002 Amit Lucknow
PM003 2200 UPI
V003 Aman Kanpur
V004 Rohit Delhi

Table 5:Products
ID Product Name Price Quantity
P001 Lux Soap Rs.30 455
P002 Kissan Ketchup Rs.120 240
P004 Surf Excel Washing Powder Rs.150 58
P005 Parle-G Biscuit Rs.35 170
 Experiment No-2
Objective: Draw the E-R Diagram for Library Management System.

In this diagram, there are five entities: Members, Books, Staff, Login Credentials Reports.

• The Members entity represents the people who taken the Subscription of the Library. Each member
has a unique Member ID, and Status which show if his/her subscription is active or not.
• The Books entity represents the books that are available in the Library. Each Book has a unique
Book ID, and can be requested by many Members.
• The Login Credentials entity represents the details of people account through which they can login
into the Library Software to search books. Each member has a unique username and password for
their account.
• The Staff entity represents the employees of the Library who manages the books and reports of
members. Each staff has a unique Staff ID.
• The Reports entity represents the reports of the books borrowed by the members. Each Report has
a unique Report ID, and has Book Issued Date as well as Due Date and contains Fine if the book is
returned after Due Date.
The diagram also shows the relationships between these entities, indicated by the lines connecting them:

• The Members entity has a one-to-many relationship with the Books entity, as each member can
request many books.
• The Books entity has a many-to-one relationship with the Staff entity, as each staff can manage
many books, and many books which belong to one section will be managed by one staff.
• The Members entity has a one-to-one relationship with the Login Credentials entity, as each
member can have only one account, and each username and password belong to only one
member.
• The Reports entity has a many-to-one relationship with the Staff entity, as each staff can maintain
many reports, and many reports can be maintained by one staff only.

Table 1: Members

Member ID Name Email Mobile No. Status

MI234 Archit Raj [email protected] 7987653390 Active
MI119 Aman Pandey [email protected] 8009075433 Active
MI345 Samarth [email protected] 9936654322 Active

Table 2: Login Credentials Table 3: Staff

Username Password Staff ID Name Mobile No.

archit33 Ucer01200 SI020 Sarvasva 6788605039
amanpandey23 Aman98ucer SI344 Mukesh 7112334565
samarth840 Samrth2104

Table 4: Books

Book ID Title Author Quantity

CS290 Python Programming Pankaj Jalote 90
ME230 Fluid Mechanis Richa Chaudhary 33
CS345 Core Java Uttam K. Roy 22

Table 5: Reports

Report ID Issue Date Due Date Fine

RI9807 01-01-2023 07-01-2023 0
RI7866 05-02-2023 11-02-2023 150
RI4545 04-04-2023 10-04-2023 25
 Experiment No-3
Objective: Draw the Context Diagram of Online Shopping System.

In this diagram, there are four entities: Customer, Vendor, Employees and Banks. The diagram has one
process Online Shopping System which comprises of many sub processes.

• The Vendors entity represent the person which supply the various products to the Shopping System
and the Shopping System informs the list of orders for the products by customers.
• The Customer entity represents the people who uses Online Shopping System. The customer sign in
using their login credentials and the Online Shopping System give access to the customer to view
the products if the login credentials is correct else show Invalid details.
• The Employees entity represents the people who work for the Shopping System. The Shopping
System provides the Enquiry given by customer to the Employees and Employee provide the
solution for the Enquiry back to the Online Shopping System.
• The Customer do the payment from Banks to the Online Shopping System for the product they
purchased. The Shopping System gives Invoice to the Bank for the payment.
 Experiment No-4
Objective: Draw the Context Diagram of Library Management System.

In this diagram, there are three entities: Customer, Vendor, Staff. The diagram has one process Library
Management System which comprises of many sub processes.

• The Vendors entity represent the persons which sells books. The Library request for the various
books for the Library and, the Vendor deliver the respective books.
• The Customer entity represents the people who are subscribed to the Library. The customer search
for the book as per his/her needs. The Library Management System display the list of books which
matched with user searched book to the Customer.
• The Staff entity represents the people who work in the Library. The Library Management System
gives the information of the requested book by the customer to the staff. The Staff Allot the book to
the person if it is available in the Library.
 Experiment No-5
Objective: Draw DFD of Library Management System.

In this diagram, there are two entities: Student and Librarian. The diagram has five processes Login, Search
Book, Issue Book, Generate and Display Report and Check Availability.

• The Student provide Login Credentials to Login processes which further check with the record of
student and if the data matches in the record the processes will give access to the student to the
function of other Library Management Processes.
• The Student provide book title to the Search Book process and it find for all the books similar with
the title in the Book Record and display it to the student.
• The Issue Book process accept the requested book by the student and give the requested book Id to
the Librarian.
• The Librarian check for the availability of the book in the Book Record through Check Availability
process and if the book is available it informs to the Librarian.
• The Librarian then allot the book to the respective Student and Issued Book process will Issue it to
the Student and at the same time it will update the Book records.
• Also, the Issue Book process will provide the student ID and Book Id to the Generate and Display
Report Process which will create the report of the book such as to which student it is issued and the
due date of the book in the Report Record Table.
• The Student can request for its report of the issued book to the Generate and Display Report
Process which will further find the report in the Report Record and will display it back to the
Student.
 Experiment No-6
Objective: Draw DFD of Online Shopping System.

In this diagram, there are three entities: Customer, Vendor and Banks. The diagram has five processes
Login, Search Product, Manage Shopping Cart, Checkout and Payment.

• The Customer entity represent the user who buy product using Online Shopping System.
• The Vendor entity represent the people who sell product on Online Shopping System.
• The Customer and Vendor provide login credentials to Login process and it check the details in the
User Record table and grant access to the user if details are correct.
• The Customer search for the product using Search Product process which find the product in
Product Record table and display the product to the Customer.
• After searching products the Customer can either direct purchase it or add it to the cart which will
be manged by Manage Shopping Cart process.
• When the Customer choose to buy the product it will redirect it to checkout page where he/she
enters the bank details and payment amount, the data is passed to Payment process.
• The Payment Process request for the payment to the Bank which check for the sufficient balance is
present in the customer account or not using the Account Details table.
• If the balance I sufficient the Bank approve for the Payment and then Payment process complete
the payment for the product.
• As soon as the payment is made the Checkout process will reduce the stock of the product
purchased by the customer in the Product record Table.
 Experiment No-7
Objective: Draw the use case diagram for online shopping system. Discuss the role of each
actor and function of each Use-case.

In this diagram, there are two actor: Customer and Vendor. The Vendor can add the product to the
Shopping System to sell its products. The Customer is further classified as New Customer which are not
registered to the shopping system and Existing Customer which has an account of the Shopping System.

• Register Use-case is used by the New Customer which create an account for the new users.
• Login Use-case take the login credentials from user and verify it and give access to the Customer
and Vendor. It is accessed by both Existing Customer and Vendor. If the details are incorrect it
display Invalid Credentials to the user.
• Search Product Use-case will find for the product searched by the user and display it to the user.
• Add item to Cart Use-case will add the item to the bucket of the user and create list of all items
added by the user and generated total amount for the products.
• Add Product Use-case will add the product on the shopping system which make it visible to all the
user.
• Payment Use-case will make the payment for the product purchased. It is further classified as the
user can pay either using Debit Card, Credit Card or UPI.
 Experiment No-8
Objective: Prepare Activity Diagram and UML Diagram for Online shopping System.
 INDEX
S. No. List of Programs Page No.