X Team Work Breakdown



Milestone Deliverables Name1 Name2 Name3 Name4 Name5 Name6
0 Link to related tool website AwesomeTestTool.com          
1 Section 1.x file
Section 1.5.x file 		intro-section.html
related-tool-section.html 		         
2 Section 2 files scenario-a.html
scenario-b.html (50%) 		         
3 Java Package(s)
and/or Class(es) 		package_dir
A.java
B.java (50%) 		         
4 Section 2 files
Java code
inspection test files 		Same file types
as Milestone 3 +
testing files 		         
5 Section 2 files
Java code
Testing code 		Same file types
as Milestone 3 +
testing files 		         
6 Section 2 files
Java code
Testing code 		Same file types
as Milestone 3 +
testing files 		         
7 Java code
Testing code 		Same code file types
as Milestone 3 +
testing files 		         
8 Java code
Testing code 		Same code file types
as Milestone 3 +
testing files 		         
9 Java code
Testing code 		Same code file types
as Milestone 3 +
testing files 		         
10 Java code
Testing code 		Same code file types
as Milestone 3 +
testing files 		         

The following are instructions for filling in this file; delete the instructions when done.

  1. Fill in your team name where "X" appears above.

  2. Fill in the member names where Name1 through Name6 appear, adjusting the number of names as necessary for your team size.

    The contents of this file will expand throughout the quarter, as you work on each milestone.

  3. As requirements file assignments are determined, fill in the requirements files links for each team member; these are the .html files stored in the project requirements directory. Each team member is assigned one or more requirements files, most likely more than one. If two or more team members work on the same file, the list in parentheses after the file link what percentage each member contributes. The percentages must add up to 100 for each multi-author file.

  4. As specification file assignments are determined, fill in the specification package and class links for each team member. These links to Java package directories or individual .java files, in the project specification directory. If a team member is responsible for an entire package, then only the package link is necessary. Each team member is one or more Java packages assigned one or more .rsl files, typically the parts of the specification that correspond to the parts of the requirements that each team member works on.
IMPORTANT: All entries in this table must be actual file names and defined as HTML links to the files themselves. For example, here's the entry for the Milestone 1 file named intro.html: 
<a href="../requirements/intro.html">
intro.html
</a>