Use Case ID Use Case Name: Page 1 of 9

Use Case Document
“FTS” Trading System
USE CASE - 1
Use Case ID FTS-01

Use Case Name Integrate FTS with Interactive Brokers API
Document Version Control
Version Date Created Originator Changes Made

1.0 01/03/2023 AM NA (First version)
Use Case Definition
Description To integrate the FTS platform to Interactive Brokers
Primary Roles 
Pre-Conditions  Application should be UP and Running
Trigger  Need to know if its perpetual or integration is based on trigger points
Step Interaction
Basic Flow
Step Interaction
Alternate Flows a.
1
b.
2
Post-Conditions

(If Any)
Use Case Diagram

Note: Below is
the Sampel Flow
which will be
built once the
complete
requirement
understanding
is arrived.
Page 1 of 9
Use Case Document
Page 2 of 9
Use Case Document
USE CASE - 2
Use Case ID FTS-02

Use Case Name To create an automated exit strategy

Use Case Definition
Description System rules to exit a stock position that already exists
Primary Roles 
Pre-Conditions  Need to understand the pre-conditions to trigger this function.
Trigger 
Step Interaction
If
Subject stock price (Existing Position) closes below the 20 period
Moving Average of a 5-minute price bar on a closing basis…
and
the closing price of the price bar is below the opening price (a
“Bearish Candle”)
and
the proceeding price bar is also a bearish price bar
and
Basic Flow it closes below the 20 period moving average
Then
place an order to exit the position at the midpoint of the Bid-Ask Price
Then If
the order does not execute in 10 seconds
then
modify the order to exit a long position at the Bid Price
If Order executed, then End
If order not executed in 5 seconds
then
continue to modify order every 5 seconds till executed.
Alternate Flows
Step Interaction
1 c.
Page 3 of 9
Use Case Document
d.
2
Post-Conditions

(If Any)
Page 4 of 9
Use Case Document
USE CASE - 3
Use Case ID FTS-03

Use Case Name To create an alarm for a BUY or SELL signal

Use Case Definition
A “Buy” or “Sell” alarm pops up with a message if certain well-defined rules are
Description met for a user defined list of stocks. The alarm is then also added to a list of
alarms that have popped during the day along with some pertinent data.
Primary Roles 
Pre-Conditions  Defined rules need to be understood.
Trigger 
Step Interaction
Alarms to be added based on the rules and

The following table shows an example list of alarms that have
popped during the day.
Basic Flow
Symbol, Buy/Sell Strategy, Price Alert, Current Price, Gain/Loss
since Alert
AAPL, Strategy 1, $121.15, $123.25, $2.1
AMZN, Strategy 4, -$95.26, $96.75, -$1.49
, , , ,
Step Interaction
Alternate Flows e.
1
f.
2
Post-Conditions

(If Any)
Page 5 of 9
Use Case Document
USE CASE - 4
Use Case ID FTS-04

Use Case Name To SET position sizes

Use Case Definition
A “Position Size” is the percent of Equity that a trader wants to wager on a

particular trade. The following table shows the type of information that may be
Description populated on the message box. This is just a rough layout for discussion
purposes only.
Primary Roles 
 When the order is entered in the Broker order entry system, a message box
Pre-Conditions pops up showing the number of shares and Dollar amount of Equity that will
be entered.
Trigger 
Step Interaction
Symbol: AAPL, Add 2% - $10K (83 Shares), Add 40% -$200K

(1667 Shares)
Total BOD Equity:$500,000, Add 5% -$25K (208 Shares), Add 50% -
$250K (2083 Shares)
Existing AAPL Equity:Share Price - $120Shares Held – 500% of
Basic Flow
Equity – 12%, Add 10% -$50K (416 Shares), Add Custom % -
Current UR Gain/Loss:$2100, Add 20% -$100K (833 Shares),
Cover
Alternate Flows
Step Interaction
1 g.
h.
Page 6 of 9
Use Case Document
Post-Conditions

(If Any)
Page 7 of 9
Use Case Document
USE CASE - 5
Use Case ID FTS-05

Use Case Name Dashboard

Use Case Definition
Dashboard will recap activity w.r.t existing positions, alarms, Buy and Sell
Description
Strategies etc.
Primary Roles 
Pre-Conditions
Trigger 
Step Interaction
An example dashboard is provided below for discussion purposes.
Basic Flow
Alternate Flows
Step Interaction
1 i.
j.
Page 8 of 9
Use Case Document
Post-Conditions

(If Any)
Page 9 of 9

Use Case ID Use Case Name: Page 1 of 9

Uploaded by

Document Information

Original Description:

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

Use Case ID Use Case Name: Page 1 of 9

Uploaded by

Copyright:

Available Formats

Use Case Document

“FTS” Trading System

Use Case ID FTS-01

Document Version Control

Version Date Created Originator Changes Made

Use Case Definition

Description To integrate the FTS platform to Interactive Brokers

Pre-Conditions  Application should be UP and Running

Trigger  Need to know if its perpetual or integration is based on trigger points

Use Case Diagram

Use Case ID FTS-02

Document Version Control

Version Date Created Originator Changes Made

Use Case Definition

Description System rules to exit a stock position that already exists

Pre-Conditions  Need to understand the pre-conditions to trigger this function.

Use Case ID FTS-03

Document Version Control

Version Date Created Originator Changes Made

Use Case Definition

Pre-Conditions  Defined rules need to be understood.

Alarms to be added based on the rules and

Use Case ID FTS-04

Document Version Control

Version Date Created Originator Changes Made

Use Case Definition

A “Position Size” is the percent of Equity that a trader wants to wager on a

Symbol: AAPL, Add 2% - $10K (83 Shares), Add 40% -$200K

Use Case ID FTS-05

Document Version Control

Version Date Created Originator Changes Made

Use Case Definition

An example dashboard is provided below for discussion purposes.

You might also like