Difference between revisions of "Behavioral Architecture (glossary)"

From SEBoK
Jump to navigation Jump to search
Line 1: Line 1:
<blockquote> (1) "An arrangement of functions and their sub-functions and interfaces (internal and external) which defines the execution sequencing, conditions for control or data-flow and the performance requirements to satisfy the requirements baseline." (ISO/IEC/IEEE 24748 - 5?)</blockquote>
+
<blockquote> (1) ''An arrangement of functions and their sub-functions and interfaces (internal and external) which defines the execution sequencing, conditions for control or data-flow and the performance requirements to satisfy the requirements baseline.'' (ISO/IEC/IEEE 24748 - 5?)</blockquote>
  
 
<blockquote> (2) ''A behavioral architecture can be described as a set of inter-related scenarios.''</blockquote>
 
<blockquote> (2) ''A behavioral architecture can be described as a set of inter-related scenarios.''</blockquote>

Revision as of 15:01, 10 May 2012

(1) An arrangement of functions and their sub-functions and interfaces (internal and external) which defines the execution sequencing, conditions for control or data-flow and the performance requirements to satisfy the requirements baseline. (ISO/IEC/IEEE 24748 - 5?)

(2) A behavioral architecture can be described as a set of inter-related scenarios.


Source(s)

(1) ISO/IEEE. 24748 - 5?. Systems and Software Engineering -- xxxxxxxxxxxxxxx. Geneva, Switzerland: International Organization for Standards (ISO)/International Electronical Commission (IEC), ISO/IEC 24748 - 5?:2012.

IN PROGRESS

Discussion

This area is for the Glossary Term Owner to provide discussion on the context and uses of the term. This is not where you should provide comments. Please use the “Discussion” tab (above) to provide feedback if you are not the term owner.

Please note that if there is more than one definition, it is very important to provide information on the context of the different terms and to explain to the user why it is not possible to identify only one definition. For example, is this an emerging concept for which there is still much research to be done? Or have two different definitions emerged as the result of two different disciplines interacting with systems engineering?