Difference between revisions of "Behavioral Architecture (glossary)"
m (Text replace - "====Source(s)====" to "===Sources===") |
m (Text replace - "Electronical" to "Electrotechnical") |
||
| Line 4: | Line 4: | ||
===Sources=== | ===Sources=== | ||
| − | (1) ISO/IEC. 2010. Systems and Software Engineering, Part 1: Guide for Life Cycle Management. Geneva, Switzerland: International Organization for Standardization (ISO)/International | + | (1) ISO/IEC. 2010. Systems and Software Engineering, Part 1: Guide for Life Cycle Management. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 24748-1:2010. |
(2) This definition was developed for the SEBoK. | (2) This definition was developed for the SEBoK. | ||
Revision as of 15:26, 17 April 2013
(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 2010)
(2) A set of inter-related scenarios. (Created for SEBoK)
Sources
(1) ISO/IEC. 2010. Systems and Software Engineering, Part 1: Guide for Life Cycle Management. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 24748-1:2010.
(2) This definition was developed for the SEBoK.
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 modified because in the standard functional and behavioral aspects are mixed. 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.
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus