CSE3001-Software Engineering

Project Report

Title- Velmart- Creating smart cart using

Apriori and FP growth algorithm in an e-
commerce website

Team Members-

Yash Mehta- 19BCE0837

Naman Kumar Thakur- 19BCE2563
Samyak Jain- 19BCE2516
 Software Requirements
Specification
for

Velmart- Creating smart cart

using Apriori and FP growth
algorithm in an e-commerce
website
Prepared by- Yash Mehta (19BCE0837)
Naman Kumar Thakur (19BCE2563)

Samyak Jain (19BCE2516)

Vellore Institute of Technology

08.02.2022
Table of Contents
Table of Contents ......................................................................................................................... iii
Revision History ............................................................................... Error! Bookmark not defined.
1. Introduction ..............................................................................................................................4
1.1 Purpose............................................................................................................................................. 4
1.2 Document Conventions .................................................................................................................... 4
1.3 Intended Audience and Reading Suggestions .................................................................................. 4
1.4 Product Scope .................................................................................................................................. 4
1.5 References ........................................................................................................................................ 2
2. Overall Description ..................................................................................................................5
2.1 Product Perspective.......................................................................................................................... 5
2.2 Product Functions ............................................................................................................................ 5
2.3 User Classes and Characteristics ..................................................................................................... 3
2.4 Operating Environment .................................................................................................................... 4
2.5 Design and Implementation Constraints .......................................................................................... 4
2.6 User Documentation ........................................................................................................................ 4
2.7 Assumptions and Dependencies ...................................................................................................... 5
3. External Interface Requirements ...........................................................................................5
3.1 User Interfaces ................................................................................................................................. 5
3.2 Hardware Interfaces ......................................................................................................................... 5
3.3 Software Interfaces .......................................................................................................................... 5
3.4 Communications Interfaces ............................................................................................................. 6
4. System Features .......................................................................................................................6
4.1 Order History ................................................................................................................................... 6
4.2 Cart Details ...................................................................................................................................... 6
4.3 Product Review ................................................................................................................................ 6
4.4 FAQ.................................................................................................................................................. 6
5. Other Nonfunctional Requirements .......................................................................................7
5.1 Performance Requirements .............................................................................................................. 7
5.2 Safety Requirements ........................................................................................................................ 7
5.3 Security Requirements ..................................................................................................................... 7
5.4 Software Quality Attributes ............................................................................................................. 8
6. Other Requirements ................................................................................................................8
Appendix A: Glossary....................................................................................................................8
Appendix B: Analysis Models .......................................................................................................9
Appendix C: To Be Determined List ....................................................................................................... 12
1. Introduction

1.1 Purpose

This document is meant to delineate the features of VELMART, so as to serve as a guide to

the developers on one hand and a software validation document for the prospective client on
the other. The Online Shopping System for the shop website and application is intended to
provide complete solutions for vendors as well as customers through a single get way using the
internet. It will enable vendors to setup online shops, customer to browse through the shop and
purchase them online without having to visit the shop physically. The administration module
will enable a system administrator to approve and reject requests for new shops and maintain
various lists of shop category.
The product whose SRS is being specified in the current document is an E Commerce website
and application solely run by and for project purpose using scripting languages. The release is
to be made in the upcoming weeks around April. This is being done to promote the overall
sales of the enterprise and make a easy process for buyers to purchase from the firm.

1.2 Document Conventions

Font- Times New Roman

Font Size- 12
Heading- Bold

1.3 Intended Audience and Reading Suggestions

The document is intended to be analysed by the frontend and backend developers, stakeholders,
investors, resource managers, testers, team members and company owners.
The SRS contains an overview of the project with scope, deliverables, performa, overall
description and everything that would be required to work on the project. It basically contains
an overall requirement for the investors and business owners to let them know what all things
would be required beforehand.
The document is in an organized order and could be easily read and interpreted by the readers.

1.4 Product Scope

Software Requirements Specification Document (SRS) gives business owners a clear vision of
how much does it cost to develop their custom software product.

We’re basically dividing our project into 2 frames: frontend and back- end where the
programming languages used are HTML, SQL, PHP, CSS and JavaScript.

Project to help us run our website offline. This XAMPP server software gives us the suitable
environment for testing MYSQL and PHP projects on the local computer.

The frontend part is what the user witnesses when he logs into the website which is a
combination of HTML codes which gives us the structure and CSS which is used for the
presentation of Web pages, including colors, layout, and fonts.
The backend portion mainly consists of SQL queries which helps us to retrieve the User
credentials, Cart Orders, FAQs and the necessary details which could be saved without any
objections. PHP is used to connect our SQL database to the website. Cart orders, order quantity,
requirements through FAQs, reviews and payment details can be administered by the website
owner

1.5 References

[1] The applicable IEEE standards are published in “IEEE Standards Collection,” 2001 edition.
[Bruade] The principal source of textbook material is “Software Engineering: An Object-
Oriented Perspective” by Eric J. Bruade (Wiley 2001).

[2] SRS Document Proposal Analysis on the Design of Management. According to IEEE STD
830-1998, The 3rd International Conference on e-Learning ICEL 2011, 23-24 November 2011,
Bandung, Indonesia, Eko Handoyoa, R Rizal Isnantoa, Mikhail Anachiva Sondaa a
Diponegoro University, Indonesia.Overall Description.

2. Overall Description

2.1 Product Perspective

VELMART is an online website which supports shopping via web and supports a number of
functions both for customer and our VELMART’S management. VELMART will also be used
as app name which is app version of our website.

This product has two objectives

1. This is an online smart e-commerce store, so it aids us to reach more people on web.
2. The people who want to purchase can’t visit the shop as they might not be having time
or maybe they live very far from the shop, so our (VELMART) online store aims to
deliver our products to the users(customers) more efficiently, using a website.

2.2 Product Functions

These are the numerous functions used –

INVERTORY MANAGEMENT
~Allows manager to specify stop-order for a velvet which won’t be sold now as of being
outdated or out of stock.
~Allows manager to add/update the inventory.

CATEGORY MANAGEMENT
~Maintains records for all the categories of the products that are to be displayed to the user.
~Also keeps the record of the quantity, price, material etc.

CART MANAGEMENT
~Allowing to add, remove and replace any material added.

USER LOG MANAGEMENT

~Any customer can log in, any person can sign up for a customer account and log in.
~Customer would have option to log in, log out, update to member (for only trusted customers)

SHIPPING MANAGEMENT
~Allows any customer when they place any order to track their delivery at any instant and
receiver their order.

ORDER MANAGEMENT
~Allows any user to place and order whatever they like.

PROFILE MANAGEMENT
~Allows any user to create, update their profile(account)

FAQ MANAGEMENT
~Allows any user, manager to post any query, ask any question and answer to that query.

2.3 User Classes and Characteristics

Database and server manager-Updating the database with all products available and out of
stock or outdated, server manager to checkout all server requests and execute accordingly.

Users-
Users who want to use this for their hotels, buildings, apartments etc.

Amateur users-
Users who want to use for their own use.

Our project will support two user privileges-

Customers Management(managers)
Customers(users) should be able to retrieve all the information, about products, about
shipping start to delivery from the database, offers etc.

Customers -
View product details, offers available and profile info Ordering item.
Adding to cart, removing an item from cart Creating, updating and upgrading account
Processing of payment and view shipping details.

Management -
Managers should be able to update the website according to the stock and managing every
important aspect of website and app.

For management (Administration)-

Get all order items, total billing amount.
Get all shipping schedule and delay in delivery.
Add new item, removing out of stock and outdated item Update shipping schedules.

2.4 Operating Environment

Operating environment for our project VELMART is as listed below.

WEBSITE :
XAMPP for helping local host to test websites.
XAMPP is the local web server used in the project to help us run our website offline.

WBS:
Microsoft Visio for WBS.

Operating system:
Windows and Mac (different member)

Programming languages :
Programming languages used are HTML, SQL, PHP, CSS and Javascript.

2.5 Design and Implementation Constraints

1. User should have minimum android KitKat 4.4 and all versions for IOS.
2. User should have proper internet connectivity.
3. Minimum requirement for windows is XP and for MAC (no restriction).

2.6 User Documentation

User will be provided about FAQ page and customer care number beforehand to solve any
query about any issue they face.
We will update further, as much progress we make in our business if possible, in website.

HTML (Hypertext Markup Language) is the most basic building block of the Web.
It defines the meaning and structure of web content. Other technologies besides HTML are
generally used to describe a web page's appearance/ presentation (CSS) or
functionality/behavior (JavaScript).
https://devdocs.io/html/
https://developer.mozilla.org/en-US/docs/Web/HTML

Cascading Style Sheets (CSS) is a stylesheet language used to describe the presentation of a
document written in HTML or XML (including XML dialects such as SVG, MathML or
XHTML).
CSS describes how elements should be rendered on screen, on paper, in speech, or on other
media.
https://developer.mozilla.org/en-US/docs/Web/CSS

PHP documentation
https://www.php.net/docs.php
https://www.php.net/download-docs

PHP SQL documentation

https://docs.microsoft.com/en-us/sql/?view=sql-server-ver15
https://dev.mysql.com/doc/

2.7 Assumptions and Dependencies

Assumption is basically that the designed website or software will be working correctly for
both end users and providing the best cost for the items we provide and could be displayed to
user with all delayed and delivery time being shown.

Users have a good experience in handling the ordering and cancelling item or paying using any
mode.
3. External Interface Requirements

3.1 User Interfaces

User should be able to see the interface for login /signup page, view all products, order
products, placing orders page, cart page and profile page, able to appropriately use the FAQ
page, should be able to see all the offer and coupons page, tracking shipping details page etc.

WEBSITE
Front-end software: HTML, CSS, JAVASCRIPT Back-end software: PHP, SQL.

3.2 Hardware Interfaces

Windows, MAC or LINUX or any other Operating System

A browser which supports HTML, JavaScript, CSS, SQL and other basic requirements.
Following are the PC requirements for a proper functionality –
Minimum 2GB RAM
Minimum 4GB ROM
Pentium or any other processor.

Android KitKat 4.4 and above, any IOS.

3.3 Software Interfaces

Software used Description

Operating system We have chosen Windows operating system for its best
support and user-friendliness. But this software can be used
on any operating system with a web browser which supports
HTML and JAVASCRIPT.
Database To save the customer orders, product details and customer
details we have chosen SQL database.
Xampp To implement the project we have chosen Xampp to create a
working environment on our system.

3.4 Communications Interfaces

This project supports all types of web browsers. We are using internet and web browser to visit
the website and place an order. The ordering system of the website shall give an e-mail
confirmation to the customer that the goods purchased will be sent to the mailing address along
with the identity of the buyer. Users will be able to avail every information about product, cart,
order, delivery in proper internet connectivity, Database would be updated frequently to
provide best experience
and in this way with good internet connectivity communication would be effective and
efficient.
4. System Features

We may prefer to organize this section by use case, mode of operation, user class, object class,
functional hierarchy, or combinations of these, whatever It makes the most logical sense for
your product.

4.1 Order History

1. User can see their order history, repeat their orders. It is of low priority.
2. After user confirms his order and the order is completed it would be reflected on his
order history page. It would show the number of items bought, quantity, total cost, etc.

4.2 Cart Details-

1. After viewing the product user can add items to the cart as per requirement
2. and review it if the user wants to purchase it.
3. User cannot access cart if he/she is logged out. It is of high priority. He/ she can only
add items to cart if they are logged in.
The cart would display the number of items, quantity, total cost, etc present in the
cart.

4.3 Product Review-

1. User can review any number of products they want any number of times.
2. User can do so by going to respective product page and writing a review for the
purchased products if and only if he/she has purchased the particular item because
trusted reviews should be entertained
3. The backend team could monitor all the reviews given to all the products by the users
without the access of manipulating the as only the administrator could do so.

4.4 FAQs-

1. User can also ask questions related to the online store, product or any other enquiries.
2. It can be done by the drop-down box in the right-hand side of the page. All questions
will be answered by the team.
3. It would help to increase user interaction and the feedback will help the SDE team to
improvise further.
REQ 1: PC with any OS but an average and constant internet connection and an interenet
explorer like Chrome or Mozilla.

REQ 2: A smartphone or iPhone with internet and a proper user account to download the app
if published on large scale.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

5.1.1 Performance
Being a web-based application, it has to be run from a web server. The product shall take initial
load time depending on internet connection strength and the media device from which the
product is run. The performance shall depend upon hardware components of the
client/customer as well. The system shall be robust enough to have a high degree of fault
tolerance.

5.1.2 Capacity
The maximum capacity for a Mongo database running on a Windows Server is 64 terabytes.

5.2 Safety Requirements

The product causes no harm to the user. Although, the user must not share his credentials with
anyone, as sensitive information could fall into the wrong hands. It is essential that the user
keeps his/her credentials private.

5.3 Security Requirements

5.3.1 Data Transfer

The system uses secure sockets in all transactions that include any confidential customer
information. The system shall not leave any cookies on the customer’s computer containing
the user’s password. It shall not leave any cookies on the customer’s computer containing any
of the user’s confidential information.

5.3.2 Data Storage

The user’s password shall always be echoed with special characters representing typed
characters. The password is hash protected and then stored in the database. The system’s back-
end servers shall never display a customer’s password. The customer’s password may be reset
but never shown. The system’s back-end servers shall only be accessible to authenticated
administrators.

5.4 Software Quality Attributes

5.4.1 Flexibility
The proposed system is fully responsive and can be accessed from both a computer and a
mobile device. It is fully proportional for multiple devices and can automatically adjust to fit
multiple screen sizes.

5.4.2 Reliability
The proposed system will be reliable. Data will be protected even in undesirable conditions.
The system shall compensate customer experience for anything.

5.4.2.1 Maximum bug rate

There will be a maximum of 1 bug/KLOC.

5.4.2.2 Maximum time to repair

The maximum time to repair database is less than 2-3 minutes.
6. Other Requirements

6.1 Gantt Chart

6.2 Timeline Chart

6.3 WBS

6.4 Architecture
6.5 Data Flow Diagram

6.6 Entity-Relationship Diagram

 Software Design
Specification

Velmart-Creating smart cart using

Apriori and FP growth algorithm in
an e-commerce website
Revision 1.0

By- Yash Mehta (19BCE0837)

Naman Kumar Thakur (19BCE2563)
Samyak Jain (19BCE2516)

Development Revision 1.0 Page i Velmart

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ........................................................................................................................... iii
Approved By ................................................................................................................................. iii
1. Introduction ..............................................................................................................................1
1.1 Purpose ........................................................................................................................................ 1
1.2 System Overview......................................................................................................................... 1
1.3 Design Map ................................................................................................................................. 1
1.4 Supporting Materials ..................................................................Error! Bookmark not defined.
1.5 Definitions and Acronyms ........................................................................................................... 1
2. Design Considerations .............................................................................................................1
2.1 Assumptions ................................................................................................................................ 1
2.2 Constraints ................................................................................................................................... 2
2.3 System Environment ................................................................................................................... 2
2.4 Design Methodology ................................................................................................................... 2
2.5 Risks and Volatile Areas ............................................................................................................. 2
3. Architecture ..............................................................................................................................8
3.1 Overview ..................................................................................................................................... 8
3.2 Subsystem, Component, or Module 1 …N.................................................................................. 8
3.3 Strategy 1…N .............................................................................................................................. 8
4. Database Schema .....................................................................................................................9
4.1 Tables, Fields and Relationships ................................................................................................. 9
4.1.1 Databases................................................................................................................................. 9
4.1.2 New Tables.............................................................................................................................. 9
4.1.3 New Fields(s) .......................................................................................................................... 9
4.1.4 Fields Change(s)...................................................................................................................... 9
4.1.5 All Other Changes ................................................................................................................... 9
4.2 Data Migration........................................................................................................................... 10
5. High Level Design ..................................................................................................................12
5.1 View / Model Element 1…N ..................................................................................................... 12
6. Low Level Design ...................................................................................................................13
6.1 Module 1…N ............................................................................................................................. 13
7. User Interface Design ............................................................................................................14
7.1 Application Controls ................................................................................................................. 14
7.2 Screen 1… N ............................................................................................................................. 14
Appendix A: Project Timeline ....................................................................................................15

Development Revision 1.0 Page ii Velmart

Revision History
Version Name Reason For Changes Date
1.0 Yash Mehta Initial Revision 01/03/2022
(19BCE0837) UML Models
-Use Case
Naman Kumar -Class
Thakur
-State Chart
(19BCE2563)
-Activity
-Sequence
Samyak Jain
-Collaboration
(19BCE2516)
-Deployment
ER Model
Architecture-System Model
-Objectives
Low Level Design- Pseudocode for possible modules
User Interface

Approved By
Approvals should be obtained for project manager, and all developers working on the project.

Name Signature Department Date

Development Revision 1.0 Page iii Velmart

1. Introduction

1.1 Purpose
This design will detail the implementation of the requirements as defined in the Software Requirements
Specification – Velmart – Phase 2.

1.2 System Overview

This project extends the functionality of the Velmart. Additional fields and features will be added to the
website, new workflow sub-processes will be added to the smart cart process.

1.3 Design Map

Use Case Diagram- It is a graphical depiction of a user's possible interactions with a system.
Class Diagram- The class diagram is the main building block of object-oriented modeling. It is used for general
conceptual modeling of the structure of the application.
State Chart Diagram- It is a type of diagram used in computer science and related fields to describe the behavior of
systems.
Activity Diagram- Activity diagram visually presents a series of actions or flow of control in a system similar to a
flowchart or a data flow diagram.
Sequence Diagram- It is a type of interaction diagram because it describes how—and in what order—a group of
objects works together.
Collaboration Diagram- It is an illustration of the relationships and interactions among software objects.
Deployment Model- It shows the execution architecture of a system.

1.4 Definitions and Acronyms

Task – One step or piece of a workflow

Apriori- It uses prior knowledge of frequent itemset properties.
FP Growth- FP growth algorithm represents the database in the form of a tree called a frequent
pattern tree or FP tree.

2. Design Considerations
Following designs will be used for developing of the project.

2.1 Assumptions
This is an ecommerce website designed for users to smoothly purchase their goods.

Development Revision 1.0 Page 1 Velmart

2.2 Constraints
This application can only run on a system that supports web browser and has internet connection.

2.3 System Environment

System should support web browser and JavaScript. It should also have stable internet connection for
website to load for smooth user experience.

2.4 Design Methodology

OOAD- Object-oriented analysis and design is a technical approach for analyzing and designing an
application, system, or business by applying object-oriented programming, as well as using visual modeling
throughout the software development process to guide stakeholder communication and product quality.

2.5 Risks and Volatile Areas

None have been identified.

Development Revision 1.0 Page 2 Velmart

UML Diagrams-

-USE Case Diagram

Development Revision 1.0 Page 3 Velmart

-Class Diagram

-State Chart Diagram

Development Revision 1.0 Page 4 Velmart

-Activity Diagram

Development Revision 1.0 Page 5 Velmart

-Sequence Diagram

Development Revision 1.0 Page 6 Velmart

-Collaboration Diagram

-Deployment Diagram

Development Revision 1.0 Page 7 Velmart

3. Architecture

3.1 Overview
This section provides a high level overview of the structural and functional decomposition of the system.

3.2 Subsystem and Modules

INVERTORY MANAGEMENT
~Allows manager to specify stop-order for a velvet which won’t be sold now as of being outdated or out
of stock.
~Allows manager to add/update the inventory.

CATEGORY MANAGEMENT
~Maintains records for all the categories of the products that are to be displayed to the user.
~Also keeps the record of the quantity, price, material etc.

CART MANAGEMENT
~Allowing to add, remove and replace any material added.

USER LOG MANAGEMENT

~Any customer can log in, any person can sign up for a customer account and log in.
~Customer would have option to log in, log out, update to member (for only trusted customers)

SHIPPING MANAGEMENT
~Allows any customer when they place any order to track their delivery at any instant and receiver their
order.

ORDER MANAGEMENT
~Allows any user to place and order whatever they like.

PROFILE MANAGEMENT
~Allows any user to create, update their profile(account)

FAQ MANAGEMENT
~Allows any user, manager to post any query, ask any question and answer to that query.

3.3 Strategy

3.31 Order History

1. User can see their order history, repeat their orders. It is of low priority.

Development Revision 1.0 Page 8 Velmart

 2. After user confirms his order and the order is completed it would be reflected on his order
history page. It would show the number of items bought, quantity, total cost, etc.

3.32 Cart Details-

1. After viewing the product user can add items to the cart as per requirement
2. and review it if the user wants to purchase it.
3. User cannot access cart if he/she is logged out. It is of high priority. He/ she can only add
items to cart if they are logged in.
The cart would display the number of items, quantity, total cost, etc present in the cart.

3.33 Product Review-

1. User can review any number of products they want any number of times.
2. User can do so by going to respective product page and writing a review for the purchased
products if and only if he/she has purchased the particular item because trusted reviews
should be entertained
3. The backend team could monitor all the reviews given to all the products by the users
without the access of manipulating the as only the administrator could do so.

3.34 FAQs-

1. User can also ask questions related to the online store, product or any other enquiries.
2. It can be done by the drop-down box in the right-hand side of the page. All questions will be
answered by the team.
3. It would help to increase user interaction and the feedback will help the SDE team to
improvise further.

4. Database Schema

4.1 Tables, Fields and Relationships

Table Fields
1. User ID, Password
2. Administrator Email, Password
3. Customer C_ID, C_Name,
C_Phone_Number
4. Category Category_ID, Category

Development Revision 1.0 Page 9 Velmart

 _Name
5. Products Product_ID, P_Name,
Stock, Price
6. Cart Cart_ID, Quantity, Cost
7. Review Review_ID, Review
8. Order Order_ID, Total_Amount,
Date
9. FAQ Question, Answer
10. Shipping Info Name, Address,
Ph_Number
11. Order History Quantity, Cost

4.1.1 Databases

MySQL database to be used. Integrating with php.

4.1.2 New Tables

Not Applicable.

4.1.3 New Fields(s)

Not Applicable

4.1.4 Fields Change(s)

Not Applicable

4.1.5 All Other Changes

No Changes.

4.2 Data Migration

(Optional) - Provide a description of how existing data should be migrated to new tables and fields.

Development Revision 1.0 Page 10 Velmart

ER-Diagram

Development Revision 1.0 Page 11 Velmart

5. High Level Design

5.1 Smart Cart

Every user will have a personalized smart cart. That cart will have products frequently bought by that user.
User can directly add products to his cart. Combos will also be offered to user for frequently bought together
products.

5.2 User Interface Modifications

User will be able to view their previous orders in their order history tab. They can change their
password, name and other details.

5.3 Workflow sub-processes

Workflow subprocesses will be created for each individual order placed by user. Each order will
have a unique order id and shipping information. User can view the order status as in process or
delivered.

6. Low Level Design

This section provides low-level design descriptions that directly support construction of modules. Normally
this section would be split into separate documents for different areas of the design.

6.1 User Options

6.1.1 Login/ Signup

User will be able to sign in or create an account using email and password.

6.1.2 Add product to cart button

User can add as many products as they want in cart without any constraints.

6.1.3 Checkout Button

The checkout button in cart page will confirm the order and ask for shipping information
from user to deliver the product.

Development Revision 1.0 Page 12 Velmart

6.1.4 Placing Order

Order history, each order will have a unique order id and shipping information. User can
view the order status as in process or delivered.

6.1.5 Other Changes

User can edit their personal details such as name information, and password.

6.2 Workflow sub-processes

Workflow subprocesses will be created for each individual order placed by user. Each order will
have a unique order id and shipping information. User can view the order status as in process or
delivered.

7. User Interface Design

This section provides user interface design descriptions that directly support construction of user interface
screens.

7.1 Application Controls

Detail the common behavior that all screens will have. Common look and feel details such as menus, popup
menus, toolbars, status bar, title bars, drag and drop mouse behavior should be described here.

7.2 Screen
Product Page-

Development Revision 1.0 Page 13 Velmart

Billing Page-

7.2.1 Workflow Reports

Appendix A: Project Timeline..

Development Revision 1.0 Page 14 Velmart

 Software GUI

Velmart-Creating smart cart using

Apriori and FP growth algorithm in
an e-commerce website
Revision 1.0

By- Yash Mehta (19BCE0837)

Naman Kumar Thakur (19BCE2563)
Samyak Jain (19BCE2516)

Development Revision 1.0 Page i Velmart

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ........................................................................................................................... iii
Approved By ................................................................................................................................. iii
1. Introduction .............................................................................. Error! Bookmark not defined.1
1.1 Sign-up Page .............................................................................................................................. 1
1.2 Home Page ................................................................................................................................. 1
1.3 Landing Page ............................................................................................................................. 2
1.4 Shop Page .................................................................................................................................... 2
1.5 Product Page ................................................................................................................................ 3
1.6 Cart Page .................................................................................................................................... 3
1.7 Billing Page ............................................................................................................................... 4
1.8 Checkout-shipping Page .............................................................................................................. 4
1.9 Profile Page ................................................................................................................................ 5
1.10 Review Page .............................................................................................................................. 5
1.11 Login Page ................................................................................................................................... 6

Development Revision 1.0 Page ii Velmart

Revision History
Version Name Reason For Changes Date
1.0 Yash Mehta Graphical User Interface 15/03/2022
(19BCE0837)

Naman Kumar
Thakur
(19BCE2563)

Samyak Jain
(19BCE2516)

Approved By
Approvals should be obtained for project manager, and all developers working on the project.

Name Signature Department Date

Development Revision 1.0 Page iii Velmart

1. Graphical User Interface

1) Sign-up Page

2) Home Page

Development Revision 1.0 Page 1 Velmart

3) Landing Page

4) Shop Page

Development Revision 1.0 Page 2 Velmart

5) Product Page

6) Cart Page

Development Revision 1.0 Page 3 Velmart

7) Billing Page

8) Checkout-shipping Page

Development Revision 1.0 Page 4 Velmart

9) Profile Page

10) Review Page

Development Revision 1.0 Page 5 Velmart

11) Login Page

Development Revision 1.0 Page 6 Velmart

 Software Testing

Velmart-Creating smart cart using

Apriori and FP growth algorithm in
an e-commerce website
Revision 1.0

By- Yash Mehta (19BCE0837)

Naman Kumar Thakur (19BCE2563)
Samyak Jain (19BCE2516)
1. Manual test cases-

Test Test Test Data Expected Actual Status

ID Name Output Output (Pass/ Fail)
Test Login Using invalid credentials Invalid Email Invalid Fail
Case 1 Email
Email- abc@gmail
Password- 123
Test Login Using valid credentials Login Login Pass
Case 2 Successful Successful
Email- [email protected]
Password- 123
Test Updating New Name- xyz Name Name Pass
Case 3 user name Updated Updated
Successfully Successfully
Test Update Using Different Passwords Passwords Fail
Case 4 Password Password- not match not match
Old Password- 123
New Password- 12345
Confirm New Password-
1234
Test Change Using Different Password Password Pass
Case 5 Password Password- changed changed
successfully successfully
Old Password- 123
New Password- 12345
Confirm New Password-
12345
Test Add Adding a product to cart Product Product Pass
Case 6 product to added added
cart successfully successfully
Test Search Search item in search bar Item Item Pass
Case 7 displayed displayed
2. Automated test cases using any open source testing tool of project modules

Testing Tool-
Selenium-
Selenium is an open-source automated testing framework used to validate web
applications across different browsers and platforms. It is one of the most widely
used open source Web UI automation testing suite. It can be easily deployed on
platforms such as Windows, Linux, Solaris and Macintosh. Moreover, it supports
OS for mobile applications like iOS, windows mobile and android. Selenium
supports a variety of programming languages through the use of drivers specific
to each language. Languages supported by Selenium include C#, Java, Perl, PHP,
Python and Ruby. Few other features of selenium are as follows:
Lesser resources required – Selenium requires lesser resources when compared
to its competitors like UFT, RFT, etc.
• Parallel Test Execution – It also supports parallel test execution which
reduces time and increases the efficiency of tests.
• No installation Required - Selenium web drivers do not require server
installation, test scripts interact directly with the browser
• Increased test coverage – With the uses of Selenium, testing time gets
reduced and hence the tester can do more testing on other test scenarios
at the same time.
• Cost reduction for Clients – The Business needs to pay the testers their
salary, which is saved using automation testing tool. The automation not
only saves time but gets cost benefits too, to the business.
• Easier to understand and implement – Selenium commands are categorized
in terms of different classes which make it easier to understand and
implement.
Test Case Report From Selenium IDE-
Reference-
https://www.selenium.dev/
 Velmart- Creating smart cart using Apriori and FP
growth algorithm in an e-commerce website
Yash Mehta Samyak Jain Naman Kumar Thakur
School of Computer Science and School of Computer Science and School of Computer Science and
Engineering Engineering Engineering
Vellore Institute of Technology Vellore Institute of Technology Vellore Institute of Technology
Vellore, India Vellore, India Vellore, India
yash.mehta2019@vitstudent. samyak.jain2019a@vitstuden namankumar.thakur2019@vits
ac.in t.ac.in tudent.ac.in

Dr. SWARNALATHA P
School of Computer Science and
Engineering
Vellore Institute of Technology
Vellore, India
[email protected]

Abstract— In this era of internet, e-commerce is growing scarce and expensive because of their socio-economic
by leaps and bounds keeping the growth of businesses in condition.
the dust. Our project is an E-Commerce website (similar
to Amazon, Flipkart) for Velvet products. We have
created a fully functioning website using HTML, SQL, II. LITERATURE REVIEW
PHP, CSS and JavaScript with a database of all the Title: Design and Implementation for an Ecommerce
products that we offer. The users have to first sign-up on Development
the website and then choose the product they want to Author: He JunHua
purchase from the various categories available. The users Methodology: Included multi-tiered architecture, server and
will get a personalized cart containing their regular client side scripting techniques, implementation, here
purchases for faster checkout. This will help the user to consumer is provided with a shopping cart application and
order in an effective manner. also to know about the technologies used to develop such an
application.
Keywords— E-commerce, Product Recommendation,
Drawback: a)The existing system can reach large numbers
Apriori Algorithm, FP Growth Algorithm
of users and their friends
I. INTRODUCTION b) It can obtain users’ personal information such as email
address, home town, and gender, and etc. and also“re-
During these tough times, when small-scale businesses are
produce" by making other malicious apps popular.
suffering and for the overall growth of small businesses, we
need to develop a website which would be a business specific
E-Commerce platform. The people who are far away and they Title: Security and Privacy Issues as a Potential Risk for
are having any issues or if there is a lockdown, could order Further E- commerce Development(Assoc. Prof. Dr. Rashad
from VELMART feasibly. The main aim of this project is to Yazdanifard)
fill the gap between buyers and sellers with the help of an e- Author: Rashad Yazdanifard1 , Noor Al-Huda Edres2 and
commerce website which will be beneficial to both of them. Arash Pour Seyedi3
Sellers will be able to sell their products without any issues Methodology: Introducing a P3P system into company’s
and buyers can get their needs fulfilled easily. sites that shows customers how the site collects handles and
uses their personal information is also advisable.
Our aim is to bring grocery items and similar products online
Drawback: Companies must take actions or more precisely
while simultaneously providing a seamless experience to our
customers. The people who want grocery can’t visit the shop increase the quality and amount of measures they provide in
as they might not be having time or maybe they live very far order to deliver secure, less risky services to customer
from the shop, so our (VELMART) online store aims to
deliver our products to the users(customers) more efficiently, Title: The Evolution of Social Commerce: The People,
using a website. Users can directly place their order from our Management, Technology, and Information Dimensions
Website. Author: Wang, C., & Zhang, P.
Methodology: Untraceable off line electronic cash flow in e-
The entire development process will be primarily divided into commerce
three parts: the front-end development, the back-end Drawback: Electronic cash and e-commerce security
development and the machine learning model development
part. The database design is also discussed with an emphasis
on its relational connectivity. This method of developing an Title: The Evolution of Software Process Models: From the
e-commerce website can be easily replicated and followed in Waterfall Model to the Unified Modeling Language (UML)
developing e-commerce websites in the developing and Author: Saad Subair
under-developed countries where computing resources are Methodology: Real time examples of using this process
model, advantages and disadvantages. The conventional
activities of problem solving in software development phase thereby giving the customers an opportunity to see the
consists of: Analyze the problem, Plana solution for the product early in the life cycle. [Fig 1]
problem, Code the solution, Test the coded program, and
Maintain the program The Reason to choose the particular prototype model was
Drawback: The duration of time from the start of the project because if the customer is not clear with the idea we just ask
to the delivery time of a solution is very high. Various models him for the modifications needed and could be implemented
and approaches of system development have been reviewed later. It is good for technical and requirement risks which
and discussed in this study. Each model has its own mean if the customer is not clear with his technical
advantages and disadvantages. specifications we could suggest to him a probable model
and plan with this process model. This kind of project needs
Title: Consumer-driven e-commerce: A literature review, constant updating of goods and features based on the
design framework, and research agenda on last-mile logistics customer reviews, FAQs and suggestions gathered through
emails which inclines us to proceed with this particular
models (Li et al., 2011)
Author:Stanley Frederick W.T. Lim, Xin Jin, Jagjit Singh
Srai
Methodology: Privacy-aware access control with trust
management in web service. The systematic literature review
examines the interface between e-commerce and LML.
Following a protocol-driven methodology, combined with a
“snowballing” technique, a total of 47 articles form the basis
of the review. To circumvent subjective selection of articles
for inclusion, all papers were assessed independently by two
researchers and counterchecked with two independent
logistics experts.
Drawback: Privacy is a major concern in mobile commerce.
From a theoretical contribution perspective, this paper
identifies attributes of delivery performance linked to
product-market segments and the system dynamics that
underpin them

III. METHODOLOGY Fig1. Evolutionary Prototyping Model

A. Process Model model. Increase in cost of development - Both an advantage
The Evolutionary Prototyping Model is one of the most and disadvantage as it is easier for us to provide the toy or
popularly used Software Development Life Cycle Models rough model before implementation but also at the same
(SDLC models).This model is used when the customers do time everything has to be recreated every time.
not know the exact project requirements beforehand. In this
model, a prototype of the end product is first developed,
B. Planning and Execution
tested and refined as per customer feedback repeatedly till a
final acceptable prototype is achieved which forms the basis We have divided the work in different segments and have
for developing the final product. In this process model, the given a specific time to complete each segment and move to
system is partially implemented before or during the analysis the next segment. In [Fig 2] gantt chart has been made to
trace the timeline of the project. Gantt chart is a type of bar

chart that illustrates a project schedule.

C. PRODUCT CUSTOMER REQUIREMENT etc. This project supports all types of web browsers. We are
using the internet and web browser to visit the website and
place an order. The ordering system of the website shall give
an email confirmation to the customer that the goods
purchased will be sent to the mailing address along with the
identity of the buyer.

Non-Functional Requirements:
System - This section lists the hardware and software
requirements for model-driven apps and mobile device client
applications. This website could easily be accessed on a PC
running windows or any other Operating System like
Windows , MacOS etc. The online shopping system protects
the users account and his payments details and personal login
Fig4. Product Requirements addresses . When a buyer types or inserts an incorrect
username or password in the login page, the system displays
Functional Requirements: an error message. Also the users' personal details need to be
User Interfaces – User should be able to see the interface for secured in the database and should also have a local backup.
The user must be a verified customer and he/she would be
login /signup page, view all products ,order products, placing
blocked by the administrator if some kind of unethical
orders page, cart page and profile page , able to appropriately
use the FAQ page , should be able to see all the offer and activities are noticed on the website or application. The
addresses should be valid and the payments should be in a
coupons page , tracking shipping details page
verified manner.

Fig5. Functional Requirements

Fig6. Non-Functional Requirements
D. Software Modules After viewing the product user can add items to the cart as
per requirement and review it if the user wants to purchase
it. User cannot access cart if he/she is logged out. It is of
Module 1: Homepage high priority. He/ she can only add items to cart if they are
logged in. The cart would display the number of items,
The homepage is the face of the website. It displays all the quantity, total cost, etc present in the cart.
latest products and offers a unique design interface. It also
displays the various product categories.
Module 5: Account
Module 2: Category Every customer has to make an account with the website for
shopping on it. They have to enter their Name, Email ID and
All the products that are listed on the platform are segregated password during signup. After that otp will be sent to their
into various categories for a better shopping experience and email id and it will be validated. Then user can view the
to make everyone's life easier. products and add them to cart and place order.

Module 3: Products Module 6: FAQs

We have a range of products like grocery items. User can Customers can send their queries on the website regarding
review any number of products they want any number of any of the products or services. This will help us deliver a
times. User can do so by going to respective product page and better experience to our customers. User can also ask
writing a review for the purchased products if and only if questions related to the online store, product or any other
he/she has purchased the particular item because trusted enquiries. It can be done by the drop-down box in the right-
reviews should be entertained hand side of the page. All questions will be answered by the
team. It would help to increase user interaction and the
feedback will help the SDE team to improvise further.
Module 4: Cart
The cart is the place where all the products that the customer
has chosen will be shown with all the product details, prices,
quantity, billing details, Total cost, etc
E. Required Diagrams for Software Development
 IV. RESULTS & CONCLUSION [4] Saad Subair. The Evolution of Software Process Models:
From the Waterfall Model to the Unified Modeling Language
We created a website for basically those who can’t or don’t (UML).
want to visit our store because of distance or lack of time, so
[5] Stanley Frederick W.T. Lim, Xin Jin, Jagjit Singh Srai.
this provides users with all the products which are available
Consumer-driven e-commerce: A literature review, design
on store to them on the website online, so as they can buy
framework, and research agenda on last-mile logistics models (Li et
products from then and there. This provides us a free hand al., 2011)
also over the store as we can directly access the website and [6] Pekka Abrahamsson, Outi Salo, Jussi Ronkainen, Juhani
can update products and manage everything corresponding to Warsta. Agile Software Development Methods: Review and Analysis
the user, products and everything related to the website. So it [7] Henri Barki,Suzanne Rivard &Jean Talbot. Toward an
is an online website (VELMART) for shopping products like Assessment of Software Development Risk
grocery etc easily and efficiently. [8] H.D. Mills. Software Development
[9] Justus D. Naumann and A. Milton Jenkins. Prototyping: The
New Paradigm for Systems Development
ACKNOWLEDGMENT [10] Vaibhav Bhatnagar &Ramesh C. Poonia. Design of prototype
model for irrigation based decision support system
We are grateful to Dr. Swarnalatha P for guiding us [11] Vaibhav Bhatnagar &Ramesh C. Poonia. A prototype model for
throughout the research, helping us to attain effective results decision support system of NPK fertilization
and motivating us throughout the work. [12] Susan Sproule, Norm Archer. A buyer behaviour framework for
the development and design of software agents in e‐commerce
REFERENCES [13] Ms.Ayushi Y. Vadwala. E-Commerce: Merits and Demerits A
[1] He JunHua. Design and Implementation for an Review Paper
Ecommerce Development. [14] Tom Addison. E-commerce project development risks: evidence
[2] Rashad Yazdanifard1 , Noor Al-Huda Edres2 and Arash from a Delphi survey
Pour Seyedi3 . Security and Privacy Issues as a Potential Risk for [15] M. S. Krishnan &Ramanath Subramanyam. Quality Dimensions
Further E- commerce Development(Assoc. Prof. Dr. Rashad in E-Commerce Software Tools: An Empirical Analysis of North
Yazdanifard) American and Japanese Markets.
[3] Wang, C., & Zhang, P. The Evolution of Social
Commerce: The People, Management, Technology, and Information
Dimensions
 PLAGIARISM SCAN REPORT

Date 2022-04-23

9% 91% Words 999

Plagiarised Unique

Characters 11428

Content Checked For Plagiarism

Velmart- Creating smart cart using Apriori and FP

growth algorithm in an e-commerce website

Yash Mehta Samyak Jain Naman KumarThakur

School of Computer Science and School of Computer Science and School of Computer
Science and
Engineering Engineering Engineering
Vellore Institute of Technology Vellore Institute of Technology Vellore Institute of Technology
Vellore, India Vellore, India Vellore, India
yash.mehta2019@vitstudent. samyak.jain2019a@vitstuden namankumar.thakur2019@vits
ac.in t.ac.in tudent.ac.in

Dr. SWARNALATHAP
School of Computer Science and
Engineering
Vellore Institute of Technology
Vellore, India
[email protected]

Abstract— In this era of internet, e-commerce is in the developing and under-developed countries
where
growing by leaps and bounds keeping the growth of computing resources are scarce and expensive
because of
businesses in the dust. Our project is an E-Commerce their socio-economic condition.
website (similar to Amazon, Flipkart) for Velvet
products. We have created a fully functioning website
using HTML, SQL, PHP, CSS and JavaScript with a II. LITERATURE REVIEW
database of all the products that we offer. The users have
Title: Design and Implementation for an Ecommerce
to first sign-up on the website and then choose the
Development
product they want to purchase from the various
Author: He JunHua
categories available. The users will get a personalized
Methodology: Included multi-tiered architecture, server and
cart containing their regular purchases for faster
client side scripting techniques, implementation, here
checkout. This will help the user to order in an effective
consumer is provided cart application and
manner.
also to know used to develop such an
application.
Keywords— E-commerce, Product Recommendation,
Drawback: a)The existing system can reach large numbers

Page 1 of 4
 Apriori Algorithm, FPGrowthAlgorithm
of users and their friends
I. INTRODUCTION b) It can obtain users’ personal information such as email
address, home town, and gender, and etc. and
During these tough times, when small-scale businesses
also“re-produce" by making other malicious apps popular.
are suffering and for the overall growth of small businesses,
we need to develop a website which would be a business
Title: Security and Privacy Issues as a Potential Risk for
specific E-Commerce platform. The people who are far
away and they are having any issues or if there is a Further E- commerce Development(Assoc. Prof. Dr.
Rashad
lockdown, could order from VELMART feasibly. The main Yazdanifard)
aim of this project is to fill the gap between buyers and Author: Rashad Yazdanifard1 , Noor Al-Huda Edres2
and
sellers with the help of an e-commerce website which will Arash Pour Seyedi3
be beneficial to both of them. Sellers will be able to sell Methodology: Introducing a P3P system into
company’s
their products without any issues and buyers can get their sites that shows customers how the site collects
handles and
needs fulfilled easily. uses their personal information is also advisable.
Drawback: Companies must take actions or more precisely
Our aim is to bring grocery items and similar products
increase the quality asures they provide in
online while simultaneously providing a seamless
order to delivers risky services to customer
experience to our customers. The people who want grocery
can’t visit the shop as they might not be having time or
maybe they live very far from the shop, so our (VELMART) Title: The Evolution of Social Commerce: The
People,
online store aims to deliver our products to the Management,Technology, and Information Dimensions
users(customers) more efficiently, using a website. Users Author: Wang, C., & Zhang, P.
can directly place their order from ourWebsite.
Methodology: Untraceable off line electronic cash flow in
e-commerce
The entire development process will be primarily
Drawback: Electronic cash and e-commerce security
divided into three parts: the front-end development, the
back-end development and the machine learning model
Title: The Evolution of Software Process Models: From the
development part. The database design is also discussed
Waterfall Model to the Unified Modeling Language (UML)
with an emphasis on its relational connectivity. This method
Author: Saad Subair
of developing an e-commerce website can be easily
replicated and followed in developing e-commerce websites

Methodology: Real time examples of using this process analysis phase thereby giving the customers an
opportunity
model, advantages and disadvantages. The conventional to see the product early in the life cycle. [Fig 1]
activities of problem solving in software development
consists of: Analyze the problem, Plana solution for the The Reason to choose the particular prototype model
was
problem, Code the solution, Test the coded program, and because if the customer is not clear with the idea
we just ask
Maintain the program him for the modifications needed and could be implemented
Drawback: The duration of time from the start of the later. It is good for technical and requirement risks
which
project to the deliverution is very high. mean if the customer is not clear with his technical
Various models and approaches of system development have specifications we could suggest to him a
probable model

Page 2 of 4
 and plan with this process model.This kind of project needs
been reviewed and discussed in this study. Each model has
constant updating of goods and features based on the
its own advantages and disadvantages.
customer reviews, FAQs and suggestions gathered through
emails which inclines us to proceed with this particular
Title: Consumer-driven e-commerce: A literature review,
design framework, and research agenda on last-mile
logistics models (Li et al., 2011)
Author:Stanley Frederick W.T. Lim, Xin Jin, Jagjit Singh
Srai
Methodology: Privacy-aware access control with trust
management in web service. The systematic literature
review examince between e-commerce and
LML. Following a protocol-driven methodology, combined
with, a total of 47 articles form
the basis of the review. To circumvent subjective selection
of articles for inclusion, all papers were assessed
independently counterchecked with
two independent logistics experts.
Drawback: Privacy is a major concern in mobile
commerce. From a theoretical contribution perspective, this
underpin them
Fig1. Evolutionary Prototyping Model
ovide the toy or
rough model
This section the hardware and software
for apps and mobile device
client applications. This website be accessed on
a PC running or any Operating System like
Windows , etc. shopping system protects
the . Also the users' details need to be
secured in the .
The user must

Matched Source

Similarity 25%
Title:(PDF) (IJACSA) International Journal of Advanced Computer ...

https://www.academia.edu/32397211/_IJACSA_International_Journal_of_Advanced_Computer_Science_and_Applications_Vol_7_No_1_2016_P

Similarity 25%
Title:Programsonfiles Vellore Institute of Technology ... - StuDocu

https://www.studocu.com/in/document/vellore-institute-of-technology/virtualization/programsonfiles-vellore-institute-of-
technology-vellore-institute-of-technology-vellore-institute-of-technology/19603221

Similarity 9%
Title:the design and implementation of an e-commerce - CiteSeerX

https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.379.8865

Similarity 5%
Title:[PDF] Security and Privacy Issues as a Potential Risk for ...

https://www.semanticscholar.org/paper/Security-and-Privacy-Issues-as-a-Potential-Risk-for-Yazdanifard-
Edres/01c55d28035e91cb5882bda08cb599cc63f44578

Page 3 of 4
Similarity 3%
Title:(PDF) Untraceable off-line electronic cash flow in e-commerce

https://www.researchgate.net/publication/3890066_Untraceable_off-line_electronic_cash_flow_in_e-commerce

Similarity 3%
Title:HalO [Indoor Positioning Mobile Platform] - Cumincad
by Z Hu · 2017 · Cited by 2 — The HalO platform development includes the front-end design, the back-end development
and the machine learning model. • The Front-end Design: HalO serves as an ...
http://papers.cumincad.org/data/works/att/acadia17_284.pdf

Similarity 3%
Title:Developing an E-commerce website | IEEE Conference ...
· This no-nonsense method of developing an e-commerce website can be easily replicated and followed in developing e-
commerce websites in the developing and under …
https://ieeexplore.ieee.org/document/7522526

Similarity 3%
Title:www.researchgate.net › publication › 329467473(PDF) Developing an Userfriendly Online Shopping Web-Site
This no-nonsense method of developing an e-commerce website can be easily replicated and followed in developing e-
commerce websites in the developing and under-developed countries where computing ...
https://www.researchgate.net/publication/329467473_Developing_an_Userfriendly_Online_Shopping_Web-Site/

Similarity 2%
Title:www.researchgate.net › publication › 311986589(PDF) Consumer-driven e-commerce: A literature review, design ...
Consumer-driven e-commerce: A literature review, design framework, and research agenda on last-mile logistics models
December 2017 International Journal of Physical Distribution & Logistics ...
https://www.researchgate.net/publication/311986589_Consumer-driven_e-
commerce_A_literature_review_design_framework_and_research_agenda_on_last-mile_logistics_models/

Similarity 2%
Title:Lim, Stanley Frederick W. T. [WorldCat Identities]

http://worldcat.org/identities/np-lim,%20stanley%20frederick%20w%20t

Page 4 of 4