skip to main content
10.1145/507574.507588acmconferencesArticle/Chapter ViewAbstractPublication PagesadaConference Proceedingsconference-collections
Article

Electronic maneuvering board and dead reckoning tracer decision aid for the officer of the deck

Published:30 September 2001Publication History

ABSTRACT

The U.S. Navy currently bases the majority of our contact management decisions around a time and manning intensive paper-based Maneuvering Board (MOBOARD) process. The use of Maneuvering Boards is a perishable skill that has a steep learning curve. In order to overcome inherent human error, it is not uncommon to have up to four people simultaneously involved in solving just one maneuvering problem. Additional manning requirements are involved on many Naval Ships in order to accurately convey the information to the Officer of the Deck (OOD) and/or the Commanding Officer. When given situations where there exist multiple contacts, the current system is quickly overwhelmed and may not provide Commanding Officers and OODs a complete and accurate picture in a timely manner.

The purpose of this research is to implement a stand-alone system that will provide timely and accurate contact information for U.S. Navy Commanding Officers, OODs, and CIC watch teams. By creating a reliable, automated system in a format that is familiar to all Surface Warfare Officers we will provide the Navy with a valuable decision-making tool, while increasing ease of data exchange and reducing current redundancies and manning inefficient practices.

Our software design is diagramed using the Unified Modeling Language (UML) with the underlying purpose of implementing an Ada-based system that is neither operating system nor hardware dependent. This approach allows us to develop and implement a design for a wide range of platforms, and will ultimately result in an extremely modular and portable system.

Model-View-Controller

Additionally, we approached our project using the Model View Controller (MVC). This approach has allowed for flexibility in the current and future use of our core model. Not only does the model meet today's current needs, it is highly extensible and will meet emerging needs for many years to come.

In order to meet all of our criterion (i.e. operating system independent and hardware independent) we have implemented our project using GtkAda libraries and a GNAT compiler. Although GNAT makes it possible to link to other languages, we have avoided the use of other languages. This approach has resulted in a robust program that compiles and runs on a wide variety of platforms. The ultimate goal of our thesis is to produce an automated navigation system for the U.S. Navy that will help the Navy to meet reduced manning requirements while increasing the accuracy and reliability of its navigation and contact management systems.

The MOBOARD software takes advantage of Ada's capability to separate the system specification from its implementation. In this design, the specification is designed to represent only those features necessary for the required features. That is, designing the context clauses at the specification level, we moved them to the package body so there would be a minimum of dependency on the graphics packages and other platform-specific library units. This approach facilitates a platform-independent presentation of multiple views of the same data.

Of particular interest to some Ada practitioners will be our use of the floating-point facilities of Ada 95. We have made extensive use of the floating-point attributes as well as the generic elementary functions package. This was necessary because we are doing a lot of calculations that involve global coordinates, the movement of targets relative to a reference point, navigation calculations, prediction of position, and timing.

Ada has proven useful in this project because of its underlying language structure. This structure has allowed us to decompose the software architecture along:

1) A coherent conceptual view

2) A platform-independent module view

3) A maintainable code view

4) A platform-targeted execution view.

Each of these views evolves naturally as we progress from the UML use cases through the class and interaction diagrams, and onward to the Ada specifications.

References

  1. Riehle, Richard, D. Ada and Object Technology (August 1999).Google ScholarGoogle Scholar
  2. ACM SIG PROCEEDINGS template. http://www.acm.org/sigs/pubs/proceed/Google ScholarGoogle Scholar
  3. Feldman, M. B. and Koffman, E. B. Ada 95 Problem Solving and Program Design, 2nd Ed. Addison-Wesley Publishing Company, New York, October 1996. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. Cohen, Norman, H. Ada as a second language, 2nd Ed. McGraw-Hill Companies, New York, 1996. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. Schufeldt, H. H. USNR(Ret.) and Dunlap, G. D. Piloting and Dead Reckoning, 3rd Ed. Naval Institute Press, Annapolis, MD. 1991.Google ScholarGoogle Scholar
  6. Etter, Delores, M. Structured Fortran 77 for Engineers and Scientists, 5th Ed. Addison-Wesley Publishing Company, New York, 1997. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. Bowditch, Nathanial. American Practical Navigator---An Epitome of Navigation, Volume 1, 1984 Edition. Defense Mapping Agency Hydrographic/Topographic Center, 1984.Google ScholarGoogle Scholar
  8. Clynch, J. R. Naval Postgraduate School. Fortran Algorithm for GEODESIC GDSDIR and GDSINV from Geodesic Routines, 1999.Google ScholarGoogle Scholar
  9. Brobecker, J. and Briot, E. and Charlet, A. GtkAda Reference Manual, Version 1.2.10, Document Revision level 1.12, November 20th, 2000.Google ScholarGoogle Scholar
  10. Ada Core Technologies, Inc. GNAT User Guide, GNAT for Windows NT, GNAT GNU Ada 95 Compiler, Document Revision Level 1.316, GNAT Version 3.13p, May 5th, 2000.Google ScholarGoogle Scholar
  11. Ada Core Technologies, Inc. GNAT Reference Manual, GNAT for Windows NT, GNAT GNU Ada 95 Compiler, Document Revision Level 1.135, GNAT Version 3.13p, May 5th, 2000.Google ScholarGoogle Scholar
  12. Brukardt, R.(Editor), Ada 95 Reference Manual, Technical Corrigendum 1 (ISO/IEC 8652:1995/COR1:2000).Google ScholarGoogle Scholar

Index Terms

  1. Electronic maneuvering board and dead reckoning tracer decision aid for the officer of the deck

      Recommendations

      Comments

      Login options

      Check if you have access through your login credentials or your institution to get full access on this article.

      Sign in
      • Published in

        cover image ACM Conferences
        SIGAda '01: Proceedings of the 2001 annual ACM SIGAda international conference on Ada
        September 2001
        144 pages
        ISBN:1581133928
        DOI:10.1145/507574

        Copyright © 2001 ACM

        Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

        Publisher

        Association for Computing Machinery

        New York, NY, United States

        Publication History

        • Published: 30 September 2001

        Permissions

        Request permissions about this article.

        Request Permissions

        Check for updates

        Qualifiers

        • Article

      PDF Format

      View or Download as a PDF file.

      PDF

      eReader

      View online with eReader.

      eReader