Difference between revisions of "Operational Scenario (glossary)"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "<center>'''SEBoK v. 2.6, released 13 May 2022'''</center>" to "<center>'''SEBoK v. 2.6, released 20 May 2022'''</center>")
 
(19 intermediate revisions by 5 users not shown)
Line 1: Line 1:
''<blockquote>(1) A set of actions or functions representing the dynamic of exchanges between the functions allowing the system to achieve a mission or a service. </blockquote>''
+
''<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) stories which describe the expected utilization of the future system in terms of actions.</blockquote>''
+
''<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>
  
====Source====
+
''<blockquote>(3) Stories which describe the expected utilization of the future system in terms of actions.'' (Created for SEBoK)</blockquote>
This definition was developed for the SEBoK version 0.5. ''Note to reviewers '': If you are aware of a more authoritative definition, please provide this information in your review.  
+
 
 +
===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===
There is currently no discussion for this term.  This will be completed for SEBoK version 1.0.
+
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.6, released 20 May 2022'''</center>
{{5comments}}
 

Latest revision as of 19:28, 19 May 2022

(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.

SEBoK v. 2.6, released 20 May 2022