COP 3540 – Data Structures with OOPProject 2 – Fall 2009 Priority QueuesUsing NetBeans 6.7.1, you are to write a Java program using OOP principles to accommodate the following functionality Assignment #2Objectives:Provide student with additional experiences with file input output.Provide student with exercises in learning UMLProvide student with exercises in Javadoc and its various formatsProvide student with exercises in building an array of objects to support priority queuing.Provide student with experience in inserting, deleting, and searching priority queue of objects.Functionality: Given a sequential file, States.Fall2009.txt on my web page, you are to build a series of priority queues discussed ahead, and one single input queue (not a priority queue– just a regular queue). You are specifically required to build six priority queues one for each Region with entries ultimately ordered on State Name for that region. Please note that there is considerable additional data in each record in the file that you may not need for this program. Do NOT eliminate it. Just don’t process it.The input data is not sorted in any way. As you read an input record from this file, create an object of type (class) State. Add this object to one of the six queues, depending on the State Name itself. Thus the insert() priority is based on State Name. All other inputs are to be ignored. Be certain to add internal comments in the insert() routine citing your procedure.You will note that at the conclusion of building your priority queues, each priorityqueue may well have a different number of objects within it. Once all six priority queues have been built, you are to display each of the queues – by region name - with an appropriate centered header on your screen, such as Region 1: New_England<skip a line>ConnecticutMassachusetts MaineNew HampshireRhode IslandVermont.<skip two lines>Region 2: Middle_Atlanticetc. .Once you have displayed the six priority queues, you are to open a transaction file called newStates.Fall2009. You are to read each of these input streams and build an array of objects. (This will be a small array – fewer than ten records). The format of the objects, however, should be the same as the format of the objects in the priority queues. Ensure your program is not dependent upon exact number of input records. (Read and build your input array – until end of file – before you start to process the inputs)Once this non-priority queue is built, you are to display the queue in a professional manner – simply a text listing, centered and titled will be sufficient.Then, taking each of these entries, insert them into the appropriate priority queues using your same insert() algorithm you used when the priority queues were initially built.Display only those queues which have been updated and these should appear as before. Bingo! You are done.Your zipped folder to me MUST include copies of both input files. I will need these to run your program and to test it. Do not provide me with output your program generates. I will get your program to generate your outputs. As noted, your outputs will be displayed on the screen.UMLYou are to include a UML class diagram. You may use Word or Power Point. Drag your UML design file into your P2 subfolder within your COP3540 desktop folder. It will be included in the zip file to me.JavadocAll programming is to be accompanied by appropriate Javadoc. Generate your Javadoc files and include these in your submission to me. You are to zip all files in your P2 as expected and Send them to be via Digital Dropbox using the same naming conventions as in P0 and P1. Your zip file is NOT to include yourN-number. Rather, it must be project2.youruserid, as project2broggio NOT project2n00010109.GradingSource Code – 30 pointsIndentationInternal commentsScope terminatorsOverall program structureProgram Design – 20 pointsAppropriateness of the objects and their services providedInterface to objectsAttribute and method visibilityJavadoc – 10 pointsAppropriateness and completeness of commentsALL methods must have Javadoc comments up front that are meaningful, please.UML – 10 pointsCorrectness, associations, completeness. This means that the classes you identify are correct, that associations are indicated, and that the attributes and methods are documented within the classes.Outputs – 30 pointsAccuracy and FormatSkip lines in between displayed numbers for readability.Include headers / descriptors as you may feel appropriate. Program must run correctly to receive a passing grade and to receive at least partial credits above. If the program does not successfully run to end of job and include all major functional requirements, all bets are off.Start early and do this a little at a time. You know the drill.
View Full Document
Unlocking...