1 / 21

OPR 1 Team 8 Hi Fidelity

OPR 1 Team 8 Hi Fidelity. David Thomas, Bradley Herrin Daniel Shusko, Ron Bradley. Sponsor Background Problem Summary Requirements, Design, Implementation, and Testing Project Goals/Benefits Feasibility Needed Resources Action Steps. Presentation Summary. Fidelity Investments

tiger-lancaster
Télécharger la présentation

OPR 1 Team 8 Hi Fidelity

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OPR 1 Team 8Hi Fidelity David Thomas, Bradley Herrin Daniel Shusko, Ron Bradley

  2. Sponsor Background • Problem Summary • Requirements, Design, Implementation, and Testing • Project Goals/Benefits • Feasibility • Needed Resources • Action Steps Presentation Summary

  3. Fidelity Investments • FMR LLC, Founded 1946 • 50,000 Employees • Large Corporation handles many investments • Online Brokerage, CD’s, Bonds, Annuities, Mutual Funds, Money Market Accounts, Life Insurance • IT • 3,000 Strong • 200-300 Semi Technical testers running unit tests Sponsor Background

  4. Presentation Summary Sponsor Background Problem Summary Requirements, Design, Implementation, and Testing Project Goals/Benefits Feasibility Needed Resources Action Steps

  5. Problem Summary

  6. Unit testing requires data • Pulled from production data • Randomized to protect privacy • Must be heavily ‘mined’ to get to test case • Data isn’t always in production environment • Data changes from day to day • Person/situation to be tested does not exist • Time spent on a test case (hours/days) could be wasted • Create a tool that generates these persons/situations • Safer in terms of confidentiality • No need to mine from Production • Save a model that is repeatable regardless of Production • Easily share models between testers • Generate interesting test cases that may not exist in Production Problem Summary

  7. Presentation Summary Sponsor Background Problem Summary Requirements, Design, Implementation, and Testing Project Goals/Benefits Feasibility Needed Resources Action Steps

  8. Requirements, Design, Implementation, Testing • (Optional) Front end implementation (GUI) • Must accept Generic Schema • User can enter Rule set on data • Person’s age, salary, life events, etc. • DB Connection Info • The front end compiles this info into a XML file

  9. Requirements, Design, Implementation, Testing

  10. Requirements, Design, Implementation, Testing • (Necessary) Back end accepts this Backend • Interpret this XML and insert data into the appropriate DB • Restricted to ODBC • Ensure the rule set is enforced • Ensure Atomicity

  11. Requirements, Design, Implementation, Testing ? ? ? ? ? ? ? ? ? ?

  12. Presentation Summary Sponsor Background Problem Summary Requirements, Design, Implementation, and Testing Project Goals/Benefits Feasibility Needed Resources Action Steps

  13. Goals • Backend to interpret XML script, Insert into DB • Front end to compile XML Script based on User provided information • Benefits • Help 300 testers repeat tests easily • Reduce searching massive amounts of production data • Prevent manual insertion of data • Save Fidelity money!!!!! Project Goals/Benefits

  14. Presentation Summary Sponsor Background Problem Summary Requirements, Design, Implementation, and Testing Project Goals/Benefits Feasibility Needed Resources Action Steps

  15. Getting obscure/old DB software • Finding and setting up some old software may be difficult • ODBC Toolset • It may only contain a hammer, even if we need a screwdriver Feasibility

  16. Presentation Summary Sponsor Background Problem Summary Requirements, Design, Implementation, and Testing Project Goals/Benefits Feasibility Needed Resources Action Steps

  17. Obscure/Old DB software • Testing Schema Needed Resources

  18. Presentation Summary Sponsor Background Problem Summary Requirements, Design, Implementation, and Testing Project Goals/Benefits Feasibility Needed Resources Action Steps

  19. Requirements Refinement • Wiki • Google Group • Phone Meetings • Model development • XML Script Syntax • ODBC Compliant insertion/removal • Rule set for data • Backend Engine, Front end GUI Action Steps

  20. OPR 1 Team 8Hi Fidelity David Thomas, Bradley Herrin Daniel Shusko, Ron Bradley

  21. NCSU Logo - http://www.nescent.org/news/Darwins_Birthday.php • Fidelity Logo – http://www.brightscope.com/blog/2009/03/11/new-plans-with-brightscope-ratings/ • Headache Picture - http://tamilandenglish.com/blog/wp-content/uploads/2010/09/blurred-vision-headache1.jpg • All others – original creations of “Hi Fidelity” Images

More Related