Difference between revisions of "Operational Scenario (glossary)"

From SEBoK
Jump to navigation Jump to search
m (Text replace - "{{5comments}}" to "")
m (Text replacement - "<center>'''SEBoK v. 2.4, released 19 May 2021'''</center>" to "<center>'''SEBoK v. 2.5, released 15 October 2021'''</center>")
(12 intermediate revisions by 3 users not shown)
Line 1: Line 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. </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>''
  
Note: Operational scenarios are used to evaluate the requirements and design of the system and to verify and validate the system.
+
''<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>(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. </blockquote>''
+
''<blockquote>(3) Stories which describe the expected utilization of the future system in terms of actions.'' (Created for SEBoK)</blockquote>
  
''<blockquote>(3) Stories which describe the expected utilization of the future system in terms of actions.</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.
  
====Source====
+
(2) and (3) These definitions were developed for the SEBoK.
(1) ISO/IEC 29148, 2011. Systems and software engineering - Life cycle processes - Requirements engineering
 
 
 
(2) The present SEBoK within Architecture and Design modeling activities.
 
 
 
(3) The present SEBoK as informal definition.
 
  
 
===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.5, released 15 October 2021'''</center>
 
 
{{DISQUS}}
 

Revision as of 03:26, 14 October 2021

(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.5, released 15 October 2021