Difference between revisions of "Behavioral Architecture (glossary)"
Afaisandier (talk | contribs) |
Afaisandier (talk | contribs) |
||
| 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.'' | + | <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.'' </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> | ||
| Line 5: | Line 5: | ||
====Source(s)==== | ====Source(s)==== | ||
| − | + | See discussion below. | |
| − | |||
===Discussion=== | ===Discussion=== | ||
| − | + | Within the terms and definitions related to System Architecture, the present SEBoK tries to fit the real practices and to provide some consistency between those terms. | |
| + | Definition (1) comes from ISO/IEC/IEEE 24748 - 4 (past IEEE 1220, ISO/IEC 26702) as functional architecture. But in reality the functional architecture emphasizes more on transformations performed rather than the sequencing of their executions. See definition of [[Functional Architecture (glossary) |functional architecture (glossary)]]. | ||
| − | + | Definition (2) is a good suggestion to represent a behavioral architecture, because a scenario of functions chains the execution of functions taking into account synchronization between functions and arrival of triggers. | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
Revision as of 15:47, 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.
(2) A behavioral architecture can be described as a set of inter-related scenarios.
Source(s)
See discussion below.
Discussion
Within the terms and definitions related to System Architecture, the present SEBoK tries to fit the real practices and to provide some consistency between those terms. Definition (1) comes from ISO/IEC/IEEE 24748 - 4 (past IEEE 1220, ISO/IEC 26702) as functional architecture. But in reality the functional architecture emphasizes more on transformations performed rather than the sequencing of their executions. See definition of functional architecture .
Definition (2) is a good suggestion to represent a behavioral architecture, because a scenario of functions chains the execution of functions taking into account synchronization between functions and arrival of triggers.