Software Engineering

12.2.3 
Behavioral analysis
Behavioral modeling and simulation support the functional analysis and design 
synthesis practices by providing a comprehensive, integrated representation of 
the software architecture (product and process architectural representations). 
Behavioral models capture the relationships among the elements of the architec-
ture that provide traceability from design elements, characteristics, and features 
back to stakeholder requirements and software specifications. Behavioral models 
should represent the software architecture via the following design representations 
or model perspectives:
1. 
Functional decomposition diagram
—a depiction of the functional hierarchy that 
captures decomposition bidirectional relationships among functional compo-
nents and units.
2. 
Operational model
—a depiction of the operational or business process repre-
sented as an integrated view of functional, data, and control flows. The opera-
tional model is a composite view of a functional flow block, data flow, and 
control flow diagrams.
3. 
Execution timeline
—a depiction of the software product or process execution 
timeline that identifies functional sequencing, data exchange durations, and 
resource utilization graphs. The operational models should provide a simulation 
capability that can automatically generate the execution timeline.
4. 
Entity-relationship diagram
—a depiction of a single element of the soft-
ware architecture and its established relationships to other elements of the 
architecture.
5. 
Interface block diagram
—a depiction of the physical interfaces an element of 
the structural configuration has with other structural elements, external systems, 
or applications.
6. 
Structural configuration diagram
—a depiction of the structural elements that 
comprise the software product structural configuration, structural assemblage, 
or component. It identifies the decomposition of the software product or a struc-
tural component into lower-level structural elements (components or units). 
(
Note:
 When viewed in a bottom-up manner, this diagram should identify the 
software integration strategy.)
7. 
Engineering assembly diagram
—a variation of the structural configuration 
diagram that identifies the structural subelements, test stubs, or drivers that are 

---