• Save
Application Roadmap for an Electronic Trading System
Upcoming SlideShare
Loading in...5
×
 

Application Roadmap for an Electronic Trading System

on

  • 5,961 views

 

Statistics

Views

Total Views
5,961
Views on SlideShare
5,901
Embed Views
60

Actions

Likes
5
Downloads
2
Comments
0

6 Embeds 60

http://www.slideshare.net 39
http://www.punitsahni.com 11
http://punitsahni.blogspot.com 4
http://www.linkedin.com 3
http://mycareerandlearnings.blogspot.com 2
http://www.lmodules.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Application Roadmap for an Electronic Trading System Application Roadmap for an Electronic Trading System Presentation Transcript

  • Application Roadmap for an Electronic Trading System Punit Sahni [email_address]
  • Contents
    • Introduction
    • Functional Architecture
      • Business Functions
      • Business Processes
    • Data Architecture
      • Reference Data
      • Data Standards
    • Application Architecture
      • Application Components
      • Application Environment
    • Technology Architecture
      • Execution Environment
      • Operations Environment
      • Development Environment
    Identify Sections of the Application Roadmap
  • 1. Introduction Application Roadmap
    • Capture Background Information on the Application
  • 1. Introduction Application Identification This application provides <front>, <middle>, <back> office trading capabilities for < products >. It provides < order capture >, < pricing >, < trading > and < booking > functionality for < these products >. Trading takes place on the < these exchanges > and < ECNs >. Capture Background Information on the Application
  • 2. Functional Architecture Application Roadmap
    • Describe the business functions of this application, including:
      • Business products processed
      • Business areas supported
      • Geographical scope of the functionality
    • Also highlight :
      • Key business processing flows
      • Interaction with other business processes
  • 2. Functional Architecture Business Functions
    • Identify asset classes to be traded using this system
      • Equities
      • Fixed Income
      • Commodities
      • FX
    • Identify where trading will happen < exchanges >, < ECNs >, < markets > etc.
    • Identify user community (by geography )
    • A new application, <Asset Class> Trading System, based on the <homegrown or commercial package> will be developed to support this business.
    Provide a summary of the Business Functions provided by this Application
  • 2. Functional Architecture Business Functions
    • Identify < front-office >, < middle-office > and < back-office > functions for <asset classes, product groups> provided by this system.
    • Identify phases for delivery of business functions.
    • Pre-Trade
    • Trade Pricing
    • Risk Analytics
    • Client Portfolio Analytics
    • Order Management
    • Order Capture
    • Order Routing
    • Order Notification
    • Execution Management
    • Order Crossing
    • Market Execution
    • Order to Execution Allocation
    • Position Management
    • Position Valuation
    • Risk Management
    • Interfacing Services
    • Market Data
    • Client Gateways
    • Exchange Gateways
    • Exchange Trading
    • Floor Trading
    • Electronic Trading
    Identify the business functions provided by this Application
  • 2. Functional Architecture Business Processes - 1
    • Draw the key business flows
    Pre-Trade – Trade Pricing Client requests price quote Route to Sales Trader Assemble price quote Dispatch quote to client Client views price quote Client Sales-Trader Market Data Pre-Trade – Client Portfolio Analytics Client requests portfolio analytics Route to Sales Trader Run analytics modelling Dispatch results to client Client views results Client Sales-Trader Market Data Trader Pre-Trade – Risk Analytics Run risk modelling Market Data Trader Positions Map the business processes handled by this Application
  • 2. Functional Architecture Business Processes - 2
    • Draw key transaction processing steps.
    Capture manual order Validate order Capture electronic order Sales-Trader Reference Data To Transaction Management Cross orders Dispatch results to client Value positions Market Data Route to Trader Route to market Receive execution results Assemble market trades Allocate orders to executions Run risk modelling Market Data A A Exchange Gateways Exchange Gateways Order Management Execution Management Interfacing Services Position Management Position Management Map the business processes handled by this Application
  • 3. Data Architecture Application Roadmap
    • Describe the data components of this application, including:
      • Use of Reference Data
      • Data standards used within the application
    • Also highlight :
      • Data created and supplied to other applications
      • Reference data not sourced from standard sources (e.g. internal, external)
  • 3. Data Architecture Reference Data
    • List the key items of reference data used by this application, and their sources
    Identify Reference Data used by this Application
  • 3. Data Architecture Data Standards
    • List the key data standards used by this application.
    Identify Data Standards used by this Application
  • 4. Application Architecture Application Roadmap
    • Describe the key components of this application, including:
      • Application layers and processing tiers
      • Functional software products used within the application
    • Also highlight :
      • Geographic instances of the application
      • Interfaces to other applications
      • Existing applications that are to be de-commissioned
  • 4. Application Architecture Application Components
    • Identify the key components in n-tier architecture
    Sales-Traders, Traders TradeBlotter and TraderFrontEnd Used by Trading staff primarily Provide a real-time, multi-dimensional deal capture and position-tracking environment. Core trading engine provides key functions covering order and execution management, position and risk management, Exchange connectivity, market data management messaging components to connect to other apps Exchange Gateways Internal Gateways DBMS Database to store transactional information. Separate application processes for communicating with other internal applications (e.g. for order capture and feeds to downstream systems) and with gateways to Exchanges Describe Components of this Application TradeBlotter TraderFrontEnd Order Management Execution Management Position Management Interfacing Services
  • 4. Application Architecture Application Environment Trading Application ISV market gateway Other Trading systems Market Prices, Product Reference Data Trades, Executions Text in blue describes key data items on each interface Trades, Executions Transaction messaging and routing Standardised pricing & risk analytics library Transactions, Analytics Results Completed transactions Reference Data Cash transaction payments Credit risk data warehouse Transaction data warehouse Books & records for cash transactions Payments Completed transactions Transactions, Analytics Results Reference data Book data Client data Reference data Product reference data Identify Interfaces to other applications
  • 5. Technology Architecture Application Roadmap
    • Describe the technology to be used to implement the application. It includes:
      • Tools, techniques and infrastructure used to develop and maintain the application
      • Software products and infrastructure used to run the application
      • Tools and infrastructure used to operate the application
    • Also highlight :
      • Changes in the components, platform or infrastructure used by the application
      • Functions or capabilities that can be re-used by other areas
      • Services used by the application
      • Adherence to security standards
  • 5. Technology Architecture Execution Environment
    • Identify Components of the Execution Environment
    • Draw Logical Layout of the Execution Environment
    • Figure Implementation of Clustering & Redundancy
    • Figure Implementation of Data Center Strategy
    • Identify Components of the Operations Environment
    • Identify Components of the Development Environment