FOREIGN TRADING SYSTEM SRS 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 practice of currency trading is also commonly referred to as foreign exchange, Forex or FX for short. All currency has a value relative to other currencies on the planet. Currency trading system uses the purchase and sale of large quantities of currency to leverag leveragee the shifts in relative value into profit. The online Foreign Currency Trading system is almost entirely a "spot" market. A "spot" market means that the trading is made immediately or "on the spot". The settlement of those Foreign Currency Trading spot transactions is made within two working days. DOCUMENT CONVERSION:
The document follows the IEEE format standard (IEEE Std. 830 – 830 – 1998). 1998). INTENDED AUDIENCE AND READING SUGGESSIONS: 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 the investors. PROJECT 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.
REFERENCES:
Pressman, Roger S. Software Engineering: A Practitioner’s Approach. New York, NY: McGrawHill, 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 . OVERALL DESCRIPTION: 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. Product function
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.
USER CHARACTERISTICS:
There are various kinds of users for this product
Investors
Traders
Brokers
Banks.
DESIGN AND IMPLEMENTATION CONSTRAINTS: Design 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.
FUNCTIONAL REQUIREMENTS: External Interface Requirements:
The system uses the GUI – Graphical User Interface for easy interaction with the customer. The system maintains a relationship with the Rational Rose Tool. According to the code generated by the Rose tool, the system is developed. This gives more sequential access for the functions and the functions can be coded easily. User Interfaces:
GUI is used in generating forms. The credit card processing system provides a good user interface. It is more interactive with the user that the user can easily operate the system. This can be achieved by providing the snap shots describing the functionality of the system. By viewing into the snap shots, the user can gain better knowledge about the system. Hardware Interfaces
Needed: Computers Hard Disk: 100-150 GB RAM: 512-1 GB required Internet Connection required. Cables, wires, Network adapters are required. Communication Interfaces The local system must be connected to the server via Internet Connection. Email and file transfer services are provided. E-Shopping is the key concept. OTHER NON-FUNCTIONAL REQUIREMENTS: Performance Requirements
The system must be able to perform in adverse weather conditions like heavy rain, hot climate etc. Connection can be interrupted but service must be uninterrupted. Transportation of stocks must be efficient and punctual. Database should support large amount of data and also must preserve integrity, consistency of data and should prevent data loss.
Software system attributes:
System attributes or quality factors will have the following requirements.
The software is more reliable as it causes no damage to the system in which it works. If it leads to any malfunction, it has the capability to recover from that damage.
The system is available at all the places where the users fell it comfortable to work with this.
The software is as secure as it is user-friendlier and the user can use the system efficiently. It won’t cause any system attacks
The software is easy to maintain and the updating over the system are verified daily, in order to have more secure data
The software can be installed in any system that satisfies the hardware and software requirement of this system. It is more portable.
The system provides easiness for the customer to use it and of course it is more userfriendly.
Appendix A: Glossary
The purpose of following the software requirement specification in foreign trading is to maintain or remain in good standing. If the rules are violated then the consequence will be more. The worst being revocation of the agreement with the credit card processing.
.
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.
A/C Details
BankAuthority
DataBase
TradingA/C Investor
Buy
Sell
MarketAuthority
CLASS DIAGRAM:
Market Status
Broker
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.
1: submit(A/C no,password) 3: reset(A/C no,password) : Trading A/C 2: invalid,enter correct details : Investor 7: insufficient balance 4: checks(marketStatus) 9: updateBank A/C
6: bank A/C balance > trading A/C balance 8: makeInvestment
: Investment 5: Buy : Bank Database
: Market Authori
10: sell
11: currency hold 13: getAmount
: Trading Database 12: notHeld
ACTIVITY DIAGRAM:
14: updateTradingA/C
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.
SCREEN SHOTS
CONCLUSION: Thus the study and implementation of Foreign Trading System has been done and verified successfully.
