Architects document behavior to show how an element behaves when stimulated in a particular way or to show how an ensemble of elementsup to and including the whole systemreact with one another. In an architecture documentation package, where behavior is shown depends on what exactly is being shown. For example, in a view's supporting documentation, behavior
- Has its own section in the element catalog. Here, the behavior of the element is documented.
- Can be part of an element's interface documentation. The semantics of a resource on an element's interface can include the element's externally visible behavior that occurs as a result of using the resource. Or, in the usage guide section of an interface document, behavior can be used to explain the effects of a particular usage pattern, that is, a particular sequence of resources used.
- Can be used to fill in the design background section, which includes results of analysis. Behavior is often a basis for analysis, and the behaviors that were used to analyze the system for correctness or other quality attributes can be recorded here.
In the documentation that applies beyond views, the rationale for why the architecture satisfies its requirements can include behavioral documentation as part of the architect's justification.