i have attached the file
OOF Assign A 1OOF Assignment Part A - due: 10:00 am Tues 7th of April, this is the first and final hand in date p. 1 of 13 Department of Computer Science and Information Technology La Trobe University CSE1OOF Semester 1, 2020 Assignment Part A Due Date: Tuesday, 7th of April, at 10.00 a.m. First and Final date for SUBMISSION Tuesday 7th of April at 10.00 am Delays caused by computer downtime cannot be accepted as a valid reason for a late submission without penalty. Students must plan their work to allow for both scheduled and unscheduled downtime. There are no days late or extensions on this assignment as execution test marking will begin on Tuesday 7th of April – in your normal lab (Week 5) This is an individual Assignment. You are not permitted to work as a Pair Programming partnership or any other group when writing this assignment. Copying, Plagiarism: Plagiarism is the submission of somebody else’s work in a manner that gives the impression that the work is your own. The Department of Computer Science and Information Technology treats academic misconduct seriously. When it is detected, penalties are strictly imposed. Refer to the subject guide for further information and strategies you can use to avoid a charge of academic misconduct. Assessment Objectives: • To practise using the String class. (Lecture/Workshop 2 and Lab 2) • To practise using if, if-else statements (Lecture 5 and 6, Lecture/Workshop 3) • To practise reading from and writing to the console and reading from a text file. Submission Details: Full instructions on how to submit electronic copies of your source code files from your latcs8 account are given at the end. If you have not been able to complete a program that compiles and executes containing all functionality, then you should submit a program that compiles and executes with as much functionality as you have completed. (You may comment out code that does not compile.) Note you must submit electronic copies of your source code files using the submit command on latcs8. Ensure you submit all required files, one file at a time. For example, the file Task3.java would be submitted with the command: > submit OOF Task3.java PLEASE NOTE: While you are free to develop the code for this progress check on any operating system, your solution must run on the latcs8 system. Marking Scheme: This assignment is worth 5% of your final mark in this subject. Implementation (Execution of code) 100%, see conditions on page 3 You may be required to attend a viva voce (verbal) assessment (to be used as a weighting factor on the final mark). Do NOT use the LMS to submit your files, use latcs8 only 1OOF Assignment Part A - due: 10:00 am Tues 7th of April, this is the first and final hand in date p. 2 of 13 Return of Mark sheets: The face to face execution test marking in the lab (Week 5) constitutes a return of the assignment mark, subject to the conditions on pages 3 and 11 - 12. Please note carefully: The submit server will close at 10:00 am on Tuesday 7th April After the submit server has closed, NO assignments can be accepted. Please make sure that you have submitted all your assignment files before the submit server closes. (see pages 11 - 12) There can be NO extensions or exceptions. Everyone has been given a 1 week extension on the normal hand in date for this assignment. Your assignment will be marked in your normal lab, starting week 5, Wednesday 8th April. If you cannot attend a lab in week 5, please email us to arrange another time. Marking scheme: 100% for the code executing correctly You will be asked to explain (and / or alter) parts of your code, this may decrease your mark, in extreme cases to 0, see page 3. You should attend the lab you been have assigned by Allocate+ to have your assignment marked. Turn up to a lab in Week 5, regardless of Allocate+. Non-attendance at a week 5 lab will result in your assignment being awarded 0, except as detailed below. This notice overrides any information on Allocate+. 1OOF Assignment Part A - due: 10:00 am Tues 7th of April, this is the first and final hand in date p. 3 of 13 Please also note carefully that whilst we encourage innovation and exploring java beyond what has been presented in the subject to date, above all, we encourage understanding. All of the Tasks that follow can be solved using techniques that have been presented in lectures, lecture / workshops and labs so far. These are the techniques and knowledge that we will later be examining in the Real Time Test (20 marks) and the exam (50 marks). Code and techniques that are outside the material presented will not be examined, of course. You are free to solve the Tasks below in any way, with one exception and one condition. Any assignment that uses code that is outside what has been presented to this point must be fully explained at the marking execution test. Not being able to fully explain code outside what has been presented in the subject so far will result in the assignment being awarded a mark of 0, regardless of the correctness of the program. Submitting an assignment with code outside what has been presented so far and not attending the marking execution test will result in an automatic mark of 0, regardless of the correctness of the submission. An example would be the split( ) method in the String class. The reason being that this method returns an array and we haven't studied arrays yet. So using the split( ) method would require you to be prepared to explain to the marker how arrays worked in Java, plus anything else that maybe involved in getting split( ) to compile and run. Another example is the use of BufferedReader, this is not being taught at all, so it won't be on the exam. Everything you need to do this assignment has already been covered up to and including, Lecture 6, Workshop 3 and Lab 3. All assignments in OOF are marked, face to face, in the lab, in an execution test. This means that we mark running code. Your code must compile and display a result to the screen. Regrettably, we don't have the time or resources to look at code. The smallest amount of code that produces and displays a correct result will gain more marks than lots of code that doesn't compile, run or display something to the screen. Using code not taught in OOF - READ THIS How this assignment is marked 1OOF Assignment Part A - due: 10:00 am Tues 7th of April, this is the first and final hand in date p. 4 of 13 In all the Tasks that follow, the String for City maybe empty (how you can detect this is described below). If the City String is empty, then the text "No City Listed" is assigned to the City String. Task 1 – Task1.java Write a Java program called Task1.java that, firstly, prompts (asks) the user to enter an input file name. This is the name of a text file that can contain any number of records. A record in this file is a single line of text in the following format: Country|Airport code|City|State|Airport Name where Country, is the name of the airport. This is a String (text) and maybe more than one word. The Country is followed by a '|' character, there are no spaces before or after the '|'. Airport code is the IATA airport code. This code uniquely identifies any airport in the world. It is always text, a String. The Airport code is followed by a '|' character, there are no spaces before or after the '|)'. City, is the name of the city of the airport. This is a String (text) and maybe than one word. The City may also be empty, it would look like this || The City is followed by a '|' character, there are no spaces before or after the '|'. State, is the name of the state, or province, that the airport is in. This is a String (text) and maybe more than one word. The State is followed by a '|' character, there are no spaces before or after the '|'. Airport name is the name of the airport