Sketchy E-COMMERCE WEBSITE

A project report submitted in partial fulfilment of the requirements

for the award of the degree of

MASTER’S OF COMPUTER APPLICATION

Submitted by

SUMIT- 21MCA3225
Under the guidance of
Ms. Harneet Kaur
Assistant Professor
IN
University institute of computing

DEPARTMENT OF UNIVERSITY INSTITUTE OF COMPUTING

Chandigarh University
(Approved by AICTE and Accredited by NAAC with ‘A’ Grade)

Mohali, Punjab, India

Feb-June 2023

1
Sketchy E-COMMERCE WEBSITE

2
 BONAFIDE CERTIFICATE
Certified that this project report “EXPLORATORY DATA ANALYSIS ON
STUDENT PERFROMANCE” is the bonafide work of “SUMIT” who carried out the
project work under the supervision of MS/ HARNEET KAUR.

Signature Signature

DR. Abdullah Ms. Harneet Kaur Head of Department

Supervisor
University Institute of Computing University Institute of Computing

Submitted for the project viva-voce examination held on

INTERNAL EXAMINER EXTERNAL EXAMINER

3
 ACKNOWLEDGEMENT
I would like to express our deep gratitude to our project guide Harneet Kaur, Assistant Professor,
Department of UIC for her guidance with unsurpassed knowledge and immense encouragement. I
am grateful to DR ABDULLAH, Head of the Department, UIC, for providing us with the required
facilities for the completion of the project work.
I am very much thankful to the Principal and Management, for their encouragement and cooperation to
carry out this work.
I express our thanks to Project Coordinator HARNEET KAUR, for her continuous support and
encouragement. I thank all teaching faculty of Department of UIC, whose suggestions during reviews
helped us in accomplishment of our project. I would like to thank HARNEET KAUR of the Department of
UIC for providing great assistance in accomplishment of our project.

4
 ABSTRACT

The purpose of an e-commerce website is one that allows people to buy and sell physical goods,
services, and digital products over the internet rather than at a brick-and-mortar location. Through an e-
commerce website, a business can process orders, accept payments, manage shipping and logistics, and
provide customer service. It’s tough to imagine daily life without e-commerce. We order food, clothes,
and furniture; we register for classes and other online services; we download books, music, and movies;
and so much more. E-commerce has taken root and is here to stay. The term “e-commerce” simply
means the sale of goods or services on the internet. In its most basic form, e-commerce involves
electronically transferring funds and data between 2 or more parties. This form of business has evolved
quite a bit since its beginnings in the electronic data interchange of the 1960s and the inception of online
shopping in the 1990s. In recent years, e-commerce has enjoyed a massive boost from the rise of
smartphones, which allow consumers to shop from nearly anywhere.

5
 GRAPHICAL ABSTRACT
Graphical Abstract is a single, concise, pictorial and visual summary of the main findings of the article.
It could either be the concluding figure from the article or better still a figure that is specially designed
for the purpose, which captures the content of the article for readers at a single glance.

6
 TABLE OF CONTENTS

List of Figures ............................................................................................................

CHAPTER 1. INTRODUCTION.........................................................9

1.1. Client Identification and Recognition Need...............................................................10

1.2. Recognition & Knowledge of Relevant Contemporary..............................................11

1.3. Project Identification...................................................................................................15

1.4. Task Identification......................................................................................................17

1.5. Timeline & Gant Chart...............................................................................................18

CHAPTER 2. LITERATURE SURVEY............................................19

2.1. Literature Review........................................................................................................20

2.2. Literature Summary....................................................................................................20

2.3. Goals and Objectives..................................................................................................20

2.4. Features .……………………………………………………………………………..21

CHAPTER 3. DESIGN FLOW/PROCESS.......................................22

3.1. Data Flow Diagram.....................................................................................................24

3.2. Er Diagram..................................................................................................................26

3.3. Security Testing of Project..........................................................................................28

CHAPTER 4. RESULTS ANALYSIS AND VALIDATION............32

4.1. Implementation of Design using modern technology...............................................32

4.2 Database and language used……………………………………………….36

4.3 Pert Chart ………………………………………………………………….39

7
CHAPTER 5. CONCLUSION AND FUTURE WORK...................40

5.1. Limitations of the Project............................................................................41

5.2 Screenshots of the Project…………………………………………………42

REFERENCES......................................................................................54

8
 CHAPTER I. INTRODUCTION
The company name was Boston Exchange. It was the first company that launched ecommerce back in
1982. It was introduced in May 1989. It is a platform for the developing merchandise world. It is a
platform where we can sell and buy products over the internet rather than selling products physically at a
brick-and-mortar location. From this site, a customer can make orders, and the seller can accept
payments, manage shipping and logistics, and provide customer service. If we see the big picture, then it
is obvious that every major site on the internet is e-commerce. It might be the platform, marketplace,
portals, apps, entertainment, shopping, and online class sites. E-commerce involves the programmed
transfer of funds and data between parties. It is a business that has been developed since the beginning
of the 1960s and the launch of online shopping in the 1990s. It is hard to think of our daily life without
e-commerce. We order food, clothes, furniture, etc., and many other online services; we download
books, music, and movies. In short, we can see e-commerce has taken root in our daily lives. ReactJS is
a framework that is used along with HTML, CSS, and Javascript. And these frameworks are being used
in my front-end part and for the backend, MongoDB and Node.js. This software helps us to improve
customer service and relationship management. It is capable of adding or selling products; storing data
about customers; and managing it systematically.

WHAT IS AN E-COMMERCE WEBSITE?

It is like a traditional retail store. An e-commerce website allows customers and sellers to buy and sell
their products to one another on a designated platform. It is way better than physical trade because, in
physical commerce, we have to vend the products face-to-face at specific locations, and in e-commerce,
we can. With the use of the internet, we can sell anywhere. We can sell all over the globe. We can say
that it is a platform for communication via the internet that takes place bet ween companies and
customers. These sites provide various kinds of services. It is one of the marketing services that allows
users to buy, sell, order, and view goods online using their mobile phones or computers. If we face
reality, the world is now connected via the internet, and future generations prefer to use technology
rather than do things manually (by going physically).

Examples of an e-commerce website:

There are well-known sites that are considered the best e-commerce sites like Amazon, Flipkart,
Shopclues, Ajio.com Etc. If we say for ourselves, every website is an e-commerce website and platform
on the internet. Due to the sites, there is a rise in internet usage. Commerce is the source of income for
online companies and many local merchants. Without the internet, there would be no commerce.

9
 CLIENT IDENTIFICATION AND RECOGNITION OF NEED
Definition
Customer needs and identification is the way to determine what and how a customer wants the product
to perform. Their needs are non-technical, and it reflects their views about the product, not the actual
design, but they are closely related.

Statement of Problem
In today's world, everything is available, but some things are not. For example, an artist can't get a
platform for selling sketches, like portraits, landscapes, and anime. There are sites, but they are way
bulkier. For example, Amazon is a platform where you can buy or sell anything, but it is not a specific
platform for artists, and many people don't know that the app sells sketches. So, to meet the
expectations, this site has been developing. So, everyone with talent can reveal their talent and earn
something from their passion or hobbies. This site will contain add, sell, buy, and add-to-cart like
features.
This project will provide:

Identification: The main points in my project are:

1. It works very fast compared to other sites.

2. I provide a platform for artists and handcrafted items.

3. This site is only available for hand-made items, either sketches, portraits, or crafts, etc.

Enhance shopping cart:

In this, I will create a simple check-out process after purchasing so that users don’t have to deal with
lengthy check-out, security-related issues, and unclear returns policy.

Flexible Return Policy:

There are some cases when the user doesn’t like the product, and there can be manufacturing or
packaging defects too during the process. So, there should be a way for customers to return or exchange
the products they have bought.

Mobile-Friendly Policy:
There might be customers who will use the site from their mobile phones rather than PCs, or there may
be customers who don’t have a PC. So, making a mobile-friendly site will help both the customers.

10
Highly Customizable Themes:
Some customers want to see some products and to filter the products, there should be a specific
customizable filter.
Customer Support and Interface:
Providing a platform so that users can solve their queries.

RECOGNITION & KNOWLEDGE OF RELEVANT

CONTEMPORARY
Main points to be consider are below:
Building Trust with User:
As a developer, we have to give users the surety of their security, especially on online sites that
typically ask the user to provide their details like a home address and credit card for the completion of
purchase.
A website that is not usable on mobile phones:
Many users or visitors gradually check the sites on mobile rather than an app. And if the site is not
mobile- friendly, users will leave it before viewing our products.
A site that takes too long to load:
If the site is too slow, the user will get exhausted and leave the site. For example, if we, as a customer,
are looking for products on an online e-commerce site where we are facing issues like slow working or
having to refresh the page continuously due to its working. What will we do? We will leave the site
before browsing any products because we will get frustrated after watching it work. So, providing a
website with good work and speed will help to attract more users.
Banners, ads, and pop-ups:
Just imagine bombarding your user's screen will only demoralize and exhaust them from visiting that
sites. And these things usually happen on mobile phones while browsing random ads, banners, or pop-
ups that take up the whole screen.
Dishonest Advertising:
It is easy to use copy and offers that will encourage users to buy the product from the site, but the
advertisement that allured the user is dishonest when a user comes to make the purchase and finds out
that the charges are summed to the fee cost. For example, as a user, you are buying a product from a
store that provides Free Shipping from Russia, and you think shipping is free and go for it. And
suddenly, while checking out, you discover that additional charges are added. It will be the worst
experience you will face as a customer.
Lack of Security:
The user always seeks third-party proof that it’s secure. For example, if we get the SSL certificate for
our site, a verified icon will appear next to the URL. And this will ensure users that the services we are

11
pro providing are genuine.

Low-quality or irrelevant product images:

The images of the pic should be clear or should snap in the light. The quality of the image should be
user- friendly or high so that the visuals remain clear and the user can see the product clearly without
any issues.
Spammy product description and copywriting:
Nobody likes spam, no matter how good business owners think those spammy keywords will help in
their search engine optimization. It is also the reason for users leaving the sites. They lose their faith in
the sites due to spammy activities.

Payment processing:

One of the main perspectives is we have to enhance our e-commerce sales. To do that, the site should be
able to process payments according to the user's will. For example, a user wants to do a transaction via
credit or debit card, Paytm, Bhim, google pay, cash, or from a bank account cause they find it
comforting and convincing, or maybe they think it of more secure. Then we have to think of the service
and the processing fees, which can quickly add to a huge amount from the sales you’ve made.

Shipping:
A thorough guide should be provided so that the purchased product reaches the exact location from
where it was ordered. The order should be well packed. Use the best packaging materials. And always
try to keep the weight as low as possible you can. Consider providing free shipping on a specific amount
to the user.
Product Reviews:
Product reviews should be maintained. The key factors that must keep in mind are:
1. By showing an average star to a high star for polling.

2. Display the number of reviews from low to high star.

3. Replying to negative reviews and telling them how to exchange the product.

Navigation Pages:
The pages should be smooth like butter. As the user clicks on the second it should render it smoothly.
And the most popular pages should be visible on top cause if users have to dig deeper into the site to
find a particular page, then we are making them do extra work.

SYSTEM ANALYSIS:
System analysis is a process of gathering and interpreting facts, diagnosing problems and the
information about the Art ecommerce website to recommend improvements on the system. It is a
12
problem-solving activity that requires intensive communication between the system users and system
developers. System analysis or study is an important phase of any system development process. The
system is studied to the minutest detail and analyzed. The system analyst plays the role of the
interrogator and dwells deep into the working of the present system. The system is viewed as a whole
and the input to the system are identified. The outputs from the organizations are traced to the various
processes: System analysis is concerned with becoming aware of the problem, identifying the relevant
and decisional variables, analyzing and synthesizing the various factors and determining an optimal or at
least a satisfactory solution or program of action. A detailed study of the process must be made by
various techniques like interviews, questionnaires etc. The data collected by these sources must be
scrutinized to arrive to a conclusion. The conclusion is an understanding of how the system functions.
This system is called the existing system.

Now the existing system is subjected to close study and problem areas are identified. The designer now
functions as a problem solver and tries to sort out the difficulties that the enterprise faces. The solutions
are given as proposals. The proposal is then weighed with the existing system analytically and the best
one is selected the proposal is presented to the user for an endorsement by the user. The proposal is
reviewed on user request and suitable changes are made. This is loop that ends as soon as the user is
satisfied with proposal. Preliminary study is the process of gathering and interpreting facts, using the
information for further studies on the system. Preliminary study is problem solving activity that requires
intensive communication between the system users and system developers. It does various feasibility
studies. In these studies, a rough figure of the system activities can be obtained, from which the decision
about the strategies to be followed for effective system study and analysis can be taken.

Existing System of Ecommerce Website

In the existing system the exams are done only manually but in proposed system we have to computerize
the exams using this application.

• Lack of security of data.

• More man power.
• Time consuming
• Consumes large volume of pare work.
• Needs manual calculations.
• No direct role for the higher officials
One of the main perspectives is we have to enhance our e-commerce sales. To do that, the site should be
able to process payments according to the user's will. For example, a user wants to do a transaction via
credit or debit card, Paytm,
Bhim, google pay, cash, or from a bank account cause they find it comforting and convincing, or maybe

13
they think it of more secure. Then we have to think of the service and the processing fees, which can
quickly add to a huge amount from the sales you’ve made.

Shipping:
A thorough guide should be provided so that the purchased product reaches the exact location from
where it was ordered. The order should be well packed. Use the best packaging materials. And always
try to keep the weight as low as possible you can. Consider providing free shipping on a specific amount
to the user.
Product Reviews:
Product reviews should be maintained. The key factors that must keep in mind are:
1. By showing an average star to a high star for polling.

2. Display the number of reviews from low to high star.

3. Replying to the negative reviews and tell them now to replace it.

Navigation Pages:
The pages should be smooth like butter. As the user clicks on the second it should render it smoothly.
And the most popular pages should be visible on top cause if users have to dig deeper into the site to
find a particular page, then we are making them do extra work.

Proposed System of website:

The aim of proposed system is to develop a system of improved facilities. The proposed system can
overcome all the limitations of the existing system.

• The system provides proper security and reduces the manual work.

• Security of data Ensure data accuracies

• Proper control of the higher officials.

• Minimize manual data entry.

• Minimum time needed for the various processing.

14
 PROJECT IDENTIFICATION

Functionalities provided by art website are as follows:

• Provides the searching facilities based on various factors. Such as animation art, Customer,
Order, Confirm Order
• This website also manage the Payment details online for Order

• It tracks all the information of Category, Payment, Order etc

• Manage the information of Category

• Shows the information and description of the each art piece, Customer

• To increase efficiency of managing the Food Item. Category

• It deals with monitoring the information and transactions of Order.

• Manage the information of Art pieces

• Editing, adding and updating of Records is improved which results in proper resource management
of Art work.
• Manage the information of Order.

• Integration of all record of Confirm Order.

SCOPE OF THE PROJECT

It may help collecting perfect management in detail. In a very short time, the collection will be
obvious, simple and sensible. It will help a person to know the management of passed year perfectly
and vividly.

15
It also helps in current all works relative to Art E-Commerce Website. It will be also reduced the cost of
collecting the management & collection procedure will go on smoothly.
• Our project aims at Business process automation, i.e. we have tried to computerize various
processes to order arts of different artists.
• To utilize resources in an efficient manner by increasing their productivity through automation.

• The system generates types of information that can be used for various purposes.

• It will satisfy the user requirement.

• Be easy to operate.

• Have a good user interface.

• Be expandable

• Delivered on schedule within the budget.

MODULES OF ART E-WEBSITE

 Product Management Module: Used for managing the product details.

 Confirm Order Module: Used for managing the details of Confirm Order
 Payment Module: Used for managing the details of Payment
 Category Management Module: Used for managing the information and details of the
Category.
 Customer Module: Used for managing the Customer details
 Order Module: Used for managing the Order information
 Login Module: Used for managing the login details
 Users Module: Used for managing the users of the system.

16
 TASK IDENTIFICATION
Following tasks should be done in this project:

1. It should be user friendly.

2. Building back-end APIs,
3. Designing database.
4. Designing front-end.
5. Securing user data and privacy.

TIMELINE OF THE PROJECT (IN WEEKS)

8-10 weeks (It might take more or less but most probably the mention given weeks).

Methodology:
In this system, has very simple in design and to implement. The system is not very complex. It is very
easy to maintain. It is very handy. Below are the following features:
• It will maintain data correctness.

• The data will be maintained efficiently by DBMS (Data Base Management System).
data maintained by the functions. The functional requirements are presented in scenes that point to an
operational system from the perspective of its users. Included are one or more examples of all system
features and an enumeration of all the specific requirements associated with these functions:
• The system shall corporate mechanisms for the privacy of its users.
• The system shall verification and maintain all user input and should inform in case of error finding and
should help the user in error finding.
• Sharing of data and files should be easy.
• Support great communication likewise send and receive messages.

Non-Functional Requirement:-
Non-functional requirements are aspects of the system other than any particular functions it performs.
These aspects include system performance, price, and such general system characteristics as reliability,
security, and portability. The non-functional requirements also address things of the system-building
process and operational personnel.
It includes the following:
• The project should fulfill customer needs, must be reliable, and should be customer friendly.

17
 • The system shall provide user’s attractive graphical interface
• The system should allow developer access.
• The system shall target the customer base.

The architecture of The Proposed System:

This processing will support present system needs and gives desired suggestions for hardware solutions
based on present and projected user requirements. Application needs, data sources, and employees within
a company are all necessary for finding the required hardware technical. It is presented using a three-
phase architecture that provides a user interface, process cycle maintenance, and a Database
Management System. It illustrates the features of the system, the facilities it gives, and the way they
send and receive to find out about the system’s works.

GANTT CHART OF PROJECT:

Task Sept w- Sept. w- Sept. Oct. w-1 Oct. w-2 Oct. w-3 Oct. w-4
2 3
Information
Requirements
UI Design
Back End
Code
Documentatio
n

CHAPTER-2 LITERATURE SURVEY

Literature Review features providing

1)Online shopping

2)Virtual maintenance.
18
3)Web services.

4)User can buy the product online while surfing internet.

5)The online system helps the user to check the availability of the product before purchasing.
As we all know, the internet and e-commerce are entirely committed to every developed country. But we
think it can be accomplished and can make a remarkable benefit to developing countries also if an ideal
business purpose can be made. Ohidujja man et.al discussed that E-commerce is a revolution & turning
point in online business practices and can make a huge contribution to the economy and Hasan et.al [5]
also indicated that currently, e-commerce organizations have increasingly become a fundamental
component of business strategy and a strong catalyst for economic development. A huge amount of
research works has been done on e- Commerce which is online shopping. A large group of researchers
has found out and also pointed out the necessity and possibilities of Online Shopping. On the other
hand, limitation of e-commerce is found and at the same time, they provided essential suggestion and
came to a prediction to make Online Shopping more useful for consumers. But the contribution of
traditional marketing is also inescapable but compared to online shopping it is less effective than we
think. So on this basis, Mehrdad Salehi et.al [17] found the distinction between online marketing &
traditional marketing. Though most of the people of Bangladesh especially the rural people are not
enough capable of operating the internet to run an online business. For that reason, they need to be
dependent on traditional marketing.

SPECIFIC AIMS

A system that supports fast recording of the data and purchasing rather than the current paperwork or
manually. To increase work by increasing productivity.
The project will support the bureau to come out with error-free data.

A dependable and necessary starting of information that will help in 24 hours activities of the bureau by
ending up the present manually terminology.

REVIEW OF PREVIOUS SOLUTIONS OR RELATED

MATERIALS, EXTENT AND RELEVANCE OF THE
MATERIALS AND REVIEWED TO THE PROJECT

19
 This literature review will emphasize On transaction processing system is all about in terms of needs
associated to functions of this system as it made in various models for different requirements .This is
necessarily part in writing as it provides a direct overview of other studies completed on the same and
how information is send or received in the company that is from primary phase where rent is collected to
middle level and records and data are upgraded to top level and reports are made and history of tops.

SUMMARY OF HOW REVIEWED LITERATURE HELPED IN

DEFINING
Our initiative is only a modest effort to meet their requirement for project management. Many user-
friendly coding styles have also been adopted. This bundle will prove to be effective in meeting all of
the school's criteria. The goal of software planning is to give the manager a framework for making
credible predictions within a constrained time period at the start of the software project. This framework
should then be updated often as the project moves forward.
At the conclusion, it is determined that the following efforts have been undertaken.
• An explanation of the project's history, setting, and relationship to earlier work in the region.
• Developed a statement of the project's goals and objectives.
• An explanation of the purpose. Dimensions and applicability
• We outline the prerequisite. details about the system and any actions that may be taken in
relation to these items.
• We provided thorough details on features and functions, including screen layouts.
• We created the user interface and addressed system security concerns.

OBJECTIVES OF THE PROJECT

The main objective of this study is to automate the manual process of booking a product made through
the seller company. This the system is said to be an automatic system and customers can choose any
product by themselves. Specifically, the motive of this project is:
 Providing an electronic product booking function where a customer can book a product through the
online system without a need to look into the shop.

 Enabling customers to check the availability and types of products online.

 Easing purchasing payments by UPI payments and card payments.
 Ability of customers to cancel their purchase.
FEATURES OF ART E-COMMERCE WEBSITE:

 Product and Component base

 Creating & Changing Issues at ease
20
 Query Issue List to any depth
 Reporting & Charting in more comprehensive way
 User Accounts to control the access and maintain security
 Simple Status & Resolutions
 Multi-level Priorities & Severities.
 Targets & Milestones for guiding the programmers
 Attachments & Additional Comments for more information

 Robust database back-end

 Various level of reports available with a lot of filter criteria's
 It contains better storage capacity & Accuracy in work.

21
 CHAPTER- 3 DESIGN FLOW /PROCESS

USE CASE MODEL OF THE PROJECT:

The use case model for any system consists of "use cases". Use cases represent different ways in which
the system can be used by the user. A simple way to find all the use case of a system is to ask the
questions "What the user can do using the system?" The use cases partition the system behavior into
transactions such that each transaction performs some useful action from the users' point of view.
The purpose of the use case to define a piece of coherent behavior without revealing the internal
structure of the system. A use case typically represents a sequence of interaction between the user and
the system. These interactions consist of one main line sequence is represent the normal interaction
between the user and the system. The use case model is an important analysis and design artifact (task).
Use cases can be represented by drawing a use case diagram and writing an accompany text elaborating
the drawing.
In the use case diagram, each use case is represented by an ellipse with the name of use case written
inside the ellipse. All the ellipses of the system are enclosed with in a rectangle which represents the
system boundary. The name of the system being module appears inside the rectangle. The different users
of the system are represented by using stick person icon. The stick person icon is normally referred to as
an Actor. The line connecting the actor and the use cases is called the communication relationship.
When a stick person icon represents an external system, it is annotated by the stereo type<<external
system>>.

22
 Use Case Diagram For Users And Admin :

Product AvailAbilityEnquiry

To
Adding

CancelPurchase

Printinvoice
Client

Login

Admin
Update route

Update product
product

23
 DATA FLOW DIAGRAM
Data flow diagram is the starting point of the design phase that functionally decomposes the
requirements specification. A DFD consists of a series of bubbles joined by lines, The bubbles represent
data transformation and the lines represent data flows in the system. A DFD describes what data flow
rather than how they are processed, so A data-flow diagram (DFD) is a graphical representation of the
"flow" of data through an information system. DFDs can also be used for the visualization of data
processing (structured design). A data flow diagram (DFD) is a significant modeling technique for
analyzing and constructing information processes DFD literally means an illustration that explains the
course or movement of information in a process. DFD illustrates this flow of information in a process
based on the inputs and outputs. A DFD can be referred to as a Process Model.
The data flow diagram is a graphical description of a system's data and how to Process transform the
data is known as Data Flow Diagram (DFD).
There are seven rules for construct a data flow diagram.

 Arrows should not cross each other.

 Squares, circles and files must wear names.

 Decomposed data flows must be balanced.

 No two data flows, squares or circles can be the same names

 Draw all data flows around the outside of the diagram.

 Choose meaningful names for data flows, processes & data stores. Control information such as
record units, password and validation requirements are not penitent to a data flow diagram.
Additionally, a DFD can be utilized to visualize data processing or a structured design.This basic DFD
can be then disintegrated to a lower level of diagram demonstrating smaller steps exhibiting details of
the system that is being modeled. On a DFD, data items flow from an external data source or an internal
data store to an internal data store or an external data sink, via an internal process. It is common practice
to draw a context-level data flow diagram first, which shows the interaction the system and external
agents, which act as data sources and data sinks. On the context diagram (also known as the Level 0
DFD'), the system's interactions with the outside world are modeled purely in terms of data flows across
the system boundary. The context diagram shows the entire system as a single process and gives no
clues as to its internal organization.This context-level DFD is next "exploded", to produce a Level 1
DFD that shows some of the detail of the system being modeled. The Level 1 DFD shows how the
system is divided into sub-systems (processes), each of which deals with one or more of the data flows

24
to or from an external agent, and which together provide all the functionality of the system as a whole.
The level 1 DFD is further spread and split into more descriptive and detailed description about the
project as level 2 DFD. The level 2 DFD can be have a few data it does not have hardware, software
and data structure flows which will finally show the entire description of the software project.

25
 ER DIAGRAM
Entity Relationship Diagram
E-R Model is a popular high level conceptual data model. This model and its variations are frequently
used for the conceptual design of database application and many database design tools employ its
concept.
A database that confirms to an E-R diagram can be represented by a collection of tables in the relational
system. The mapping of E-R diagram to the entities are:
 Attributes
 Relations
 Many-to-many
 Many-to-one
 One-to-many
 One-to-one
 Weak entities
 Sub-type and super-type. The entities and their relationships between them are shown using the
following conventions
 An entity is shown in rectangle.
 A diamond represents the relationship among number of entities.
 The attributes shown as ovals are connected to the entities or relationship by lines.
 Diamond, oval and relationships are labeled.

 Model is an abstraction process that hides super details while highlighting details relation to
application at end.

26
 A data model is a mechanism that provides this abstraction for database application

 Data modeling is used for representing entities and their relationship in the database.

 Entities are the basic units used in modeling database entities can have concrete existence or
constitute ideas or concepts.

 Entity type or entity set is a group of similar objects concern to an organization for maintain data,

 Properties are characteristics of an entity also called as attributes.

 A key is a single attribute or combination of 2 or more attributes of an entity set is used to
identify one or more instances of the set.

 In relational model we represent the entity by a relation and use tuples to represent an instance of
the entity.

 Relationship is used in data modeling to represent in association between. an entity set.

27
 SECURITY TESTING OF THE PROJECT

Testing is vital for the success of any software no system design is ever perfect. Testing is also carried
in two phases, first phase is during the software engineering that is during the module creation, second
phase is after the completion of software. this is system lasting which verifies that the whole set of
programs hanged together.

White Box Testing:

In this technique, the close examination of the logical parts through the software are tested by cases that
exercise species sets of conditions or loops. all logical parts of the software checked once errors that can
be corrected using this technique are typographical errors, logical expressions which should be executed
once may be getting executed more than once and error resulting by using wrong controls and loops.
When the box testing tests all the independent part within a module a logical decisions on their true and
the false side are exercised, all loops and bounds within their operational bounds were exercised and
internal data structure to ensure their validity were exercised once.
Black Box Testing:
This method enables the software engineer to device sets of input techniques that fully exerase all
functional requirements for a program black box testing tests the input, the output and the external data.
It checks whether the input data is correct and whether we are getting the desired output.
Alpha Testing:
Acceptance testing is also sometimes called alpha testing Be spoke systems are developed for a single
customer. The alpha testing proceeds until the system developer and the customer agree that the
provided system is an acceptable implementation of the system requirements.
Beta Testing:
On the other hand, when a system is to be marked as a software product, another process called beta
testing is often conducted. During beta testing, a system is delivered among a number of potential users
who agree to use it The customers then report problems to the developers. This provides the product for
real use and detects errors which may not have been anticipated by the system developers.
Unit Testing:
Each module is considered independently, it focuses on each unit of software as implemented in the
source code. it is white box testing.

Integration Testing:

Integration testing aims at constructing the program structure while at the same constructing tests to
uncover errors associated with interfacing the modules are integrated by using the top-down approach.

28
Validation Testing:
Validation testing was performed to ensure that all the functional and performance requirements are met.
System Testing:

It is executing programs to check logical changes made in it with intention of finding errors. a system is
tested for online response, volume of transaction, recovery from failure etc. System testing is done to
ensure that the system satisfies all the user requirements.
Implementation and Software Specification Testing’s Detailed
Design of Implementation
This phase of the systems development life cycle refines hardware and software specifications
establishes programming plans, trains users and implements extensive testing procedures, to evaluate
design and operating specifications and/or provide the basis for further modification
Technical Design
This activity builds upon specifications produced during new system design, adding detailed
technical specifications and documentation.
Test Specifications and Planning
This activity prepares detailed test specifications for individual modules and programs, job streams,
subsystems, and for the system as a whole.
Programming and Testing
This activity encompasses actual development, writing, and testing of program units or modules

User Training

This activity encompasses writing user procedure manuals, preparation of user training materials,
conducting training programs, and testing procedures.
Acceptance Test
A final procedural review to demonstrate a system and secure user approval before a system becomes
operational
Installation Phase
In this phase the new Computerized system is installed, the conversion to new procedures is fully
implemented, and the potential of the new system is explored.
System Installation
The process of starting the actual use of a system and training uner personnel in its operation
Review Phase
This phase evaluates the successes and failures during a systems development project, and to measure
the results of a new Computerized Trans system in terms of benefits and savings projected at the start of
the project.

29
 Development Recap
A review of a project immediately after completion to find successes and potential problems in future
work.
Post-Implementation Review
A review, conducted after a new system has been in operation for some time, to evaluate actual system
performance against original expectations and projections for cost-benefit improvements. Also identifies
maintenance projects to enhance or improve the system.

The Steps in The Software Testing

The steps involved during Unit testing are as follows:
 Preparation of the test cases.

 Preparation of the possible test data with all the validation checks.

 Complete code review of the module.

 Actual testing done manually.

 Modifications done for the errors found during testing.

Prepared the test result scripts
The unit testing done included the testing of the following items:
 Functionality of the entire module/forms

 Validations for user input.

 Checking of the Coding standards to be maintained during coding.

 Testing the module with all the possible test data

 Testing of the functionality involving a type of calculations etc.

 Commenting standard in the source files.

After completing the Unit testing of all the modules, the whole system is integrated with all es
dependencies in that module. While System Integration, we integrated the modules one by one and
tested the system at each step. This helped in reduction of errors at the time of the system testing.
The steps involved during System testing are as follows:
• Integration of all the modules/forms in the system
• Preparation of the test cases.
• Preparation of the possible test data with all the validation checks.
• Actual testing done manually.
30
• Recording of all the reproduced errors.
• Modifications done for the errors found during testing.
Prepared the test result scripts after rectification of the errors.

The System Testing done included the testing of the following items:
The unit testing done included the testing of the following items
 Function with of the entire module forms
 Valid reason for user input.

 Checking of the Coding standards to be maintained during coding

 Testing the module with all the possible test data.

 Testing of the functionality involving all type of calculations etc.
 Commenting standard in the source files.
After completing the Unit testing of all the modules, the whole system is integrated with ta
dependencies in that module While System integration. We integrated the modules on one try and
listed the system at each step. This helped in reduction of amors at the time of the system testing.
The steps involved during System testing are as follows:
Integration of all the modules/forms in the system
 Preparation of the test cases.
 Preparation of the possible test data with all the validation checks actual
testing done manually.
 Recording of all the reproduced errors.
 Modifications done for the errors found during testing.
 Prepared the test result scripts after rectification of the errors.

31
 CHAPTER - 4 RESULTS ANALYSIS
& VALIDATION

1. IMPLEMENTATION OF DESIGN USING MODERN

ENGINEERING TOOLS IN ANALYSIS:
The Tools/Software’s is used in this project are as follows:
Visual Studio Code:
Visual Studio Code is a source-code editor that can be used with a variety of programming
languages, including Java, JavaScript, Go, Node.js, Python, C++, Rust and Fortran. It is
based on the Electron framework, which is used to develop Node.js web applications that run
on the Blink layout engine. Visual Studio Code employs the same editor component
(codenamed "Monaco") used in Azure DevOps (formerly called Visual Studio Online and
Visual Studio Team Services)

Out of the box, Visual Studio Code includes basic support for most common programming
languages. This basic support includes syntax highlighting, bracket matching, code folding,
and configurable snippets. Visual Studio Code also ships with IntelliSense for JavaScript,
TypeScript, JSON, CSS, and HTML, as well as debugging support for Node.js. Support for
additional languages can be provided by freely available extensions on the VS Code
Marketplace.

An orange version of the Visual Studio Code logo for the insider’s version of Visual Studio
Code. Instead of a project system, it allows users to open one or more directories, which can
then be saved in workspaces for future reuse. This allows it to operate as a language-agnostic
code editor for any language. It supports many programming languages and a set of features
32
that differs per language. Unwanted files and folders can be excluded from the project tree
via the settings. Many Visual Studio Code features are not exposed through menus or the user
interface but can be accessed via the command-palette.

Visual Studio Code can be extended via extensions, available through a central repository.
This includes additions to the editor and language support. A notable feature is the ability to
create extensions that add support for new languages, themes, debuggers, time travel
debuggers, perform static code analysis, and add code linters using the Language Server
Protocol.

Source control is a built-in feature of Visual Studio Code. It has a dedicated tab inside of the
menu bar where users can access version control settings and view changes made to the
current project. To use the feature, Visual Studio Code must be linked to any supported
version control system (Git, Apache Subversion, Perforce, etc.). This allows users to create
repositories as well as to make push and pull requests directly from the Visual Studio Code
program.

Visual Studio Code includes multiple extensions for FTP, allowing the software to be used as
a free alternative for web development. Code can be synced between the editor and the
server, without downloading any extra software.

Visual Studio Code allows users to set the code page in which the active document is saved,
the newline character, and the programming language of the active document. This allows it
to be used on any platform, in any locale, and for any given programming language.

Visual Studio Code collects usage data and sends it to Microsoft, although this can be
disabled. Due to the open-source nature of the application, the telemetry code is accessible to
the public, who can see exactly what is collected.

33
DATABASE-
Mongo DB:
MongoDB is an open-source document database and leading NoSQL database. MongoDB is written in
C++. This tutorial will give you great understanding on MongoDB concepts needed to create and
deploy highly scalable and performance-oriented database

The Languages Are Used as Follows:

I. HTML: The Hyper Text Markup Language or HTML is the standard markup language for
documents designed to be displayed in a web browser. It can be assisted by technologies such as
Cascading Style Sheets and scripting languages such as JavaScript

II. CSS: Cascading Style Sheets is a style sheet language used for describing the presentation of
a document written in a markup language such as HTML or XML. CSS is a cornerstone technology of
the World Wide Web, alongside HTML and JavaScript.

III. JavaScript: JavaScript, often abbreviated as JS, is a programming language that is one of the
core technologies of the World Wide Web, alongside HTML and CSS. As of 2022, 98% of websites use
JavaScript on the client side for webpage behavior, often incorporating third-party libraries.

IV. AJAX: Ajax is a set of web development techniques that uses various web technologies on
the client-side to create asynchronous web applications. With Ajax, web applications can send and
retrieve data from a server asynchronously without interfering with the display and behaviour of the
existing page.
34
 V. JSX: JSX is an embeddable XML-like syntax. It is meant to be transformed into valid
JavaScript, though the semantics of that transformation are implementation specific. JSX rose to
popularity with the React framework but has since seen other implementations as well. TypeScript
supports embedding, type checking, and compiling JSX directly to JavaScript.

2)Project management, and communication:

Feasibility Study:

Feasibility study includes consideration of all the possible ways to provide a solution to the given
problem. The proposed solution should satisfy all the user requirements and should be flexible enough
so that future changes can be easily done based on the future upcoming requirements.

A. Economical-Feasibility
This is a very important aspect to be considered while developing a project. We decided the technology
based on minimum possible cost factor.
All hardware and software cost has to be borne by the organization.
Overall, we have estimated that the benefits the organization is going to receive from the proposed
system will surely overcome the initial costs and the later on running cost for system.
B. Technical Feasibility
This included the study of function, performance and constraints that may affect the ability to achieve an
acceptable system. For this feasibility study, we studied complete functionality to be provided in the
system, as described in the System Requirement Specification (SRS), and checked if everything was
possible using different type of frontend and backend platforms.
C. Operational Feasibility

No doubt the proposed system is fully GUI based that is very user friendly and all inputs to be taken all
self-explanatory even to a layman. Besides, a proper training has been conducted to let know the essence
of the system to the users so that they feel comfortable with new system. As far our study is concerned
the clients are comfortable and happy as the system has cut down their loads and doing.
Project Planning:
Software project plan can be viewed as the following:

1) Within the organization: How the project is to be implemented? What are various constraints
(time, cost, staff)? What is market strategy?
2) With respect to the customer: Weekly or timely meetings with the customer with presentation
on status reports. Customers feedback is also taken and further modification and developments are done.
Project milestones and deliverables are also presented to the customer.
35
Cost estimation of the project:
Software cost comprises a small percentage of overall computer-based system cost. There are a number
of factors, which are considered, that can affect the ultimate cost of the software such as - human,
technical, Hardware and Software availability etc.
The main point that was considered during the cost estimation of project was its sizing. In spite of
complete software sizing, function point and approximate lines of code were also used to "size" each
element of the Software and their costing.
The cost estimation done by me for Project also depend upon the baseline metrics collected from past
projects and these were used in conjunction with estimation variables to develop cost and effort
projections. We have basically estimated this project mainly on two bases -
1) Effort Estimation - This refers to the total man-hours required for the development of the
project. It even includes the time required for doing documentation and user manual.
2) Hardware Required Estimation - This includes the cost of the PCs and the hardware cost
required for development of this project.
Project Profile:
There has been continuous effort to develop tools, which can ease the process of software development.
But, with the evolving trend of different programming paradigms today's software developers are really
challenged to deal with the changing technology. Among other issues, software reengineering is being
regarded as an important process in the software development industry. One of the major tasks here is to
understand software systems that are already developed and to transform them to a different software
environment. Generally, this requires a lot of manual effort in going through a program that might have
been developed by another programmer. This project makes a novel attempt to address the issue of
program analysis and generation of diagrams, which can depict the structure of a program in a better
way. Today, UML is being considered as an industrial standard for software engineering design process.
It essential provides several diagramming tools that can express different aspects/ characteristics of
program such as Use cases: Elicit requirement from users in meaningful chunks. Construction planning
is built around delivering some use cases in each interaction basis for system testing.
Class diagrams: shows static structure of concepts, types and class. Concepts how users think about the
world; type shows interfaces of software components; classes show implementation of software
components. Interaction diagrams: shows how several objects collaborate in single use case.
Package diagram: show group of classes and dependencies among them. State diagram: show how
single object behaves across many use cases. Activity diagram: shows behaviour with control structure.
Can show many objects over many uses, many object in single use case, or implementations methods
encourage parallel behaviour, etc.

36
 What is UML?
UML stands for Unified Modelling Language is the successor to the wave of Object-Oriented Analysis
and Design (OOA&D) methods that appeared in the late 80's. It most directly unifies the methods of
Booch, Rumbaugh (OMT) and Jacobson. The UML is called a modelling language, not a method. Most
methods consist at least in principle, of both a modelling language and a process. The Modelling
language is that notation that methods used to express design.

Notations and meta-models:

The notation is the graphical stuff; it is the syntax of the modeling language. For instance, class diagram
notation defines how items are concepts such as class, association, and multiplicity are represented.
These are: Class Diagram: The class diagram technique has become truly central within object-oriented
methods. Virtually every method has included some variation on this technique.
Class diagram is also subject to the greatest range of modelling concept. Although the basic elements are
needed by everyone, advanced concepts are used less often. A class diagram describes the types of
objects in the system and the various kinds of static relationship that exist among them. There are two
principal kinds of static relationship:
● Association

● Subtype

Class diagram also show the attributes and operations of a class and the constraints that apply to the way
objects are connected.
Association: Association represent between instances of class. From the conceptual perspective,
association represents conceptual relations between classes. Each association has two roles. Each role is
a direction on the association. A role also has multiplicity, which is a indication of how many object
may participate in the given relationship.
Generalization: A typical example of generalization evolves the personal and corporate customer of a
business. They have differences but also many similarities. The similarities can be placed in
generalization with personal customer and corporate customer sub type.
Aggregation: aggregation is the part of relationship. It is like saying a car has engine and wheels as its
parts. This sounds good, but difficult thing is considering, what is the difference is aggregation and
association. Interaction: interaction diagrams are models that describes how groups of objects
collaboration in some behaviour.

Typically, an interaction diagram captures the behaviour a single use cases. The diagram shows a
37
number of example objects and the messages that are passed between these objects in use cases. These
are following approaches with simple use case that exhibits the following behaviour. Objects can send a
message to another. Each message is checks with given stock item. There are two diagrams: Sequence
and Collaboration diagram. Package Diagram: One of the oldest questions in software methods is: how
do you break down a large system into smaller systems? It becomes difficult to understand and the
changes we make to them. Structured methods used functional decomposition in which the overall
system was mapped as a function broken down into sub function, which is further
broken down into sub function and so forth. The separation of process data is gone, functional
decomposition is gone, but the old question is still remains. One idea is to group the classes together into
higher-level unit. This idea, applied very loosely, appears in many objects. In UML, this grouping
mechanism is package. The term package diagram for a diagram that shows packages of classes and the
dependencies among them.
A dependency exists between two elements if changes to the definition of one element may cause to
other. With classes, dependencies exist for various reasons: one class sends a message to another; one
class has another as part of its data; one class mentions another as a parameter to an operation. A
dependency between two packages exists; and any dependencies exist between any two classes in the
package. State diagram: State diagram are a familiar technique to describe the behaviour of a system.
They describe all the possible states a particular object can get into and how the objects state changes as
a result of events that reach the objects. In most OO technique, state diagrams are drawn for a single
class to show the lifetime behaviour of a single object. There are many forms of state diagram, each with
slightly different semantics. The most popular one used in OO technique is based on David
Harel's state chart.

38
 PERT CHART (Program Evaluation Review Technique)
PERT chart is organized for events, activities or tasks. It is a scheduling device that shows graphically
the order of the tasks to be performed. It enables the calculation of the critical path. The time and cost
associated along a path is calculated and the path requires the greatest amount of elapsed time in critical
path.

39
 CHAPTER -5 CONCLUSION AND FUTURE
WORK
Our project is only a humble venture to satisfy the needs to manage their project work. Several user -
friendly coding have also adopted. This package shall prove to be a powerful package in satisfying all
the requirements of the school. The objective of software planning is to provide a frame work that
enables the manger to make reasonable estimates made within a limited time frame at the beginning of
the software project and should be updated regularly as the project progresses.
At the end it is concluded that we have made effort on following points...
• A description of the background and context of the project and its relation to work already done in
the area.

• Made statement of the aims and objectives of the project.

• The description of Purpose, Scope, and applicability.
• We define the problem on which we are working in the project.

• We describe the requirement Specifications of the system the actions that can be done on these things.
• We understand the problem domain and produce a model of the system which describes operations
that can be performed on the system.
• We included features and operations in detail, including screen layouts.

• We designed user interface and security issues related to system.

• Finally, the system is implemented and tested according to test cases.

FUTURE SCOPE OF THE PROJECT

In a nutshell, it can be summarized that the future scope of the project circles around maintaining
information regarding:
We can add printer in future.

• We can give more advance software including more facilities

• We will host the platform on online servers to make it accessible worldwide

• Integrate multiple load balancers to distribute the leads of the system

• Create the master and slave database structure to reduce the overload of the database queries

• Implement the backup mechanism for taking backup of codebase and database: on regular
basis on different servers

40
The above, mentioned points are the enhancements which can be done to increase the applicability and
usage of this project. Here we can maintain the records of art Item and Category. Also, as it can be seen
that now-a-days the users are versatile, i.e., so there is a scope for introducing a method to maintain the
Categories of Art painting, products & Enhancements can be done to maintain all the Products,
Category, Customer, Order, Confirm Order.
We have left all the options open so that if there is any other future requirement in the system by the
user for the enhancement of the system then it is possible to implement them. In the last we would like
to thanks all the persons involved in the development of the system directly or indirectly. We hope that
the project will serve its purpose for which it is develop there by underlining success of process

LIMITATION OF PROJECT
Although have put my best efforts to make the software flexible, easy to operate but limitations cannot
be ruled out even by me. Though the software presents a broad range of options to its users some
intricate options could not be covered into it, partly because of logistic and partly due to lack of
sophistication. Paucity of time was also major constraint thus it was not possible to make the software
tool proof and dynamic Lack of time also compelled me to ignore some part such as storing old result of
the candidate etc.
Considerable efforts have made the software easy to operate even for the people not related to the field
of computers but it is acknowledged that a layman may find it a bit problematic at the first instance. The
user is provided help at each step for his convenience in working with the software.

41
 SCREENSHOTS OF ART E-COMMERCE WEBSITE-
Home Page:

42
Login Page:

43
Cart:

Compare Products:
44
Contact Us:

45
Admin Pannel:

Login Page:

Dashboard:
46
Customers:

Add Products:

47
Brand:

Add Category:

48
Add Color:

Add Coupon:

49
Add Blog:

Enquiries:

50
Database:

51
52
REFERENCES

[1] Al ert H., Judd, Rivers, (2006) “Creating a winning E-Business”, Wagner Course Technology
Thomson Learning, pp. 37-255

. [2] Alawneh A., and Hattab E, (2007) “E-Business Value Creation: An Exploratory Study, Proceedings
of the Seventh International Conference on Electronic Business”, Taipei, pp. 181-188.

[3] Alawneh A., and Hattab E (2009). “International Arab Journal of eTechnology”, Vol. 1, No. 2,
pp. 1-8
[4] Amit B. and Steve M. (2007), “How to Plan E-Business Initiatives in Established Companies”,
Vol. 49, No. 1, pp. 11-22
[5] Aranda-M., G. and Stewart, P. (2005), “Barriers to E-Business Adoption in construction
international literature review”, pp. 33-49
[6] Ayo, Charles K. (2006). “The Prospects of e-Commerce Implementation in Nigeria, Journal of
Internet Banking and Commerce”, Vol. 11, No.3, pp. 68-75
[7] Amar. K., Sohani, (2009), “Technology and Banking Sector”, ICFAI University Press, pp. 1-39

[8] Brahm C., (2009) “E-Business and Commerce Strategic Thinking and Practice”, Houghton
Mifflin, pp. 114-312.
[9] Chiemeke, S. C., Evwiekpaefe, A. and Chete, F. (2006), “The Adoption of Internet Banking in
Nigeria: An Empirical Investigation, Journal of Internet Banking and Commerce”, vol. 11, No.3, pp 33-
49
[10] David W, (2001) “E-Commerce Strategy, Technologies and Applications”, Tata McGraw Hill,
pp. 3-143.
[11] Daft, Richard L. (1982), “ Bureaucratic Versus Nonbureaucratic Structure and the process of
Innovation and Change”, pp. 129-166
[12] Earl, M. (2000), “Evolving the E-Business, Business Strategy Review”, pp. 33-38

[13] Eben.O (2003) “A Systematic Approach to E-Business Security”, pp. 87-103

[14] Hackbarth, G. & Kettinger W. J. (2000), “Building an E-Business Strategy: Information

Systems Management” pp. 78-90.

53
[15] Kalakota, R. and Robinson M. (1999), “E-Business: Roadmap for success”,
Addison-Wesley, 112-149
[16] Karjaluoto H., Mattila M. (2002). “Electronic Banking in Finland: Consumer
Beliefs and Reactions to a New Delivery Channel, Journal of Financial Services Marketing”, Vol. 6,
No. 4, 2002, pp. 346–361

54