Assignment 5 Checklist
Grade Criteria
Maximum available assignment points: 100. Each topic is scored with a value that ranges from 1 to 10 (best). Each category is weighted to generate a final score. The categories and weighting values are:
On-Time 5%
Code Quality 15%
Use of Abstract class 5% Simulation Quality 20% Multi-Rule Quality 10% Start/StopFunction 5% UI Functionality 10% Thread/Messaging 15% Visual Quality 15%
Criteria Notes
Code Quality
• Good code structure and design – Simpler is better
• Avoid overly lengthy classes and methods
• Avoid overly repetitive code
• Intuitive naming for methods and variables
• JavaDoc Comments on classes and methods Use of Abstract
• Demonstrate use of an Abstract class within the UI
Simulation Quality
• Clarity of simulation operation and structure
• Demonstrates Modular design and rule implementation
• Simulation technical merit
Multi-rule Quality
• Demonstrates usage of alternate rule options
• Usage of differing class implementations
Start/Stop Function
• Has buttons for controlling simulation action
• Program will restart correctly after stopping
UI Functionality
• UI works correctly and does not freeze when the simulation is started
• Window resizing works when the simulation thread is running
• Simple operation with intuitive functionality
Thread/Messaging
• Simulation executes on a managed thread
• The application demonstrates proper thread management and control
• Information about simulation activities is properly conveyed to a display
panel for rendering.
Visual Quality
• A subjective assessment of the display quality
• Good usage of visual elements and color
Pre-submission Checklist
• Ensure that your simulation produces data on a consistent and periodic basis. Slow the thread down if computations occur too quickly.
• Ensure that all buttons work, and perform correctly over multiple simulation runs.
• Check UI thread operation by attempting to run a simulation and then resize the display to see if there are thread or update anomalies.
• Check your .jar file and ensure that it contains a manifest file with appropriate values.
• Ensure that simulation processing occurs on its own thread, and doesn’t run on the GUI thread.
• Name your .jar file: assign5-username.jar
• Ensure that your software runs outside of an IDE by using a the console
command:
o > java –jar assign5-username.jar
• Check your code functionality by having a friend or associate run the .jar file
on their computer
• Upload your source code as a .zip or .rar archive
• Upload your working program as a .jar file
• Submit copies/scans of any UML sequence diagrams that haven’t been scored
to ensure full credit.