Information

System Design
Project
Freshmen year

Titled

1
 DECLARATION

I certify that I am the author of this report and that any assistance I have received in its preparation is
fully acknowledged and disclosed in this report. I have also cited any source from which I used data,
ideas, or words, either quoted or paraphrased. Further, this report meets all of the rules of quotation
and referencing in use at TBS, as well as adheres to the fraud policies listed in the TBS honor code.

No portion of the work referred to in this report has been submitted in support of an application for
another degree or qualification to this or any other university or academic institution.

Azza Jomni 20/03/2023

Student Name Signature Date

2
 Table of Contents

A. Introduction-----------------------------------------------------------------------------------
1.1 Origin of need ………………………………………………………………..………………………………………
1.2 Purpose………………….……………………………………………..……………………………………………….
1.3 References ……………………………………………………………………………………………………………

B. System Requirements -------------------------------------------------------------------

1.1 Interfaces with Other Systems………………….……………………………..

………………….
1.2 Functional Requirements ………………………………………………………………..
………..
1.3 Non-Functional Requirements….
………………………………………………………………...

C. System Design--------------------------------------------------------------------------------

1.1 Use case

Diagram………………………………………………………………………………….
1.2 Class Diagram...…...
……………………………………………………………………………….

D. System Development----------------------------------------------------------------------

1.1 Relational Schemas………………………………..

……………………………………………….
1.2 SQL
Program……………………………………………………………………………………….
1.3 Results of the program ………………………….……..
…………………………………………..

3
 E. Conclusion--------------------------------------------------------------------------------------

1.1Conclusion………………………………………………………………………………………..

1.2 Our Vision...…...…………………………………………………………………………..

……..

A. Introduction:
1.Origin of Need:
Artisans located in rural areas, face significant challenges in generating profit
from their goods due to two reasons:
 many artisans lack the skills and resources to effectively market their
products (due to high illiteracy rate).
 Artisans access to potential customers is limited by geographical
boundaries.
Key functionalities include: product listings managed by employees,
simplified artisan agreements, inventory management and seamless
transactions with integrated payment gateways and order tracking.
This platform aims to increase artisans' profitability and provide a user-
friendly interface for customers to purchase handmade goods.

2.Purpose
The purpose of the Software Requirements Specification document is to
outline the functionality and features of the Artisanal Goods Sales System
(AGSS).
The intended audience of this document includes the administrators of the
AGSS platform, artisans who will be selling their goods through the system,
shop owners or managers who will host the physical placements of goods, the
direct buyers from the online shop, as well as developers and other
stakeholders involved in the development process such as the requirements
team, requirements analyst, design team, and other members of the
developing organization.

3.References:
Visitor: any individual with the access to the system interface.

4
 Member: registered visitor of the platform who can purchase goods.
Artisan: an individual who can add goods and remove them.
Employee: individual who can add and remove goods and artisans from the
inventory.
AGSS: artisanal goods sales system.

B. System Requirements
1. Interfaces with Other Systems:

The AGSS is a web-based system that interfaces with the owner's email system for
communication purposes (notifications and updates). Additionally, it interacts with
various web browsers used by customers to access the platform.

This system provides web access for all customer and artisan functions. The user interface
will be intuitive enough so that no training is required by customers, artisans or store
personnel. All online financial transactions and the storage of confidential member
information will be done in a secure environment. Persistent storage for membership,
rental, and video inventory information will be maintained.

2.Functional requirements:

1. The system shall allow visitors to become members.

1.1 The system shall assign a member ID and allow the member to set a password.
1.2 The system shall store membership information for future reference.
2. The system shall allow visitors or members to search for artisanal goods
information.
3. The system shall ensure secure login for browsing and making purchases.
4. The system shall allow members to search for artisans.
5. The system shall provide artisans’ contact information to members.
6. The system shall allow members to add artisanal goods to cart.
7. The system shall allow members to pay for goods added to cart.
8. The system shall allow members to modify their membership information.
9. The system shall allow employees to add artisanal goods.
10. The system shall allow employees to remove artisanal goods from the inventory.
11. The system shall allow employees to add artisans to the inventory.
12. The system shall allow artisans to add artisanal goods.
13. The system shall allow artisans to remove
14. The system shall send notifications to members.
14.1 The system shall send notifications when a new good is added.
14.2 The system shall send an email notification after the confirmation of an
order.
15. The system shall send notifications to artisans.
15.1 The system shall send an email notification after the confirmation of an
order.

5
 15.2 The system shall send an email notification if a good is out of stock.

3.Non-Functional Requirements:
1. The system shall offer a user interface that requires no training.
2. The system shall support visitors at the same time while maintaining optimal
performance.
3. The system shall be compatible with the company’s data storage system.
4. The system shall be reliable and shall perform without failure in any use case.
5. The system shall guarantee a protection of all data inside it against malware
attacks or unauthorised access.

C. System design:
1.UML Use Case Diagram:

6
2.UML Class Diagram:

addemployee()
removeeployee()

7
 D. System Development:
1. Relational Schemas

Member (Memail, credit_card, name, address, phonenumber)

Artisan (artisanID, address, workshop, #managerID)
Admin (#employeeID)
Employee (employeeID, ename, eemail)
Product (productID, price, artisan, #employeeID)
Payment (payID, total, #Memail, #productID, #cartID)
offline (#payID, cash_tendered)
online (#payID, paytype:{visa, e-dinard, banktransfer, paypal}, Vcardnum, ecardnum,
bancnum,pcardnum,#bankID)
Bank (bankID, Bname, Baddress, Bemail, Bphone)
Cart (cartID, numofproducts, total)
Product_Cart (#productID, #cartID)

2.SQL Program:

CREATE DATABASE AGSS

USE AGSS

CREATE TABLE Member (

Memail VARCHAR(50),
credit_card VARCHAR(16),
name VARCHAR(50),
address VARCHAR(255),
phonenumber VARCHAR(8),
PRIMARY KEY (Memail)
);

CREATE TABLE Artisan (

artisanID INT,
address VARCHAR(255),
workshop BOOLEAN,
managerID INT,
PRIMARY KEY (artisanID),
FOREIGN KEY (managerID) REFERENCES Employee(employeeID)
);

8
CREATE TABLE Employee (
employeeID INT,
ename VARCHAR(50),
eemail VARCHAR(50),
PRIMARY KEY (employeeID)
);

CREATE TABLE Admin (

employeeID INT,
PRIMARY KEY (employeeID),
FOREIGN KEY (employeeID) REFERENCES Employee(employeeID)
);

CREATE TABLE Product (

productID INT,
price DECIMAL(10, 2),
artisan INT,
employeeID INT,
PRIMARY KEY (productID),
FOREIGN KEY (artisan) REFERENCES Artisan(artisanID),
FOREIGN KEY (employeeID) REFERENCES Employee(employeeID)
);

CREATE TABLE Payment (

payID INT,
total DECIMAL(10, 2),
Memail VARCHAR(50),
productID INT,
cartID INT,
PRIMARY KEY (payID),
FOREIGN KEY (Memail) REFERENCES Member(Memail),
FOREIGN KEY (productID) REFERENCES Product(productID),
FOREIGN KEY (cartID) REFERENCES Cart(cartID)
);
CREATE TABLE Bank (
bankID INT,
Bname VARCHAR(100),
Baddress VARCHAR(255),
Bemail VARCHAR(50),
Bphone VARCHAR(20)
PRIMARY KEY (BankID),
);
CREATE TABLE Cart (
cartID INT PRIMARY KEY,
numofproducts INT,
total DECIMAL(10, 2)
);

9
CREATE TABLE Product_Cart (
productID INT,
cartID INT,
PRIMARY KEY (productID, cartID),
FOREIGN KEY (productID) REFERENCES Product(productID),
FOREIGN KEY (cartID) REFERENCES Cart(cartID)
);

CREATE TABLE offline (

payID INT,
cash_tendered DECIMAL(10, 2),
PRIMARY KEY (payID),
FOREIGN KEY (payID) REFERENCES Payment(payID)
);

CREATE TABLE online (

payID INT PRIMARY KEY,
paytype ENUM('visa', 'e-dinard', 'banktransfer', 'paypal'),
Vcardnum VARCHAR(16),
ecardnum VARCHAR(16),
bancnum VARCHAR(16),
pcardnum VARCHAR(16),
bankID INT,
PRIMARY KEY (payID),
FOREIGN KEY (payID) REFERENCES Payment(payID),
FOREIGN KEY (bankID) REFERENCES Bank(bankID)
);

INSERT INTO Member (Memail, credit_card, name, address, phonenumber)

VALUES ('[email protected]', '5896146375', 'azza jomni', '25 Hay
Hachad Ejdid, 2050', '50212885');

INSERT INTO Employee (employeeID, ename, eemail)

VALUES (1, 'Aziz Chouala', '[email protected]');

INSERT INTO Artisan (artisanID, address, workshop, managerID)

VALUES (1, '23 Hay eicha Bir el Kasaa', TRUE, 2);

INSERT INTO Admin (employeeID)

VALUES (3);

INSERT INTO Product (productID, price, artisan, employeeID)

VALUES (12, 250, 1, 2);

INSERT INTO Cart (cartID, numofproducts, total)

VALUES (2, 2, 500);

10
INSERT INTO Payment (payID, total, Memail, productID, cartID)
VALUES (1, 257, '[email protected]', 12, 1);

INSERT INTO Bank (bankID, Bname, Baddress, Bemail, Bphone)

VALUES (1453, 'Amen Bank', 'Avenue Mohammed V, Tunis 1002',
'[email protected]', '');

INSERT INTO Product_Cart (productID, cartID)

VALUES (12, 2);

INSERT INTO offline (payID, cash_tendered)

VALUES (1, 510);

INSERT INTO online (payID, paytype, Vcardnum, ecardnum, bancnum,

pcardnum, bankID)
VALUES (1, 'visa', '400911086431000', NULL, NULL, NULL, NULL);

3. Results of the program:

(generated by SQLite)

11
 E. Conclusion:
1. conclusion
Handiworks is a solution designed to help artisans overcome challenges in selling
their products and increase their profitability by expanding their target audience.
This document has outlined the system requirements for the AGSS, its system
design and system development ensuring a use-friendly experience for everyone
that interacts with its interface. By supporting artisans and enhancing customer
satisfaction, AGSS aims to create a sustainable and profitable ecosystem for
handmade goods.

12
 2.Next steps
AGSS can bridge the gap between the artisans and their potential customers.
With ongoing development and maintenance, AGSS can become an important
tool to empower economic growth and Tunisia’s cultural heritage. We envision
the AGSS evolving into a platform that constantly adapts to the evolving needs
of its customers.
To transform this vision into a reality, the next steps are as mentioned:
developing a user-friendly interface, securing funding, partnering with artisans,
and finallyn, creating, sponsoring and managing artisanal fairs for our members.
By following these steps, the AGSS can transform from a concept into a reality,
empowering artisans, connecting them with a global audience, and ultimately,
preserving the beauty and tradition of handcrafted goods.

13