SWE 2410, Lab: The Garden in Action

• Complete the implementation you specified previously and started to implement. All team members must contribute; in particular, all must write a significant portion of the implementation.

• Randomly generate the locations of the bees and flowers. Ask if you need help with this!

• Allow the user to adjust the number of bees and flowers. The user should be able to enter 0 for both, and if you have an upper limit it should be at least 100. Do set the default counts to illustrate all of the expected behaviors (multiple types of flowers, multiple types of bees, and a reasonable chance of each bee encountering a flower).

• Your implementation will have a number of parameters that are somewhat arbitrary such as how far a bee moves on each step and how much energy is drained when a bee encounters a “bad” flower. Experiment with different values so a simulation with a reasonable number of bees and flowers illustrates all of the behaviors and all bees die off within about 30 seconds (while pressing the arrow key continuously). This default should be large enough that there are multiple instances of each flower and bee type. As an example of a parameter that might need adjusting, if bees gain too much energy from flowers then the bees will never die, but if they lose too much while flying between flowers then they die too quickly.

• Check that your user experience is reasonable. For example, the number of bees and flowers should be adjustable on the main screen, either with a text box with a default or a slider. Ensure focus is on the right element so pressing the arrow key does not require clicking somewhere else first. The image legend (showing types of bees and flowers) should be placed (possibly in a separate window) so that the garden space is as large as possible. In general, ensure the program’s user experience is consistent with what you would expect on Windows.

• Check that your solution meets your instructor’s coding standard. Document responsibilities for classes, but you do not have to write Javadoc for methods.

• Check your project in to the Git repository as described before. That is, check all sources are committed to the main branch.

• Check out your project in a new folder and ensure it builds. This helps ensure you did not fail to check in a critical file and that files are in the correct location. Mistakes in this often lead to losing points for easily-corrected issues.

• When you are finished, create a PDF containing the following:

  • A reverse-engineered class diagram (exported to a .PNG and then inserted into the document) of your implementation. Be sure to reorganize the classes on the diagram so the structure is clear and all of the classes fit on a single page.
  • A paragraph describing any significant changes to the design such as classes you add. Recall that you do not have to introduce design patterns into this lab.
  • A paragraph describing who implemented which portions of the system.
  • Screen shots of solution in action. You do not have to capture every behavior, but do capture that bees move in the correct directions and that they change energy levels. Be sure to describe what the screen shots show. Also include one or more screen shots, with many flowers and bees, that show how a botanist might use the program to answer their questions.
  • A sequence diagram illustrating how a bee targets a random flower and moves in a direct line to that flower. Draw a sequence diagram capturing the user clicks on the right arrow to have the bee execute one step to reach a targeted flower, interact with that flower, select a new flower, and then have the user click right arrow again so the bee executes one step towards the new flower. For the purposes of the diagram, assume the garden has just one bee and two flowers. Remember that the items at the top of the sequence diagram are objects, not classes; be sure to name each object. See the EA resource page for directions to create a sequence diagram.
  • A discussion of any known problems, either in the implementation or the design. Typically, documenting known problems reduces the penalty.

You will upload this PDF to Canvas. You can use MSWord or similar tools to create the PDF.

See Canvas for any additional submission instructions.