This checklist is provided to assist you in understanding the system integration issues of your project. If you cannot answer a question affirmatively, you should carefully examine the situation and take appropriate action.
q 1. Have you implemented systems engineering as an integrated life cycle effort?
q 2. Do your test plans include and support integration efforts?
q 3. Does your development plan allocate adequate time and resources for system integration efforts, including rework time?
q 4. Are the interfaces between components, assemblies, subsystems, and systems defined in adequate detail?
q 5. Will hardware be available for testing software during integration?
q 6. Is there a contingency plan if the schedule slips if and the integration schedule is compressed?
q 7. Are all elements of the system included in the integration plan?
q 8. Is all documentation current and available for reference?
q 9. Is there an efficient rework cycle in place to fix problems found during integration testing?
q 10. Are “fixed” modules or components integrated and retested at all levels of integration up to the level where the problem was found?
q 11. Is the people element (operators, maintainers, logisticians, trainers, etc.) being prepared to work with the system when it is deployed?
q 12. Is the support systems element (logistics, maintenance, training, etc.) being prepared to support the new system when it is deployed?
q 13. Are you following an iterative, progressive integration process?
q 14. Are experienced integrators involved with the integration?
q 15. Are area/subject matter experts involved with the integration?
q 16. Is adequate time being allowed for integration, testing, rework, reintegration, and retesting?
q 17. Are all necessary resources being made available for integration?
q 18. Is adequate testing being performed on integrated units (assemblies, subsystems, elements, system) to ensure that there are no surprises during acceptance testing?
q 19. Are you updating documentation during rework?
q 20. Are integration and system test errors being traced back to requirements and design? And if so, are the requirements and design being updated?
