Title

Design and development of Equity Trading Portfolio manager

Abstract of the project Equity Trading Portfolio (ETP) manager is assistant software for traders who normally do the trading though some stock brokers. These traders mostly track the share prices using News channels or news papers and place the order for stock buy or sell to stock broker. Stock broker actually does the buy or sell action on behalf of such traders. ETP manager keeps the track of share prices offline (if time permits this can be made online) and provides charts and analysis of the particular companies share with available data. At End of Day, the broker will update the closing stock rates to database. Similarly at Days open the broker will update the opening stock rates (if time permits this can be made online). It also keeps the records of buy and sell done by the trader. This system facilitates the traders to see the DMAT allocations of trader with current price. Equity Trading Portfolio (ETP) manager is a true assistant to those traders who do not have electronic trading facility and do trading through brokers. Keywords Generic Keywords Databases, Middleware, Programming Specific Technology Keywords SQL Server, ASP/JSP, HTML, JavaScript/VBScript Project Type keywords Analysis, Design, Implementation, Testing, Graphical User Interface

Copyright 2004-2005 Infosys Technologies Limited

Functional components of the project Following is a list of functionality of the system. More functionality that you find appropriate can be added to this list. And, in places where the description of functionality is not adequate, you can make appropriate assumptions and proceed. Users of the system: Multiple user system with each user is either a trader or a broker. Functionality: The functionality of this system is based on the offline feature of stock prices. There might be relevant changes in the functionality if the stock prices are captured online. When the user types in the URL of the website, a Welcome page is shown which has a menu on the left hand side, a banner at the top and any related links to other sites Login Screen This site contains an online catalog for the user. User has to login to Welcome Page before ordering anything. Login functionality should check the authenticity of the user from the database. Menu should contain following screens Registration Screen Each Insurance agent is the registered user of this system. If the user is not registered, then registration screen should be available
Stock registration Screen This screen facilitates the trader to add a new share that he/she has purchased and slo those stocks which are not purchased (traders normally track the stock for substantial duration before purchase). System shall accommodate the new stock entry for user.

Stock Performance Screen 1 This screen facilitates the trader to see the stock performance in graphical representation over the time duration specified by trader. If the data range is invalid or the stock prices not available this screen should provide error messages

Stock Performance Screen 2 This screen facilitates the trader to see the stock performance in tabular form with standard deviation from average stock price. This representation is based on the time duration specified by trader. If the data range is invalid or the stock prices not available this screen should provide error messages. Based on the last 15 prices of the stock over the average cost of the same stock, system should suggest a Buy or Sell flag.

Copyright 2004-2005 Infosys Technologies Limited

 Asset Indicator screen The trader will use this screen to see the summary of his / her stocks in comparison with respective buy prices. A deviation of total asset need to be captured by system. Buy Stock Request screen Trader will use this screen to send an email to broker to buy a specific stock with quantity . (Each buy/sell will have a percentage brokerage to be paid to broker.)

Sell Stock Request screen Trader will use this screen to send an email to broker to sell a specific stock with quantity(Each buy/sell will have a percentage brokerage to be paid to broker.) Buy Stock screen Broker will use this screen when the broker confirms the successful purchase of stock with rate of purchase. This screen facilitates to record the details with date references. Submit operation will send an auto generated email to trader(Each buy/sell will have a percentage brokerage to be paid to broker.) (Each buy/sell will have a percentage brokerage to be paid to broker.)

Sell Stock screen Broker will use this screen when the broker confirms the successful sell of stock with rate of purchase. This screen facilitates to record the details with date references. Trader Asset Screen Traders will use this screen to see the balance sheet in terms of Cash and/or DEMAT allocation. In case of cash and DEMAT allocation balance sheet, dual entry system should be followed Submit operation will send an auto generated email to trader Broker Screen Broker should be able to upload Day in and day out stock prices in offline module(Online module can have real data, by linking to existing stock exchange servers) Brokerage Screen Broker can change the brokerage percentage by using this screen Brokerage Report Broker can change the brokerage percentage by using this screen

Copyright 2004-2005 Infosys Technologies Limited

Steps to start-off the project: Java Platform : The system is developed using Java Server Pages/ Servlets as the front end and Oracle/SQL Server/DB2 as the back end and Tomcat server OR Microsoft platform: The system is developed using Active Server Pages as the front end and Oracle/SQL Server/DB2 as the back end and IIS server The following steps will be helpful to start off the project 1. Get a firm grasp on the above technology. 2. Get the domain knowledge. (speak to a trader for extending the requirement specification, go through any stock market websites and refer to stock market oriented channel) 3. Decide on the number of users and their profile, number of products, type of products, business rules. 4. Help should be very user friendly. 5. UI should include good images and have a constant look and feel throughout the application. Requirements Hardware requirements Number Description Alternatives (If available) 1 PC with 5 GB hard-disk Not-Applicable and 512 MB RAM Software requirements Number Description Alternatives (If available) 1 Windows 95/98/XP with Not Applicable MS-office 2 Java, JSP, Servlets C#, VB.net,ASP 3 MS-SQL server /Oracle 4 Windows Linux 5 Tomcat IIS for MS Manpower requirements 2 to 3 students can complete this in 4 6 months if they work fulltime on it. Milestones and Timelines

Copyright 2004-2005 Infosys Technologies Limited

Number Milestone Name

Milestone Description

Timeline

Remarks

Requirements Specification

Technology familiarization

Database creation

High-level and Detailed Design

Implementation of the front-end of the system

Integrating the front-end with the database

Week no. from the start of the project Complete 2-3 Attempt should be made to specification of the add some more relevant system (with functionalities other than appropriate those that are listed in this assumptions) that document. constitutes this milestone. A document detailing the same should be written and a presentation on that be made. Understanding of the 4-5 The presentation should be technology needed to from the point of view of implement the project. being able to apply it to the project, rather than from a theoretical perspective. A database of atleast 5-7 It is important to finalize on 100 entries of users, the database at this stage 500-600 products, itself so that development should be created. and testing can proceed with the actual database itself. Listing down all 7-9 The scenarios should map to possible scenarios the requirement specification and then coming up (ie, for each requirement that with flow-charts or is specified, a corresponding pseudocode to handle scenario should be there). the scenario. Implementation of the 10-12 During this milestone period, main screen giving the it would be a good idea for login facility, screen the team (or one person from that follows the login the team) to start working on giving various a test-plan for the entire options, screens for system. This test-plan can be each of the options. updated as and when new scenarios come to mind. The front-end 12-13 developed in the earlier milestone will

Copyright 2004-2005 Infosys Technologies Limited

Integration Testing

Final Review

now be able to update the database. Other features like. In short, the system should be ready for integration testing. The system should be 14-15 thoroughly tested by running all the testcases written for the system (from milestone 5). Issues found during 16-18 the previous milestone are fixed and the system is ready for the final review.

Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged. During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)

Guidelines and References http://java.sun.com (Java, JSP, Servlets) http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnasp/html/asptutorial.asp (ASP tutorial) http://www.functionx.com/sqlserver/ (SQL-server tutorial)

Copyright 2004-2005 Infosys Technologies Limited