The concept of operations: The bridge from operational requirements to technical specifications

Annals of Software Engineering

Volumn 3, Issue , 1997, Pages 417-432

  Fairley, Richard E ^a   Thayer, Richard H ^b  

^a Colorado Technical University ^*  (United States)

^b California Stt Univ Sacramento   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 0031480178     PISSN: 10227091     EISSN: None     Source Type: Journal    
DOI: 10.1023/a:1018985904689     Document Type: Article

References (11)

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. NASA (1983), Science Operations Concept, Part 1 (Final), Space Telescope Science Institute, Prepared for NASA Goddard Space Flight Center, Greenbelt, MD, May 1983.
7. US DoD (1985), Operational Concept Document (OCD), DI-ECRS-8×25, DoD-STD-2167, US Department of Defense, June 4, 1985.
8. US DoD (1988a), System/Segment Design Document (SSDD), DI-CMAN-80534, DoD-STD-2167A, US Department of Defense, February 29, 1988.
9. US DoD (1988b), Military Standard: Defense System Software Development, DoD-STD-2167A, US Department of Defense, February 29, 1988.
10. US DoD (1988c), "Functional Description (FD)," DoD Automated Information Systems (AIS) Documentation Standards, DoD-STD-7935A, US Department of Defense, October 31, 1988.
11. US DoD (1995), Software Development and Documentation Standard, MIL-STD-498, US Department of Defense, December 5, 1995.