XP Team A
Stories (Third Draft)
2/19/2002


Changes since last draft:


Priority (P):

Risk (R):

Cost (C):


Iteration 1

Story 1.1: The user can choose a stock symbol and a time interval (resolution). Once user defines stock symbol and time resolution, the system should register the stock symbol to data server, and wait for the stock information (TOS) from data server. If user wants to query another stock, the system should unregister the previous symbol, register the new one and recompute the data from 9:30 am. 

P: 1
R: 1
C: 3 weeks 

Story 1.2: The system should display current information textually on the screen. Specifically, the output should contain the direction of the trend (long or short), the price of the current stock, and the break price. The information should be listed with the most recent transactions first. The computation should be displayed on the PC screen within 5~8 seconds. 

P: 1
R: 1
C: 1 week

Story 1.3: The system should provide a different interface notation for a price point (up or down) that is a Fibonnaci point in the sequence. For example, the up sequences can be printed in green... then the L3, L5, L8, L13, L21, etc. lines should be darker green, or bold to indicate the Fibonnaci level. The same should be done for down sequences.

P: 1
R: 1
C: 2 weeks

Story 1.4: The system should have an indicator to assure the user that the program is actually running. This should be a window displaying the current transaction price of the stock if it is different from the previous transaction price. This window should be clearly separated from the rest of the data display.

P: 1
R: 1
C: 2 weeks

Story 1.5: The system should analyze data based on the Three-Price Break Method of Trend Determination as described in Appendix A of A Different Style of Trading. 

P: 1
R: 1
C: 2 weeks

Story 1.6: The system should calculate and display information concerning trends in the data. For example, the system should display information such as "1 Long sequence of length 3", "2 Short sequences of length 5" and "4 Long sequences of length 2." This information should be recomputed if the time interval or the current stock is changed by the user.

P: 1
R: 1
C: 2 weeks

Story 1.7: The system should contain an adapter to allow for differences in data stream formats. In other words, the system should work different data providers.

P: 1
R: 1
C: 2 weeks

Story 1.8: When the system starts up, it should ask the user for a username and password. This information should be passed through to the data feed provider.

P: 1
R: 1
C: 1 week 


Iteration 2 (should be done eventually)

Story 2.1: The system should allow display a graphical representation of the direction of the trend (long or short), the price of the current stock, the trading volume, and the break price. The representation should be modeled after Figure A.3 in the Three-Price Break handout. The price levels should be represented in the margins and colors and thickness should be user selectable.

P: 2
R:
C: 3 weeks

Story 2.2: The user should be able to click a button to display a window of raw TOS data. This window should display the data in real time and should correspond to the stock the user has currently selected.

P: 2
R: 1
C: 1 week

Story 2.3: The system should sound an audible signal when a reversal of trends occurs. This computation depends on the time interval chosen by the user.

P: 2
R: 1
C: 1 week


Iteration 3 (would be nice to have some day)

Story 3.1: The system should have the ability to signal the buy/sell software owned by the brokerage. When a trend occurs strongly in one direction the user should have an easy way to buy/sell stocks. The actual buying and selling is handled by existing software at the brokerage and is beyond the scope of this project.

P: 3
R: 3
C: 3 weeks

Story 3.2: The system should be able to save data and do real-time computing of the stock information at background simultaneously all the time, even if user samples at coarser temporal interval. If there is a drastic change in trends an audible alarm should sound to alert the user.

P: 3
R: 1
C: 2 weeks

Story 3.3: The system should have the ability to track several stocks at once, not just a single stock. This needs to be handled through a single connection with the data server. 

P: 3
R: 3
C: 3 weeks

Story 3.4: The system should be able to define formulas on some standard variables (HOD, LOD, yesterday's close, etc.) and have the values of the formulas represented on the graphical interface with horizontal lines.

P: 3
R: 2
C: 2 weeks


Webpage Update History
2/19/2002, 11:40pm    Kok-Lim Low