Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. 1. Itinerary Information Screen(Jody Hughes, ) The itinerary information screen is one that is navigated to from the returning user screen. When it is navigated to, the user’s name and unique RFID tag identification number is obtained from the returning user screen and the itinerary rides associated with that patron’s information is loaded onto the screen. If the page cannot obtain the user’s name and tag identification number the itinerary will not load successfully and there is an error in the parameters of the returning user screen. The screen displays from zero to six itinerary rides, one on each line, and provides a radio button, ride name, and the registered time for each ride, as shown in the following diagram.
  2. 2. The itinerary information page provides the ability for a patron to remove a selected ride from their itinerary. For adding or modifying rides to an itinerary the user must navigate to the modify itinerary screen, and that link is provided on the itinerary information page. The process for removing a ride from the itinerary on the itinerary information screen is as follows: • Step 1: Select the radio button corresponding to the desired ride to be removed from the itinerary. • Step 2: Click the Remove Selected button to remove the ride from the patron’s itinerary. See the image below for an illustration of where the radio button and the remove selected button are located on the screen.
  3. 3. Once the Remove Selected button has been selected a confirmation box will appear where the patron will verify that they desire to remove the selected ride from their itinerary as shown below. If the patron selects to remove the ride from the itinerary by clicking the OK button the ride associated with the selected radio button will be removed from the user’s itinerary in the database and the page will reload indicating these changes. If no radio button was selected, no ride will be removed from the patron’s itinerary. Also, if the user selects Cancel on the confirmation screen the user will be returned to the itinerary information page and no modification to the patron’s itinerary will have been made. In addition to removing rides from a patron’s itinerary, the following navigational functionality is available on the itinerary information page. These buttons include: Modify Itinerary: When clicked, this button navigates to the modify itinerary screen. Back to Account: When clicked, this button navigates back to the returning user’s screen and keeps the user logged in.
  4. 4. Logout: When clicked, this button will log the patron out of the ThrillTracker application and will navigate them back to the initial Patron Welcome Screen.
  5. 5. 2. RFID Interface Screen(Jody Hughes, ) The RFID interface screen displays the ability of the RFID reader to read the unique identification number of the RFID tag. The first step in performing this part of the demonstration is to physically verify the USB connection of the RFID reader to the target computer. When the application is initialized, information about the vendor included software library version is displayed on the screen. If the library is not installed the program will not initialize and the library information will not be displayed on the screen. If this happens, the Phidget library must be installed in the Java runtime environment directory, most commonly located at, system_driveProgram FilesJavajre1.6.0_03libPhidget. Once the library is properly installed, the first step of the application is to connect to the Phidget RFID reader. The application scans and locates the reader and returns text to the screen to indicate that the RFID reader has been connected to the application successfully and returns the serial number of the RFID reader that can be transferred to the database. To verify that the RFID reader is properly connected to the application, the following output is displayed
  6. 6. to the screen. If the RFID reader is not connected to the system, or if it is connected in an incorrect way, confirmation that the reader is attached will not be displayed and the screen will pause after the line “The system is waiting for the RFID reader to attach. . .”. If this happens the application must be forced to be terminated, and the RFID reader needs to be attached, or reattached to the system, and the application needs to be reinitialized. Once the RFID reader is properly connected, the following output on the screen indicates that the program is now poised to display output as an RFID tag is read by the reader. If the user wishes to terminate the application, it can be done by pressing the return or enter key. Once an RFID tag is placed close enough to the RFID reader its unique hexadecimal identifier is read by the reader and displayed to the screen. The following are five sample RFID tag numbers being read by the reader.
  7. 7. If an RFID tag is placed near the reader and no output is written to the screen there is most likely either not an RFID in the tag or the tag is faulty. Repeat this process using another tag until output of the tag’s identification number can be seen. Finally, once the user is finished having the reader read RFID tags, pressing the enter or return key will terminate the application. Confirmation of successful termination of the application is displayed to the screen as follows. This indicates that the program has terminated and the RFID reader is no longer reading tags. The following is the entire screen with all of these pieces displayed together.
  8. 8. The purpose of this interface is to retrieve the unique RFID tag information, and the RFID reader serial number from the reader each time a tag is read by the reader and transfer it to the ThrillTracker system. This simple screen is included in the prototype to demonstrate how this process works and to show that the RFID information can be easily obtained from the tag.