Table of Contents Executive Summary 2
Download 471.88 Kb.
|
- Navigate this page:
- 3.5 Figure 1: A high level view of the system’s communication between the 4 major parts.
- 3.5 Figure 2: High level view of data flow in and out of the database system.
- 3.5 Figure 3: A high level diagram of the data flow in and out of the fan application.
3.5 Expanded Design SummaryThe Little League Statistic Tracking system is a 4 tiered approach to providing a similar statistical network to that which is currently being used by the MLB and other professional sports leagues. It will provided Little League coaches with the ability to track the individual performance of all of their players in addition to providing metrics for these coaches to better prepare against other teams in the league who also use the tracking system. Additionally, the system provides the parents and relatives of the players with a means to both follow their games in real time if they are not able to make it to them in person as well giving them access to professional levels of statistics for every player in the league. The system itself will consist of 4 major undertakings:
The high level diagram showing the general flow of information between the 4 system parts can be seen below in 3.5 Figure 1. 
3.5 Figure 1: A high level view of the system’s communication between the 4 major parts. The umpire indicator will be similar to what is currently used by umpires to keep track of strike, ball, and out counts. The device will use three screens to inform the user of the strike, ball, and out counts and will increment when the appropriate push button is pressed. The device will also have special functions to advance the umpire device to the next batter and to reset the data on the device if an accidental increment has been triggered. Finally, the indicator device will have one single Bluetooth modules built in to the device to connect to each of the devices running the coach application. The Bluetooth module being used allows the umpire device to send data to both coach devices at the same time. This circumvents the need to have the device upload the information directly to the database and have the strike, ball and out information pulled back from the database to the coaching applications. The coach application will be written for the Android operating system to be used on any of the emerging tablet devices that support the operating system. It will consist of several interfaces that provide 3 main functionalities: pre-game preparation, in-game play recording, and post-game review. The pre-game manager will allow a coach to both edit and review his current roster, displaying an array of statistics and in-depth details for each individual payer. It will also provide a means for the coach to easily and intuitively create both a batting lineup and a starting field lineup before a game so as to minimize the complexity of the next component, the in-game manager. The in-game manager will be the interface through which all play data enters the database. Prior to the beginning of the game, the 2 devices must sync via a Bluetooth connection with the umpire indicator. Once connected, any change in state in the umpire indicator will almost immediately be indicated within the coach application. All offensive plays made will be entered by the coach of the team currently at bat in a manner that will record all statistics that have previously been recorded by the baseball scorecards that this system intends to replace. The plays will be uploaded to the online database as a play object as they are confirmed to ensure easy compatibility with the fan application. Finally, the coach application will allow for a user to browse the plays of previous games, and individual team and player statistics from other teams that are utilizing this system. The backbone of this system will ultimately be the database to which everything will be loaded into as it will be the medium through which individual plays will be turned into meaningful information, and also in that it will be what distributes this data to all the devices in this system. The database will organize team statistical information into separate records, allowing each player to maintain their own unique portfolio, while simultaneously providing accumulated statistical analysis for entire team records. Additionally, the database will manage query response resources, as well as data backups and record migration. For variable-dependant statistics, the database will seamlessly calculate and record averages and seasonal data, and store them for the team to view for analysis purposes. For security purposes, the database will implement an identifier system to ensure only properly authorized clients have the ability to read or write data to the database, based on their according role. A very high level view of the information flowing in and out of the database can be understood by viewing 3.5 Figure 2 below. 
3.5 Figure 2: High level view of data flow in and out of the database system. The final component in the system is the fan application, through which parents, or any fans, can follow games in real time as they are occurring from anywhere with an internet connection. Once a fan has chosen to follow a particular game, the application will ping the database on a frequent interval (about every 30 seconds) to see if any new plays have been uploaded by the coach applications. If any new data is found, it will be displayed at the top of the scrolling play list. Clicking on any of the play within the aforementioned list will bring the user to the detailed play view, which gives a more in depth description of the play and all of the players involved. Additionally, users will be able to search the database and bring up detailed player info similar to that within the coach application’s Roster Management interface. The fan application will also have a feature that sort all of the teams in the league to determine rankings by sorting information from the database according to games played and number of wins. Basic data flow through the application is shown in 3.5 Figure 3 below. 
3.5 Figure 3: A high level diagram of the data flow in and out of the fan application. Directory: seniordesign -> fa2010sp2011 seniordesign -> Hvac control and Feedback System 0 Group 2 Steve Jones Mathew Arcuri Elroy Ashtian, Jr seniordesign -> Group 5 Spr-Sum 2011 seniordesign -> Senior Design II paper seniordesign -> Remote Touchscreen-Controlled Defense Turret Senior Design Documentation Courtney Mann, Brad Clymer, Szu-yu Huang Group 11 seniordesign -> Flight Performance Data Logging System seniordesign -> Amphibious vehicle seniordesign -> T-100 Watch Dog (Autonomous Security Vehicle) seniordesign -> Ehvac: Wireless Modular Multi-Zone hvac controller Group b javier Arias Ryan Kastovich Genaro Moore Michael Trampler Download 471.88 Kb. Share with your friends:
|