OPR 1 Team 8Hi FidelityDavid Thomas, Bradley HerrinDaniel Shusko, Ron Bradley

Presentation Summary

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

Sponsor Background

• 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

Presentation Summary

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

Problem Summary

Problem Summary

•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

Presentation Summary

• Sponsor Background• Problem Summary• Requirements, Design, Implementation, and

Testing• Project Goals/Benefits• Feasibility• Needed Resources• Action Steps

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

Requirements, Design, Implementation, Testing

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

Requirements, Design, Implementation, Testing

???

? ?

??

?? ?

Presentation Summary

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

Project Goals/Benefits

• 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!!!!!

Presentation Summary

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

Feasibility

• 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

Presentation Summary

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

Needed Resources

• Obscure/Old DB software

• Testing Schema

Presentation Summary

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

Action Steps

• 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

OPR 1 Team 8Hi FidelityDavid Thomas, Bradley HerrinDaniel Shusko, Ron Bradley

Images

• 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”