SE 2811, Lab 4: Planting the Garden

• Develop the system you specified in Lab 3. All team members must contribute; in particular, all must write a significant part of the implementation.

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

• Your implementation will have a number of things 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 within about a minute of runtime. For instance, if bees gain too much energy from flowers, it is unlikely that your instructor will ever be able to see a bee consume all of its energy. Adjusting paremeters such as energy gain/energy drain is a critical part of the lab.

• Lab 3 specifies that the user will be able to adjust the number of bees and flowers. There should not be an upper or lower limit on either. Do set the default values 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).

• 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. This includes

  • Checking that all sources are committed. Use the standard, global gitignore file to ensure you do not check in .class files and other build products. The sample bee code contains a .gitignore file to be placed in the top directory; it is good for you to include that in your submission. Do include build configuration files created by IntelliJ in the .idea folder (except the workspace.xml file).
  • Ensure your project is at the top level of the repository. That is, if your group’s repository is lab2–2811-knuth-djikstra, then the src folder should be lab2-2811-knuth-djikstra\src.
  • Ensure all code is in the main branch (or, if using an old environment, master) - your instructor will not check other branches. Branches are unlikely to help on such a small project anyways.

• It is always a good practice to 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 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.