-45%

CMSC 335 CMSC335 CMSC/335 ENTIRE COURSE HELP – UNIVERSITY OF MARYLAND GLOBAL CAMPUS (UMGC)

$149.99$275.00

CMSC 335 CMSC335 CMSC/335 ENTIRE COURSE HELP – UNIVERSITY OF MARYLAND GLOBAL CAMPUS (UMGC)

CMSC 335 Project 4 SeaPort

Introduction – the SeaPort Project series
For 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 JFrame
    • variables used by the GUI interface
    • world: World
  • Thing implement Comparable <Thing>
    • index: int
    • name: String
    • parent: int

Description

  

CMSC 335 CMSC335 CMSC/335 ENTIRE COURSE HELP – UNIVERSITY OF MARYLAND GLOBAL CAMPUS (UMGC)

CMSC 335 Project 4 SeaPort

Introduction – the SeaPort Project series
For 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 JFrame
    • variables used by the GUI interface
    • world: World
  • Thing implement Comparable <Thing>
    • index: int
    • name: String
    • parent: int
  • World extends Thing
    • ports: ArrayList <SeaPort>
    • time: PortTime
  • SeaPort extends Thing
    • docks: ArrayList <Dock>
    • 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
  • Dock extends Thing
    • ship: Ship
  • Ship extends Thing
    • arrivalTime, dockTime: PortTime
    • draft, length, weight, width: double
    • jobs: ArrayList <Job>
  • PassengerShip extends Ship
    • numberOfOccupiedRooms: int
    • numberOfPassengers: int
    • numberOfRooms: int
  • CargoShip extends Ship
    • cargoValue: double
    • cargoVolume: double
    • cargoWeight: double
  • Person extends Thing
    • skill: String
  • Job extends Thing – optional till Projects 3 and 4
    • duration: double
    • requirements: ArrayList <String>
      // should be some of the skills of the persons
  • PortTime
    • 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 the 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 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.

General Objectives

Here are some notes about the projects, the particular features of object-oriented design and object-oriented programming (OOD/OOP) the we want to cover in this class and some of the features of Java to help support that style of programming. We also want to explore the Java GUI system a little, with particular emphasis on viewing the data structures and effective ways to display the running of multiple threads competing for resources.

The particular scenarios selected for each semester ask you to implement as many of these objectives as possible in some compelling way. We are always open to additions and suggestions.

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
    • including a UML class diagram
    • classes, variables and methods: what they mean and why they are there
    • tied to the requirements of the project
  • User’s Guide
    • how would a user start and run your project
    • any special features
    • effective screen shots are welcome, but don’t overdo this
  • Test Plan
    • do this BEFORE you code anything
    • what do you EXPECT the project to do
    • 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:
    • Resources in pools – how many people with skill are currently available
    • Thread progress, resources acquired, and resources requests still outstanding

CMSC 335 CMSC335 CMSC/335 ENTIRE COURSE HELP – UNIVERSITY OF MARYLAND GLOBAL CAMPUS (UMGC)

CMSC 335 Project 3 SeaPort

Introduction – the SeaPort Project series
For 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 JFrame
    • variables used by the GUI interface
    • world: World
  • Thing implement Comparable <Thing>
    • index: int
    • name: String
    • parent: int
  • World extends Thing
    • ports: ArrayList <SeaPort>
    • time: PortTime
  • SeaPort extends Thing
    • docks: ArrayList <Dock>
    • 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
  • Dock extends Thing
    • ship: Ship
  • Ship extends Thing
    • arrivalTime, dockTime: PortTime
    • draft, length, weight, width: double
    • jobs: ArrayList <Job>
  • PassengerShip extends Ship
    • numberOfOccupiedRooms: int
    • numberOfPassengers: int
    • numberOfRooms: int
  • CargoShip extends Ship
    • cargoValue: double
    • cargoVolume: double
    • cargoWeight: double
  • Person extends Thing
    • skill: String
  • Job extends Thing – optional till Projects 3 and 4
    • duration: double
    • requirements: ArrayList <String>
      // should be some of the skills of the persons
  • PortTime
    • 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 the 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 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.

General Objectives

Here are some notes about the projects, the particular features of object-oriented design and object-oriented programming (OOD/OOP) the we want to cover in this class and some of the features of Java to help support that style of programming. We also want to explore the Java GUI system a little, with particular emphasis on viewing the data structures and effective ways to display the running of multiple threads competing for resources.

The particular scenarios selected for each semester ask you to implement as many of these objectives as possible in some compelling way. We are always open to additions and suggestions.

Project 3 General Objectives
Project 3 – More JDK classes – GUI’s and threads

  • Explore other GUI classes, such as JTree, JTable, and JProgressBar.
  • Create and run threads
    • Competing for one resource.

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
    • including a UML class diagram
    • classes, variables and methods: what they mean and why they are there
    • tied to the requirements of the project
  • User’s Guide
    • how would a user start and run your project
    • any special features
    • effective screen shots are welcome, but don’t overdo this
  • Test Plan
    • do this BEFORE you code anything
    • what do you EXPECT the project to do
    • 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 3 Specific Goals:
Implement threads and a GUI interface using advanced Java Swing classes.

  1. Required data the data structure specified in Project 1:
    1. World has SeaPort’s
    2. SeaPort has Dock’s, Ship’s, and Person’s
    3. Dock has a Ship
    4. Ship has Job’s
    5. PassengerShip
    6. CargoShip
    7. Person has a skill
    8. Job requires skills– NEW CLASS for this project!
    9. PortTime
  2. Extend Project 2 to use the Swing class JTree effectively to display the contents of the data file.
    • (Optional) Implement a JTable to also show the contents of the data file. There are lots of options here for extending your program.
  3. Threads:
    • Implement a thread for each job representing a task that ship requires.
    • Use the synchronize directive to avoid race conditions and insure that a dock is performing the jobs for only one ship at a time.
      • the jobs of a ship in the queue should not be progressing
      • when all the jobs for a ship are done, the ship should leave the dock, allowing a ship from the que to dock
      • once the ship is docked, the ships jobs should all progress
      • in Project 4, the jobs will also require persons with appropriate skills.
    • The thread for each job should be started as the job is read in from the data file immediately after the entire data file has been read.
    • Use delays to simulate the progress of each job.
    • Use a JProgressBar for each job to display the progress of that job.
    • Use JButton’s on the Job panel to allow the job to be suspended or cancelled.
  4. As before, the GUI elements should be distinct (as appropriate) from the other classes in the program.
  5. See the code at the end of this posting for some suggestions.

Suggestions for Project 3 Job class. Here is a sample of code for a Job class in another context, the Sorcerer’s Cave project. The code for this class will need some modifications, but this should give you an idea of the issues involved.
In fact, you should find much of this code redundant.

Also, some of the code at the following sites might give you some ideas about how to proceed with this project:

CMSC 335 CMSC335 CMSC/335 ENTIRE COURSE HELP – UNIVERSITY OF MARYLAND GLOBAL CAMPUS (UMGC)

CMSC 335 Project 2 SeaPort

Introduction – the SeaPort Project series
For 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 JFrame
    • variables used by the GUI interface
    • world: World
  • Thing implement Comparable <Thing>
    • index: int
    • name: String
    • parent: int
  • World extends Thing
    • ports: ArrayList <SeaPort>
    • time: PortTime
  • SeaPort extends Thing
    • docks: ArrayList <Dock>
    • 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
  • Dock extends Thing
    • ship: Ship
  • Ship extends Thing
    • arrivalTime, dockTime: PortTime
    • draft, length, weight, width: double
    • jobs: ArrayList <Job>
  • PassengerShip extends Ship
    • numberOfOccupiedRooms: int
    • numberOfPassengers: int
    • numberOfRooms: int
  • CargoShip extends Ship
    • cargoValue: double
    • cargoVolume: double
    • cargoWeight: double
  • Person extends Thing
    • skill: String
  • Job extends Thing – optional till Projects 3 and 4
    • duration: double
    • requirements: ArrayList <String>
      // should be some of the skills of the persons
  • PortTime
    • 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 the 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 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.

General Objectives

Here are some notes about the projects, the particular features of object-oriented design and object-oriented programming (OOD/OOP) the we want to cover in this class and some of the features of Java to help support that style of programming. We also want to explore the Java GUI system a little, with particular emphasis on viewing the data structures and effective ways to display the running of multiple threads competing for resources.

The particular scenarios selected for each semester ask you to implement as many of these objectives as possible in some compelling way. We are always open to additions and suggestions.

Project 2 General Objectives:

Project 2 – Map class, Comparator, sorting

  • Use the JDK Map class to write more efficient code when constructing the internal data structures from the data file.
  • Implement SORTING using the Comparator interface together with the JDK support for sorting data structures, thus sorting on different fields of the classes from Project 1.
  • Extend the GUI from Project 1 to let the user sort the data at run-time.

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
    • including a UML class diagram
    • classes, variables and methods: what they mean and why they are there
    • tied to the requirements of the project
  • User’s Guide
    • how would a user start and run your project
    • any special features
    • effective screen shots are welcome, but don’t overdo this
  • Test Plan
    • do this BEFORE you code anything
    • what do you EXPECT the project to do
    • 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 2 Specific Goals:

Extend Project 1 to use advanced data structures and support sorting on various keys.

  1. Required data structure – the data structure specified in
    Project 1:

    1. World has SeaPort’s
    2. SeaPort has Dock’s, Ship’s, and Person’s
    3. Dock has a Ship
    4. Ship has Job’s
    5. PassengerShip
    6. CargoShip
    7. Person has a skill
    8. Job requires skills – optional until Project 3
    9. PortTime
  2. Use the HashMap class to support efficient linking of the classes used in Project 1.
    1. The instances of the hash map class should be local to the readFile (Scanner) method.
    2. These instances should be passed as explicit parameters to other methods used when reading the data file.
      1. For example, the body of the methods like the following should be replaced to effectively use a <Integer, Ship> hash map, the surrounding code needs to support this structure:

        Ship getShipByIndex (int x, java.util.HashMap <Integer,
        Ship> hms) {
        return hms.get(x);
        } // end getDockByIndex
      2. Since the body of this method has become trivial, perhaps the call to this method can be simply replaced by the get method of the HashMap.
      3. Your code should be sure to handle a null return from this call gracefully.
    3. The instances should be released (go out of scope, hence available for garbage collection) when the readFile method returns.
    4. Comments: The idea here, besides getting some experience with an interesting JDK Collections class, is to change the operation of searching for an item with a particular index from an O(N) operation, ie searching through the entire data structure to see if the code can find the parent index parameter, to an O(1) operation, a hash map lookup. Of course, this isn’t so very interesting in such a small program, but consider what might happen with hundreds of ports, thousands of ships, and perhaps millions of persons and jobs.
    5. Comments: Also, after the readFile operation, the indices are no longer interesting, and could be completely eliminated from the program. In this program, removing the index references could be accomplished by removing those variables from the parent class, Thing.
  3. Implement comparators to support sorting:
    • ships in port que ArrayList’s by weight, length, width, draft within their port que
    • all items withing their ArrayList’s by name
    • OPTIONALLY: sorting by any other field that can be compared
    • The sorting should be within the parent ArrayList
  4. Extend the GUI from Project 1 to allow the user to:
    • sort by the comparators defined in part 2.
  5. Again, the GUI elements should be distinct from the other
    classes in the program.

CMSC 335 CMSC335 CMSC/335 ENTIRE COURSE HELP – UNIVERSITY OF MARYLAND GLOBAL CAMPUS (UMGC)

CMSC 335 Project 1 SeaPort

Introduction – the SeaPort Project series
For 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 JFrame
    • variables used by the GUI interface
    • world: World
  • Thing implement Comparable <Thing>
    • index: int
    • name: String
    • parent: int
  • World extends Thing
    • ports: ArrayList <SeaPort>
    • time: PortTime
  • SeaPort extends Thing
    • docks: ArrayList <Dock>
    • 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
  • Dock extends Thing
    • ship: Ship
  • Ship extends Thing
    • arrivalTime, dockTime: PortTime
    • draft, length, weight, width: double
    • jobs: ArrayList <Job>
  • PassengerShip extends Ship
    • numberOfOccupiedRooms: int
    • numberOfPassengers: int
    • numberOfRooms: int
  • CargoShip extends Ship
    • cargoValue: double
    • cargoVolume: double
    • cargoWeight: double
  • Person extends Thing
    • skill: String
  • Job extends Thing – optional till Projects 3 and 4
    • duration: double
    • requirements: ArrayList <String>
      // should be some of the skills of the persons
  • PortTime
    • 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 the 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 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.

General Objectives

Here are some notes about the projects, the particular features of object-oriented design and object-oriented programming (OOD/OOP) the we want to cover in this class and some of the features of Java to help support that style of programming. We also want to explore the Java GUI system a little, with particular emphasis on viewing the data structures and effective ways to display the running of multiple threads competing for resources.

The particular scenarios selected for each semester ask you to implement as many of these objectives as possible in some compelling way. We are always open to additions and suggestions.

General objects for each project:

  • Project 1 – classes, text data file, GUI, searching
    • Define and implement appropriate classes, including:
      • instance and class variables,
      • constructors,
      • toString methods, and
      • other appropriate methods.
    • Read data from a text file:
      • specified at run time,
        • JFileChooser
          jfc = new JFileChooser (“.”);

          // start at dot, the current directory
      • using that data to create instances of the classes,
      • creating a multi-tree (class instances related in
        hierarchical, has-some, relationships), and
      • organizing those instances in existing JDK structures
        which can be sorted, such as ArrayList’s.
    • Create a simple GUI:
      • presenting the data in the structures with with some
        buttons and
      • text fields supporting SEARCHING on the various fields of
        each class.