Power Market Game
Group Info Team Members Brian Jacobowitz (CprE) Corey Peterson (CprE) Kurt Niggemeyer (CprE) Client/Advisor Prof Gerald Sheble (Power Systems) Additional Advisors Prof Charles Richter (Power Systems) Valentin Petrov (EE)
Presentation Overview Background Problem Statement Functional Requirements Design Constraints Users Limitations Technical Approach Product Game Info Milestones Budget Future Work Lessons Learned Summary
Background Power market confusing to users Popularity of stock trading games
Problem Statement Create GUI (Graphical User Interface) and network solutions for the power market game. This interface will provide a user friendly environment for players to get a feeling for how the power market works.
Functional Requirements Web-based Login Timer Activity Log Graphs Submit Bids Display Status Documentation
Design Constraints Accessible Web based Java User-friendly Multi-user Capable
Users Limitations Professors and students Researchers Fast Internet connection Up to 24 players Java capable web browser
Technical Approach Decide on project Java vs. Visual Basic vs. C++ Builder SWING vs. AWT Applet vs. stand-alone application Development tools: Java JDK Metrowerks Codewarrior Client/Server interactions
Product Client Server Java components Documentation
Game Info Client Server ESCO/GENCO Place buy/sell bids User-friendly documentation Server Preferences Monitor all transactions and statistics
Client Startup
Client Main
Server Startup
Server Main
Milestones Learning Genetic Algorithms Getting specifications finalized Getting and using development tools Learning Java Getting applets to work on the web and with the server
Budget Financial Personnel Planned: $950 Actual: $39 Planned: 180 hours per person Actual: 200 hours per person
Future Work User testing/Interface improvement Buy power by hour instead of day Note: any non-interface changes will need to be done concurrently with the server program Configure CGI scripts through an applet
Lessons Learned Time management Stay on task Learn specifics as early as possible Be flexible Loss of group member Project change
Summary GUI and Network solutions Worked through project difficulties Thanks
Questions?