Difference between revisions of "Operational Scenario (glossary)"
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023") |
|||
| (25 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
| − | ''<blockquote>(1) | + | ''<blockquote>(1) Description of an imagined sequence of events that includes the interaction of the product or service with its environment and users, as well as interaction among its product or service components. '' (ISO/IEC 2011)</blockquote>'' |
| − | ''<blockquote>(2) | + | ''<blockquote>(2) A set of actions or functions representing the dynamic of exchanges between the functions allowing the system to achieve a mission or a service.'' (Created for SEBoK)</blockquote> |
| − | + | ''<blockquote>(3) Stories which describe the expected utilization of the future system in terms of actions.'' (Created for SEBoK)</blockquote> | |
| − | + | ||
| + | ===Source=== | ||
| + | (1) ISO/IEC/IEEE. 2011. Systems and software engineering - Requirements engineering. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission/ Institute of Electrical and Electronics Engineers (IEEE), (IEC), ISO/IEC/IEEE 29148. | ||
| + | |||
| + | (2) and (3) These definitions were developed for the SEBoK. | ||
===Discussion=== | ===Discussion=== | ||
| − | + | Operational scenarios are used to evaluate the requirements and design of the system and to verify and validate the system. | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| + | |||
| + | <center>'''SEBoK v. 2.9, released 20 November 2023'''</center> | ||
Latest revision as of 22:38, 18 November 2023
(1) Description of an imagined sequence of events that includes the interaction of the product or service with its environment and users, as well as interaction among its product or service components. (ISO/IEC 2011)
(2) A set of actions or functions representing the dynamic of exchanges between the functions allowing the system to achieve a mission or a service. (Created for SEBoK)
(3) Stories which describe the expected utilization of the future system in terms of actions. (Created for SEBoK)
Source
(1) ISO/IEC/IEEE. 2011. Systems and software engineering - Requirements engineering. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission/ Institute of Electrical and Electronics Engineers (IEEE), (IEC), ISO/IEC/IEEE 29148.
(2) and (3) These definitions were developed for the SEBoK.
Discussion
Operational scenarios are used to evaluate the requirements and design of the system and to verify and validate the system.