TaskList

/************************************************************
  p2 Task List (must be completed and submitted for Team Building 102)
  
  Team Number: ____7_____   Team Name: ___________The Brogrammers_________________

In an effort to help students improve the process of learning to
to work together in their teams and as a way to provide each team with 
a way to document and communicate the work required and how each 
team member contributed, each team must complete this document as 
part of their p2 work.

Task List Usage:
1. Use this to document the tasks that you each complete for p2.
   Each task to be completed is identified and listed in this document 
   with a (i) symbol to indicate that it is not yet started.

2. When one or more team members are working on a specific task, 
   they change the (-) to a (o) and add their code letter.
   This lets other team members know that someone is working on that task.
   
3. You can only be working on one task at a time.
   
4. Once a task is completed, change the (o) to a (+) symbol. Leave your
   code letter with that task, and select another task to work on.
   
5. Not all tasks take the same amount of effort and time.  It is usually
   a good idea to work on easy tasks first and better understand the problem
   before tackling harder and more time consuming tasks.  It is okay if 
   some members complete more tasks than others.  It is okay if more 
   than one member is working on a specific task.
   
6. It is okay to start a task by identifying sub-tasks to be completed.
   Anyone can work on any subtask (not just the person who identified
   the sub task).

- Task 0: Each team member must carefully read the assignment and put
  some notes together regarding how they might approach the work 
  required for this programming assignment.  Plan to meet in person
  to discuss how you can best complete this assignment.  Do you want 
  to work in smaller groups on specific tasks?
     
o Task 1: Assign Code Letters for each Team Member

  Each team member is assigned a code letter.
  It can be the first letter of your name or any other unique letter.
  Change - to + when all members have selected a code letter and 
  added their code letter and name to this table.
  
  Complete this table:
  Code letter = Student name
  ---------------------------
            b = Bryan Watson
            z = Zexing Li
              =
              =
              =
              =
              =
              
+zb Task 2: Define the JobList class so that it implements the ListADT
  as described in p0.  List sub-tasks here.
  
    +b Create an Eclipse project for p2
    +b Download provided files, need these for sure:
      +b ListADT interface
      +b Listnode class
      +b Job class
    +b Add p2 files to your p2 project
    +b make sure that all classes and interfaces are in the default package
    +z Create a new class named JobList and add stub methods for
      all required methods of the ListADT
    +z Add declaration to "implements ListADT<Job>" to this class
    +z implement each method
       +z add(item)
       +z add(pos,item)
       +z remove(pos)
       +z contains(item)
       +z get(pos)
       +z isEmpty()
       +z size()
       +z iterator()
    +b Debugging
       
+zb Task 3: Write a Test_JobList class 
  This can be written before Task 2 is finished.
  Just write test methods that will pass when JobList is finished
  +z add a main method
  +z add a test to create a JobList
  +z test add(item) method
  +z test add(pos,item) method
  +b test remove(pos) method
  +b test contains(item) method
  +b test get(pos) method
  +b test isEmpty() method
  +b test size() method
  +b test iterator() method
  
+zb Task 4: Write a JobListIterator class
  Make sure that it is implemented as described in the assignment.
  +z add a constructor 
  +z hasNext()
  +z next()
  +b debugging
  
+b Task 5: Add a test to your Test_JobList class to test that the 
  JobList can return an iterator and that the JobListIterator
  works as expected.
  
ob Task 6: Write the Scoreboard class so that it implements all
  required operations of the ScoreboardADT. Review the Game class
  to see how the Scoreboard class is being used.
  
- Task 7: Complete the Game class implementation by completing the
  TODO tags.
  
- Task 8: Re-read the assignment and map out the actions that must
  happen in the GameApp (main) class.  There is much to do here and
  it may be much more convenient to write methods and call them 
  from the main method.
  
- Task 9: Implement the GameApp class incrementally.  
  Compile and run after each of these items
  - main: get the command line arguments (use the getIntegerInput method)
  - Add the Welcome message as output
  - main: construct a Game instance with the command line values
    - Try calling Game methods to see if Game was constructed
      and initialized correctly.
      
- Task 10: Define a main_menu_loop() method: 
  Put code for one iteration of game play
  - Get the outputs to display in the right order
  - Add a call to this method from the main method
  - Get input value and echo to screen
  - output the job list

- ADD MORE SUB-TASKS TO ANY OF THE ABOVE TASKS

- ADD MORE TASKS AS YOU IDENTIFY WORK THAT MUST BE DONE

- DON'T FORGET TO SUBMIT EARLY AND OFTEN SO THAT THERE 
  IS NO RISK OF MISSING THE SUBMISSION DEADLINE.
    
*****************************************************************/