Summary Checklist

  • Documenting behavior adds semantic detail to elements and their interactions that have time-related characteristics. Behavioral models add information that reveals ordering of interactions among the elements, opportunities for concurrency, and time dependencies of interactions, such as at a specific time or after a period of time.
  • Behavior documented in the element catalog of a view and in interface specifications can be used to fill in the design background section, which includes results of analysis.
  • At a minimum, the stimulation of actions and transfer of information should be modelled from one element to another.
  • Constraints on the interaction between elements in the form of synchronous or asynchronous communication should be documented. Document any ordering constraints on actions or interactions. Document a clock if your system depends on time.
  • Most behavioral languages include representations of stimulus and activity, ordering of interactions, and structural elements with some relationships to which the behavior maps.
  • Trace-oriented models consist of sequences of activities or interactions that describe the system's response to a specific stimulus when in a specific state. They document the trace of activities through a system described in terms of its structural elements and their interactions. Use cases, use case maps, sequence diagrams, collaboration diagrams, and message sequence charts are trace-oriented modeling languages.
  • Static models, often state based, show the complete behavior of a structural element or set of elements. Statecharts, SDL, and Z are static behavior modeling languages.

Software Architectures and Documentation

Part I. Software Architecture Viewtypes and Styles

The Module Viewtype

Styles of the Module Viewtype

The Component-and-Connector Viewtype

Styles of the Component-and-Connector Viewtype

The Allocation Viewtype and Styles

Part II. Software Architecture Documentation in Practice

Advanced Concepts

Documenting Software Interfaces

Documenting Behavior

Choosing the Views

Building the Documentation Package

Other Views and Beyond

Rationale, Background, and Design Constraints


Documenting Software Architectures(c) Views and Beyond
Documenting Software Architectures: Views and Beyond
ISBN: 0201703726
EAN: 2147483647
Year: 2005
Pages: 152 © 2008-2020.
If you may any questions please contact us: