• DocumentCode
    1873152
  • Title

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

  • Author

    Fairley, Richard E. ; Thayer, Richard H. ; Bjorke, Per

  • Author_Institution
    SEMA Inc., Drexel Univ., Philadelphia, PA, USA
  • fYear
    1994
  • fDate
    18-22 Apr 1994
  • Firstpage
    40
  • Lastpage
    47
  • Abstract
    The authors describe the role of a “concept of operations” (ConOps) document in the specification and development of a software-intensive system. They also describe the process of developing a ConOps, its uses and benefits, who should develop it, and when it should be developed. The ConOps described, is compared to other forms of operational concept documents. A recommended format for the ConOps document is presented
  • Keywords
    formal specification; software engineering; system documentation; ConOps document; concept of operations; conceptual analysis; operational concept documents; operational requirements; software engineering; software requirements; software-intensive system; specification; technical specifications; Application software; Bridges; Information analysis; Manuals; Prototypes; Scheduling; Software engineering; Software prototyping; User interfaces;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Requirements Engineering, 1994., Proceedings of the First International Conference on
  • Conference_Location
    Colorado Springs, CO
  • Print_ISBN
    0-8186-5480-5
  • Type

    conf

  • DOI
    10.1109/ICRE.1994.292405
  • Filename
    292405