This document outlines the requirements for a final project in an object-oriented and concurrent programming course. Students must design and implement a program to simulate creatures completing jobs or tasks over time. The program must include resource pools, creature job threads that can block until required resources are available, and a GUI to display progress. Students will be graded based on their program design, functionality, testing, documentation, and code quality. The project is due by the assigned date and must follow specific formatting and submission guidelines.

1. Buy here:
http://theperfecthomework.com/cmsc-335-final-project/
Final Project - Due
CMSC 335 6381 Object-Oriented and Concurrent Programming (2158)
The star indicates that the pair of fields may be repeated 0 or more times.
j:<index>:<name>:<creature index>:<time>[:<required artifact type>:<number>]*
Project 4
The project will be
graded according the
criteria for the final
project - see below.
Elaboration:
1. 1. An
addition to
the data file
- specifying
jobs for
creatures.
● o
j:<index>:<na
me>:<creatur
e
index>:<time>
[:<required
artifact
type>:<numb
er>]*
●
NOTE - The details of this section are subject to change, but
the spirit will remain:
This is meant to be a learning experience, not a death march!
Do the best you can, explain what you have done, what should
still be done and how you would go about implementing the
additional features. Make sure your test cases cover ALL the
issues - thus demonstrating that you have considered and
understood all the issues in the project, even you have have
not had time to implement all the features.
One more thing - ​you can help each other​ , just be clear about
what code is yours and what you have shared from others.
So, let's focus on the aspect that I think is most critical here -
communicating threads.
Start with the following (Functionality points):
1. 1. Start a thread for each job, by implementing
Runnable in the Job (or equivalent) class.
2. 2. (F: 30/40) Read the data file and create the
appropriate jobs (threads).

2. ●
1. 2.
Resource
pools - data
structures
supporting
unassigned
artifacts of a
given type,
along with
supporting
assignment
to creatures
2. 3.
Creature job
threads -
connected
to the
resource
pools and
supporting
the concept
of blocking
until
required
resources
are
available
before
proceeding.
3. 4. GUI
showing:
● o Resources
in pools
● o Thread
progress,
resources
acquired, and
resources
requests still
outstanding
1. 5.
(options)
3. 3. (F: 35/40)Implement the resource pools.
4. 4. (F: 38/40)Implement the connections between
the resource pools and the threads using a
resource management approach.
5. 5. (F: 40/40) Add elements to the GUI to make
user control convenient.
I would say that accomplishing 1-2 is worth 90% of this
project, 3 goes to 95%, and 4 would produce a 98% project,
then the final GUI for 100%.
ND.

3. Deliverables
1. 1. Java source code files
2. 2. any configuration files used
3. 3. a well-written Word document describing:
4. a. your overall design, including a UML class diagram showing the type of the
class relationships
5. b. description of how to set up your application
6. c. your test plan, including test data and results, with screen snapshots of
each of your test cases
7. d. your approach, lessons learned, design strengths and limitations, and
suggestions for future improvement and alternative approaches
Your project is due by midnight, EST, on the date posted in the class schedule. Your
instructor's policy on late projects applies to this project.
Submitted projects that show evidence of plagiarism will be handled in accordance with
UMUC Policy 150.25 — Academic Dishonesty and Plagiarism.
Format
Documentation format and length. The documentation describing and reflecting on your
design and approach should be written using Microsoft Word, and should be no more than
five pages in length and no less than two pages. The font size should be 12 point. The page
margins should be one inch. The paragraphs should be double spaced. All figures, tables,
equations, and references should be properly labeled and formatted using APA style.
● Code format:
● o header comment block
● o appropriate comments within the code
● o appropriate variable and function names
● o correct indentation
Grading
This activity is awarded 20 percent of the total grade in the course. In the grade book, the
total number of points will be set to 100. The project elements will be assessed as follows:

4. Attributes Value
Project design 20 points
Project functionality 40 points
Test data 20 points
Approach
documentation
15 points
Grammar and spelling 5 points
Total 100 points
Final Project
​Due October 11 at 11:59 PM
The star indicates that the pair of fields may be repeated 0 or more times.
j:<index>:<name>:<creature index>:<time>[:<required artifact type>:<number>]*
Project 4 - Due Oct 13
The project will be
graded according the
NOTE - The details of this section are subject to change, but
the spirit will remain:
This is meant to be a learning experience, not a death march!
Do the best you can, explain what you have done, what should

5. criteria for the final
project - see below.
Elaboration:
1. 1. An
addition to
the data file
- specifying
jobs for
creatures.
● o
j:<index>:<na
me>:<creatur
e
index>:<time>
[:<required
artifact
type>:<numb
er>]*
●
●
1. 2.
Resource
pools - data
structures
supporting
unassigned
artifacts of a
given type,
along with
supporting
assignment
to creatures
2. 3.
Creature job
threads -
connected
to the
resource
pools and
supporting
the concept
of blocking
still be done and how you would go about implementing the
additional features. Make sure your test cases cover ALL the
issues - thus demonstrating that you have considered and
understood all the issues in the project, even you have have
not had time to implement all the features.
One more thing - ​you can help each other, just be clear about
what code is yours and what you have shared from others.
So, let's focus on the aspect that I think is most critical here -
communicating threads.
Start with the following (Functionality points):
1. 1. Start a thread for each job, by implementing
Runnable in the Job (or equivalent) class.
2. 2. (F: 30/40) Read the data file and create the
appropriate jobs (threads).
3. 3. (F: 35/40)Implement the resource pools.
4. 4. (F: 38/40)Implement the connections between
the resource pools and the threads using a
resource management approach.
5. 5. (F: 40/40) Add elements to the GUI to make
user control convenient.
I would say that accomplishing 1-2 is worth 90% of this
project, 3 goes to 95%, and 4 would produce a 98% project,
then the final GUI for 100%.
ND.

6. until
required
resources
are
available
before
proceeding.
3. 4. GUI
showing:
● o Resources
in pools
● o Thread
progress,
resources
acquired, and
resources
requests still
outstanding
1. 5.
(options)
Deliverables
1. 1. Java source code files
2. 2. any configuration files used
3. 3. a well-written Word document describing:
4. a. your overall design, including a UML class diagram showing the type of the
class relationships
5. b. description of how to set up your application
6. c. your test plan, including test data and results, with screen snapshots of
each of your test cases
7. d. your approach, lessons learned, design strengths and limitations, and
suggestions for future improvement and alternative approaches
Your project is due by midnight, EST, on the date posted in the class schedule. Your
instructor's policy on late projects applies to this project.
Submitted projects that show evidence of plagiarism will be handled in accordance with
UMUC Policy 150.25 — Academic Dishonesty and Plagiarism.
Format

7. Documentation format and length. The documentation describing and reflecting on your
design and approach should be written using Microsoft Word, and should be no more than
five pages in length and no less than two pages. The font size should be 12 point. The page
margins should be one inch. The paragraphs should be double spaced. All figures, tables,
equations, and references should be properly labeled and formatted using APA style.
● Code format:
● o header comment block
● o appropriate comments within the code
● o appropriate variable and function names
● o correct indentation
Grading
This activity is awarded 20 percent of the total grade in the course. In the grade book, the
total number of points will be set to 100. The project elements will be assessed as follows:
Attributes Value
Project design 20 points
Project functionality 40 points
Test data 20 points
Approach
documentation
15 points
Grammar and spelling 5 points
Total 100 points