Stock Screener

Application is a Windows front end, written in C# using Visual Studio that allows a user to enter criteria for screening a simple financial database for potential investment ideas. The database is implemented using SQL Server 2005. For example, in criteria 1 the user might enter “price >= 10?? and the application would return a result set with only those stocks in the database that have a price over $10. For criteria 2, the user might enter “(debtTotal / equityShareholder) BETWEEN 0 AND 100?? and the application would use the results of the first criteria as the starting set for the second criteria to return companies that are priced above $10 and have a Debt-to-Equity ratio between 0 and 100. The application is already fully functional using simple criteria that can be passed straight through using dynamic T-SQL statements like the ones in the examples above. (See attached screenshots). I will provide the current working application, source code, and sample database for development in Visual Studio. Application currently runs at 1600x1200. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition and must be compilable and extensible from within Visual Studio. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). 4) The user should be able to enter expressions like “Earnings[-12]?? to use the Earnings from 12 months ago. For example, “Earnings > Earnings[-12]?? would return all companies whose current Earnings are greater than their Earnings from 12 months ago. 5) The user should be able to enter expressions like ‘Sales[Feb06]’ to use the Sales from a specific month. For example, “Sales[Feb06] > 1000000?? would return all companies whose Sales as of February 2006 were greater than 1 million. 6) Enable selectable user option that allows a NULL field in the database to be replaced by an earlier month’s data. For example if the current month’s value for a particular company’s Earnings is NULL the previous month’s Earnings should be used instead. The user should be able to specify a maximum number of months to “look back?? in any such calculation. (The user interface has already been implemented). 7) Override divide-by-zero error so that no exception is thrown and instead zero is returned for any calculation where the numerator is zero, and a very large float is returned for any calculation where the numerator is non-zero. 8) Allow the creation of aliases to simplify screening. For example, a user should be able to enter the statement “PE BETWEEN 0 AND 30?? where PE has already been defined as Price/Earnings. (User interface has already been implemented). 9) Aliases should be nestable such that an alias itself could be used in the definition of another alias. For example, the user might define PEG as (PE/EarningsGrowth) where PE and EarningsGrowth are themselves aliases. 10) You may store these aliases in the database itself or in a client side file, whichever works fastest. They are currently stored in a client side file. 11) Enable a selectable user option that allows certain text strings in the database to be replaced with a zero value in all calculations. (The user interface has already been implemented). 12) Implement Rank and RankDown. For example, “RANK (Price/Earnings)?? should return the ordered, no ties, dense ranking for each company sorted by PE. This could be used to get the 10 companies with the lowest PEs using "(Rank PE) <= 10". 13) Implement simple syntax for base sets that allows union, subtraction, intersect ($1 + $2). ($1 - $2). ($1 & $2). 14) Allow base set for a criteria to come from a client side file. (Viewing, loading and saving sets has already been implemented). 15) The entire database is currently loaded client-side into a memory resident dataset. This should be changed so that the database remains on the server without being loaded client side. 16) All code should be written in a clean, extensible framework that would allow a competent programmer to easily add additional functionality. 17) All code should be written in a way that allows each line to be executed against a SQL Server 2005 database with **query speed being a high priority**. 18) I am unsure of whether this spec can be implemented using pure dynamic T-SQL or if CLR stored procedures are the way to go. Perhaps some other approach? Please advise. 19) I suspect that a lexical analyzer may need to be written to parse criteria in order to implement the requested features, but I am not certain. Please advise. ## Platform Application should run under Windows XP at 1600x1200. Source code and all resources should be developed and compilable within Visual Studio using MS C# and MS SQL Server 2005.