The I&I "problem" must be defined before a serious attack on building the Knowledge Base can be mounted. A full definition and discussion of the I&I problem we are trying to solve must be available before a serious attempt can be made at developing Categories, Templates, and Questions. This definition and discussion will set the boundaries and some of the internal divisions of the I&I issue.
A complete and comprehensive definition with an accomplishing discussion that points out special principles and areas of consideration, known pitfalls and difficult areas, special concerns (such as security or survivability), potential gaps and shortfalls, and potential areas of duplication and commonality, will form the basis for producing the Knowledge Base. This same information is also required for analysis of interoperability and integration issues. It will be needed to find solutions to interoperability issues for the foreseeable future.
Other considerations include areas where the various architectures influence interoperability or integration. The Joint Technical Architecture is especially important, but Operational Architectures must also be investigated to determine if I&I issues can be resolved by slight potential change in design or in the culture.