Foreign Trading System

FOREIGN TRADING SYSTEM
Submitted By
Vigneshwari.M & Mithradevi. - 3 rd year

INTRODUCTION :
This project emphasizes about the Foreign Trade System which is an
interface between the Account holder and the market. In the initial phase
details about the various currencies and the profit and loss of currency
hold is collected.
PROBLEM STATEMENT:
The main activity of international marketing is the export-import
procedure. This procedure involves the actual and operational procedure
of export and import trade. It also involves documentation, procedures,
rules and regulations imposed by both the exporting and importing
countries. These procedures include excise clearance, foreign exchange, etc.
SOFTWARE
REQUIREMENTS SPECIFICATION:
INTRODUCTION :
Foreign trading system is the interface between the exporter and
buyer. It aims at improving the efficiency in the production, export process
and reduce the complexities involved in it to the maximum possible extent.
PURPOSE :
Considering the fact that the number of buyer is increasing every
year, an Automated System becomes essential to meet the demand. So this
system uses several programming and database techniques to elucidate the
work involved in this process. The system has been carefully verified and
validated in order to satisfy it.
SCOPE:
The System provides an online interface to the buyer where they can
fill in their personal details and submit the necessary documents (may be
by scanning). The authority concerned with the production and shipment
of goods can use this system to reduce his workload and process the
application in a speedy manner.
DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS :
 Exporter – One who wishes to export the goods
 Importer - One who wishes to obtain the goods
 Regional authorities – Who provide service authority to individual
and business firms intending to export and/or import goods
 IEC Number – Importer-Exporter Number
 QC – Quality Control in order to ensure the quality of products
REFERENCES :
IEEE Software Requirement Specification format
TECHNOLOGIES TO BE USED :
 HTML
 JSP
 Java script
 Java
TOOLS TO BE USED :
 Eclipse IDE (Integrated Development Environment)
 Rational Rose tool (for developing UML Patterns)
OVERVIEW :
SRS includes two sections overall description and specific
requirements.
Overall description will describe major role of the system
components and inter-connections.
Specific requirements will describe roles & functions of the actors.
OVERALL DESCRIPTION:
It will describe major role of the system components and inter-
connections.
PRODUCT PERSPECTIVE :
This system tries to make the interface as simple as possible and at
the same time not risking the security of data stored in. This minimizes the
time.
SOFTWARE INTERFACE :
 Front End Client - The exporter online interface is built using JSP
and HTML.
 Web Server – Apache Tomcat Server (Oracle Corporation)
 Back End - Oracle 11g database
HARDWARE INTERFACE :
The server is directly connected to the client systems. The client
systems have access to the database in the server.
USE-CASE DIAGRAM:
The book bank use cases are:
1. Preliminaries
2. Offer order
3. Production of goods
4. Shipment
5. Negotiation of documents
ACTORS INVOLVED:
1. Exporter
2. Buyer
USE CASE DIAGRAM:

A use-case diagram is a graph of actors, a set of use cases enclosed by
a system boundary, communication associations between actors and the use
cases and generalization among use cases.
Use cases are text documents, not diagrams, and use-case modeling is
primarily an act of writing text, not drawing diagrams.
CLASS DIAGRAM:
A class diagram in the Unified Modeling Language (UML) is a type
of static structure diagram that describes the structure of a system by
showing the system's classes, their attributes and operations.
INTERACTION DIAGRAMS:
Sequence diagram:
Sequence diagrams are an easy and intuitive way of describing the
behavior of the system by viewing the interaction between the system and
its environment. A sequence diagram shows the objects participating in a
time sequence. It shows the objects participating in an interaction by their
lifelines and the messages they exchange, arranged in a time sequence. We can
also use terminologies like Opt, Alt, and Loop.
Collaboration diagram:
A collaboration diagram represents a collaboration, which is a set of
objects related in a particular context, and interaction, which is a set of
objects within the collaboration, to achieve a desired outcome.
ACTIVITY DIAGRAM:
An activity diagram is a variation or special case of state machine, in
which the states are activities representing the performance of operations
and transitions are triggered by the completion of the operations. An
activity diagram models the entire business process.
STATE CHART DIAGRAM:
A state diagram is a type of diagram used in computer science and
related fields to describe the behavior of systems. State diagrams require
that the system described is composed of a finite number of states;
sometimes, this is indeed the case, while at other times this is a reasonable
abstraction. There are many forms of state diagrams, which differ slightly
and have different semantics.
LOGICAL ARCHITECTURE DIAGRAM:
TECHNICAL SERVICES LAYER:
The Infrastructure Layer may be partitioned into different levels
(high-level or low-level technical services). Though, it is not unusual that
developers only consider the persistence (data access) and therefore only
talk about the Persistence Layer or the Data Access Layer (instead of an
Infrastructure Layer or Technical services Layer). In other words, the
other kind of technical services are not always being explicitly thought of as
being part of any particular layer.
DOMAIN LAYER:
A domain layer also known as the business logic layer (BLL) is a
software engineering practice of compartmentalizing. The business logic
layer is usually one of the tiers in a multitier architecture. It separates the
business logic from other modules, such as the data access layer and user
interface. By doing this, the business logic of an application can often
withstand modifications or replacements of other tiers.
USER INTERFACE LAYER:

This layer provides the user interface (UI) within a composite
application. To increase user productivity, user interfaces should support
easy adoption. The limitations on the UI design resulting from the
capabilities of the underlying components should not be seen as constraints,
but rather as some help to provide consistent UIs.
COMPONENT DIAGRAM:
A component diagram depicts how components are wired together to
form larger components and or software systems. They are used to
illustrate the structure of arbitrarily complex systems.
Components are wired together by using an assembly connector to
connect the required interface of one component with the provided
interface of another component. This illustrates -------------
DEPLOYMENT DIAGRAM:
A deployment diagram in the Unified Modeling Language models the
physical deployment of artifacts on nodes. The nodes appear as boxes, and
the artifacts allocated to each node appear as rectangles within the boxes.
Nodes may have sub nodes, which appear as nested boxes. A single node in
a deployment diagram may conceptually represent multiple physical nodes,
such as a cluster of database servers.
IMPLEMENTATION OF DOMAIN OBJECTS LAYER AND TECHNICAL SERVICE
LAYER :
//Source file: F:\\BuyerInfo.java
public class BuyerInfo

{
private String BuyerId;
private String BuyerName;
private String BuyerAddress;
private nteger BcontactNo;
private String BEmailId;
public Production theProduction;
/**
@roseuid 515917A5029F
*/
public BuyerInfo()
{
}
/**
@roseuid 515916D502DE
*/
public void SendConfirmedOrder()
{
}
}
//Source file: F\\exporterInfo.java
public class exporterInfo

{
private String ExporterName;
private String IEC_no;
private String Reg_no;
private String Address;
private Integer ContactNo;
private String Email_id;
public OfferOrder theOfferOrder;
/**
@roseuid 515917A50213
*/
public exporterInfo()
{
}
/**
@roseuid 51591524006D
*/
public void getIECNo()
{
}
/**
@roseuid 51591530035B
*/
public void getReg()
{
}
}
//Source file: F:\\OfferOrder.java
public class OfferOrder

{
private String Order_No;
private String BuyerName;
private String DescriptionOfGoods;
private Double Price;
private String ConditionOfSale;
private String Payment_Terms;
private String StatusOfOrder;
public exporterInfo theExporterInfo;
/**
@roseuid 515917A502DE
*/
public OfferOrder()
{
}
/**
@roseuid 515916510213
*/
public void SendOfferOrder()
{
}
/**
@roseuid 5159165A009C
*/
public void RecieveRecieptOfOrder()
{
}
}
//Source file: F:\\Production.java
public class Production

{
private String Order_no;
private String StatusOfProduction;
private String BuyerId;
public BuyerInfo theBuyerInfo;
/**
@roseuid 515917A50261
*/
public Production()
{
}
/**
@roseuid 5159157C0186
*/
public void PackingAndMaking()
{
}
/**
@roseuid 5159158C0261
*/
public void QC()
{
}
/**
@roseuid 5159158F037A
*/
public void Shipment()
{
}
/**
@roseuid 5159159602BF
*/
public void SubmitDocuments()
{
}
}
SCREEN SHOTS:
RESULT:
Thus the mini project for Book Bank System has been successfully executed and
codes are generated.

Foreign Trading System

Uploaded by

Copyright:

Available Formats

Foreign Trading System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Foreign Trading System

Uploaded by

Copyright:

Available Formats

FOREIGN TRADING SYSTEM

Vigneshwari.M & Mithradevi. - 3 rd year

USE CASE DIAGRAM:

USER INTERFACE LAYER:

//Source file: F:\\BuyerInfo.java

public class BuyerInfo

//Source file: F\\exporterInfo.java

public class exporterInfo

//Source file: F:\\OfferOrder.java

public class OfferOrder

//Source file: F:\\Production.java

public class Production

You might also like