Part 0, 0 points: Create a new Java file, MyBlockingQueue.java. Include a file header that includes the names of all teammembers. I recommend doing this as a Javadoc comment:

/**
 * Models a thread-safe Blocking Queue.
 *
 * @author Barbara M. Roberts <barbie@mattel.com>
 * @author Margaret Hadley <midge@mattel.com>
 */

Part 1, 0 points: Start your MyBlockingQueue class and, in good Java practice, include a generic type for the type of objects that will be stored in your queue. In case you haven't done that before, you can do it like this:

public class MyBlockingQueue<YourGenericType> {

Part 2, 0 points: Add a constructor that takes a single int parameter. This will be the maximum number of elements that can be inside your MyBlockingQueue at any time. Think about what fields you want your class to have and do all the appropriate initialization in the constructor. (You'll likely have to come back here and change things as you continue through the project.) You can then create blocking queues like this:

MyBlockingQueue<String> blockingStrings = new MyBlockingQueue<>(5);

Part 3, 0 points: Add a method, add, that takes a parameter of your generic type and adds it to the back of your queue. The signature should start off looking like this:

public void add(YourGenericType element) {

Part 4, 10 points: Add a toString method that prints out the elements in the queue.

Part 5, 50 points: Add a method, remove, that removes and returns the element at the front of the queue.

Part 6, 7 points: Add a method, getNumElements, that returns the number of elements currently stored in the queue.

Part 7, 8 points: Add a method, getFreeSpace, that returns the number of empty spots in the queue.

Part 8, 0 points: At this point, you should be able to compile and run your queue with my code: BlockingQueueTester.java. Most of the project points are indicated there, though there isn't a perfect test for every part! If you put that in the same folder as your code, you can test your code like this:

$ javac *.java
$ java -ea BlockingQueueTester

$ java -ea BlockingQueueTester 500

Part 9, 10 points: Make sure that your queue is FIFO (First-In, First-Out).

Part 10, 30 points: Make sure that your remove method blocks appropriately: when there are no elements in the queue.

Part 11, 30 points: Make sure that your add method blocks appropriately: when the queue is full.

Part 12, 10 points: Make sure that your queue passes my stress tests. (There are some commented-out print statements you can comment-in as necessary while you're testing.)

Part 13, 20 points: Make sure that there are no race conditions or possible deadlocks in your project. You may or may not see this during testing, so be very careful. I will look carefully at your code!

Submitting your Project: Upload your MyBlockingQueue.java file to canvas. If you get it up before the deadline and send me a Slack message, I can run a test on my own computer. (There is no limit to the amount of times you can ask me to do this. The only barrier is how much time I actually have.) Make sure the names of all group members are in the code header.