Representing Navy tactical computer system knowledge for reengineering and integration

This article describes an ongoing project in representing knowledge about Navy tactical computer systems. The primary concern is for their continuing evolution and/or integration with other tactical systems. Following an introduction to this class of application and a review of how the Naval Surface Warfare Center is addressing the issue of extending the investment in these systems, the software process is examined and two alternative, incompatible paradigms are presented. The latter, which relies on the use of software knowledge, is described briefly, and an environment that implements this paradigm is presented as a proof of concept. Because the transfer of this paradigm to the desired Navy applications will not be completed in the near future, the article concludes with the presentation of a general framework for classifying Navy reengineering projects that should improve assessment and also aid in the building of a knowledge base to support the improved process model.Mr. Blum's work was supported in part by the U.S. Navy, Space and Naval Warfare Systems Command (SPAWAR) under contract N00039-89-C-0001, task VMAR9 with the Office of Naval Research (ONR) and the Naval Surface Warfare Center (NAVSWC).Ms. Moore's current affiliation is with the Defense Information Systems Agency, Arlington, VA 22204-2199. The opinions expressed in this paper do not necessarily reflect the views of the Defense Information Systems Agency.     

Integration issues elucidated in large-scale information systems development

This article explores some basic issues in system integration by examining the integration process with information systems. The article begins with a discussion of the domain of interest. Terms are defined, the software process is reviewed, and two system categories are established. It is shown that software is materially different from hardware. Moreover, these differences present opportunities for reducing the integration effort. Several methods that take advantage of software's special characteristics are identified, and a case study of one environment provides some empirical evidence that reveal the benefits that may follow. The article concludes with some observations regarding the transfer of the lessons learned with information systems to other application domains-both hardware and software.This work was supported in part by the U.S. Navy, Space and Naval Warfare Systems Command (SPAWAR) under contract N00039-89-C-001, task VMAR9 with the Office of Naval Research (ONR).