ART MARKET

Department of Computer Science

Keshav Mahavidyalaya
University of Delhi

Software Engineering

Submitted by: Supervisor:

CHINMAYA AGGARWAL (231021) PROF.
SUMIT AGARWAL
KULDEEP YADAV (231035)
DIVYANSH KARNAWAT (231025)
 CERTIFICATE

This is to certify that the work embodied in this project

entitled “ART MARKET” has been carried out in the Department
of Computer Science, Keshav Mahavidyalaya, University of
Delhi. The work presented in this project is original and has
not been submitted in part or full to this or any other
University for any diploma or degree.

SIGNATURE
 DEClARATIon

I hereby declare that the project work entitled “ ART MARKET ” submitted to the Keshav
Mahavidyalaya University of Delhi College, is a record of an original work done by me under
the guidance of Dr. Sumit Kumar Agarwal, Assistant Professor, Department of Computer
Science, Keshav Mahavidyalaya and this project work is submitted in the partial fulfilment of
the requirements for the award of the degree of Bachelors in mathematical Sci (Computer
Science). The results embodied in this thesis have not been submitted to any other
University or Institute for the award of any degree or diploma.

SUBMITTED BY:
CHINMAYA AGGARWAL (231021)
KULDEEP YADAV (231035)
DIVYANSH KARNAWAT (231025)
 Index
1. Introduction

 1.1 Overview
 1.2 Key Features
 1.3 Features of This System
 1.4 Problem Statement
 1.5 Expectations
 1.6 Advantages
 1.7 Disadvantages of This System
 1.8 Feasibility Study
 1.9 Software Process Model

2. Software Requirements Specification

(SRS)

 2.1 Purpose
 2.2 Scope
 2.3 Technology Used
 2.4 Context Level (0 level DFD)
 2.5 DFD 1- Level
 2.6 DFD 2-Llevel

3. Specific Requirements

 3.1 Functional Requirements

 3.2 Data Tables
  3.3 Non-Functional
Requirements

4. Estimations
 4.1 Function Point Estimation
 4.2 Effort Estimation
5. Risk Analysis

 5.1 Risk Analysis Table

6. Testing

 6.1 Order Placement Module

 6.2 Test Cases for the Order
Placement Module
TABLE OF CONTENT
1. Introduction
1.1 overview

Welcome to Art Market – Where Creativity Meets Opportunity!

At Art Market, we believe that every piece of art tells a story. Our platform is dedicated to
connecting talented artists with passionate buyers from around the world. Whether you're
searching for a stunning painting, a unique sculpture, or an inspiring piece to complete your
space, Art Market is your trusted destination.
We are committed to supporting artists and providing art lovers with a seamless, secure, and
enriching shopping experience.
Join us today and discover a world of creativity, craftsmanship, and inspiration — only at Art
Market .

1.2 Key Features

🎨 Key Features of Art Market:

 Wide Range of Artworks

Paintings, sculptures, prints, and digital art — all styles, all forms, from emerging and
established artists.
 Artist-First Platform
We empower artists by offering fair commissions, artist profiles, and tools to showcase their
work beautifully.
 Authenticity Guaranteed
Every piece is verified for authenticity, so buyers can shop with complete confidence.
 Custom Orders
Commission personalized artworks directly from artists to fit your exact vision.
 Secure and Easy Transactions
Safe payment gateways and a simple, user-friendly checkout process.
 Global Shipping
We deliver artworks safely to customers around the world with trusted shipping partners.
  Community & Support
24/7 customer service and a growing community where art lovers and creators connect and
inspire each other.
 Art Discovery Tools
Smart filters, curated collections, and personalized recommendations to help buyers find the
perfect piece.
 Mobile Friendly
A fully responsive design, so you can browse and shop for art easily on any device.
 Exclusive Collections
Limited edition and exclusive artwork drops only available through Art Market.

1.3 Features of This System

 User Management

 Secure user registration and login (with email, phone, or social media).
 Separate dashboards for buyers and sellers (artists).
 Profile management (bio, profile picture, portfolio for artists).

 Product Management

 Artists can upload, edit, and manage their artworks easily.

 Admin approval system for new artworks.
 Categorization by style, medium, size, and price range.

 Order Management

 Track orders in real-time (pending, shipped, delivered, completed).

 Automated invoices and order history for users.
 Easy cancellation and return requests (if applicable).

 Payment System

 Integration with secure payment gateways (e.g., Stripe, PayPal).

 Support for multiple currencies.
 Wallet feature for artists (withdraw earnings securely).

 Search and Filter System

 Advanced search (by artist name, art style, size, color, price).
 Smart filtering and sorting options for faster discovery.

 Reviews and Ratings

 Buyers can leave reviews and rate artworks/artists.

 Artists can respond to reviews to engage with their customers.

 Notifications System
  Email and SMS notifications for orders, offers, and important updates.
 In-app notifications for real-time engagement.

 Content Management System (CMS)

 Admin panel to manage site content like banners, blogs, featured artists, and
homepage layouts.

 Security Features

 SSL encryption for data security.

 Two-factor authentication (optional).
 Protection against fraud and unauthorized access.

 Analytics and Reporting

 Sales reports for artists and admin.

 Traffic insights and performance tracking through dashboards.

 Marketing Tools

 Promo codes and discount management.

 Email marketing integration (like newsletters).
 Social media sharing options for artworks.

1.4 Problem Statement

 Artists struggle to find platforms to showcase and sell their art easily.
 Traditional galleries charge high commissions and offer limited exposure.
 Buyers face difficulty finding authentic and diverse artworks online.
 Existing platforms lack artist empowerment and buyer trust.
 There is a need for a secure, user-friendly marketplace connecting artists and art
lovers globally.

1.4 Expectations
The main expectations from the ART MARKET are:

 Provide a global platform for artists to sell their work easily.

 Offer buyers a wide variety of authentic and unique artworks.

 Ensure secure, smooth, and fast transactions.

 Create a user-friendly and visually appealing website experience.

 Build a trusted community for both artists and art lovers.

 Support artists with fair commissions and promotional tools.

 Enable easy management of artworks, orders, and payments.

 Drive growth through strong marketing and customer engagement

1.5 Advantages
The ART MARKET offers the following advantages:

• Global Reach: Artists can showcase their work to buyers worldwide.

• Low Commission: Better earnings for artists compared to traditional galleries.
• Authenticity Assurance: Buyers get verified, original artworks.
• User-Friendly Interface: Easy navigation for both artists and buyers.
• Secure Transactions: Safe payments and data protection.
• Custom Orders: Buyers can request personalized artworks directly.
• Community Building: A platform that connects and grows artists and art
lovers together.
• Marketing Support: Tools and promotions to help artists increase visibility.

1.6 Disadvantages of This System

While the ART MARKET offers numerous benefits, it also comes with a few limitations:

 High Competition: Many artists on the platform may make it harder for new artists
to stand out.
 Quality Control: Maintaining the quality and authenticity of all uploaded artworks
can be challenging.
 Shipping Issues: Handling delicate artworks during shipping can be risky and
expensive.
 Platform Dependency: Artists may rely heavily on the platform for sales, reducing
their independence.
 Customer Trust: Building trust in a new platform takes time and strong marketing
efforts.
 Technical Maintenance: Continuous updates, security checks, and system
improvements are needed.

1.7 Feasibility Study

A feasibility study was conducted to evaluate the technical, operational, and economic viability of
the ART MARKET.
1. Technical Feasibility

 Developing an e-commerce platform for artworks is technically achievable using modern technologies (like
React, [Link], PHP, Laravel, Shopify, etc.).
 Features like user dashboards, secure payment gateways, product management, and global shipping are
technically manageable.
 Regular maintenance and updates will be required to ensure smooth operation.

2. Economic Feasibility

 Initial investment needed for website development, hosting, marketing, and team setup.
 Revenue can be generated through commissions on artwork sales, featured listings, ads, and premium artist
accounts.
 Long-term profitability is achievable as the art market is growing online.

3. Operational Feasibility

 Artists and buyers can easily use the platform with a clean, user-friendly interface.
 Admin can manage artworks, users, orders, and website content from a powerful backend dashboard.
 Customer support will be essential to handle disputes, shipping issues, and inquiries.

4. Legal Feasibility

 The platform must comply with e-commerce laws, copyright regulations, data protection (GDPR if global),
and payment security standards.
 Agreements with artists to ensure rights and responsibilities are clearly defined.

5. Schedule Feasibility

 A full platform can be developed and launched within 4–8 months depending on team size and complexity.
 MVP (Minimum Viable Product) version can launch faster (around 3–4 months) with basic features
1.8 Software Process Model
We can use WATERFALL Model in ART MARKET because it emphasizes delivering incremental
improvements over time. In the context of your project, you can start by developing an initial, simple
version of the system (a working prototype or an MVP), then iteratively improve the system by
revisiting and refining various components based on feedback.
Iteration Features to Implement Objective Duration
Iteration Basic Menu, Order Placement, Basic system that allows menu 1-2
1 Inventory Tracking viewing and placing orders weeks
Iteration Filter Menu Items, Track Order Improve menu usability, track order 2 weeks
2 Status, Enhance Inventory statuses, add stock alerts
Iteration Admin Dashboard, Login System, Allow admin to manage orders and 2-3
3 Order History view reports weeks
Iteration Payment Integration, User Reviews, Finalize features for end users and 3 weeks
4 Advanced Reporting admin
Iteration Performance Optimization, Bug Fixes Fine-tune the system for production 01-Feb
5 readiness

2. Software Requirements Specification (SRS)

2.1 Purpose
The purpose of this document is to specify the requirements and expected behavior of ART
MARKET. This system aims to provide a bridge between vendors and customers, including
customer orders, inventory tracking, and payment processing. By defining clear system
requirements, this document serves as a guide for the development and implementation process.

The key goals of the AM are:

• Simplify customer ordering and payment.

• Help the staff manage inventory, orders, and payments.

• Provide easy-to-use interfaces for both customers and vendor.

• Reduce manual errors and improve efficiency.

2.2 Scope
This section outlines the boundaries of the project, describing what the system will and will not do.

In-scope Features:

• Customer Interface: Allows customers to browse the menu, place orders, and track order
status.
 • Order Management: Staff will receive and manage customer orders, updating their status (e.g.,
pending, completed).

• Menu Management: Admin/staff can add, edit, or remove items from the menu and update
prices.

• Inventory Management: Track inventory levels and alert staff when items are running low.

• Payment System: Customers can pay for orders (either through cash or online payment
methods).

• Reporting: Generate simple reports for staff/admin on daily sales, inventory, and customer
feedback.

Out of Scope:

• Advanced Analytics: Features like predictive analytics, customer behavior analysis, or advanced
financial forecasting will not be included in the initial version.

2.3 TECHNOLOGY USED

• Software Tool: Vscode

• Front end : HTML AND CSS

• Backend: NODE JS WITH [Link]

2.4 Data flow diagram

2.4.1 Level 0 Dfd

2.4.1 Level 1 DFD

2.4.2 Level 2 Dfd
3. SPECIFIC REQUIREMENTS

3.1 Functional Requirements

Here, we’ll focus on the key features that the system must have, written in simple terms for the
backend (Python) and frontend (SQL) environment.

Customer Functionalities:
1. Browse Menu:

o Customers can see the menu items with their name, description, and price.

o The menu will be displayed dynamically based on what's available.

2. Place Orders: o Customers can select items from the menu, specify the quantity, and place the

order.

3. Track Order Status:

o Customers can check the status of their order (e.g., "In Progress", "Completed").

4. Payment:

o Customers can pay either by cash or online payment (this can be a simple placeholder for
your project).

Staff/Admin Functionalities:

1. Manage Menu:

o Staff can add, edit, or remove menu items using Python scripts and SQL queries.

2. Manage Orders:

o Staff can view all orders, update statuses (e.g., mark orders as completed), and
assign them for preparation.

3. Inventory Management: o Track stock levels of menu items and get

alerts when stock is low.

4. Generate Reports: o Basic reports on the total number of orders and

inventory levels.

General Functionalities:

1. Login System: o Admin and staff will log in using a username and password

(authentication system).
 2. Notifications:

o Simple alerts for staff when an order is ready or stock is running low.

3.2 Data Tables

user_id INT (Primary Unique identifier for each
In this system, SQL will be used for
Key) user.
the database part. Here are the
username VARCHAR(50) Username for login. necessary data tables:
password VARCHAR(255) Encrypted password. 1. Users Table
Column Name Data Type Description
This table stores information about admin and staff.
2. Menu Table

This table stores all available menu items.

Column Name Data Type Description

item_id INT (Primary Key) Unique identifier for each item.

name VARCHAR(100) Name of the food item.

description TEXT Description of the food item.

price DECIMAL(10, 2) Price of the food item.

available BOOLEAN Is the item available? (True/False)

3. Orders Table

This table tracks customer orders.

Column Name Data Type Description

order_id INT (Primary Key) Unique identifier for each order.

user_id INT (Foreign Key) Link to the user (customer).

order_date DATETIME Date and time when the order was placed.

status VARCHAR(20) Status of the order (e.g., "pending", "completed").

total_price DECIMAL(10, 2) Total price for the order.

4. Order_Items Table

This table stores the details of each item in an order.

Column Name Data Type Description

order_item_id INT (Primary Key) Unique identifier for each order item.

order_id INT (Foreign Key) Link to the Orders table.

item_id INT (Foreign Key) Link to the Menu table.

 quantity INT Number of items ordered.

5. Inventory Table

This table keeps track of stock levels.

stock
Column Name INT
Data Type Amount of stock available.
Description

reorder_level
item_id INT (Primary Key, Foreign Key) Link
Stockto the
level at table.
Menu which to
reorder.

3.3 Non-Functional Requirements

Non-functional requirements specify the general system attributes and performance expectations.

1. Performance:

• Response Time: The system should respond to user actions (such as placing an order or browsing
the menu) within 2-3 seconds.

• Concurrency: The system should be able to handle up to 50 simultaneous users.

2. Usability:

• The system should have a simple, user-friendly interface for customers and staff.

• Customers should easily browse the menu and place orders, while staff should quickly update
orders and inventory.

3. Security:

• User Authentication: Staff and admin must log in with a username and password.

• Data Security: Passwords must be hashed and stored securely in the database.

4. Availability:

• The system should be available 24/7, but may have planned downtime for maintenance.

5. Scalability:

• The system should be scalable to handle a larger number of users as needed, especially during
peak hours like lunch.

4. Estimations
Estimating the size and effort involved in a software project is critical for planning, resource
allocation, and setting timelines. In this section, we'll use Function Points as a method to estimate
the size of the system, and Effort estimates to determine the resources (time and people) required to
complete the project.
 4.1 Function Points
Function points (FP) are a standardized way to measure the size and complexity of software based on
its functional requirements. Function points are calculated based on the number of features
(functions) the system will deliver and their complexity.

Steps for Function Point Estimation:

1. Identify and Categorize the Functional Components: Based on your project description, we
can identify several key functional components of the CMS. These will fall into one of the
following categories:

o External Inputs (EI): Data that enters the system (e.g., customer orders, admin login).

o External Outputs (EO): Data that leaves the system (e.g., order status, reports). o

User Inquiries (UI): Data retrieval requests (e.g., tracking order status).

o Internal Logical Files (ILF): Internal data storage entities (e.g., menu, inventory, user
accounts).

o External Interface Files (EIF): Data from external systems (e.g., external payment
gateways, supplier inventory).

2. Assign Complexity Levels: For each function, you'll assign a complexity level (Low, Average,
High) based on the amount of data processed or the complexity of the task. Typically, this is
done using the following criteria:

o Low Complexity: Simple tasks with few data elements (e.g., adding a single menu
item).

o Average Complexity: Tasks involving multiple data elements or several data fields (e.g.,
placing an order).

o High Complexity: Tasks involving large amounts of data or multiple interactions (e.g.,
generating detailed reports or complex order management systems).

3. Assign Function Points: Based on the complexity level, you will assign a function point value to
each category.

Functional Component Category Complexity Function Breakdown

of Function
Points
Points for
Customer Order Placement External Input High 4 the CMS:
(EI) Total
Customer Payment (Online or External Input Average 3 Function
Cash) (EI) Points:
Order Status Tracking User Inquiry (UI) Average 3
Menu Management External Input Average 3
(Add/Edit/Remove Items) (EI)
Inventory Management Internal Logical High 5
File (ILF)
Admin Login/Authentication External Input Low 2
(EI)
Order History for Admin External Output Average 3
(EO)
Generate Sales/Inventory External Output High 4
Reports (EO)
Payment Integration External Input High 4
(EI)
Notifications (Order ready, Low External Output Average 3
Stock) (EO)

 Sum of Function Points = 4 + 3 + 3 + 3 + 5 + 2 + 3 + 4 + 4 + 3 = 36 Function Points

4.2 Efforts
Effort estimation refers to the amount of time and resources required to implement the system based on
its function points. There are various methods to estimate efforts, but one common approach is using a
productivity factor.

Effort Estimation Formula:

The typical formula used for effort estimation in function point analysis is:

Effort (in person-hours)=Function Points×Productivity Factor\text{Effort (in person-hours)} =

\text{Function Points} \times \text{Productivity Factor}Effort (in personhours)=Function
Points×Productivity Factor

The Productivity Factor varies depending on the complexity and the development environment. A
typical range for Function Point to Person-Hour Conversion in an average-sized project is:

• Low Complexity: 10 - 15 person-hours per function point

• Medium Complexity: 15 - 25 person-hours per function point

• High Complexity: 25 - 40 person-hours per function point

For this estimation, let’s assume a medium complexity (since your CMS includes some moderately
complex features like real-time tracking, menu management, payment integration, and reporting).
Based on this, we’ll use a productivity factor of 20 person-hours per function point.

Effort Calculation:

Effort=36Function Points×20Person-Hours/Function Point

Effort=720 Person-Hours

Effort Breakdown:

You can further break down this effort into phases of the project based on the iterations. For example:

• Iteration 1 (Basic Menu and Order Placement): 150 hours (focus on basic functionality)

• Iteration 2 (Enhanced Menu, Order Status Tracking, and Inventory): 200 hours (focus on more
complex functionality like inventory alerts)

• Iteration 3 (Admin Dashboard and User Authentication): 170 hours

• Iteration 4 (Payment Integration, User Reviews, Reports): 150 hours

• Iteration 5 (Optimization, Bug Fixes): 50 hours

Summary of Estimates:

1. Function Points: 36 FP 2. Total

Effort: 720 person-hours

Project Timeline:
Considering an average developer working at 40 hours/week, the total estimated effort translates to:

Project Duration=720Person-Hours/ 40Hours/Week=18Weeks

This translates to around 4 to 5 months for the development of your CMS, depending on the size of
the development team and other factors.

5. Risk Analysis

Risk Impact Probability Mitigation

(Quantified) (%) Strategy

1. Staff 15-25% decrease 10-15% Cross-training,

Illness in operational backup staff,
efficiency. flexible shifts.
2. System 20-40% of orders 5-10% Backup servers,
Downtime delayed. cloud hosting,
(Network UPS.
Failure)
3. Incorrect 10-20% of stock 5-10% Automated
Inventory inaccurate. alerts, regular
Tracking checks.
4. Payment 10-15% of orders 3-5% Reliable
Processing delayed. payment
Failures gateways,
monitoring.
5. Low User 20-30% fewer 15-20% Tutorials,
Adoption users. promotions,
awareness
campaigns.
6. Admin 5-10% of menu 5-10% Admin training,
Errors items wrong. verification
(Menu before
Updates) deployment.
7. Slow 5-10% of orders 10-15% Optimize
System delayed. backend, load
Performance testing, query
improvements.

[Link]
6.1 Order placement module
# Run the order module

place_order()

# ArtMarket Website - Simplified

Source Code and Explanation

## [Link] - SIMPLIFIED

<!DOCTYPE html>

<html lang="en">

<head>

<meta charset="UTF-8">

<meta name="viewport"

content="width=device-width, initial-

scale=1.0">

<title>ArtMarket - Home</title>

<!-- Tailwind CSS for styling -->

<script

src="[Link]

script>

<style>

/* Basic style for the hero

background and card animations */

.hero-bg {
 background-image:

url('[Link]

oto-1579546929518-9e396f3cc809');

background-size: cover;

.card:hover {

transform: translateY(-5px);

</style>

</head>

<body class="bg-gray-50">

<!-- Navigation Bar -->

<header class="bg-white shadow-

sm">

<nav class="container mx-auto

px-4 py-4 flex justify-between items-

center">

<div class="text-2xl font-bold

text-indigo-600">ArtMarket</div>

<!-- Main Navigation Links -->

<div class="space-x-4">

<a href="#" class="text-gray-

600

hover:text-indigo-600">Home</a>
 <a href="#" class="text-gray-

600 hover:text-indigo-

600">Artists</a>

<a href="#" class="text-gray-

600 hover:text-indigo-

600">Artworks</a>

</div>

<!-- Login Buttons -->

<div class="space-x-4">

<a href="[Link]"

class="bg-indigo-600 text-white px-4

py-2 rounded-md">Artist Login</a>

<a href="[Link]"

class="bg-white text-indigo-600

border border-indigo-600 px-4 py-2

rounded-md">Customer Login</a>

</div>

</nav>

</header>

<!-- Hero Section with Background

Image -->

<section class="hero-bg h-screen

flex items-center justify-center">

<div class="text-center text-

white">
 <h1 class="text-5xl font-bold

mb-4">Welcome to ArtMarket</h1>

<p class="text-xl mb-

8">Discover and showcase unique

artworks from talented artists

worldwide</p>

<div class="space-x-4">

<a href="[Link]"

class="bg-indigo-600 text-white px-6

py-3 rounded-md">Join as Artist</a>

<a href="[Link]"

class="bg-white text-indigo-600 px-6

py-3 rounded-md">Browse

Artworks</a>

</div>

</div>

</section>

<!-- Features Section (Why Choose

Us) -->

<section class="container mx-auto

px-4 py-16">

<h2 class="text-3xl font-bold

text-center mb-12">Why Choose

ArtMarket?</h2>
 <div class="grid grid-cols-1

md:grid-cols-3 gap-8">

<!-- Feature Card for Artists -->

<div class="card bg-white p-6

rounded-lg shadow-md">

<div class="text-indigo-600

text-4xl mb-4">🎨</div>

<h3 class="text-xl font-

semibold mb-2">For Artists</h3>

<p class="text-gray-

600">Showcase your work, connect

with buyers, and manage your art

business in one place.</p>

</div>

<!-- More feature cards would

go here -->

</div>

</section>

<!-- Simple Footer -->

<footer class="bg-gray-800 text-

white py-8 text-center">

<p>&copy; 2024 ArtMarket. All

rights reserved.</p>

</footer>
</body>

</html>

6.2 Test Cases for the Order Placement Module

1. Test Case 1: Valid Order Placement

2. Test Case ID: TC01

3. Objective:
Verify that the system successfully allows a customer to select artwork, add it to the cart,
proceed to payment, and complete the order correctly.

4. Preconditions:

5. User is logged into the system.

6. Artworks are available in the catalog.

7. Test Steps:

8. Open the Art Market platform.

9. Browse and select a valid artwork.

10. Click "Add to Cart."

11. Proceed to Checkout.

12. Enter valid payment details.

13. Confirm payment.

14. Expected Result:

15. Order is placed successfully.

16. Payment success message displayed.

17. Order summary shown.

18. Email/SMS confirmation received.

19.

20. Test Case 2: Invalid Artwork Selection

21. Test Case ID: TC02

22. Objective:
Verify that the system handles invalid artwork selections.

23. Test Steps:

24. Attempt to select an invalid artwork ID.

25. Try to add it to the cart.

26. Expected Result:

27. Error message displayed: "Invalid Artwork Selected."

28. No artwork is added to the cart.

29.

30. Test Case 3: Invalid Quantity Input

31. Test Case ID: TC03

32. Objective:
Ensure that the system handles non-numeric quantity inputs correctly.

33. Test Steps:

34. Select a valid artwork.

35. Input non-numeric value (e.g., "two") for quantity.

36. Expected Result:

37. Error message displayed: "Please enter numeric quantity."

38. System does not proceed.

39.

40. Test Case 4: Order Cancellation

41. Test Case ID: TC04

42. Objective:
Verify that users can cancel an order before payment.

43. Test Steps:

44. Add artwork to cart.

45. Proceed to checkout.

46. Click "Cancel Order."

47. Expected Result:

48. Order is canceled.

49. Message displayed: "Order Cancelled."

50.

51. Test Case 5: Empty Cart Checkout

52. Test Case ID: TC05

53. Objective:
Ensure the system prevents checkout when the cart is empty.
 54. Test Steps:

55. Without adding any artwork, click on "Checkout."

56. Expected Result:

57. Warning displayed: "No items in cart to checkout."

58.

59. Test Case 6: Multiple Artworks Checkout

60. Test Case ID: TC06

61. Objective:
Verify correct total calculation when multiple artworks are selected.

62. Test Steps:

63. Select multiple artworks.

64. Add them to the cart.

65. Proceed to checkout.

66. Expected Result:

67. System correctly calculates and displays subtotal and total.

68.

69. Test Case 7: Correct Order Summary Display

70. Test Case ID: TC07

71. Objective:
Verify that the order summary displays correct item names, quantities, and total cost.

72. Test Steps:

73. Add artworks to cart.

74. View the cart/checkout page.

75. Expected Result:

76. Order summary shows accurate details for each artwork.

Test Case ID Test Case Description Test Steps Expected Result

TC01 Valid Artwork Purchase Select artwork → Add Payment success, order
to cart → Make generated
payment

TC02 Invalid ARTWORK Selection Select non-existing Error: "Invalid Artwork

artwork ID Selected"
TC03 Invalid Quantity Input Input non-numeric Error: "Please enter
quantity (e.g., 'two') numeric quantity"

TC04 Order Cancellation Add to cart → Cancel "Order Cancelled"

before payment message shown
.

TC05 Empty Cart Checkout Try checkout with Warning: "No items in
empty cart cart"

TC06 Multiple artworks checkout Add multiple artworks Correct total, order
→ Checkout summary accurate

TC07 Correct Order Summary Select artworks → View Correct items, quantities,
Display cart summary and total shown
.

[Link]

The art market stands as a dynamic intersection of culture, creativity, and commerce. Over time, it has
evolved from traditional gallery spaces to global online platforms, expanding access and reshaping how art
is bought, sold, and valued. Driven by collectors, investors, institutions, and emerging technologies, the
market reflects broader economic, social, and political trends. While it offers opportunities for artists and
investors alike, it also faces challenges such as issues of authenticity, inequality, and market volatility.
Looking ahead, the art market is expected to continue growing, embracing innovation while preserving its
deep cultural significance.