Internal Code: TV643
Advanced Java Assignment Help:
Task:
Introduction
The kind of assignments that we are seeking is the one that has significant scope for the application of the subject’s content in continuation the assignment 1 and its improvement. We need a problem for the assignment 2 that has potential for the nice application of the user interface technologies of Swing/JavaFx and Graphics 2D, the use of multi-threading, documentation and the computational strength to make performance and memory management a significant issue in the quality of the solution. The tasks of adding automation and more interactive graphical features to the assignment 1 work will be related to assignment 2.
As a result, we have opted to improve the Safe-Driving Practice Simulation problems with automated demo and more graphical interactions and representation. The system must be implemented in Java.
Logistics
The assignment can be done in a group of 2 people.
The assignment is worth a total of 30% of the total assessment.
The assignment is due by 11 pm, Friday, 20th Oct, 2017.
The assessment of the assignment will be based on the presence of working features and on submission of the assignment according to the rules and deadlines. Assignment marks may be reduced by the presence of acknowledged external software comprising more than 20% of your assignment (based on lines of code).
If your assignment is found to contain the same or similar codes to another source and this has not been acknowledged, the marks penalty will be extremely high. Important: the portions of imported code from any source
must be acknowledged as comments in the code by clearly delimiting the boundaries of the imported code and providing a reference to the source of the code. The readme.txt file should also indicate that there is imported code.
The Problem
An automated demo-initiated simulated safe-driving practice test program familiarizes a user with the road safety and the functionality of the program. Upon logging with your userid and password, you can select the demo version for maximum three times before you proceed for the real test. On selecting the demo, the demo program will graphically show a complete road safety by considering a hazard scenario with a random number of cars<=5. At the end of the demo, the automated program will show the statistics in a graphical format – bar or pie chart. To move into the practice test, you can select any number of car>=4, and you can also select any of the listed diverse scenarios with a traffic hint. You need to use JTree, JList, JTable, check box, radio button or combo box or similar for selecting the number of cars, color of the cars, and a traffic hint. Implement the first scenario that has been detailed below; and you are required to propose, implement, and test an additional scenario with two suitable hazard types in the same manner as detailed for the first scenario.
The first scenario includes 4 (or more depending your selection) moving cars with a traffic hint of a school hour; each car driver needs to maintain a speed limit of <=40 kmpr, any car going beyond 40 kmpr will be instantly shown PINK, any brake attempt by a driver in a front car will lead other drivers in the back to pressing the brake as well. You are required to record the number of times a brake is pressed by a car driver for an abruptly appearing and graphically visible hazard; the first scenario will exist for 400 (or more depending on your selection for the duration of the scenario) seconds upon a click on the start button. You are also required to click on the car(s) that needs to be put into brake immediately upon a hazard which must be visible for six to eight seconds; if your click on a car (a button designated for that car) nearly matches (acceptable delay<=3 seconds) with the program-generated track of the same car in need for control, GREEN status light will be on for 3 seconds. You are required to propose and implement two suitable hazard types for your scenario and check which of the cars is/are in need for brake or control to avoid accident. At the end of the 400 (or more as selected) seconds, the program needs to show a comparative table of your clicks to identify a car in need for control and your program- generated record for each car that was in need for control. The table needs to show the date and time related to a car and your click for the car and the program-generated track of the same car that was in need for control; there must be an additional column to show three Green Stars for a situation in which your click on a car (a button designated for that car) nearly matches or coincides (acceptable delay<=3 seconds) with the program-generated track of the same car in need for control. There must be an option to save the table data in an xml format.
The total mark for the Assignment 2 will be obtained by adding all the marks, dividing by 10, rounding up to the next whole number and then subtracting marks for acknowledged code > 10% of total, any penalties for lateness and the inclusion of unacknowledged code.
The order of the feature list is also designed as a suggestion for the order of development and will guide the order of presentation of the lecture material. Ideally, you should have all the theory before you start the assignment, but this is, of course, not possible. Therefore, we have sequenced the lecture material in order to support the development of the assignment as much as is practicable.