|
by Venu Kosuri
Start ý Basic
Views ý The Whole Picture ý Use
Case View ý Use Case Diagram ý Structural
View ý Domain Modeling ý Class
Diagram ý Behavioral View ý Sequence
Diagram ý Collaboration Diagram ý
FSM ý Scalability
Limitations ý Lack of Support ý State
Charts ý Activity Diagram ý Implementation
View ý Environmental View ý Sources
and PDF
BEHAVIORAL VIEW
So far, the system has been described
structurally how it implements the desired requirements. Now, the
most important concept is modeling its run behavior with each use
case, the domains that are participating, and interaction of the classes
within each domain.
For each use case, some domains involve
certain specific paths of interaction within a specific time, fulfilling
the use case requirement. This specific path of interaction is termed
a scenario. Each use case may involve more than one scenario. In modeling,
the behavior of the system involves identifying all of these scenarios.
To represent these interactions, UML provides two sets of diagrams,
sequence diagram and collaboration diagram.
PREVIOUS
NEXT
Circuit Cellar provides up-to-date information for engineers. Visit
www.circuitcellar.com for
more information and additional articles.
For subscription information, call (860) 875-2199, subscribe@circuitcellar.com
or subscribe online.
ýCircuit Cellar, the Magazine for Computer Applications. Posted with
permission. |