ABSTRACT
Before automated information fusion (IF) can be quali ed as a technical solution to a problem, we must consider a de ned need, function, and capability. The need typically includes data gathering and exploitation to augment the current workload such as a physician desiring assistance in detecting a tumor; an economist looking for in ationary trends; or a military commander trying to nd, locate, and track targets. “Information needs” can only be designated by these users who will utilize the information fusion system (IFS) developments.1 Once the needs have been de ned, decomposing the needs into actionable
functions requires data availability and observability. Finally, transforming the data into information to satisfy a need has to become a realizable capability. All too often, IF engineers gather user information needs and start building a system without developing in the interaction, the guidance, or the planned role of the users.
