The Road Safety Authority (RSA) is tasked with improving safety on our roads in order to reduce death and injury resulting from road collisions. The legal basis for the RSA is set out in the Road...

The Road Safety Authority (RSA) is tasked with improving safety on our roads in order to reduce death and injury resulting from road collisions. The legal basis for the RSA is set out in the Road Safety Authority Act 2006. The RSA formally came into existence on 1st September 2006. The RSA have enlisted you to develop an application which will test users ability to identify and understand different road signs. They have given you a free hand with regard to how the application will look and work. The only stipulations they have placed on you are as follows: 1. You must make use of all the road sign images they have given you. Although, not all images need to be used in a single run of the test. 2. The images must be logically grouped in the test*. 3. Due to the high number of people now residing in the country who speak a language other than English, your final deliverable must be capable of running in English and your choice of two other languages (add more if you like). 4. The date and time must be displayed in the top left hand corner of your application (on all screens) and must be localized to the locale that the application is currently running in. 5. A splash screen must be used when it runs initially. 6. (Localised) Feedback must be given to the user after they have finished. 7. They require you to add at least one innovation (unique feature) to the application. This innovation must complement the existing functionality. *A suggestion to group your images would be along the following guidelines: 1. Information Signs. 2. Motorway Signs 3. Regulatory Traffic Signs 4. Tourist Information Signs 5. Warning Signs 5.1 General purpose Warning Signs 5.2 Roadworks 5.3 Warning Traffic Signs I will be assessing your final deliverable under the following headings. 1. Functionality and Innovation offered (45%) 2. Unique feature (15%) 3. Complexity (10%). 4. Quality of the UX (10%) 5. Completeness (5%). 6. Clarity and quality of code (2%). 7. Ability to withstand user error (3%) 8. Weekly Demo’s (10%). NOTE: 1. You must upload your work to Moodle on the following dates by 6pm:  07/10/2020  14/10/2019  21/10/2020  28/10/2020 (**** final upload ****) Failure to upload your code, will see your final mark reduced by 3% for every upload you miss. Your code needs to be checked into Moodle regardless of whether you have made any progress or not. When you are uploading you code, please make sure that you don’t overwrite previous uploads. To prevent this, incorporate the date of submission into the file name you upload. 2. You are required to demonstrate your code weekly in class to me between now and the final submission (28/10/2020). 10% is allotted to these demonstrations; clear progress will be expected from week to week. Failure to demonstrate your work in a given week will see you forfeit your marks for that demonstration. Demonstrations will be required on the following days  07/10/2020 (3%)  14/10/2019 (3%)  21/10/2020 (4%)  28/10/2020 (**** final upload, so no demo this day ****