Reference no: EM13332164

Create a console-mode executable class (no GUI in this project; let's keep it simple) using the following specifications:

• Name your executable class RockFiles
• Prompt the user to enter the full (absolute) path and filename of the input file to read

o  Read the path/file name from the keyboard and use it for opening and processing the input file
o  The input file will contain an unknown number of rows up to a maximum of 200 that will contain both good and bad data
o  Using ONLY File class supplied methods, test for file's existence and the fact that it is a file MUST be verified PRIOR to opening the file.
-  If file does not exist OR if the user entry is not a file, exit the program immediately (do not try opening the file) and supply an appropriate message to the screen explaining that they program is terminating and why.

• Hard-code (do not prompt for & read) the absolute path and name of the first output file.

o  Must be called validRecords.csv and placed in the root directory of the "D:" drive.
-  Use code that will allow it to be used on as many platforms as you can; don't hard code the separator (\ or /)...demonstrated in class.
o  This is where you will write your "valid" records from your array of type Rocks (the interface from the last project)...yes, you again are using polymorphism.

• Hard-code the absolute path and name of a second output file.

o  Must be called suspense.csv and must also be placed in the root directory of the "D:" drive.
-  This file will hold ALL records with formatting issues (wrong type of data in a field), and/or the wrong number of fields necessary to instantiate ANY of the 3 classes used.
-  Hint:  If a Monument object is to be instantiated and placed into the array, how many fields should be on the input line? What about the MonumentBase class?  You are still only to use the largest constructors of each class.

• Create an array of type Rocks FROM THE VALID INPUT LINES ONLY (based upon the above two qualifiers) in the same manner as the supplied Project 03 executable class; after you validate the line and determine it is OK, just instantiate the appropriate object and add the object to the array.

o  You must determine if a line is valid by using exception processing (when appropriate) AND field (token) counting (when appropriate) and any bad data lines are to be written to suspense.csv EXACTLY AS THEY ARE/EXIST
IN THE INPUT FILE...just write the entire input String row itself without any changes.
-  For a full description of bad data, see below
-  The input file layout that must be used follows at the end of this document

• Write to the "bad data" (suspense.csv) file, each line written EXACTLY as it exists in the input file, when a line contains:

o  The incorrect number of fields to instantiate EITHER of the 2 object types...Monument or MonumentBase
o  OR Character or String data in a numeric field (improper format)
o  OR float ing point data in an integer field (improper format)
-  Do not worry about any other data checks; the above three are sufficient for this project to cut down on
programming time.

• Create a second file (validRecords.csv), WRITING IT FROM YOUR Rocks array AFTER THE ARRAY HAS BEEN

CREATED IN ITS ENTIRETY (entire input file processed), which contains all valid records/lines (and ONLY valid records) from the input file.
o  This must be the LAST function of your program and written only after the Rocks Array has been satisfactorily completed; write it from a single loop that does nothing else but write the file.
o  A record is valid when it passes the aforementioned data checks.