CSSE 220 – Object-Oriented Software Development

Homework 25

Objectives

Start developing an intuition for algorithm analysis. Experiment with sorting and searching. More design practice.

Tasks

  1. Complete the assigned reading for the next session, according to the course schedule. As you read, see if you can answer the self-check questions. If there is something you do not understand, make note of it so you can ask about it.
  2. Complete the assessment exercises over this reading on ANGEL (under Lessons → Assignments).
  3. Solo Work :
    1. Your solo work for this part must be done in the SortingAndSearching project inside Eclipse. Use the SVN Repository Exploring perspective to check out this project, then switch back to the Java perspective.
    2. For this task, you’ll be working in the Loops class of the counting package. For each method in that class, add a comment stating how many times the array variable is accessed in the best and worst cases. Give your answers as closed form formulae in n, the length of the input array. Do not count array.length as an array access. One of the comments is given as an example.

      You may add profiling code if you wish, but should not change the behavior of the given methods.

    3. In-class: Complete the TODO items in sorting.FunctionObjectsExample.
    4. Open the file, writtenProblems.txt, in the SortingAndSearching project in Eclipse. Edit the file to answer to the questions that you’ll find there.
  4. Team Assignment: First, do the quite brief Cycle 2 Evaluation of Team Performance survey on Angel, under Lessons → Assignments (at the top of the list) if you haven't (ASAP). Then continue working with your team toward the next assigned milestone of the Vector Graphics.

Remember, in all your code:

  • Write appropriate comments:
    • Javadoc comments for public fields and methods.
    • Explanations of anything else that is not obvious.
  • Give self-documenting variable and method names:
    • Use name completion in Eclipse, Ctrl-Space, to keep typing cost low and readability high.
  • Use Ctrl-Shift-F in Eclipse to format your code.
  • Take care of all auto-generated TODO's.
    • Then delete the TODO comment.
  • Correct ALL compiler warnings.
    • Quick Fix is your friend!

Here is the grading rubric for this assignment.

Turn-in Instructions

Turn in your individual work by committing it to your SVN repository.

See the Vector Graphics assignment description for team project deliverables.