Integration Schedule Template

An important tool for scheduling is the Integration Schedule. It is a table which shows every module to be developed during the current stage and the order that modules will be implemented and integrated into the build.  This schedule requires very careful planning and is crucial to getting your product completed on time.  This table is a central plannning & tracking document and everyone will frequently refer to it. It must be kept accurate and current! It is the Implementation Manager's job to update it and publicize it daily.
 
 
Module Name Package Req # Developer
 Unit Test
Written		 Unit Code
Written
 Unit
Review 		Unit Test
Committed
 Unit Code
Compiles
Unit Tests
Pass 		Unit Code
Integrated
Est 
LOC		 Actual
LOC
       


         

Field Descriptions:

Module: The name of the module, such as "Employee.AddSkill()"
Package: The name of the java package the module is in.
Req #: The reference number of the requirement from the specification that this module is needed for. If you didn't number your requirements, then you need to invent some other cross-referencing mechanism. 
Developer: Name of person responsible for the module.
Unit Code Written: The planned date a module is written.
Unit Test Written: The planned date a module unit test (isolation test) scaffolding is implemented.
Unit Review: The planned date and time of the unit code and unit test review or inspection.
Unit Test Committed:  After unit test passes review it should be committed to the repository so the testers can create an integration test from it.
Unit Code Compiles, Unit Test Passes: The planned date the compiled module passes all the unit tests.
and JUnit Submitted: The planned date the unit tested module (and associated unit test) is to be submitted for integration with the build. (That means committed to CVS).
Unit Code Integrated: The date the unit is successfully integrated into the repository.  (The build compiles and passes the Smoke Test). The integration is performed during scheduled lab time using the integration lab procedure.
LOC Est. and Actual: Estimated LOC and Actual LOC for the module. 

Note: The plan initially contains planned dates.  When the task is completed the actual date should be noted below the planned date, as in the following example.
 
Unit Test
Committed
4/21/04 1100
4/22/04 1700

Example student integration schedule

Other potential fields

Consider adding other fields that may be appropriate for your project, such as:
Consider using color coding or other visual indicator to identify integration "increments" or "steps."

Document History
3/31/09 JD Changed name from "plan" to "schedule".
2/19/09 JD Made all fields required.
1/4/09  JD  Revised entries in plan to reflect current integration strategy.
4/26/04  JD  Clarified "planned" vs "actual" dates.
2/20/04  JD  Added a few minor clarifying comments to field descriptions.