Project 4 Introduction - the SeaPort Project series For this set of projects for the course, 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 JFrame o variables used by the GUI interface o world: World  Thing implement Comparable <Thing> o index: int o name: String o parent: int  World extends Thing o ports: ArrayList <SeaPort> o time: PortTime  SeaPort extends Thing o docks: ArrayList <Dock> o que: ArrayList <Ship> // the list of ships waiting to dock o ships: ArrayList <Ship> // a list of all the ships at this port o persons: ArrayList <Person> // people with skills at this port  Dock extends Thing o ship: Ship  Ship extends Thing o arrivalTime, dockTime: PortTime o draft, length, weight, width: double o jobs: ArrayList <Job>  PassengerShip extends Ship o numberOfOccupiedRooms: int o numberOfPassengers: int o numberOfRooms: int  CargoShip extends Ship o cargoValue: double o cargoVolume: double o cargoWeight: double  Person extends Thing o skill: String  Job extends Thing - optional till Projects 3 and 4 o duration: double o requirements: ArrayList <String> // should be some of the skills of the persons  PortTime o time: int Eventually, in Projects 3 and 4, you will be asked to show the progress of the jobs using JProgressBar's.

Here's a very quick overview of all projects: 1. Read a data file, create the internal data structure, create a GUI to display the structure, and let the user search the structure. 2. Sort the structure, use hash maps to create the structure more efficiently. 3. Create a thread for each job, cannot run until a ship has a dock, create a GUI to show the progress of each job. 4. Simulate competing for resources (persons with particular skills) for each job. Project 4 General Objectives Project 4 - Concurrency  Resource pools o Threads competing for multiple resources  Blocking threads  Extending the GUI interface to visualize the resource pools and progress of the various threads. Documentation Requirements: You should start working on a documentation file before you do anything else with these projects, and fill in items as you go along. Leaving the documentation until the project is finished is 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)  Design o including a UML class diagram o classes, variables and methods: what they mean and why they are there o tied to the requirements of the project  User's Guide o how would a user start and run your project o any special features o effective screen shots are welcome, but don't overdo this  Test Plan o do this BEFORE you code anything o what do you EXPECT the project to do o justification for various data files, for example  Lessons Learned o express yourself here o a way to keep good memories of successes after hard work
Project 4 Specific Goals: Extend project 3 to include making jobs wait until people with the resources required by the job are available at the port. Elaboration: 1. Reading Job specifications from a data file and adding the required resources to each Job instance. 2. Resource pools - SeaPort.ArrayList <Person> list of persons with particular skills at each port, treated as resource pools, along with supporting assignment to ships and jobs. 3. Job threads - using the resource pools and supporting the concept of blocking until required resources are available before proceeding. 4. The Job threads should be efficient: 1. If the ship is at a dock and all the people with required skills are available, the job should start. 2. Otherwise, the Job should not hold any resources if it cannot progress. 3. Use synchronization to avoid race conditions. 4. Each Job thread should hold any required synchronization locks for a very short period. 5. When a job is over, all the resources used by the job (the people) should be released back to the port. 6. When all the jobs of a ship are done, the ship should depart the dock and if there are any ships in the port que, one of then should should be assigned to the free dock, and that ships jobs can now try to progress. 7. NOTE: If a job can never progress because the port doesn't have enough skills among all the persons at the port, the program should report this and cancel the job. 5. GUI showing: o Resources in pools - how many people with skill are currently available o Thread progress, resources acquired, and resources requests still outstanding

You expect someone to write such a project for you?

Just take it step by step. As you know the Java documentation is very through, and there are surely code snippets online for any of the steps where you feel unsure.

The SeaPort Project series involves simulating aspects of various sea ports. The project consists of several classes with their corresponding instance variables:

1. SeaPortProgram:
This class extends JFrame and includes variables used by the GUI interface. It also has a variable called "world" of type World.

2. Thing:
This class implements the Comparable interface and has the following instance variables: index (int), name (String), parent (int).

3. World:
This class extends Thing and includes the following instance variables: ports (ArrayList<SeaPort>) - a list of sea ports, time (PortTime) - the current time.

4. SeaPort:
This class extends Thing and includes the following instance variables: docks (ArrayList<Dock>) - a list of docks in the sea port, que (ArrayList<Ship>) - the list of ships waiting to dock, ships (ArrayList<Ship>) - a list of all the ships at this port, persons (ArrayList<Person>) - people with skills at this port.

5. Dock:
This class extends Thing and includes the following instance variable: ship (Ship) - the ship currently docked at the dock.

6. Ship:
This class extends Thing and includes the following instance variables: arrivalTime, dockTime (PortTime) - the time of ship's arrival and docking, draft, length, weight, width (double) - ship's specifications, jobs (ArrayList<Job>) - the list of jobs associated with the ship.

7. PassengerShip:
This class extends Ship and includes the following instance variables: numberOfOccupiedRooms, numberOfPassengers, numberOfRooms (int) - passenger ship specific attributes.

8. CargoShip:
This class extends Ship and includes the following instance variables: cargoValue, cargoVolume, cargoWeight (double) - cargo ship specific attributes.

9. Person:
This class extends Thing and includes the following instance variable: skill (String) - the skill of the person.

10. Job:
This class extends Thing (optional until Projects 3 and 4) and includes the following instance variables: duration (double) - the time required to complete the job, requirements (ArrayList<String>) - the skills required for the job.

11. PortTime:
This class includes a single instance variable: time (int) - the time value.

The overall goal of Project 4 is to extend Project 3 to include waiting for required resources (people with specific skills) for each job. This is achieved through the use of resource pools, job threads, and synchronization.

The specific objectives of Project 4 are as follows:
1. Reading job specifications from a data file and adding the required resources to each job instance.
2. Implementing resource pools using ArrayList<Person> to represent persons with specific skills at each port.
3. Implementing job threads that block until the required resources are available before proceeding.
4. Ensuring efficiency in job threads by starting the job only if all the required skills are available and not holding any resources if the job cannot progress.
5. Using synchronization to avoid race conditions and ensuring that each job thread holds synchronization locks for a short period.
6. Releasing all the resources used by a job back to the port once the job is completed.
7. Allowing ships to depart the dock when all their associated jobs are done and assigning a new ship from the port queue to the now free dock.
8. Reporting and canceling jobs that cannot progress due to insufficient skills available at the port.
9. Updating the GUI to show the resources in the pools (e.g., number of people with a specific skill), thread progress, and outstanding resource requests.