100 likes | 426 Views
Reality Fantasy Sports. Yoshito Kosai David Couvrette. Operational Concepts. Purpose: Create a more complex fantasy sports league Give a more realistic position of GM Be able to use only one league year-round Why?: Sports culture has high demand for fantasy sports leagues
E N D
Reality Fantasy Sports Yoshito Kosai David Couvrette
Operational Concepts • Purpose: • Create a more complex fantasy sports league • Give a more realistic position of GM • Be able to use only one league year-round • Why?: • Sports culture has high demand for fantasy sports leagues • New playing system, will trigger a new generation of fantasy sports fans • Current fantasy leagues are non-business based • User-friendly and only have to keep track of one league. No multiple accounts necessary.
System Requirements (1) • Features: • Team revenue (factors) • Attendance at games • Selling players • Players • When the league is created, there will be a draft where each team takes turns selecting players from the player pool • Will have contracts, which can’t be terminated unless the player “approves” • For a player to approve he must get paid at least as much as he is currently getting paid • When a player’s contract expires, he will either stop playing or he will play for the team with the highest bidder • Other features • Team managers (users) have the option of trading players with other teams • Have a choice to recruit players who are currently in the minor league • For leagues that do not fill to maximum capacity, or for managers who stop playing, there will be an AI that will complete the season.
System Requirements (2) • Website based interaction • Main database server holds information • TCP/IP connection to transfer data • Similar website format as current leagues • Admin specific software
System and Software Architecture • Http service accessed through web-browser • TCP/IP connection to transfer data • Main database server holds all information • Admin and users have different accessibility • Following diagram shows the integration of all necessary components:
Scheduled Timeline • Week 1-4: Create a stable database structure for information management. • Week 5-6: Establish a working client-server interface for users. • Week 7: Complete administrative up-keeping interface for administrators to maintain the up-to-date service and finalize release.
Feasibility Rationale Integrity and Compatibility: • Similar to fantasy system in place • Same concept, different playing platform Risks: • Sports culture deteriorates • Too complex for people to enjoy • Incompatible with previous platform style
Project Summary • Similar to current fantasy sports • Whole new different style of management • Involves a more financial standpoint to sports club management • Produces a more real-life experience of GM position • One account/league for all sports for the whole year • Provides AI for leagues without sufficient users
Finally……… Is this project really possible to develop and release in this amount of time?
Finally……… Is this project really possible to develop and release in this amount of time? Yes, this project is very well within realm and can be applied to the present day demand for fantasy sports.