Software Requirements
Specification
For

FOREIGN TRADING SYSTEM

Version 1.0 approved

Prepared by KRISHNA PANDI

PRIYADHARSAN
PONNIEN SELVAN
NARESH KUMAR

PSNA COLLEGE OF ENGINEERING AND TECHNOLOGY,DINDIGUL

15 SEPTEMBER 2021
th
 Table of Contents

Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose 1
1.2 Document Conventions 1
1.3 Intended Audience and Reading Suggestions 1
1.4 Product Scope 1
1.5 References 1
2. Overall Description 2
2.1 Product Perspective 2
2.2 Product Functions 2
2.3 User Classes and Characteristics 2
2.4 Operating Environment 2
2.5 Design and Implementation Constraints 2
2.6 User Documentation 2
2.7 Assumptions and Dependencies 3
3. External Interface Requirements 3
3.1 User Interfaces 3
3.2 Hardware Interfaces 3
3.3 Software Interfaces 3
3.4 Communications Interfaces 3
4. System Features 4
4.1 System Feature 1 4
4.2 System Feature 2 (and so on) 4
5. Other Nonfunctional Requirements 4
5.1 Performance Requirements 4
5.2 Safety Requirements 5
5.3 Security Requirements 5
5.4 Software Quality Attributes 5
5.5 Business Rules 5
6. Other Requirements 5
Appendix A: Glossary 5
Appendix B: Analysis Models 5
Appendix C: To Be Determined List 6

Revision History
Name Date Reason For Changes Version
1. Introduction
1.1 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.

1.2 Document Conventions

T he document follows the IEEE format standard (IEEE Std. 830-1998).

1.3 Intended Audience and Reading Suggestions

Audience:
The intended audience of this document is investors, traders and all business
entrepreneurs.
Organization
This software is used by the trade brokerage organizations that perform
the trade on behalf of theinvestors

1.4 Product Scope

The online Foreign Currency Trading system enables you can
have 24 hour updates of  your investment in currency from the
convenience of your own home. 
The Foreign Currency trading system involves no exchange fees,
commissions and payments of  that sort. The margin and leverage
trading allows you to increase your earnings by up to 100  times more
than regular currency trading. This means larger profits and can benefit
some  investors. Currency Converter gives you accurate and instant
foreign currency conversions. The  options are varied for minimum
currency trading investments. There is also mini account where  with a
very small initial investment in a leveraged foreign currency, you can
reach a high reward  through minimal risk. 

1.5 References
- Pressman, Roger S. Software Engineering: A Practitioner’s
Approach. New York, NY: McGraw Hill, 2005.
 - Lecture slides 
The user manual can be read in order to understand the
specification. In case of classification and  details of access the manual
can be referred. 

2. Overall Description
2.1 Product Perspective

The proposed foreign trading system is an on-line system. This

system will provide an  online currency trading service for investors by
taking in live feed in of international  currency status. 

2.2 Product Functions

⮚ Generates working software quickly and early during the

software life cycle.

⮚ More flexible-less costly to change scope and

requirements. 

⮚ Easier to test and debug during a smaller iteration. Easier to manage

risk during its  Iteration. 
⮚ Each iteration is an easily managed milestone. 
⮚ Each component is delivered to the client when it is complete. This
allows partial  utilization of product and avoids long
development time. 
. 
2.3 User Classes and Characteristics

  There are various kinds of users for this product 

∙ Investors 
∙ Traders 
∙ Brokers 
∙ Banks.  

4. Operating Environment

The environment of foreign trade is regarded as the sum total of all the
external forces working upon the firm as it goes about its affairs in foreign
and domestic markets. The foreign environment can be taken as those factors,
which operate in those other countries within which the MNC operates.

5. Design and Implementation Constraints

▪ LOGIN: The Login module contains the form which contain

membership name and  member password. It includes
Username and Password. 
▪ TRADING ACCOUNT DETAILS: This form contains the
information about account  holder, market status, currency
held, trading histories, etc. 
▪ BUY: After the user logged in they can buy stocks online the
user can buy stock only it is  available for buying. 
▪ SELL: After the user logged in they can sell stocks online , the
user can sell his own  stocks only 
▪ BANK ACCOUNT DATABASE: After the trading is finished
user has to select the type  of transaction whether credit card
Demat account. 
 6. User Documentation
The product will include user manual. The user manual will include product overview, complete
configuration of the used software (such as SQL server), technical details, backup procedure
and contact information which will include email address. There will be no online help for the
product at this moment. The product will be compatible with the Internet Explorer 6.0 or higher.
The databases will be created in the Microsoft SQL server 2000.

7. Assumptions and Dependencies

The product needs following third party product. Microsoft SQL server to store the database.

3. External Interface Requirements

1. User Interfaces

It should be simple and easy for consumers to understand and use. It should also be an
immersive interface. For the user and administrator, the device should prompt the login to the
program and correct feedback parameters.

2. Hardware Interfaces

 The program offers a decent graphical interface for the user that can be run on the device by
an
administrator, performing the necessary tasks such as designing, reviewing, displaying the book
information.

 Allows users to access quick reports in between real hours, such as Book
Issues/Returned, etc. Based on various requirements, stock verification, and search
service.
  Server side:  
OS –Windows 9x 
Processor: Pentium 3.0 GHZ or higher 
RAM: 256 Mb or more 
 Hard drive: 
10 GB or more Client side: 
OS: Windows 9x 
Processor: Pentium 2.0 GHZ or higher 
RAM: 256 MB or more

3. Software Interfaces
 Database SQL server 
 Platform: Java language 
 MS- windows operating system  

4. Communications Interfaces

Window

4. System Features
The users of the system should possible by providing be provided the surety that their account
is secure. This is

 User authentication and validation of members using their unique member ID

  Proper monitoring by the administrator which includes updating account status,
showing a popup if the member attempts to issue number of books that exceed the limit
provided by the library policy, assigning fine to members who skip the date of return

 Proper accountability which includes not allowing a member to see other member's
account. Only administrator will see and manage all member accounts

4.1 Database-Storage

4.1.1Description and Priority

Proposed Database is intended to store, retrieve, update, and

manipulate information related to university which include

  Books availability

 Staff information

 Student details

 My Account,

 Calculation of fines

4.1.2. Stimulus / Response Sequences.

Responses for Administrator: The administrator can Login and Logout. When the Administrator
Logs into the Library system. The system will check for validity of login.If the Login and
password are valid, the response to this action is the administrator will be able to modify, view,
add, deleting and all other functions that can be performed on the database.
software Requirements Specification for library management

4.2. Functional Requirements

This section gives the list of Functional requirements

which are applicable to the Library Management System.

4.2.1 Interface Requirements

This section describes how the software interfaces with other software products or users for
input or output.

4.2.1.1Userinterfaces

Describes how this product interfaces with the user.

GUI

Describes the graphical user interface if present. This section should

include a set of screen features.

  Features.

1. Description

The user interface must be customizable by the administrator

2. Criticality

This issue is essential to the overall system. All the modules

provided with the software must fit into this graphical user

interface and accomplish to the standard defined

3. Technical issues

In order to satisfy this requirement, the design should be simple and all the different interfaces
should follow a standard template. There will be the possibility of changing colours and images,
plus switching between interfaces with the minimum impact for the users.

4. Risks

To reduce the circumstances under which this requirement might

not able to be satisfied, all the designers must have been

5. Other Nonfunctional Requirements

1. Performance Requirements

The proposed system that we are going to develop will be used as the Chief performance
system within the different campuses of the university which interact with the university staff and
students. Therefore, it is expected that the database would perform functionally all the
requirements that are specified by the university.

2. Safety Requirements
The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.

3. Security Requirements
We are going to develop a secured database for the university. There are different categories of
users namely teaching staff, administrator, library staff, students etc., depending upon the
category of user the access rights are decided. It means if the user is an administrator then he
can be able to modify the data2delete2append etc.., All other users other than library staff only
have the rights to retrieve the information about database.
Software Quality Attributes
 The quality of the database is maintained in such a way so that it can be very user friendly to
all the users of the database

4. Software Quality Attributes

The development of the system will be constrained by the availability of required software such
as web servers, database and development tools. The availability of these tools will be
governed by the university of Balart. The most recent versions of software development tools
may not be installed at the university of Balart.

5. Business Rules
There is no maximum number of books that can be borrowed Books must be returned within 4
weeks. Borrowers can borrow a maximum of 4 books Borrowers are unable to borrow items if
there are items overdue on the borrower's account .Borrowers are invoiced for items that have
not been returned

6. Other Requirements
There are different categories of users namely staff, librarian, admin, students, etc. Depending
upon the category of users the access rights are decided. All the users except the librarian only
have the rights to retrieve the information about database.

Appendix A: Glossary
 System: Who updates the record 

 User/member: A general login ID is provided to most users 

 Use case: A diagram of the project showing a basic overview. 

 Interface: It is used to communicate with a database.