SBC Architecture

Structure-Behavior Coalescence (SBC) architecture is the system architecture that demands the structure and behavior views must be integrated and coalesced. The core concept of SBC architecture is: “Architecture = Structure + Behavior.”
A system comprises multiple views such as planning, , design, implementation, deployment, structure, behavior, input data, and output data views. A system architecture is an integrated, holistic, united, coordinated, coherent, and coalescence system model of multiple views in which (A) a system comprises many components; (B) multiple views are derived from the interactions between these components; (C) multiple views are all contained in this model.
Since the structure and behavior views are the two most prominent ones among multiple views, integrating the structure and behavior views is the most appropriate method for integrating multiple views of a system. In other words, structure-behavior coalescence (SBC) results in integrating multiple views of a system.
SBC Architecture includes a) SBC architecture description language (SBC-ADL) and b) SBC architecture framework (SBC-AF).
Overview
A system comprises multiple views such as planning, requirement (analysis), design, implementation, deployment, structure, behavior, input data, and output data views. A system model is required to represent all these multiple views. The system model describes and represents the system multiple views possibly adopting two different approaches. The first one is the non-architectural approach and the second one is the architectural approach. The non-architectural approach respectively picks a model for each view. The architectural approach, also known as system architecture, instead of picking many heterogeneous and unrelated models, will use only one single coalescence model.
In general, multiple view coalescence (MVC) architecture is a synonym for system architecture. Since the structure and behavior views are the two most prominent ones among multiple views, integrating the structure and behavior views is the most appropriate method for integrating multiple views of a system. In other words, structure-behavior coalescence (SBC) results in the coalescence of multiple views. Therefore, SBC architecture is also a synonym for system architecture.
History
SBC architecture was created during the late-1980s by Dr. William S. Chao. The initial idea of SBC architecture comes from the calculus of communicating systems (CCS) and developed by Robin Milner.
Robin Milner used the CCS and <math>\pi</math>-calculus, mainly, for analyzing theoretical concurrency problems. Nevertheless, both CCS and <math>\pi</math>-calculus were magnificently appealing to Dr. Chao because of their superior ability to integrate the structure and behavior views of a system.
Since 1989, the year that the CCS book was published, Dr. William S. Chao has been working on a structure-behavior coalescence model which later successfully leads to the SBC architecture.
Topics in SBC architecture
Topics in SBC Architecture include a) SBC architecture description language (SBC-ADL) and b) SBC architecture framework (SBC-AF).
SBC Architecture Description Language (SBC-ADL)
SBC Architecture Description Language consists of six fundamental diagrams. These diagrams are: a) architecture hierarchy diagram, b) framework diagram, c) component operation diagram, d) component connection diagram, e) structure-behavior coalescence diagram, and f) interaction flow diagram.
Architecture Hierarchy Diagram
The architecture hierarchy diagram (AHD) enables architects to examine the multi-level decomposition and composition of a system. AHD is the first fundamental diagram to achieve structure-behavior coalescence.
Framework Diagram
The framework diagram (FD) enables architects to examine the multi-layer (sometimes referred to as multi-tier) decomposition and composition of a system. FD is the second fundamental diagram to achieve structure-behavior coalescence.
Component Operation Diagram
For a system, architects use the component operation diagram (COD) to display all components' operations. COD is the third fundamental diagram to achieve structure-behavior coalescence.
Component Connection Diagram
A component connection diagram (CCD) is utilized to describe how all components and actors are connected within a system. CCD is the fourth fundamental diagram to achieve structure-behavior coalescence.
Structure-Behavior Coalescence Diagram
The structure-behavior coalescence diagram (SBCD) enables architects to observe the integration of system structure and system behavior simultaneously. SBCD is the fifth fundamental diagram to achieve structure-behavior coalescence.
Interaction Flow Diagram
An interaction flow diagram (IFD) is utilized to describe each individual behavior of the overall system behavior. IFD is the sixth fundamental diagram to achieve structure-behavior coalescence.
SBC Architecture Framework (SBC-AF)
SBC Architecture Framework consists of: a) Two-Level SBC-AF for System Analysis and Design, and b) Multi-Level SBC-AF for General Purpose.
Two-Level SBC-AF for System Analysis and Design
In the two-level SBC-AF for system analysis and design, we categorize the system architecture into the following: a) owner’s architecture and b) designer’s architecture.
The owner’s architecture includes the owner’s six SBC fundamental diagrams. The designer’s architecture includes the designer’s six SBC fundamental diagrams.
Multi-Level SBC-AF for General Purpose
In the multi-level SBC-AF for general purpose, we categorize the system architecture into the following: a) planner’s architecture, b) owner’s architecture, c) designer’s architecture, and d) builder’s architecture.
The planner’s architecture includes the planner’s six SBC fundamental diagrams. The owner’s architecture includes the owner’s six SBC fundamental diagrams. The designer’s architecture includes the designer’s six SBC fundamental diagrams. The builder’s architecture includes the builder’s six SBC fundamental diagrams.
Applications of SBC architecture
Applications of SBC architecture include a) SBC hardware architecture, b) SBC software architecture, c) SBC enterprise architecture, d) SBC knowledge architecture, and e) SBC thinking architecture.
SBC Hardware Architecture
When applying SBC architecture to a hardware system, SBC architecture becomes the SBC hardware architecture.
SBC Software Architecture
When applying SBC architecture to a software system, SBC architecture becomes the SBC software architecture.
SBC Enterprise Architecture
When applying SBC architecture to an enterprise system, SBC architecture becomes the SBC enterprise architecture.
SBC Knowledge Architecture
When applying SBC architecture to a knowledge system, SBC architecture becomes the SBC knowledge architecture.
SBC Thinking Architecture
When applying SBC architecture to a thinking system, SBC architecture becomes the SBC thinking architecture.

Main Menu

See Also

Main Menu