plz find attached assignments
Microsoft Word - OOF Semester 1 2018 Assignment Part A.docx OOF Assignment Part A - due: 10:00 am Tues 10th Apr this is the first and final hand in date p. 1 of 13 Department of Computer Science and Information Technology La Trobe University CSE1OOF/4OOF Semester 1, 2018 Assignment Part A Due Date: Tuesday, 10th Apr, at 10.00 a.m. First and Final date for SUBMISSION Tuesday 10th Apr 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 Wednesday 11th Apr – 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) 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. (Lecture 4, Lab 3 and example code on LMS) 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 Ticket.java would be submitted with the command: > submit OOF Ticket.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 10% of your final mark in this subject. Implementation (Execution of code) 90%, explanation of code 10% 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 OOF Assignment Part A - due: 10:00 am Tues 10th Apr 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 12 - 13. Please note carefully: The submit server will close at 10:00 am on Tuesday Apr 10th 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 12 - 13) 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 Apr 11th. If you cannot attend the lab you have signed up for on the LMS page, please email me (
[email protected]) to arrange another time. Marking scheme: 90% for the code executing correctly 10%, you will be asked to explain (and / or alter) parts of your code. You must attend the lab you have signed up for on the LMS OOF page to have your assignment marked. If you have not signed up for a lab on the LMS page, your assignment will not be marked and it will be awarded 0. Non-attendance at the week 5 lab you have signed up for on the LMS page will also result in your assignment being awarded 0, except as detailed below. OOF Assignment Part A - due: 10:00 am Tues 10th Apr 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. Another example is the use of BufferedReader. Any use of methods from the Integer or Double classes is not allowed and will result in the task being awarded 0, regardless of the correctness of execution. BufferedReader is not being taught at all, so it won't be on the exam, although it can be used provided you can fully explain its use. 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 OOF Assignment Part A - due: 10:00 am Tues 10th Apr this is the first and final hand in date p. 4 of 13 Task 1 – Tram.java Write a Java program called Tram.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: Suburb[Tracker Id[Stop Number[Cross Street[Road where Suburb is the name of the suburb through which the tram is travelling at the location indicated by the information in the last part of the record. This is a String (text) and may contain more than one word. The Suburb is followed by a '[' character, there are no spaces between the end of the Suburb, the '[' and the start of the Tracker Id Tracker Id is the Tram Tracker Id of the Tram stop. Tracker Id's are unique. Tracker Id's are always 4 digits (integers). The Tracker Id is followed by a '[' character, there are no spaces between the end of the Tracker Id, the '[' and the start of the Stop Number. Stop Number is the number of the Tram stop, this is an integer and may consist of one or two digits. The Stop Number is followed by a '[' character, there are no spaces between the end of the Stop Number, the '[' and the start of the Cross Street. Cross Street is the name of the nearest cross street to a Tram stop. This is a String (text) and may contain more than one word. This Cross Street is followed by a '[' character, there are no spaces