Define integrated testing at each level, stating objectives, what is to be tested and verified, and by whom

Identify the element level at which independent integration and/or functional testing is to be used. For each level, specify the entity that is to design and/or execute the independent tests (e.g. another programmer, section QA, group QA, project QA, independent QA department).

Define in detail all aspects of all formal interfaces that must undergo formal integration testing (e.g. range compatibility, type compatibility, and so on).

Review project interface standards for completeness, consistency, and effectiveness. Monitor conformance. If there are no interface standards, define them, and create and implement enforcement standards

Create call graphs for all elements. Record call graph cover progress as elements are integrated.

Define integration guidelines that specify the extent to which top-down, bottom-up, and big-bang methods are to be used, in what combinations and under what circumstances.

Define ground rules for the use of stubs, versus modified real sub elements, versus unmodified real sub elements, for that part of integration that is to be dominated by top-down methods.

Assure the existence of adequate test tools and test drivers for conducting that part of integration that is to be dominated by bottom-up methods

Make the written definition of the backbone part of the specification of element-level integration and testing.