Difference between revisions of "Concept of Operations (ConOps) (glossary)"
Jump to navigation
Jump to search
m (moved Concept of Operations (ConOps) to concept of operations (conops) : Changed to align with new glossary article formatting.) |
(→Source) |
||
| Line 4: | Line 4: | ||
====Source==== | ====Source==== | ||
| − | + | Fairley, Richard and Richard Thayer. 1997. The concept of operations: The bridge from operational requirements to technical specifications. ''Annals of Software Engineering.'' 3 (1):417-432. | |
===Discussion=== | ===Discussion=== | ||
Revision as of 12:43, 7 September 2011
(1) The purpose, mission and main objectives of the potential future system (solution). The definition of these elements is the starting point to elicit the set of stakeholders' requirements.
(2) A general way or approach or strategy of operation/utilization. It represents the basic option of how will be used the system in operation.
Source
Fairley, Richard and Richard Thayer. 1997. The concept of operations: The bridge from operational requirements to technical specifications. Annals of Software Engineering. 3 (1):417-432.
Discussion
Discussion as to why this is the "consensus" definition for the SEBoK.