Professional Documents
Culture Documents
Submitted by
Chapter
Title Page No.
No.
1. Abstract
2. Introduction
3. Problem Statement
4. Module Description
6. ER diagram
8. Normalization of Database
10. Conclusion
11 Appendix I - Screenshot
SIGNATURE SIGNATURE
INTRODUCTION
A foreign trading system is a complex network of institutions, individuals, and transactions that
facilitate the exchange of goods and services across international borders. The system includes
various players such as importers, exporters, manufacturers, freight forwarders, banks, customs
officials, and government agencies. The process involves a wide range of activities, including
negotiation, transportation, logistics, financing, and documentation.
PURPOSE
The purpose of a foreign trading system is to facilitate the exchange of goods and services
between countries. It is a platform that enables individuals and organizations from different
countries to conduct international trade transactions.
SCOPE
• The System provides an online interface to the user where they can fill in their personal
details and register for a trade. with the issue of invoice and ID’s which can use this
system to reduce workload and process the application in a speedy manner.
• Provide a communication platform between the seller and the buyer.
• buyers will come to know their status of foreign trade and the details of trade.
PROBLEM STATEMENT
The Foreign Trading System (FTS) is an online platform that allows traders to buy and sell
foreign currencies and other financial instruments. The problem statement for FTS is to
design and develop a system that enables traders to perform secure and efficient
transactions, access real-time market information, and manage their portfolios effectively.
The system should provide traders with a user-friendly interface that facilitates easy
navigation and quick access to relevant information. Additionally, the system should ensure
compliance with relevant regulations and security standards, and enable seamless
integration with external systems and services. Overall, the goal of the FTS is to provide a
robust and reliable platform for foreign currency trading that meets the needs and
expectations of traders and other stakeholders.
MODULE DESCRIPTION
Module-1: Is the login form in which the user or the admin has to enter the username and
password to enter into the Foreign trading application system.
Module-2: Is the form where the customer can enter in to register their details and in
the same form the admin can enter to manage the customer data base and to retrieve
it.
Module-3: Is the form where the customer buys or trades the available products.
Module-4: Is the form where the admin maintains the customer, orders and products
database to insert, delete and update. The complete data of the customer can otherwise
be viewed in grid form.
USECASE DIAGRAM
The foreign trading use cases in our system are:
1. Login
3. Register
4. Acknowledgement
5. Buyer Processing
ACTORS INVOLVED:
1. Exporter
2. Buyer
Offer is a proposal submitted by an exporter expressing his intention to export specific goods at a
specific price with specific terms and conditions. Exporter usually makes an offer in the form of a
‘Proforma Invoice’.
The exporting house after obtaining a confirmed order should produce the goods exactly as specified
in the invoice. If the exporting house does not have facilities, it has to procure the products from
others.
The exporter submits the relevant documents to his buyer (banker) for getting the payment for the
goodexported.
Preliminaries
RegionalAuthori
ties
Offer Order
Exporter Buyer
Production of goods
Shipment
USING DDL
For customers
CREATE TABLE customers (
customer_id INT PRIMARY
KEY,
customer_name VARCHAR(255) NOT
NULL, customer_email VARCHAR(255)
NOT NULL,
customer_phone VARCHAR(20) NOT NULL,
customer_address VARCHAR(255) NOT
NULL
);
For products
CREATE TABLE products (
);
For orders
CREATE TABLE Orders (order_id
INT PRIMARY KEY, customer_id
INT NOT NULL, totalamount INT
NOT NULL,
order_date DATE NOT NULL,
);
USING DML
For customers
INSERT INTO customers (customer_id, name, address, phone, email)
VALUES
(1, 'John Smith', '123 Main St., Anytown USA', '555-555-1212', 'johnsmith@email.com'),
(2, 'Jane Doe', '456 Elm St., Anycity USA', '555-555-1313', 'janedoe@email.com'),
(3, 'Bob Johnson', '789 Oak St., Anyvillage USA', '555-555-1414', 'bobjohnson@email.com');
For orders
INSERT INTO orders (order_id, customer_id, order_date, total_amount)
VALUES
(1, 1, '2022-01-01', 100.00),
(2, 2, '2022-01-02', 200.00),
(3, 3, '2022-01-03', 300.00);
For Products
INSERT INTO products (product_id, name, description, price)
VALUES
(1, 'Widget', 'A small gadget', 10.00),
(2, 'Gizmo', 'A larger gadget', 20.00),
Orders
1 1 2022-01-01 100.00
2 2 2022-01-02 200.00
3 3 2022-01-03 300.00
products
First Normal Form (1NF): Each table should have a primary key, and each column should
contain atomic values. This means that each column should hold a single value, rather than
a list or set of values.
Second Normal Form (2NF): Each non-key column should be fully dependent on the primary
key. This means that there should be no partial dependencies, where a non-key column
depends on only a portion of the primary key.
Third Normal Form (3NF): Each non-key column should be dependent only on the primary
key, and not on any other non-key columns. This means that there should be no transitive
dependencies, where a non-key column depends on another non-key column.
Customer_id Customer_name Product_name contact Product_price
1 John smith widget 555-555-1212 10.00
2 Jane doe gizmo 555-555-1313 20.00
3 Bob johnson thingamabob 555-55551414 30.00
• As the attributes of this table does not have sub attributes, it is in first normal
form.
• Because every non-primary key attribute is fully functionally dependent on the
primary key of the table and it is already in first normal form, this table is now
in second normal form.
• Since the table is in second normal form and no nonprimary key attribute is
transitively dependent on the primary key, the table is now in 3NF.
• Since the table is in 3NF and no prime key is dependent on non-prime key, so
the table is in BCNF.
{customer_name} → {first name} (functional dependency exists)
{customer_id} → {Id} (functional dependency exists)
2. ORDERS
• As the attributes of this table does not have sub attributes, it is in first normal
form.
• Because every non-primary key attribute is fully functionally dependent on the
primary key of the table and it is already in first normal form, this table is now
in second normal form.
• Since the table is in second normal form and no nonprimary key attribute is
transitively dependent on the primary key, the table is now in 3NF.
• Since the table is in 3NF and no prime key is dependent on non-prime key, so
the table is in BCNF.
3. PRODUCTS
• As the attributes of this table does not have sub attributes, it is in first normal
form.
• Because every non-primary key attribute is fully functionally dependent on the
primary key of the table and it is already in first normal form, this table is now
in second normal form.
• Since the table is in second normal form and no nonprimary key attribute is
transitively dependent on the primary key, the table is now in 3NF.
• Since the table is in 3NF and no prime key is dependent on non-prime key, so
the table is in BCNF.
2. Create a DynamoDB table: Create a table in DynamoDB to store the data. Define the
primary key for the table, which could be a single partition key or a combination of a
partition key and a sort key.
3. Define the table schema: Define the attributes that you want to store in the table. You
can also specify any secondary indexes that you want to create.
1. Data model:
• Customer
✓ ID
✓ Name
✓ Email
✓ Phone
• ORDERS
✓ ID
✓ Name
✓ Date
✓ PRICE
• PRODUCTS
✓ ID
✓ CUSTOMER_ID
✓ PRICE
✓ Date
2. DynamoDB table:
• Table name: ForeignTrading
• Primary key: Partition key - ID (string)
3. Table schema:
• Attributes:
✓ ID (string)
✓ Name (string)
✓ Email (string)
✓ product ID (string)
✓ Phone (int)
✓ Order Date (string)
✓ Price (int)
Secondary indexes:
• GSI1: Partition key - ID (string),
CODE:-
3:-
{
"ID": {
"S": "3"
},
"ADDRESS": {
"S": "789 Oak St., Anyvillage USA"
},
"EMAIL": {
"S": "bobjohnson@email.com"
},
"NAME": {
"S": "Bob Johnson"
},
"PHONE": {
"S": "99009902"
}
}
2:-
{
"ID": {
"S": "2"
},
"ADDRESS": {
"S": "456 Elm St., Anycity USA"
},
"EMAIL": {
"S": "janedoe@email.com"
},
"NAME": {
"S": "Jane Doe"
},
"PHONE": {
"S": "99009901"
}
}
1:-
{
"ID": {
"S": "1"
},
"ADDRESS": {
"S": "123 Main St., Anytown USA"
},
"EMAIL": {
"S": "johnsmith@email.com"
},
"NAME": {
"S": "John Smith"
},
"PHONE": {
"S": "9909900"
}
}
1:-
{
"ID": {
"S": "1"
},
"CUS_ID": {
"S": "1"
},
"ORDER_DATE": {
"S": "01-01-2022"
},
"TotalAmount": {
"S": "100.00"
}
}
2:-
{
"ID": {
"S": "2"
},
"CUS_ID": {
"S": "2"
},
"ORDER_DATE": {
"S": "02-01-2002"
},
"TotalAmount": {
"S": "200.00"
}
}
3:-
{
"ID": {
"S": "3"
},
"CUS_ID": {
"S": "3"
},
"ORDER_DATE": {
"S": "01-01-2002"
},
"TotalAmount": {
"S": "100.00"
}
}
1:-
{
"ID": {
"S": "1"
},
"DESCRIPTION": {
"S": "a small gadget"
},
"NAME": {
"S": "Widget"
},
"PRICE": {
"S": "10.00"
}
}
2:-
{
"ID": {
"S": "2"
},
"DESCRIPTION": {
"S": "a large gadget"
},
"NAME": {
"S": "Gizmo"
},
"PRICE": {
"S": "20.00"
}
}
3:-
{
"ID": {
"S": "3"
},
"DESCRIPTION": {
"S": "a very large gadget"
},
"NAME": {
"S": "Thingamabob"
},
"PRICE": {
"S": "30.00"
}
}
CONCLUSION
REGISTRATION FORM
Appendix II - GitHub Profile
https://github.com/jettylalith
Appendix III - AWS Course Completion certificate
RESULT:
Thus the mini project for FOREIGN TRADING SYSTEM has been successfully executed and codes are generated.