No description available.

No description available.

Approved for public release; distribution is unlimited / The automation of software development has long been a goal of software engineering to increase efficiency of the development effort and improve the software product. This efficiency (high productivity with less software faults) results from best practices in building, managing and tes ting software projects via the use of these automated tools and processes. However, each software development tool has its own characteristics, semantics, objects, and concepts. While there have been significant results achieved by use of automated software development tools (coming mainly from the widespread increase of customers' adoption of these tools), there remains many challenging obstacles: lack of communication between the different software development tools, poor shared understanding; use of di fferent syntax and concepts between tools, limits in interoperability between tools, absence of a unifying conceptual models and ideas between tools, and redundant work and cross purposes between tools. The approach undertaken in this thesis to overcome th ese obstacles was to construct a "pilot" ontology that is extensible. We applied the Feature-Oriented Domain Analysis approach to capture the commonalities between two software development tools (Rational Software Corporation's RequisitePro, a main -stream, complex, commercial tool), and a software prototyping tool (the Software Engineering Automation tool (SEATools), a research model with tool support for developing executable software prototypes) and developed an ontology for the software development tool s using the ProtgÌ Ì -2000 System. The ontology expressed in UML, promotes interoperability and enhanced communication. / Lieutenant, Tunisian Navy

No description available.

Thesis (Ph. D.)--Lehigh University, 1999. / Includes vita. Includes bibliographical references (leaves 136-151).

Thesis (M.S. in Software Engineering) Naval Postgraduate School, June 2001. / Thesis advisor(s): Berzins, Valdis. "June 2001." Includes bibliographical references (p. 137-138). Also Available online.

published_or_final_version / Electrical and Electronic Engineering / Doctoral / Doctor of Philosophy

This thesis describes an Extensible Markup Language (XML) based analysis and comparison method that could be used to identity equivalent components of heterogeneous databases. In the Department of Defense there currently exist multiple databases required to support command and control of some portion of the battlefield force. Interoperability between forces will become crucial as the force structure continues to be reduced. This interoperability will be facilitated through the integration of these command and control databases into a singular joint database or by developing inter- communication schema to support inter-database communications. The first step in either of these alternatives is the identification of equivalent components among the multiple databases. This thesis describes how XML can be used to facilitate the process of analyzing and comparing multiple databases. Each step of the process is described in detail accompanied by explanations of the XML tools/resources required to execute the step and rationale of why the step is necessary. Detailed graphics and examples are employed to simplify and justify the step by step explanations. The JavaScript code developed as part of the research to execute the XML based analysis is included. This thesis concludes with discussions of the overall value of this XML based analysis and comparison process and of potential future work, that could be pursued to further exploit this XML analysis and comparison method. / Naval Postgraduate School author (civilian)

Approved for public release; distribution is unlimited. / The Navy is aggressively pursuing a capability for Fleet units to combine intelligence information into one common picture to allow for rapid correlation of multiple pieces of intelligence. This capability would contribute significantly to reducing the "sensor-to-shooter" timeline and significantly increase the likelihood of correctly classifying and striking a contact of interest. This capability comes in the form of a program called Joint Fires Network (JFN) and the concept was forged through several Fleet Battle Experiments (FBEs) as well as lessons learned from the Persian Gulf War. The objective of this thesis is to examine JFN within the Department of Defense's ISR architecture of the future. It will look at what is envisioned for the future of DoD's ISR systems and how well JFN will function as both a customer and provider of ISR information within a Joint Force architecture. This thesis uses the ISR Integrated Capstone Strategic Plan (ISR-ICSP) developed by the Assistant Secretary of Defense for Command, Control, Communications and Intelligence (C3I) as the foundation for what DoD's ISR architecture of the future will look like. This thesis looks at the Operational and System Level Architectures spelled out in this document and examines the Navy's stated requirements and existing programs which comprise JFN. This thesis also looks at the ISR systems which each service is planning for the future and how well JFN will share ISR information with these systems. / http://hdl.handle.net/10945/1007 / Lieutenant Commander, United States Navy

Approved for public release; distribution is unlimited / The Department of Defense (DoD) is both challenged by the quest for interoperability and capable of the bottom-up development of a solution. The predominant method for achieving interoperability is the development of an intermediate representation that provides a common integration language or data model. An example is Young's Object-Oriented Method for Interoperability (OOMI), which produces a Federation Interoperability Object Model (FIOM) for the resolution of heterogeneities in representation and view of a real-world entity. An FIOM generates a standard for interoperability by associating the non-standard, component system data models into an extensible lattice, which captures translations that resolve data modeling differences. To support the bottom-up creation of an FIOM we; (1) describe a self-similar approach to data storage that allows generic data structures to be manageable, extensible and asynchronously populated, and (2) introduce a lattice concept for facilitating efficient and scalable object inheritance relationships. We assert that DoD's acquisition environment necessitates a distributed approach to solving the interoperability challenge. We present the description of a distributed software system to facilitate the collaborative construction of an FIOM within the existing DoD structure and provide an architecture to guide the development of such a distributed collaborative environment. / Lieutenant, United States Navy