skip to main content
10.1145/800174.809780acmconferencesArticle/Chapter ViewAbstractPublication Pagesacm-national-conferenceConference Proceedingsconference-collections
Article
Free Access

Ada Requirements Methodology (ARM)

Published:01 January 1982Publication History

ABSTRACT

This paper describes and evaluates the Ada Requirements Methodology (ARM - a subset of Ada Integrated Methodology) that was developed during a study sponsored by the United States Department of Defense to evaluate design support for embedded systems. ARM combines some traditional structured analysis techniques with the Ada language to develop system requirements. The use of the implementation language (in this case Ada) during the requirements phase of system development is a departure from the concept that requirements and design methodologies should be independent of the implementation language. Reasons for using Ada as a requirements language are addressed in this paper. Additionally, the results of the first application of ARM and some ideas for further study and enhancements are provided.

References

  1. 1.Page-Jones, Meilir, The Practical Guide to Structured Systems Design, Yourdon Press, New York, NY, 1981. Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. 2.Gane, C. and Saron, T., Structured Systems Analysis, Prentice-Hall, Inc., Englewood Cliffs, NJ, 1979. Google ScholarGoogle ScholarDigital LibraryDigital Library
  3. 3.SofTech, "The TRAIDEX SADT Model" (An Extract from "Final Report: TRAIDEX Needs and Implementation Study").Google ScholarGoogle Scholar
  4. 4.SofTech, "An Introduction to SADT Structured Analysis and Design Technique", Waltham, MA, November, 1976.Google ScholarGoogle Scholar
  5. 5.Ross, Douglas T., "Structured Analysis (SA): A Language for Communicating Ideas", Waltham, MA, September 16, 1976.Google ScholarGoogle Scholar
  6. 6.Alford, Mack W., "Software Requirements Engineering Methodology at the Age of Two", IEEE, 1978.Google ScholarGoogle Scholar
  7. 7.Alford, Mack W., "Software Requirements Engineering Methodology at the Age of Four", IEEE, 1978.Google ScholarGoogle Scholar
  8. 8.Peterson, James L., Petri Net Theory and The Modeling of Systems, Prentice-Hall, Inc., Englewood Cliffs, NJ, 1981. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. 9.Liskov, B., Snyder, A., Atkinson, R., and Schaffert, C., "Abstraction Mechanisms in CLU", Communications of ACM, Volume 20, Number 8, June, 1977. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. 10.Wheeler, Thomas J., "Embedded System Design with Ada as the System Design Language", Memorandum Report presented at DoD's Ada Design Contracts Prebidders' Conference, November 20, 1980.Google ScholarGoogle Scholar
  11. 11.Yeh, Zave, Conn, Cole, "Software Requirements: A Report on the State of the Art", Abstract TR-949, October, 1980.Google ScholarGoogle Scholar
  12. 12.Wegner, Peter, Programming With Ada An Introduction By Means of Graduated Examples, Prentice-Hall, Inc., Englewood Cliffs, NJ, 1980. Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. 13.Booch, Grady, "Object-Oriented Design", ACM Ada Letters, Volume I, Number 3, March-April, 1982. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. 14.Yourdon, Edward and Constantine, Larry L., Structured Design, Yourdon Press, New York, NY, 1978.Google ScholarGoogle Scholar

Index Terms

  1. Ada Requirements Methodology (ARM)

      Recommendations

      Reviews

      Ernest G Booch

      This paper provides a description of an Ada requirements methodology that takes a system level specification and maps it into a structured requirements document as input to the design process. The authors discuss the evolution of the methodology from functional analysis methodologies (Yourdon and SADT techniques). In addition, the authors discuss the relationship of the requirements methodology to the Ada programming language, and the importance of various language features that support the methodology. The authors analyze (although not very deeply) the application of the requirements methodology to the development of a message system. The paper concludes with recommendations for further research in the methodology, particularly the application of Ada as a requirements language, considerations of military standards, continuity between design and requirements analysis, and automation of the technique. The paper is not complete enough to enable the reader to understand the details of the requirements methodology, but sufficient information is given to understand its philosophy and general flow.

      Access critical reviews of Computing literature here

      Become a reviewer for Computing Reviews.

      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
        ACM '82: Proceedings of the ACM '82 conference
        January 1982
        235 pages
        ISBN:0897910850
        DOI:10.1145/800174

        Copyright © 1982 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: 1 January 1982

        Permissions

        Request permissions about this article.

        Request Permissions

        Check for updates

        Qualifiers

        • Article
      • Article Metrics

        • Downloads (Last 12 months)7
        • Downloads (Last 6 weeks)2

        Other Metrics

      PDF Format

      View or Download as a PDF file.

      PDF

      eReader

      View online with eReader.

      eReader