From the archive. Dates and instructions on this page are historical. For current information, see Conferences and the Calendar.

FLC Hackathon 2019

Prompt:

Georgia FBLA has a large database of advisers, and throughout the year, it is imperative that the information on this database is accurate to ensure that information can travel easily and consistently to advisers for conferences, competitive events, and other Georgia FBLA related activities. To make Monty’s life simpler and to ensure better translation/writing of data to our database, this year’s FLC Hackathon challenge is to create a system to update the contact information of advisers from various chapters. This information will be given to you in CSV format, and you must create a way for advisers to update their information in an easy manner. This system should be easy for advisers to understand, should protect against user error, and should have rollback protection in case an adviser inputs incorrect information. The system must be able to export updated information as a CSV.

Guidelines:

  • Projects should be able to authenticate chapters through their unique chapter ID that corresponds to their school. Refer to the example CSV file to see how information is presented.
  • Your system should be able to pull current chapter information to present for the user. Existing data should be able to be updated and blank fields should be able to be filled.
  • Your system should verify any new information with the adviser and ask for them to signoff on any changes. Remember: do not override current information. Store new data in a manner such that past information can still be easily accessed.

General Rules:

  • All database structures MUST be able to export to a finalized Excel/CSV version. You can use any database to collect and store your information, but the finalized information collected from advisers must be presented in a CSV format which is with proper row and column names.
  • All code must be unique, and not copied from any outside sources. It is okay to use open-source code as a reference to understand how to code something, but you cannot directly copy other code; everything must be unique.
  • There must be a README file in the Github page that clearly defines how to run the application, and how various features of the application are intended to function. If we are not able to run the code due to improper instructions, there may be significant penalties involved.
  • The finalized version of the project should be bug-free and properly able to compile. Code that does not compile will receive significant penalties.

Judging Criteria:

Projects will be judged by (In order of weight):

  • Functionality​ – Your program must foremost be able to perform and function according to the guidelines presented in the project rubric. It should be able to accomplish all the goals listed in the guidelines in an error-free manner.
  • Ease of Use​ – Your program should be easy to use, and shouldn’t have to be deciphered to understand. The goal is to create a simple product that anyone can use, and excessive complexity will result in a loss of points.
  • Design​ – A product is defined by the way that it looks, and such, the design of this product will also be taken into consideration when judging. Use of Georgia FBLA logos, color schemes and a GUI that is appealing to view will result in a better product and a better score on your finalized rubric.
  • Computational Workload / Database Design – ​The speed of the executed program will also be considered when finally grading. Any processes that take too long or result in a poor user experience will detract from your overall product appeal and score.

Submission:

  • Submissions must be made to this form, with all required information on Thursday, November 21 by 3:30 PM.
  • Github Link​ – A public Github repository that holds all of your code. No changes can be made to this repository after Thursday, November 21 at 3:30 PM. Please ensure that the following things are included within this page:
    • ➢  All SOURCE code for your project. DO NOT submit compiled code, as this will lead to automatic disqualification. We must be able to see your actual code.
    • ➢  A README file that contains instructions and specifics on the functionality of your program. This file should include any language(s), frameworks, or dependencies of your project. Please ensure that your README has your school name and your name(s) so that we can identify your program.
  • Youtube Link​ – An UNLISTED recording of your screen (ScreenCast) of you running through your program will serve as your “pitch”. It must show the following
    • Authentication
    • Prefilled Fields for Chapters
    • Editable Information
    • Submit and Data Writing to CSV 

Upload successful!