File: usersguidenode7.html

package info (click to toggle)
tcm 2.20%2BTSQD-1
links: PTS
area: main
in suites: sarge
size: 20,068 kB
ctags: 17,471
sloc: ansic: 78,531; makefile: 1,343; sh: 1,218; perl: 753; yacc: 558; lex: 260
file content (1552 lines) | stat: -rwxr-xr-x 49,123 bytes
parent folder | download | duplicates (9)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<!--Converted with LaTeX2HTML 98.1p1 release (March 2nd, 1998)
originally by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds
* revised and updated by:  Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
  Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>5. Behavior View Editors</TITLE>
<META NAME="description" CONTENT="5. Behavior View Editors">
<META NAME="keywords" CONTENT="User">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<LINK REL="STYLESHEET" HREF="User.css">
<LINK REL="next" HREF="usersguidenode8.html">
<LINK REL="previous" HREF="usersguidenode6.html">
<LINK REL="up" HREF="User.html">
<LINK REL="next" HREF="usersguidenode8.html">
</HEAD>
<BODY >
<!--Navigation Panel-->
<A NAME="tex2html927"
 HREF="usersguidenode8.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next_motif.gif"></A> 
<A NAME="tex2html923"
 HREF="User.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up_motif.gif"></A> 
<A NAME="tex2html917"
 HREF="usersguidenode6.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="previous_motif.gif"></A> 
<A NAME="tex2html925"
 HREF="usersguidenode1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents_motif.gif"></A> 
<A NAME="tex2html926"
 HREF="usersguidenode15.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index_motif.gif"></A> 
<BR>
<B> Next:</B> <A NAME="tex2html928"
 HREF="usersguidenode8.html">6. Architectural View Editors</A>
<B> Up:</B> <A NAME="tex2html924"
 HREF="User.html">Toolkit for Conceptual Modeling</A>
<B> Previous:</B> <A NAME="tex2html918"
 HREF="usersguidenode6.html">4. Data View Editors</A>
<BR>
<BR>
<!--End of Navigation Panel-->
<!--Table of Child-Links-->
<A NAME="CHILD_LINKS"><strong>Subsections</strong></A>
<UL>
<LI><A NAME="tex2html929"
 HREF="usersguidenode7.html#SECTION00710000000000000000">5.1 The State Transition Diagram Editor (TSTD)</A>
<UL>
<LI><A NAME="tex2html930"
 HREF="usersguidenode7.html#SECTION00711000000000000000">5.1.1 Nodes and Edges</A>
<LI><A NAME="tex2html931"
 HREF="usersguidenode7.html#SECTION00712000000000000000">5.1.2 States</A>
<LI><A NAME="tex2html932"
 HREF="usersguidenode7.html#SECTION00713000000000000000">5.1.3 Transitions, Events and Actions</A>
<LI><A NAME="tex2html933"
 HREF="usersguidenode7.html#SECTION00714000000000000000">5.1.4 Constraint Checking</A>
</UL>
<LI><A NAME="tex2html934"
 HREF="usersguidenode7.html#SECTION00720000000000000000">5.2 The Activity Diagram Editor (TATD)</A>
<UL>
<LI><A NAME="tex2html935"
 HREF="usersguidenode7.html#SECTION00721000000000000000">5.2.1 Nodes and Edges</A>
<LI><A NAME="tex2html936"
 HREF="usersguidenode7.html#SECTION00722000000000000000">5.2.2 States</A>
<LI><A NAME="tex2html937"
 HREF="usersguidenode7.html#SECTION00723000000000000000">5.2.3 Transitions</A>
<LI><A NAME="tex2html938"
 HREF="usersguidenode7.html#SECTION00724000000000000000">5.2.4 Constraint Checking</A>
</UL>
<LI><A NAME="tex2html939"
 HREF="usersguidenode7.html#SECTION00730000000000000000">5.3 The Process Structure Diagram Editor (TPSD)</A>
<UL>
<LI><A NAME="tex2html940"
 HREF="usersguidenode7.html#SECTION00731000000000000000">5.3.1 Nodes and Edges</A>
<LI><A NAME="tex2html941"
 HREF="usersguidenode7.html#SECTION00732000000000000000">5.3.2 The Process Tree</A>
<LI><A NAME="tex2html942"
 HREF="usersguidenode7.html#SECTION00733000000000000000">5.3.3 Constraint Checking</A>
</UL>
<LI><A NAME="tex2html943"
 HREF="usersguidenode7.html#SECTION00740000000000000000">5.4 The Recursive Process Graph Editor (TRPG)</A>
<UL>
<LI><A NAME="tex2html944"
 HREF="usersguidenode7.html#SECTION00741000000000000000">5.4.1 Nodes and Edges</A>
<LI><A NAME="tex2html945"
 HREF="usersguidenode7.html#SECTION00742000000000000000">5.4.2 Constraint Checking</A>
</UL>
<LI><A NAME="tex2html946"
 HREF="usersguidenode7.html#SECTION00750000000000000000">5.5 The Collaboration Diagram Editor (TCBD)</A>
<UL>
<LI><A NAME="tex2html947"
 HREF="usersguidenode7.html#SECTION00751000000000000000">5.5.1 Nodes and Edges</A>
<LI><A NAME="tex2html948"
 HREF="usersguidenode7.html#SECTION00752000000000000000">5.5.2 Interactions</A>
<LI><A NAME="tex2html949"
 HREF="usersguidenode7.html#SECTION00753000000000000000">5.5.3 Constraint Checking</A>
</UL>
<LI><A NAME="tex2html950"
 HREF="usersguidenode7.html#SECTION00760000000000000000">5.6 The StateChart Diagram Editor (TSCD)</A>
<UL>
<LI><A NAME="tex2html951"
 HREF="usersguidenode7.html#SECTION00761000000000000000">5.6.1 Nodes and Edges</A>
<LI><A NAME="tex2html952"
 HREF="usersguidenode7.html#SECTION00762000000000000000">5.6.2 And-states</A>
</UL></UL>
<!--End of Table of Child-Links-->
<HR>

<H1><A NAME="SECTION00700000000000000000">&#160;</A> <A NAME="BehaviorViewEditing">&#160;</A><A NAME="5297">&#160;</A>
<BR>
5. Behavior View Editors
</H1>

<P>
Behavior view editors manipulate various kind of diagrams to
represent system or object behavior.

<P>

<H1><A NAME="SECTION00710000000000000000">&#160;</A>
<A NAME="5299">&#160;</A><A NAME="5300">&#160;</A> 
<A NAME="5301">&#160;</A>
<BR>
5.1 The State Transition Diagram Editor (TSTD)
</H1>

<P>

<H2><A NAME="SECTION00711000000000000000">
5.1.1 Nodes and Edges</A>
</H2>

<P>
TSTD follows the notational convention of Mealy machines.
In short, a <B>Mealy machine</B><A NAME="5304">&#160;</A>
is a finite state machine in which each transition can have one 
or more actions. See figure&nbsp;<A HREF="usersguidenode7.html#STRepresentations">5.1</A> for the 
shapes and subjects.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="STRepresentations">&#160;</A><A NAME="5345">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.1:</STRONG>
State transition diagram nodes and edges.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1" ALIGN="CENTER">
<TR><TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/arrowbox.eps}$ -->
<IMG
 WIDTH="117" HEIGHT="86" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg102.gif"
 ALT="\includegraphics{p/arrowbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Initial state<A NAME="5318">&#160;</A><A NAME="5319">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/box.eps}$ -->
<IMG
 WIDTH="89" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg32.gif"
 ALT="\includegraphics{p/box.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>State<A NAME="5327">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/hexagon.eps}$ -->
<IMG
 WIDTH="116" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg42.gif"
 ALT="\includegraphics{p/hexagon.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Decision point<A NAME="5335">&#160;</A></TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
<TR><TD ALIGN="CENTER"><A NAME="5336">&#160;</A>
<P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/transition.eps}$ -->
<IMG
 WIDTH="84" HEIGHT="70" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg103.gif"
 ALT="\includegraphics{p/transition.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Transition<A NAME="5343">&#160;</A></TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
</TABLE></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H2><A NAME="SECTION00712000000000000000">
5.1.2 States</A>
</H2>

<P>
There are tree kinds of nodes: <B>initial states</B>, (normal)
<B>states</B> and <B>decision points</B>. 
All nodes should have mutually unique names.
Nameless states, also called <B>transitory states</B>, are not permitted.<A NAME="5354">&#160;</A> 
<B>Non-deterministic</B> state transition diagrams are permitted.

<P>
An initial state can have one or more initialization actions.
You can add an action by selecting the initial state, and click
on or near the arrow on top of the box. When an edit cursor
appears at the right side of the arrow, you can type in the actions. 
Each line of text will be considered as a separate action. If you stop 
editing, the actions will be placed at the right side of the arrow and
the texts become left aligned. The arrow will be resized to accommodate
the height of the texts and on top of the actions a horizontal separator 
line will be drawn. Only when the initial state
has actions then the separator line is drawn.
Note that these actions are in this notational convention
part of the initial state <I>node</I>, whereas the other actions (and events) 
of a diagram are as a notational convention part of an <I>edge</I>.

<P>

<H2><A NAME="SECTION00713000000000000000">&#160;</A><A NAME="5359">&#160;</A><A NAME="5360">&#160;</A><A NAME="5361">&#160;</A>
<BR>
5.1.3 Transitions, Events and Actions
</H2>
Transitions are drawn as arrows. They do not have a single editable name 
label like most of the other line or arrow types in TCM.
Instead they have a distinct event label and an arbitrary number of 
action labels. The action labels each occupy exactly one line of text; 
the event label can contain multiple lines.
The event and the actions are separated by a horizontal <B>separator 
line</B><A NAME="5363">&#160;</A>. When a transition is created, a separator 
line will also be created and it will be positioned near
where a name label would normally be positioned. When the transition 
line segment near the separator is drawn vertically, the separator is 
by default connected to the right side of that line segment. When the 
segment is drawn horizontally, the separator is by default positioned 
somewhat above the line. See figure&nbsp;<A HREF="usersguidenode7.html#DefaultSTDSeparators">5.2</A> for the 
two default positions.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="DefaultSTDSeparators">&#160;</A><A NAME="5368">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.2:</STRONG>
Default STD separator positions.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/defaultseparators.eps}$ -->
<IMG
 WIDTH="314" HEIGHT="209" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg104.gif"
 ALT="\includegraphics{p/defaultseparators.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>
If you click for editing a bit above the separator line, an 
edit cursor appears and you can enter an event string.
When you stop editing, the event string will be positioned above
the separator line and the separator line will be resized, if necessary. 

<P>
If you click for editing a bit below the separator, an edit cursor
appears there and you can enter a list of actions. Each line of text will
become a separate action. If you stop editing, the actions will become 
left aligned and, if necessary, the separator line will be resized. 
When the transition line segment is horizontal and the separator is
positioned above the segment, all labels are moved up so that they are all 
positioned above the line. See figure&nbsp;<A HREF="usersguidenode7.html#STDEventAndActions">5.3</A> for an example
diagram with actions and events.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="STDEventAndActions">&#160;</A><A NAME="5376">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.3:</STRONG>
STD with events and actions.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/stdeventactions.eps}$ -->
<IMG
 WIDTH="339" HEIGHT="841" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg105.gif"
 ALT="\includegraphics{p/stdeventactions.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>
It is possible to drag the separator line together with the 
event and action labels. There are two different sorts of 
movements possible. You are advised to experiment with this.
These movements are:
<DL COMPACT>
<DT>1.
<DD><B>Move it to another line segment</B>. You do this by selecting
the transition and click for editing on the desired transition segment. 
The separator line and the existing event and action labels are
moved to that line segment.  When you stop editing, the separator will 
remain in that line segment.
Summarizing: to move it to a different segment, empty the selection
and then double click the desired segment.
<DT>2.
<DD><B>Move within a line segment</B>. Drag with button-1
the separator or one of the labels to the desired position. The final
position is determined by the direction of the transition line segment.
<UL>
<LI>If the line segment is more or less horizontal, you can freely 
move the separator and labels from left to right. But you can only move 
the separator up and down to two predefined positions: either 
all labels are positioned entirely above the line segment or 
all labels are positioned entirely below the line segment.
<P>
<LI>If the line segment is more or less vertical, you can freely 
move the separator and labels up and down the segment, but you 
can only move the separator left and right to two predefined positions: 
either all labels are entirely positioned at the left side of 
the line segment or all labels are entirely positioned at the 
right of the line segment.
</UL></DL>
<P>
The automatic positioning of labels looks best when the segments 
are horizontal or vertical. When the transition arrow segments are 
diagonal or curved, then label
positioning still works but sometimes the result does not look
as great as figure&nbsp;<A HREF="usersguidenode7.html#STDEventAndActions">5.3</A>.

<P>

<H2><A NAME="SECTION00714000000000000000">
5.1.4 Constraint Checking</A>
</H2>

<P>
TSTD checks the following constraints that are summarized in
figure&nbsp;<A HREF="usersguidenode7.html#STConstraints">5.4</A>. 

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="STConstraints">&#160;</A><A NAME="5392">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.4:</STRONG>
Immediately checked and soft constraints on STDs.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/STconstraints.eps}$ -->
<IMG
 WIDTH="584" HEIGHT="403" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg106.gif"
 ALT="\includegraphics{p/STconstraints.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H1><A NAME="SECTION00720000000000000000">&#160;</A>
<A NAME="5397">&#160;</A><A NAME="5398">&#160;</A> 
<A NAME="5399">&#160;</A>
<BR>
5.2 The Activity Diagram Editor (TATD)
</H1>

<P>

<H2><A NAME="SECTION00721000000000000000">
5.2.1 Nodes and Edges</A>
</H2>

<P>
An activity diagram is a special case of a state diagram in which most 
states are action states or subactivity states, and most transitions are 
completion transitions. The purpose of an activity diagram is to focus on
flows driven by internal processing (as opposed to external events).
See figure&nbsp;<A HREF="usersguidenode7.html#ATRepresentations">5.5</A> for the shapes and subjects.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="ATRepresentations">&#160;</A><A NAME="5477">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.5:</STRONG>
Activity diagram nodes and edges.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1" ALIGN="CENTER">
<TR><TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/ellipsedbox.eps}$ -->
<IMG
 WIDTH="88" HEIGHT="44" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg43.gif"
 ALT="\includegraphics{p/ellipsedbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Action state<A NAME="5414">&#160;</A><A NAME="5415">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/roundedbox.eps}$ -->
<IMG
 WIDTH="89" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg38.gif"
 ALT="\includegraphics{p/roundedbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Inactive state<A NAME="5423">&#160;</A><A NAME="5424">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/solidhorizontalbar.eps}$ -->

<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Horizontal synchronization bar <A NAME="5432">&#160;</A>
<A NAME="5433">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/solidverticalbar.eps}$ -->
<IMG
 WIDTH="4" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg45.gif"
 ALT="\includegraphics{p/solidverticalbar.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Vertical synchronization bar <A NAME="5441">&#160;</A>
<A NAME="5442">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/blackdot.eps}$ -->
<IMG
 WIDTH="10" HEIGHT="10" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg37.gif"
 ALT="\includegraphics{p/blackdot.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Start state<A NAME="5450">&#160;</A><A NAME="5451">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/blackdotellipse.eps}$ -->
<IMG
 WIDTH="24" HEIGHT="24" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg44.gif"
 ALT="\includegraphics{p/blackdotellipse.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>End state<A NAME="5459">&#160;</A><A NAME="5460">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/minidiamond.eps}$ -->
<IMG
 WIDTH="20" HEIGHT="19" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg107.gif"
 ALT="\includegraphics{p/minidiamond.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Decision <A NAME="5468">&#160;</A></TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/arrow.eps}$ -->
<IMG
 WIDTH="94" HEIGHT="19" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg59.gif"
 ALT="\includegraphics{p/arrow.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Control flow<A NAME="5475">&#160;</A></TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
</TABLE></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H2><A NAME="SECTION00722000000000000000">
5.2.2 States</A>
</H2>

<P>
There are four kinds of nodes: <B>start and end states</B>, (active and wait)
<B>states</B>,  <B>decisions</B> and <B>synchronizations</B>. 
Nameless states and non-deterministic activity diagrams are not permitted.

<P>
A decision, represented by a small diamond, can be used as a 
decision point (one incoming arrow and two or more outgoing arrows), as a 
merge point (two or more incoming arrows and one outgoing arrow), 
or as a combined merge/decision point.
See figure&nbsp;<A HREF="usersguidenode7.html#ATDecisionMerge">5.6</A> for an example of decision and merge.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="ATDecisionMerge">&#160;</A><A NAME="5490">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.6:</STRONG>
Example decision and merge.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/decisionmerge.eps}$ -->
<IMG
 WIDTH="516" HEIGHT="141" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg108.gif"
 ALT="\includegraphics{p/decisionmerge.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>
Synchronizations, represented by horizontal or vertical synchronization
bars, should have one incoming and two or more outgoing control flows 
or two or more incoming flows and one outgoing flow.
Via the Update Node Shape Type option in the edit menu it is 
possible to convert between these two synchronization representations.
<A NAME="5494">&#160;</A><A NAME="5495">&#160;</A>

<P>
See figure&nbsp;<A HREF="usersguidenode7.html#ATDExample">5.7</A> for an example diagram with horizontal 
synchronization bars.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="ATDExample">&#160;</A><A NAME="5500">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.7:</STRONG>
ATD with action states, synchronization bars and a decision.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/atdexample.eps}$ -->
<IMG
 WIDTH="599" HEIGHT="645" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg109.gif"
 ALT="\includegraphics{p/atdexample.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H2><A NAME="SECTION00723000000000000000">&#160;</A><A NAME="5505">&#160;</A>
<BR>
5.2.3 Transitions
</H2>
Transitions are drawn as arrows, which have a single editable name 
label like most of the other line or arrow types in TCM.
Restrictions on transitions can be found in figure&nbsp;<A HREF="usersguidenode7.html#ATConstraints">5.8</A>. 

<P>

<H2><A NAME="SECTION00724000000000000000">
5.2.4 Constraint Checking</A>
</H2>

<P>
TATD checks the following constraints that are summarized in
figure&nbsp;<A HREF="usersguidenode7.html#ATConstraints">5.8</A>. 

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="ATConstraints">&#160;</A><A NAME="5512">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.8:</STRONG>
Immediately checked and soft constraints on ATDs.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/ATconstraints.eps}$ -->
<IMG
 WIDTH="600" HEIGHT="643" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg110.gif"
 ALT="\includegraphics{p/ATconstraints.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H1><A NAME="SECTION00730000000000000000">&#160;</A>
<A NAME="5517">&#160;</A><A NAME="5518">&#160;</A> 
<A NAME="5519">&#160;</A>
<BR>
5.3 The Process Structure Diagram Editor (TPSD)
</H1>

<P>

<H2><A NAME="SECTION00731000000000000000">&#160;</A><A NAME="5521">&#160;</A><A NAME="5522">&#160;</A>
<BR>
5.3.1 Nodes and Edges
</H2>
TPSD has just one special type of node, called Process and 
one type of edge called Empty edge (see figure&nbsp;<A HREF="usersguidenode7.html#PSRepresentations">5.9</A>). 
The process node is represented by a box. In the 
top right corner of the process node box, a process operator can be specified. 
You edit this operator by selecting the box and then click in the
top right corner. You go into edit mode then and the operator is typed in as 
a single character. See figure&nbsp;<A HREF="usersguidenode7.html#PSOperators">5.10</A> for the different operators.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="PSRepresentations">&#160;</A><A NAME="5545">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.9:</STRONG>
Process structure diagram nodes and edges.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1" ALIGN="CENTER">
<TR><TD ALIGN="CENTER">
<BR><HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/box.eps}$ -->
<IMG
 WIDTH="89" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg32.gif"
 ALT="\includegraphics{p/box.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Process<A NAME="5536">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/predefinedline.eps}$ -->
<IMG
 WIDTH="93" HEIGHT="1" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg68.gif"
 ALT="\includegraphics{p/predefinedline.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Empty edge<A NAME="5543">&#160;</A></TD>
</TR>
</TABLE></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="PSOperators">&#160;</A><A NAME="5593">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.10:</STRONG>
Process structure operators.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1" ALIGN="CENTER">
<TR><TD ALIGN="CENTER">Box</TD>
<TD ALIGN="CENTER">Operator</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=144>Description</TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/box.eps}$ -->
<IMG
 WIDTH="89" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg32.gif"
 ALT="\includegraphics{p/box.eps}">
<BR>
</DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=144>sequence, the default.</TD>
</TR>
<TR><TD ALIGN="CENTER"><A NAME="5560">&#160;</A>
<P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/iterationbox.eps}$ -->
<IMG
 WIDTH="88" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg111.gif"
 ALT="\includegraphics{p/iterationbox.eps}">
<BR>
</DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="CENTER"><code>*</code></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=144>iteration.</TD>
</TR>
<TR><TD ALIGN="CENTER"><A NAME="5568">&#160;</A>
<P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/choicebox.eps}$ -->
<IMG
 WIDTH="88" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg112.gif"
 ALT="\includegraphics{p/choicebox.eps}">
<BR>
</DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="CENTER"><code>o</code></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=144>choice.</TD>
</TR>
<TR><TD ALIGN="CENTER"><A NAME="5576">&#160;</A>
<P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/quitbox.eps}$ -->
<IMG
 WIDTH="88" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg113.gif"
 ALT="\includegraphics{p/quitbox.eps}">
<BR>
</DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="CENTER"><code>!</code></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=144>for premature termination.</TD>
</TR>
<TR><TD ALIGN="CENTER"><A NAME="5584">&#160;</A>
<P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/admitbox.eps}$ -->
<IMG
 WIDTH="88" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg114.gif"
 ALT="\includegraphics{p/admitbox.eps}">
<BR>
</DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="CENTER"><code>?</code></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=144>for premature termination.</TD>
</TR>
</TABLE></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H2><A NAME="SECTION00732000000000000000">&#160;</A><A NAME="5598">&#160;</A><A NAME="5599">&#160;</A>
<BR>
5.3.2 The Process Tree
</H2>

<P>
TPSD is a bit different from the other existing TCM diagram editors
because in TPSD the layout (representation) is 
significant for the meaning of the diagram. So TPSD 
has to make sure that there is always a one-one relationship 
between each node instance and its representing shape instance. 
Therefore, duplicate shapes cannot be made in TPSD.
During editing, TPSD enforces that the graph is a set of undirected 
trees. It has the constraint that an edge can only be added to the 
graph when the resulting graph would not contain a cycle. 
This constraint is also implemented for the tree editors 
(chapter&nbsp;<A HREF="usersguidenode10.html#TreeEditing">8</A>).

<P>
In TPSD, the highest box in the drawing area represents the 
root of the tree, which is called the <B>main root</B>.<A NAME="5602">&#160;</A><A NAME="5603">&#160;</A>
This is the process node whose representing box has the smallest y-coordinate. 
The <B>main tree</B><A NAME="5605">&#160;</A> is the tree that is connected to the main root.

<P>
Each process node has a set of children that is ordered from left to right. 
The ordering of the children is determined by the position of
the shapes in the drawing area&nbsp;<A NAME="tex2html99"
 HREF="#foot5606"><SUP>5.1</SUP></A>.

<P>
The <B>Update Sequence Labels</B><A NAME="5608">&#160;</A> commands 
in a submenu of the TPSD View menu make it possible to show the process 
sequence numbers in the lower right corners of the boxes.
The <B>show no sequence labels</B> command makes all the sequence numbers invisible.
The <B>update action sequences</B> command draws the sequence numbers of all
actions. <B>Actions</B><A NAME="5612">&#160;</A> are the leaf nodes of the tree,
excluding the ``quit'' boxes. 
See figure&nbsp;<A HREF="usersguidenode7.html#ProcessExample">5.11</A> for a PSD with numbered actions.
The <B>update process sequences</B> command draws sequence numbers in all process nodes. 
Each parent receives a sequence number that is one higher than the highest 
number amongst its children.
Note that the sequence numbers are not updated automatically when you edit the diagram.
The labels are only recalculated and updated when you perform an update 
sequence labels command again. However, when you save the PSD to file,
updating sequence labels is called implicitly.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="ProcessExample">&#160;</A><A NAME="5619">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.11:</STRONG>
Example PSD with numbered actions.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/processexample.eps}$ -->
<IMG
 WIDTH="394" HEIGHT="347" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg115.gif"
 ALT="\includegraphics{p/processexample.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H2><A NAME="SECTION00733000000000000000">
5.3.3 Constraint Checking</A>
</H2>

<P>
The Check Diagram command in the Diagram menu checks that 
the tree is a syntactically correct JSD process structure diagram.
Because of the immediately enforced constraints, Check Diagram assumes
that there are no duplicate nodes and no cycles. 
In figure&nbsp;<A HREF="usersguidenode7.html#PSConstraints">5.12</A> all immediately and soft constraints are
summarized.

<P>
Note that, if the box of a child has a smaller y-coordinate (is higher) 
than its parent, then a warning is given because that is an indication 
of a poor layout.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="PSConstraints">&#160;</A><A NAME="5627">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.12:</STRONG>
Immediately checked and soft constraints on PSDs.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/PSconstraints.eps}$ -->
<IMG
 WIDTH="468" HEIGHT="649" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg116.gif"
 ALT="\includegraphics{p/PSconstraints.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H1><A NAME="SECTION00740000000000000000">&#160;</A>
<A NAME="5632">&#160;</A><A NAME="5633">&#160;</A> 
<A NAME="5634">&#160;</A>
<A NAME="5635">&#160;</A>
<BR>
5.4 The Recursive Process Graph Editor (TRPG)
</H1>

<P>

<H2><A NAME="SECTION00741000000000000000">
5.4.1 Nodes and Edges</A>
</H2>

<P>
See figure&nbsp;<A HREF="usersguidenode7.html#RPRepresentations">5.13</A> for the TRPG shapes and subjects.
There are two node types and three node shape types. Process graph roots 
have their name label written on top of a downwards pointing arrow. 
In general the process graph roots are named after the process 
graph document, but in upper case letters. By default a process graph
is named <TT>UNTITLED</TT>. Process graph nodes have two node shape representations.
They can be small unnamed circles or larger rounded boxes which can
contain a name label. Process graph nodes are connected by event edges.
See figure&nbsp;<A HREF="usersguidenode7.html#RPGExample">5.14</A> for an example recursive process graph.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="RPRepresentations">&#160;</A><A NAME="5679">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.13:</STRONG>
Recursive process graph nodes and edges.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1" ALIGN="CENTER">
<TR><TD ALIGN="CENTER">
<BR><HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/arrowdot.eps}$ -->
<IMG
 WIDTH="18" HEIGHT="59" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg117.gif"
 ALT="\includegraphics{p/arrowdot.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Process graph root</TD>
<TD ALIGN="CENTER"><A NAME="5652">&#160;</A><A NAME="5653">&#160;</A>
<P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/dot.eps}$ -->
<IMG
 WIDTH="19" HEIGHT="18" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg118.gif"
 ALT="\includegraphics{p/dot.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Process graph node</TD>
</TR>
<TR><TD ALIGN="CENTER"><A NAME="5661">&#160;</A><A NAME="5662">&#160;</A>
<P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/rpgroundedbox.eps}$ -->
<IMG
 WIDTH="82" HEIGHT="54" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg119.gif"
 ALT="\includegraphics{p/rpgroundedbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Process graph node</TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/arrow.eps}$ -->
<IMG
 WIDTH="94" HEIGHT="19" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg59.gif"
 ALT="\includegraphics{p/arrow.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Event<A NAME="5676">&#160;</A><A NAME="5677">&#160;</A></TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
<TR><TD ALIGN="CENTER"><P></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
</TABLE></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="RPGExample">&#160;</A><A NAME="5686">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.14:</STRONG>
Example recursive process graph.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/rpgexample.eps}$ -->
<IMG
 WIDTH="445" HEIGHT="341" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg120.gif"
 ALT="\includegraphics{p/rpgexample.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H2><A NAME="SECTION00742000000000000000">
5.4.2 Constraint Checking</A>
</H2>

<P>
TRPG checks the immediately enforced and soft constraints
that are summarized in figure&nbsp;<A HREF="usersguidenode7.html#RPConstraints">5.15</A>.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="RPConstraints">&#160;</A><A NAME="5695">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.15:</STRONG>
Immediately checked and soft constraints on RPGs.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/RPconstraints.eps}$ -->
<IMG
 WIDTH="466" HEIGHT="287" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg121.gif"
 ALT="\includegraphics{p/RPconstraints.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H1><A NAME="SECTION00750000000000000000">&#160;</A>
<A NAME="5700">&#160;</A><A NAME="5701">&#160;</A> 
<A NAME="5702">&#160;</A>
<BR>
5.5 The Collaboration Diagram Editor (TCBD)
</H1>

<P>

<H2><A NAME="SECTION00751000000000000000">
5.5.1 Nodes and Edges</A>
</H2>

<P>
Collaboration diagrams describe the interactions among classes and 
associations. These interactions are modeled as exchanges of messages 
between classes through their associations.
See figure&nbsp;<A HREF="usersguidenode7.html#CBRepresentations">5.16</A> for the shapes and subjects.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="CBRepresentations">&#160;</A><A NAME="5773">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.16:</STRONG>
Collaboration diagram nodes and edges.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1" ALIGN="CENTER">
<TR><TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/stickman_class.eps}$ -->
<IMG
 WIDTH="33" HEIGHT="82" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg122.gif"
 ALT="\includegraphics{p/stickman_class.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Actor (Stickman/Class) <A NAME="5717">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/stickman_object.eps}$ -->
<IMG
 WIDTH="33" HEIGHT="84" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg123.gif"
 ALT="\includegraphics{p/stickman_object.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Actor (Stickman/Object) <A NAME="5725">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/UCactorbox.eps}$ -->
<IMG
 WIDTH="106" HEIGHT="46" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg124.gif"
 ALT="\includegraphics{p/UCactorbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Actor (ClassBox) <A NAME="5733">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/actor_objectbox.eps}$ -->
<IMG
 WIDTH="111" HEIGHT="51" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg125.gif"
 ALT="\includegraphics{p/actor_objectbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Actor (ObjectBox) <A NAME="5741">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/box.eps}$ -->
<IMG
 WIDTH="89" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg32.gif"
 ALT="\includegraphics{p/box.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Class <A NAME="5749">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/objbox.eps}$ -->
<IMG
 WIDTH="88" HEIGHT="44" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg91.gif"
 ALT="\includegraphics{p/objbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Object <A NAME="5757">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/CBclasslink.eps}$ -->
<IMG
 WIDTH="125" HEIGHT="41" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg126.gif"
 ALT="\includegraphics{p/CBclasslink.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Class link <A NAME="5764">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/CBobjectlink.eps}$ -->
<IMG
 WIDTH="125" HEIGHT="41" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg127.gif"
 ALT="\includegraphics{p/CBobjectlink.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Object link<A NAME="5771">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
</TABLE></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H2><A NAME="SECTION00752000000000000000">
5.5.2 Interactions</A>
</H2>

<P>
Interactions are drawn as any other line type in TCM.
In addition to the standard line types, interactions also have an arbitrary number 
of message labels located at the opposite side of the name area of the link.

<P>
On creation of an interaction an initial dummy message will be created, consisting of a 
default message text ("<code>edit this</code>") followed by a message arrow.
See figure&nbsp;<A HREF="usersguidenode7.html#DefaultCBDInteraction">5.17</A> for an example of a default interaction.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="DefaultCBDInteraction">&#160;</A><A NAME="5782">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.17:</STRONG>
Default interaction.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/interactionexample.eps}$ -->
<IMG
 WIDTH="301" HEIGHT="47" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg128.gif"
 ALT="\includegraphics{p/interactionexample.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>
The order of the interaction may be described with a sequence of numbers, 
usually starting with number 1.

<P>
The message text can be edited as usual. 
The message direction can be changed either by:

<P>
<UL>
<LI>clicking on it with the left-button: this will toggle the message direction.
<LI>by adding a "direction prefix" add the end of the message text :

<P>
<UL>
<LI>'<code>&gt;</code>' : Add message direction from "left shape" towards "right shape".
<LI>'<code>&lt;</code>' : Add message direction from "right shape" towards "left shape".
<LI>'<code>^</code>' : Add message direction from "upper shape" towards "down shape".
<LI>'<code>v</code>' : Add message direction from "down shape" towards "upper shape".
</UL>
<P>
In this way message directions can be added easy without having to switch 
between keyboard and mouse alternately.
E.g. adding two messages to an interaction: <BR>
<code>"1.2: create() &gt; [CR] 1.3: respond() &lt;"</code> <BR>
will result in:

<P>
<code>1.2: create() </code>  
<!-- MATH: $\rightarrow$ -->
<IMG
 WIDTH="20" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg129.gif"
 ALT="$\rightarrow$">
<BR>
<code>1.3: respond() </code> 
<!-- MATH: $\leftarrow$ -->
<IMG
 WIDTH="20" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg130.gif"
 ALT="$\leftarrow$">

<P>
</UL>
<P>

<H2><A NAME="SECTION00753000000000000000">
5.5.3 Constraint Checking</A>
</H2>

<P>
TCBD checks the immediately enforced and soft constraints
that are summarized in figure&nbsp;<A HREF="usersguidenode7.html#CBConstraints">5.18</A>.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="CBConstraints">&#160;</A><A NAME="5802">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.18:</STRONG>
Immediately checked and soft constraints on CBDs.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/CBconstraints.eps}$ -->
<IMG
 WIDTH="534" HEIGHT="109" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg131.gif"
 ALT="\includegraphics{p/CBconstraints.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H1><A NAME="SECTION00760000000000000000">&#160;</A>
<A NAME="5807">&#160;</A><A NAME="5808">&#160;</A> 
<A NAME="5809">&#160;</A>
<BR>
5.6 The StateChart Diagram Editor (TSCD)
</H1>

<P>
Statechart diagrams describe all the possible states a particular object 
can get into and how the object's state changes as a result of events 
that reach the object.

<P>
In contrast to most editors, TSCD starts in the hierarchical document mode.
To select a node, click near any visible part in the node, for example
on the inner side of the border.

<P>

<H2><A NAME="SECTION00761000000000000000">
5.6.1 Nodes and Edges</A>
</H2>

<P>
See figure&nbsp;<A HREF="usersguidenode7.html#SCRepresentations">5.19</A> for the shapes and subjects.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="SCRepresentations">&#160;</A><A NAME="5897">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.19:</STRONG>
Statechart diagram nodes and edges.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">
<TABLE CELLPADDING=3 BORDER="1" ALIGN="CENTER">
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/roundedbox.eps}$ -->
<IMG
 WIDTH="89" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg38.gif"
 ALT="\includegraphics{p/roundedbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>State<A NAME="5824">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/minidiamond.eps}$ -->
<IMG
 WIDTH="20" HEIGHT="19" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg107.gif"
 ALT="\includegraphics{p/minidiamond.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Decision pseudostate<A NAME="5832">&#160;</A><A NAME="5833">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/roundedfolderbox.eps}$ -->
<IMG
 WIDTH="224" HEIGHT="135" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg132.gif"
 ALT="\includegraphics{p/roundedfolderbox.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>And-state <A NAME="5841">&#160;</A><A NAME="5842">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/blackdot.eps}$ -->
<IMG
 WIDTH="10" HEIGHT="10" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg37.gif"
 ALT="\includegraphics{p/blackdot.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Default state<A NAME="5850">&#160;</A><A NAME="5851">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/solidhorizontalbar.eps}$ -->

<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Horizontal synchronization pseudostate <A NAME="5859">&#160;</A>
<A NAME="5860">&#160;</A> 
<A NAME="5861">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/solidverticalbar.eps}$ -->
<IMG
 WIDTH="4" HEIGHT="45" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg45.gif"
 ALT="\includegraphics{p/solidverticalbar.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Vertical synchronization pseudostate <A NAME="5869">&#160;</A>
<A NAME="5870">&#160;</A>
<A NAME="5871">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/blackdotellipse.eps}$ -->
<IMG
 WIDTH="24" HEIGHT="24" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg44.gif"
 ALT="\includegraphics{p/blackdotellipse.eps}">
<BR> </DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Final state<A NAME="5879">&#160;</A><A NAME="5880">&#160;</A></TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
<TR><TD ALIGN="CENTER"><P>
<HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/arrow.eps}$ -->
<IMG
 WIDTH="94" HEIGHT="19" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg59.gif"
 ALT="\includegraphics{p/arrow.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>Transition <A NAME="5887">&#160;</A></TD>
<TD ALIGN="CENTER">
<BR><HR><P></P> 
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/dashedemptyline.eps}$ -->
<IMG
 WIDTH="81" HEIGHT="1" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg133.gif"
 ALT="\includegraphics{p/dashedemptyline.eps}"></DIV>
<BR><HR>
<BR></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>And-line <A NAME="5894">&#160;</A><A NAME="5895">&#160;</A></TD>
</TR>
<TR><TD ALIGN="CENTER"><P></TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
<TD ALIGN="CENTER">&nbsp;</TD>
<TD ALIGN="LEFT" VALIGN="TOP" WIDTH=94>&nbsp;</TD>
</TR>
</TABLE></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>

<H2><A NAME="SECTION00762000000000000000">&#160;</A> <A NAME="5902">&#160;</A><A NAME="5903">&#160;</A>
<BR>
5.6.2 And-states
</H2>

<P>
Drawing an <I>and-</I>state requires special attention.
An <I>and-</I>state is divided into substates by dashed lines.
You can draw <I>and</I> lines using the middle mouse button,
like you would draw edges between different nodes.
TSCD includes a feature that automatically adds intermediary points to the and 
line<A NAME="tex2html109"
 HREF="#foot5907"><SUP>5.2</SUP></A>
Unfortunately, TSCD is not able to move or resize the <I>and</I> line with its 
intermediary points automatically
when you move or resize the <I>and-</I>state node.
To move an <I>and-</I>state, always also select the <I>and</I> lines.
After resizing an <I>and-</I>state,
you have to readjust the intermediary points in the <I>and</I> lines.

<P>
See figure&nbsp;<A HREF="usersguidenode7.html#SCExample">5.20</A> for an example diagram with an <I>and-</I>state.

<P>
<BR>
<DIV ALIGN="CENTER"><A NAME="SCExample">&#160;</A><A NAME="5931">&#160;</A>
<TABLE WIDTH="50%">
<CAPTION><STRONG>Figure 5.20:</STRONG>
SCD with an <I>and-</I>state and <I>and</I> line.</CAPTION>
<TR><TD>
<DIV ALIGN="CENTER">

<!-- MATH: $\includegraphics{p/statechart.eps}$ -->
<IMG
 WIDTH="519" HEIGHT="278" ALIGN="BOTTOM" BORDER="0"
 SRC="usersguideimg134.gif"
 ALT="\includegraphics{p/statechart.eps}"></DIV></TD></TR>
</TABLE>
</DIV>
<BR>
<P>
<BR><HR><H4>Footnotes</H4>
<DL>
<DT><A NAME="foot5606">... area&nbsp;</A><A NAME="foot5606"
 HREF="usersguidenode7.html#tex2html99"><SUP>5.1</SUP></A>
<DD>More precisely: the order
of the children is determined by the x-coordinates of the end points on 
the parent side of the edges between the parent and
the children. This sounds a bit complex, but this includes the common left
to right ordering with straight edges.

<DT><A NAME="foot5907">...
line</A><A NAME="foot5907"
 HREF="usersguidenode7.html#tex2html109"><SUP>5.2</SUP></A>
<DD>This
	is needed because a line from a node to itself always has to have at 
least two intermediary points.
	The intermediary points help in determining where on the border the and 
line needs to be attached.

</DL><HR>
<!--Navigation Panel-->
<A NAME="tex2html927"
 HREF="usersguidenode8.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next_motif.gif"></A> 
<A NAME="tex2html923"
 HREF="User.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up_motif.gif"></A> 
<A NAME="tex2html917"
 HREF="usersguidenode6.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="previous_motif.gif"></A> 
<A NAME="tex2html925"
 HREF="usersguidenode1.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents_motif.gif"></A> 
<A NAME="tex2html926"
 HREF="usersguidenode15.html">
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index_motif.gif"></A> 
<BR>
<B> Next:</B> <A NAME="tex2html928"
 HREF="usersguidenode8.html">6. Architectural View Editors</A>
<B> Up:</B> <A NAME="tex2html924"
 HREF="User.html">Toolkit for Conceptual Modeling</A>
<B> Previous:</B> <A NAME="tex2html918"
 HREF="usersguidenode6.html">4. Data View Editors</A>
<!--End of Navigation Panel-->
<ADDRESS>
<I>Henk van de Zandschulp</I>
<BR><I>2003-01-20</I>
</ADDRESS>
</BODY>
</HTML>