Abstract
This paper describes the role of a Concept of Operations (ConOps) document in specification and development of a software‐intensive system. It also describes the process of developing a ConOps, its use and benefits, who should develop it, and when it should be developed. The ConOps described in this paper is compared to other forms of operational concept documents. A detailed outline for ConOps documents is provided in an appendix to the paper.
Article PDF
Similar content being viewed by others
Avoid common mistakes on your manuscript.
References
AIAA (1992), AIAA Recommended Technical Practice, Operational Concept Document (OCD), Preparation Guidelines, Software Systems Technical Committee, American Institute of Aeronautics and Astronautics (AIAA), March 1, 1992.
IEEE (1984), ANSI/IEEE Standard 830-1984: IEEE Guide for Software Requirements Specifications, The Institute of Electrical and Electronic Engineers, Inc., approved by the American National Standards Institute, July 20, 1984.
IEEE (1995), IEEE Standard for Acquirer-Supplier Agreement for Software Life Cycle Process, Version D2, The Institute of Electrical and Electronic Engineerings, Inc., March 15, 1995.
Lano, R.J. (1980), “A Structured Approach For Operational Concept Formulation (OCF),” TRW-SS-80-02, TRW Systems Engineering and Integration Division, Redondo Beach, CA, January 1980; also In Tutorial: Software Engineering Project Management, R. Thayer, Ed., Computer Society Press, 1988.
NASA (1983), Science Operations Concept, Part 1 (Final), Space Telescope Science Institute, Prepared for NASA Goddard Space Flight Center, Greenbelt, MD, May 1983.
US DoD (1985), Operational Concept Document (OCD), DI-ECRS-8×25, DoD-STD-2167, US Department of Defense, June 4, 1985.
US DoD (1988a), System/Segment Design Document (SSDD), DI-CMAN-80534, DoD-STD-2167A, US Department of Defense, February 29, 1988.
US DoD (1988b), Military Standard: Defense System Software Development, DoD-STD-2167A, US Department of Defense, February 29, 1988.
US DoD (1988c), “Functional Description (FD),” DoD Automated Information Systems (AIS) Documentation Standards, DoD-STD-7935A, US Department of Defense, October 31, 1988.
US DoD (1995), Software Development and Documentation Standard, MIL-STD-498, US Department of Defense, December 5, 1995.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Fairley, R.E., Thayer, R.H. The concept of operations: The bridge from operational requirements to technical specifications. Annals of Software Engineering 3, 417–432 (1997). https://doi.org/10.1023/A:1018985904689
Issue Date:
DOI: https://doi.org/10.1023/A:1018985904689