250 likes | 387 Views
CSTEP Cluster Sampling for Tail Estimation of Probability. Team. Project Team and Faculty. Created by: Alan Chandler Nathan Wood Eric Brown Temourshah Ahmady Faculty Advisor : Dr. James Schwing Client: Dr. Yvonne Chueh. Introduction.
E N D
CSTEP Cluster Sampling for Tail Estimation of Probability Team
Project Team and Faculty Created by: Alan Chandler Nathan Wood Eric Brown Temourshah Ahmady Faculty Advisor: Dr. James Schwing Client: Dr. Yvonne Chueh
Introduction • Cluster Sampling for Tail Estimation of Probability • Models financial risk • Most algorithms very complicated, slow • Find extreme cases
Algorithms • Implementing Three Algorithms • Significance Method • Euclidian Distance • Present Value Distance Method
Algorithms • Significance Method • Simple operation • Time: Θ(n) • Memory: Θ(n)
Algorithms • Euclidian Distance Method • More complex • Time: Θ(n*m) • Memory: Θ(n)
Algorithms • Present Value Distance Method • More complex • Time: Θ(n*m) • Memory: Θ(n)
Architecture C++ C# CSV File Lua File GUI Params LuaFunction DataProcessor Algorithm CSV File
User Interface Design • Ease of use over extravagance • Readable over flashy • Followed default theme to ensure buttons and text boxes, etc. flowed well
User Interface Design • Visual Studio C# • Use of: • Buttons • Radio buttons • Tabs • Text boxes • Picture boxes • Combo boxes
User Interface Design • Graphical representation of data • Allows user to see universe at all times • Lets user see potential errors in universe
Quality Assurance • Documents Standards • Coding Standards • User Interface Guidelines • Change Control Process • Testing Process
Coding Standards • C# Coding Style • C++ Coding Style • Lua Coding Style
UI Guidelines • Effective and essay to use • Understanding computer skills of the intended users • Strong error handling component • Maintain tolerance
Testing Strategy • Begin testing at the module level and works toward the integration of the entire system Unit Test Performance Testing Integration Test System Validation and Verification
Test Plan • Our test plan covers: • Unit testing • Integration testing • Validation and verification • Performance testing • Usability testing • Testing the GUI for user acceptance
Test Cases • Designed test cases for each requirement of our system
Data • Real-World Data • Used to test the output of our program • Synthetic Data • Used to test the performance of our program
Conclusion • Architecture • Algorithms finished • Framework built • Components require integration • Graphical User Interface • Basic layout finished • Minor functionality incomplete • Finishing touches to make GUI as usable as possible
Schedule • To do: • Finish software • Final testing • Acceptance testing