Overview 

 In order to present our clients with a quality product it is increasingly important to assess software in before the release to clients. This will allow for the team to deal with problematic areas in a more timely manner and prevent clients from seeing faulty functionality.   Bug hunts allow the company to assess the product before shipment with people that haven’t been directly involved with development. Hunts for SDK purposes differ from UI based products by the level of technical programming experience the participants must have.   Methodology 

 All challenges are tailored to test new areas of code or known risks areas. Participants will solve the challenges while an observer identifies problematic elements to the SDK. The solution for the current round will provide means to open the password protected zip file for the next challenge.   Programming groups will be formed through formal volunteer process . These groups consist of 5 members: 4 programmers and 1 observer. See Participants section for more information on roles and volunteer process. The groups will be constructed with people of various skill levels. See Group & Challenges section for  more details.   The hunt will consist of seven (7) challenges. One challenge will be given to each programming group for each of round. The same challenges will be given to all teams, which will allow for easier monitoring and judging. The following is an example challenge comprised for the BarcodeXpress 10 Bug Hunt:  

Challenge 1: Using the resources found in the zip folder, setup the SDK licensing for the Barcode SDK to allow for use in own application. After licensing has been established, run the sample application to test licensing. Successful setup will provide the clue to open the next challenge.

 Participants 

 All participants will be acquired on a voluntary basis.    Moderators (5 people) Give teams the instructions and resources needed to complete the challenges at hand. Keep time for challenges and notify teams of approaching time limits. Collect and Analyze the 

results and feedback provided by the Observers. Identify and present awards for challenge winners.   Observers (1 person per team) Watch the progression of the programmer teams. Will note problems and bugs encountered with documentation and implementation. Marks the time when team has completed challenge. Reports findings to Moderators.   Programmers (4 people per team) Perform the challenges with the given resources. Must be able to read or write code.    Groups & Challenges 

Challenge 1 (Licensing): Using the resources found in the zip folder, setup the SDK, OEM and Runtime licensing for the Barcode SDK to allow for use in own application. After licensing has been established, run the application to test licensing. Successful setup will provide the clue to open the next challenge. Resources in File will be text file with license info, bare bones project, dlls, help documentation, application to check, nested zip for next challenge. Solution is in binary

Challenge 2 (Reading Barcodes): Read the barcodes to find the key to open the next challenge. Tests the ability to read different barcodes. Build solution to read all barcodes on a page. This will contain riddle when pulled together. Solution to riddle will be code to unlock next zip. Resources in File will be page (PDF, TIFF, PNG?) of multiple barcodes and nested zip for next challenge.

Challenge 3 (Reading Subset of Barcodes - given page with mixed barcodes): The XXX barcodes hold the key to the next challenge. Gives clues to go to different location on the campus. Wrong answer will send to “Bad” location. Right answer will bring students to location with have the answer for them to write down to open next zip folder. Padlock to Pizza? Resources in File will be page (PDF, TIFF, PNG?) of multiple barcodes and nested zip for next challenge.

Challenge 4 (Writing Barcode): Revisit the XXX Codes for the statement to be placed in a PDF417 code. Write out this code into a PNG file and run through in the supplied application (Android app?) to confirm correct answer. This will unlock the next challenge. Resources in File will be page (PDF, TIFF, PNG?) of multiple barcodes, application to check and nested zip for next challenge.

Challenge 5 (Filter on Barcode Size): With the given page of barcodes, arrange them based on size then decode in order to get key to next challenge. When placed in min to max, will give sentence (or sum the numbers read) to open zip folder. Resources in File will be page (PDF, TIFF, PNG?) of multiple barcodes and nested zip for next challenge.

Challenge 6 (Barcode Characteristics): Use the Barcode Characteristics to unlock the key to the next challenge. There is 8 QR codes, each skewed, take the integer value and concatenate for the solution. Resources in File will be eight QR codes and nested zip for next challenge.

Challenge 7 (Region of Interest): Given the provided sheet, define a region of interest that will give you the key to the Bughunt Bonus Puzzle. The output of the skews from the previous challenge can be region of interest location. Resources in File will be page (PDF, TIFF, PNG?) of multiple barcodes and locked file with final puzzle.

Bughunt Bonus Puzzle: Application to check riddle result.

  Event Details 

 Date: March 27, 2015 Location: FL Polytech  

Accusoft Onsite Team:  John Reynolds Michael Archambault Ed Krajcik Vat Patel Matt Sullivan Sylvia Traxler Christine Hairelson Tom Setzer Dusty Myers John Thomas  FL Polytech Onsite Team:    Time 

 Schedule 

7:30am ­ 9:00am  Breakfast and Event Setup 

9:00am  Registration / Meet and Greet 

10:00am  Introduction and Rules 

10:30am  Challenges 

12:30pm  Lunch (brought in) 

1:00pm  Challenges 

3:30pm  Wrap up 

4:00pm  Reward Ceremony 

 Time Totals Registration: 1 hour Introduction: 30 minutes Challenge Time: 3.5 hours Reward Ceremony: 45 minutes  Time is calculated based on number of rounds. Each round will be about 15 to 20 minutes each. There will be 4 coding rounds with 10 minutes in between.   Points 

 Each challenge will be assigned points. These points will be used to determine the winner of the round and ultimately the winner of the Hunt.   Per Challenge Points First to Complete Challenge: 1 point ­ stopwatch and skype Complete Challenge: 1 point x challenge round (ie. round 5 will be 5 points) Improvement Suggestions: Based on improvement criteria guidelines  Overall Points Team Interaction: based on teamwork criteria guidelines Solve Challenge Style: based on style criteria guidelines Hunt Bonus: 8 points for solving the Riddle/Puzzle  Preparation 

 QA Create applications and material being used in the challenge Configure packages for test day to be passed to contestants General event coordination Feedback collection  Barcode Team (Accusoft as whole?) Assist with event arrangements (Setup, food, getting volunteers, etc.) Determine prizes Test the challenges to ensure ability to complete in allotted time  Marketing Swag identification and creation Fliers and other promotion materials Filming equipment and determining what is needed for event day  External Links 

 Action Items Score Board Code Style Judging Criteria Improvement Judging Criteria Teamwork Judging Criteria