SQLI Internal Hackathon BattleBrain 2020

Hi, I’m Younes, I was happy to hear we are returning to work at SQLI offices! With the new health security policy, now the seats are no longer nominative, humm that’s an issue what if I come up late and find the sweet spot next to the window already taken?! If only there was some way simple and intuitive to choose my place...

Oh wait! We do have skilled peoples at SQLI and I believe they can help provide a solution for me to book my seat in advance!

Hey, another problem comes to my mind, how can I make sure to comply to social distancing rules while choosing my seat? Can this solution system recommend me a place appropriate based on some pre-defined rules?

Also, why not the solution even suggest seats next to my team members?

Hello SQLI Talents! Can you help Younes solve his problem?

Intermediate Uses Cases:

• Younes has the possibility to book a secure seat for one or more time ranges based on pre-defined health security policy constraints.
• Younes can see how many seats are available and their location/position.
• The provided seats for Younes should comply to occupency rules:
  • 50% of all seats in one area are occupied at most.
  • No two seats are directly located next or in front of each other.
  • Seats are not named (no one owns the seat).
  • Admin can override seat availability.

Advanced Uses Cases, the solution should be able to:

• Younes can see existing seats reservation with the names and teams.
• Younes can select the team he's working with and the solution proposes to him specific seats.
• Younes must select all the days per week that his team requires him to be on site.

Champions Uses Cases:

• Maybe you thought of a specific use case that can help Younes? Show us your skills!

• Last Generation Laptops
• Cloud Computing Vouchers
• ELearning Vouchers

Goodies: Tee-shirt, Hats and more.

• One participant can only submit a project with one team.
• All code that is submitted must be developped during the Hackathon, if the participant is reusing existing code, it must be declared in the README document. Code that is re-used but not declared can disqualify your solution.

Maximum of two per team

All technologies are accepted as long as you have an interactive user interface.

48h starting from Friday 24th at 6pm GMT+1

All teams must submit three mandatory artefacts in a github private repository:

• Screencast of the solution
• Detailed README
• Working code

You are highly encouraged to also submit photos and video of your team effort and fun moment during the Hackathon!

In order to select the first three winning teams, the organization committee will filter the submitted solutions based on a formal and transparent initial selection criteria.

Following this first selection, a Jury committee will evaluate all selected teams solutions based on a notation grid detailed below.

In order for your team's solution to be presented for Jury evaluation, you must submit all expected deliverables and they have to comply to the following rules:

• Screencast of the solution
  • The video must show one or multiple use cases that are solved by your solution.
• Detailed README
  • Based on the content of this file, the organization committee should be able to compile and run your solution.
  • Must include Team Participants
  • Must include if you are re-using code
• Working code
  • Compiling code without errors.

The Jury will evaluate your solution based on the following axis by applying a score representing to what extent your solution fulfills the specific Topic:

• Number of fully working use cases - 40%
• Innovative technologies / AI / Recommendation Algorithms - 30%
• Quality of Deliverables (Code, Ease of deployment, Video quality, etc) - 20%
• UI / User Experience - 10%

• Create or use your Account on Github
• Duplicate/Fork privately this repository and put your solutions artefacts in the dedicated folders (Video, Code)
• Once you are ready to submit your solution, add/invite the provided committee users as Read Only users to your repository.

A Teams invitation will be sent to you to join the #battlebrain channel for discussion during the 48h.