Abstract
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.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Mission Critical Computer Resources Software Support, MIL-HDBK-347, 22 May 1990.
T. Moore and K. Gibson, “The reengineering of Navy computer systems,” NAVSWC TR 90-216, September 1990, Silver Spring, MD (UNCLASSIFIED).
T. Moore, et al., “Overview of systems reengineering technology,” Second Systems Reengineering Workshop Proceedings, March 1991, NAVSWC, Silver Spring, MD, 1–8.
M.-H. Trinh and T. Moore, “Survey of CMS-2 parsers and analyzers,” NAVSWC TN 91-154, March 1991, NAVSWC, Silver Spring, MD (UNCLASSIFIED).
R. Duran, “Reengineering using a specification language base on data abstraction,” NAVSWC TR91-388, September 1991, Silver Spring, MD, (UNCLASSIFIED).
P. Naur and B. Randell (eds.),Software Engineering: Report on a conference sponsored by the NATO Science Committee, Garmish, Germany, 7th to 11th October 1968, Scientific Affairs Division, NATO, Brussels, 1969.
W.W. Royce, “Managing the development of large software systems,”IEEE WESCON, pp. 1–9, 1970.
B.W. Boehm, “Software engineering,”IEEE Transactions on Computers, vol. C-25, pp. 1226–1241, 1976.
D.N. Card with R.L. Glass,Measuring Software Design Quality, Prentice Hall: Englewood Cliffs, NJ, 1990.
H. Gomaa and D.B.H. Scott, “Prototyping as a tool in the specification of user requirements,”Proceedings, International Conference on Software Engineering pp. 333–342, 1981.
B.W. Boehm, “A spiral model of software development and enhancement,”Computer, (21, 5): 61–72, 1988.
T. Gilb,Principles of Software Engineering Management, Addison Wesley: Reading, MA, 1988.
B.I. Blum, “On the development of hardware and software,”Information and Decision Technology, (in press).
M.M. Lehman, “Life cycles and laws of program evolution,”Proceedings of the IEEE, vol. 68, pp. 1060–1076, 1980.
P. Freeman,Tutorial on Software Reusability, IEEE Computer Society Press: Washington, DC, 1987.
W. Tracz,Software Reuse—Energing Technologies, IEEE Computer Society, 1988.
R. Prieto-Diaz and G. Arango,Tutorial: Domain Analysis and Software Systems Modeling, IEEE Computer Society Press: Silver Spring, MD, 1991.
B.W. Boehm, “DARPA software strategic plan,”Proc. ISTO Software Technology Community Meeting, June 27–29, 1990.
G. Wiederhold, P. Wegner, and S. Ceri, “A paradigm for component-based programming,”Comm. ACM vol. 35, pp. 89–99, 1992.
B.I. Blum, “Integration issues elucidated in large-scale information systems development,”Journal of System Integration, vol. 1, pp. 35–53, 1991.
B.I. Blum, “Representing open requirements with a fragment-based specification,”IEEE Trans. Sys., Man, and Cyber., (in press).
B.I. Blum,TEDIUM and the Software Process, MIT Press: Cambridge, MA, 1990.
B.I. Blum, “The fourth decade of software engineering: some issues in knowledge management,”Int. J. Intelligent and Cooperative Information Systems, (in press).
J.P. Enterline, R.E. Lenhard, and B.I. Blum (eds.),A Clinical Information System for Oncology, Springer-Verlag, New York, 1989.
B.I. Blum, “Resolving the software paradox,”J. Software Maintenance, (in press).
E.J. Chikofsky and J.H. Cross II, “Reverse engineering and design recovery: a taxonomy,”Software, pp. 13–17, January 1990.
P. Zave, “The operational versus the conventional approach to software development,”Communication of the ACM, vol. 27, pp. 104–118, 1984.
B.I. Blum, “Formalism and prototyping in the software process,”Information and Decision Technologies, vol. 15, pp. 327–341, 1989.
B.I. Blum,Software Engineering: A Holistic View, Oxford University Press: New York, NY, 1992.
Author information
Authors and Affiliations
Additional information
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.
Rights and permissions
About this article
Cite this article
Blum, B.I., Moore, T. Representing Navy tactical computer system knowledge for reengineering and integration. Journal of Systems Integration 3, 331–349 (1993). https://doi.org/10.1007/BF01975519
Revised:
Issue Date:
DOI: https://doi.org/10.1007/BF01975519