SeaPort Project series..solved

SeaPort Project series..solved

Introduction - the SeaPort Project seriesFor this set of project, we wish to simulate some of the aspects of a number of Sea Ports.Here are the classes and their instance variables we wish to define:·SeaPortProgram extends JFrameovariables used by the GUI interfaceoworld: World·Thing implement Comparable <Thingoindex: intoname: Stringoparent: int·World extends Thingoports: ArrayList <SeaPortotime: PortTime·SeaPort extends Thingodocks: ArrayList <Dockoque: ArrayList <Ship // the list of ships waiting to dockoships: ArrayList <Ship // a list of all the ships at this portopersons: ArrayList <Person // people with skills at this port·Dock extends Thingoship: Ship·Ship extends ThingoarrivalTime, dockTime: PortTime

draft, length, weight, width: doubleojobs: ArrayList <Job·PassengerShip extends ShiponumberOfOccupiedRooms: intonumberOfPassengers: intonumberOfRooms: int·CargoShip extends ShipocargoValue: doubleocargoVolume: doubleocargoWeight: double·Person extends Thingoskill: String·Job extends Thing - optional till Projects 3 and 4oduration: doubleorequirements: ArrayList <String// should be some of the skills of the persons·PortTimeotime: intProject 1 - Also seeGradingThe goals are:1.Create a GUI2.Let the user select a data file, using JFileChooser

Read the data file, creating the specified internal data structure (see theIntroductionforthe classes and variables of the structure).4.Display the internal data structure in a nice format in the GUI1.use JScrollPane and JTextArea5.Display the results of a Search specified by the user1.JTextField to specify the search target2.Searching targets: name, index, skill would be a minimumyou are encouraged to provide other options3.Note that a search may return more than one item4.DO NOT create new data structures (beyond the specified internal data structure)to searchyou may create a structure of found items as a return valueDocumentationHINT: You should start working on a documentation file before you do anything else with theseprojects, and fill in items as you go along. Leaving the documentation until the project is finishedis not a good idea for any number of reasons.The documentation should include the following (graded) elements:·Cover page (including name, date, project, your class information)·Designoincluding a UML class diagramoclasses, variables and methods: what they mean and why they are thereotied to the requirements of the project·User's Guideohow would a user start and run your projectoany special featuresoeffective screen shots are welcome, but don't overdo this

Test Planodo this BEFORE you code anythingowhat do you EXPECT the project to doojustification for various data files, for example·Lessons Learnedoexpress yourself hereoa way to keep good memories of successes after hard work
Powered by