Difference between revisions of "Operational Concept (glossary)"
Jump to navigation
Jump to search
Afaisandier (talk | contribs) |
Afaisandier (talk | contribs) |
||
Line 1: | Line 1: | ||
<blockquote>''Operational Concept: verbal and graphic statement of an organization’s assumptions or intent in regard to an operation or series of operations of a system or a related set of systems. [ANSI/AIAA G-043-1992]'' (citation)</blockquote> | <blockquote>''Operational Concept: verbal and graphic statement of an organization’s assumptions or intent in regard to an operation or series of operations of a system or a related set of systems. [ANSI/AIAA G-043-1992]'' (citation)</blockquote> | ||
− | Note: The operational concept is designed to give an overall picture of the operations using one or more specific systems, or set of related systems, in the organization’s operational environment from the users’ and operators’ perspective. See also [[Concept of Operations(ConOps)(glossary)|concept of operations]]. | + | Note: The operational concept is designed to give an overall picture of the operations using one or more specific systems, or set of related systems, in the organization’s operational environment from the users’ and operators’ perspective. See also [[Concept of Operations (ConOps) (glossary)|concept of operations]]. |
===Source=== | ===Source=== |
Revision as of 07:47, 26 July 2012
Operational Concept: verbal and graphic statement of an organization’s assumptions or intent in regard to an operation or series of operations of a system or a related set of systems. [ANSI/AIAA G-043-1992] (citation)
Note: The operational concept is designed to give an overall picture of the operations using one or more specific systems, or set of related systems, in the organization’s operational environment from the users’ and operators’ perspective. See also concept of operations.
Source
ISO/IEC 29148, 2011. Systems and software engineering - Life cycle processes - Requirements engineering
Discussion
DISCUSSION