Difference between revisions of "Concept of Operations (ConOps) (glossary)"
Jump to navigation
Jump to search
(→Source) |
|||
| Line 1: | Line 1: | ||
| − | ''<blockquote>(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. </blockquote> | + | ''<blockquote>(1) The purpose, [[Mission (glossary)|mission]] and main objectives of the potential future [[System (glossary)|system]] (solution). The definition of these [[Element (glossary)|elements]] is the starting point to elicit the set of [[Stakeholder (glossary)|stakeholders']] [[Requirement (glossary)|requirements]]. </blockquote> |
<blockquote>(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.</blockquote>'' | <blockquote>(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.</blockquote>'' | ||
====Source==== | ====Source==== | ||
| − | Fairley, Richard and Richard Thayer. 1997. The | + | 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=== | ||
| − | + | There is currently no discussion for this term. This will be completed for SEBoK version 1.0. | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
Revision as of 23:28, 16 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
There is currently no discussion for this term. This will be completed for SEBoK version 1.0.