UCE CASE EDITOR (UCE) -
OPERATIONS
[UBET Installation
& Setup][MSE User Guide][UCE User Guide]
This page describes user operations supported by the Use Case Editor (UCE).
On Windows 95 or NT, an icon for UCE
is placed in the UBET program group during installation. Double
clicking it will start UCE. Entries are made in the registry during installation so
that Use Case Graphs (UCG) are recognized by the operating system and are identified with
the same icon. Thus users may use Explorer to locate them and launch UCE by double
clicking them.
On Solaris 2.5, make sure your environment has been set up for UBET. Click here if you need more detail. At your prompt, type the command, uce, to start the Use Case Editor.
Users can set several preferences that help structure their environment and make working with UCE (and other parts of UBET) much easier. The two most important for UCE are the Startup Directory and Reference Directory. Taking advantage of these will greatly reduce the user's need to browse through directories to find design objects. Use the UCE menu entry File/Preferences... to set them. The first six fields: AUTHOR, EMAIL, PHONE, PROJECT, GROUP and DEPARTMENT allow the user to capture their information in order to support any sort of output. This information currently is available for the HTML export feature only, but it will be available to any output in the short term.This displays the following dialog:

| Preferences | Description |
|---|---|
| Miscelaneous fields: Author - Email - Phone - Project, etc. | Allow to capture user information that can be used in UBET outputs. Currently HTML export use the information on these fields. |
| Start Up Directory | The Start Up Directory field identifies the default start up directory for UBET. It is a convenience. If MSE or UCE is called without a file name on the command line, it starts in this directory. |
| Document Directory | The Document Directory field identifies the path to the root directory where the Microsoft Word reference documents are located.The Create or Edit Reference Tag dialog automatically opens to this directory, showing all files that have a .doc suffix. |
UCE Parameter Settings
| Setting | Description |
|---|---|
| Filename in title for printed output | Includes the file name as part of the title in printed outputs |
| Path in title for printed output | Includes the path to the file as part of the title printed outputs. See Note on filename in output file. |
| Date and time in title for printed output | Includes the date/time as part of the title printed outputs. See Note on filename in output file. |
| Use Images in Toolbar | The tool bar is displayed with images, otherwise, the tool bar buttons display only text. |
| Use Scenario Generation Defaults | This is a new preference for accepting the default parameters. It will allow the user to rapidly generate scenarios without being prompted for things like output directory and file prefix. |
| Use Match Any Label Attribute for Edges | This is a new preference that allows the users to turn on/off this feature. For more information about this feature please follow this link. |
| Generate Textual Scenario Report | The textual report provides complete information of the list of nodes in the particular UCG and the associated ITU files used to generate the scenario. There will be a textual report for each sceario file generated. The list of textual reports will also be presented along with the sceario files in the sceanrio list for easy viewing. |
| InLine Methods | The methods for mapping edge names between an upper level use case and a subgraph are supported. These are described below (Inline Methods). |
| Show unmapped lower level edge diagnostics | A message box is shown during inlining if a lower level edge does not match an upper level edge if this is checked and the user has also checked the Strict InLine method. Otherwise, these diagnostics are not shown. |
| Enable label edit on node creation | Assist with naming of nodes during graph creation. A dialog is automatically presented each time the user adds a node. The node automatically generated name is highlighted and typing overwrites it. Hitting the carriage return closes the dialog accepting what ever the user has typed. |
| Enable label edit on edge creation | Assist with naming of edges during graph creation. A dialog is automatically presented each time the user adds an edge. The edge automatically generated name is highlighted and typing overwrites it. Hitting the carriage return closes the dialog accepting what ever the user has typed. |
| Interval for auto numbering | This sets the interval for autonumbering operations. By default, this is set to one. |
The InLine Methods preference refers to the edges from the upper and lower level graph are conected while inlining subordinate graphs. While many users are satisfied with the current method of inlining subordinate graphs (Map All), the method does not match the way future enhancements will treat hierarchical graph relationships. The new methods serve as diagnostic tools that can be used to align names of edges for use in generating useful outputs such as test generation and finite state machine generation (Spin models). If the Strict preference is set, only matching upper level edges are connected. Unmatching upper level edges are not shown, but a diagnostic is produced showing broken connections. Unmatched lower level edges are left connected to the start or stop connector. If the Direct preference is set, matching edges are directly connected and unmatching upper and lower level edges are connected to the start and stop connectors. the edge binding method will be used during inlining. Otherwise, the normal method is used.
The two preferences enable automatic properties dialog for nodes and enable automatic properties dialog for edges assist with naming of nodes and edges during graph creation. When one of these is set, a dialog is automatically presented each time the user adds of of the corresponding object. The objects automatically generated name is highlighted and typing overwrites it. Hitting the carriage return closes the dialog accepting what ever the user has typed.
To change the values for these environment preferences, do:
These values are saved in the Registry for Windows 95 and in a file, $HOME/.mp, for Solaris 2.5. Solaris users can change the preference file location their preferences save in a file other than $HOME/.mp by setting the environment variable MP_ENV to point to a different file. For example:
UBET will look at the file at $MP_ENV to get and put preferences.
RETURN TO TOP
RETURN TO TOP
Use outputs are saved as Use Case Graphs (UCG) having a .ucg suffix. For purposes of backward compatibility, the suffix .poga is also supported.
RETURN TO TOP
Click File/Exit to quit UCE. If the file has been modified, a dialog will prompt the user to save before quitting.
RETURN TO TOP
UCE outputs are saved as Use Case Graphs (UCG). Use Case Graphs have a .ucg suffix, but an earlier convention using a .poga suffix is still supported and can be read and written. Users are encouraged to comply with the new convention.
RETURN TO TOP
Several UCE commands initiated from the tool bars start modes that support repeated
operations. For examples, the button
allows the user to pick a node to
highlight its incoming and outgoing edges. In this mode, the user can pick one node after
another, showing each nodes context in turn. All of these modes can be terminated by
double clicking these buttons on the Mode toolbar.
Moded operations can be terminated in one of three ways.
RETURN TO TOP
RETURN TO TOP
You can move an edge from one node to another simply by dragging one end of the edge to another node. Some moves are not allowed:
If a user moves an edge, it is first checked for scenarios following the edge and the user is warned before completing the change.
RETURN TO TOP
Links to Message Sequence Charts or UCE sub graph files are made through the properties dialog
Pointers to bookmarks in Word documents (reference tags) can be added processes and virtually all objects in MSE. Each end of a message can also have reference tags (just use the Menu button close to the vertical process bar). The tags can be entered and edited using the property dialogs. Reference tags can be added to all objects by using the menu button to selected the Properties entry. The dialog has a scroll list that holds the reference tags.
The user is warned when the create button is clicked if the file does not exist or not readable on the file system.
Note: the data has not been saved into your file. Click File/Save to save the data into the file.
To modify or delete a tag, click on the item in the Reference Tag & Reference Document list first, then click either on the Edit or Delete button. If you click Edit, the Edit Reference Tag dialog appears. Modify the information accordingly. If you click Delete, the tag item will be removed from the list.
RETURN TO TOP
UBET now supports the notion of Uses and Extends. Release 5.1 will include Uses and Extends feature for UCG files only, our next release will provide full support for both UCG and MSC files. Users can show graphically which nodes are linked to Uses or Extends files. Users can assign a "file type" to a specific file when creating or modifying the file. There are three different "file types": "USES", "EXTENDS", "NONE". The "file type" can be assign by selecting the desired value from the Edit menu. (Edit/File Type)

It will verify the type of the file to be link to.
It will 'draw' the nodes with the correspondent characteristics depending on the type of the file.
If the user changes the file link to the node, it will draw the nodes with the characteristics to the new file type. Example: if the user has a node that is link to 'login.ucg' which is of type 'USES' and opens the 'Properties'' Window to change the link file to 'login_error.ucg' which is of type "EXTENDS", it will change the node from visually looking like a uses to an extend.
It will change the filling color to white and the outline color to black if the user erases the "Node Link".
It will assign the name of the file, leaving out the extension and
adding an identifier, to the node label.
example: file name: login.ucg
file
type of login.ucg: USES
node label: USES 1: login
If user links a different node to the same
login.ucg file the node label of this other node will be: USES 2: login.
If the file has already been linked and the 'Properties' Window is closed, and the user changes the type of the file linked. The link will remain showing the previous state. For this type of changes the user should run the 'Validation Check' and then manually open and close the node property window to refresh the information. We are working on improving this action to a more automatic one.
USES
UCG files
Node Outer Border Color: PURPLE
Node Inner Color: YELLOW
Node Outer Border Thickness: 3 (broader that normal outline)
UCG files MSC files USES
Node Outer Border Color:
Node Outer Border Thickness:
Node Inner Color:
PURPLE
3 (broader than normal outline)
YELLOW
PURPLE
3 (broader than normal outline)
WHITEEXTENDS
Node Outer Border Color:
Node Outer Border Thickness:
Node Inner Color:
DARK GREEN
3 (broader than normal outline)
YELLOW
DARK GREEN
3 (broader than normal outline)
WHITE
UBET supports the notion of a note number. A note number is an
identifier associated with a node or an edge that can be used to tie externally maintained
documentation to that object. Users can maintain tables in external documents that provide
additional information about nodes or edges and use the note number showing in exported
files to tie annotation in the table to features on the drawing. Note numbers show up on
the same line as the node or edge label. They appear in front of the label within square
brackets. Once a note number is established, they show up in all graphical outputs (GIF,
encapsulated postscript, EMF, WMF, etc.). The figure to the right shows a node with the
note number N_3 preceding the node label, SetUp.
Note numbers can be created in two ways: through the edit menu or through an individual object's properties dialog. The menu numbers all objects at once, so it makes sense to use the menu if you plan to comment on every node or every edge. The properties dialog allows the user to supply a note number for an individual object. This approach is useful if the user is only going to annotate a few of the objects in the drawing.
The
menu for note numbering is under the Edit menu. Click Edit/Auto
Number.../Auto Number All Nodes to insert note numbers for all nodes. Choose Auto
Number All Edges in the same menu to number the edges. When autonumbering is
performed, the numbers for nodes begin with the string "N_" and the edges begin
with the string "E_". Note numbers are sequenced in a left to right, top to
bottom sequence.
The counter for note number sequencing can be incremented at user-specified intervals, set in the Preferences field labeled Interval for autonumbering. The default interval is 1, but the user may wish to choose something like 10, so that they get numbers allowing insertion of new notes without changing their tables (e.g., N_10, N_20, N_30, etc.).
Note numbers can be placed on individual objects. Use the Note Number: field to enter an identifier string. Note numbers are subject to the same restrictions as labels. They do not have to have the "N_" or "E_" prefix.
Similar to creation, users can edit the contents of any note number by using the
object's properties dialog, but they can also resequence any numbers they've entered. The
resequencing is applied only to objects that already have note numbers. To resequence the
currently numbered nodes, click on Edit/Auto Number.../Renumber Nodes or use the
toolbar button
. To renumber the edges, use the menu Edit/Auto Number.../Renumber Edges
or use the toolbar button
. The sequencing interval from preferences
is used to resequence and the same prefixes as in creation are used.
Note numbers can be removed one at a time by using the object's properties dialog. The user can also remove the note numbers for all nodes or all edges by using the Edit/Auto Number.../Clear Node Numbers or Edit/Auto Number.../Clear Edge Numbers respectively.
RETURN TO TOP
Users
can compare two use cases to see what differences exist between
them. This is useful if the user has made changes to a copy of some uce. Changes are
reported text form that tells what changes would have to be made to the original use case
to achieve one matching the second.
Use the Tools/UCG Difference Report... menu item to start the comparison (There is also a command-line interface to the UCG comparison program). That pops up a dialog that allows the user to identify the original use case, the current use case (prepopulated with the current files address), and a output file where the results will be placed. Use the original UCE browse button to find the original file. Set the Show All Differences if you want to see details of changes. Details include such things as note numbering changes.

The results are presented as text in a window. All objects in the report are marked as changed, added, or deleted. Added means the object did not appear in the original file. Deleted means it was found in the original file, but not in the new file (current). Since the basis for comparison is the node names, the program reports changes in node names as a delete and an add.
A comparison example is shown below. The two comparison files are shown first. The left
![]() |
![]() |
![]() |
|
RETURN TO TOP
The validation check will create a report. The report will include any inconsistency between the current data in the current graph and the data type saved of the file link to the node. Possible inconsistencies are as follow:
- uses used as subgraphs
- uses used as extends
- uses used as 'regular' msc
- extends used as uses
- extends used as subgraphs
- extends used as 'regular msc
- subgraphs used as uses
- subgraphs used as extends
- 'regular' msc used as uses
- 'regular' msc used as extends
This window requires the user to enter the file to be validated and the name of the report file to generate. The user can select which kind of files want to validate, example only validate the uses. If only uses are going to be validated then EXTENDS and SUBGRAPHS must be in the "Not In Report" window.
The results are presented in a text window at the end of the generation.
In order to open a reference tag in a Word document two things must be in place:
After the bookmark is created in the referenced document and the object has been tagged with a reference to it, the user can navigate to the document containing that tag by doing the following:
Word will be launched if it is not already running. The reference document will be loaded and opened to the specified bookmark.
RETURN TO TOP
RETURN TO TOP
A scenario is a sequence of nodes. This is shown in UCE by highlighting the nodes and intervening edges in green. The sequence can be broken (we call them fragments). A scenario can be made a permanent part of a use case by stashing it with a name. Fragmented scenarios can be stashed and repaired later. In general, scenarios are built by entering scenario mode, then clicking in sequence on a set of nodes. If there are intervening nodes between the clicked node and a fragment already underconstruction, the tool takes the shortest path. If this is not what the user desires, clicking again on the nodes removes them from the scenario. Edges coming out of the tail end of a fragment can also be used to add nodes to the list.
Here are a few tasks that one encounters during scenario editing and methods for dealing with them:
(right)
(wrong) RETURN TO TOP
NOTE: If a node that is part of a previously defined scenario is deleted, the deleted node and all the nodes following it will not be shown. If the first node participating in a scenario is deleted, then the entire scenario will not be shown.
| FIELDS | DESCRIPTIONS |
| Scenario Path | the path of nodes the scenario actually contains |
| Missing Nodes | the nodes that are missing in the graph which are part of the Scenario Path |
| Missing Edges | he edges that are missing in the graph which are part of the Scenario Path. A missing edge is described by a node pair that includes: the originating node (the node that the edge should have originated from), and the terminating node (the node the edge should be terminated on) |
Notes: The name of the current working scenario is always displayed on the lower right hand corner of the tool which is part of the status bar. Any changes you made with named scenarios are not committed until you save the Use Case Graph. Also, while you have nodes inlined (see Inlining UCE Subgraphs below), display/create/update/delete/audit of name scenarios are prohibited.
RETURN TO TOP
This operation allows a user to view a composite MSC generated from MSCs referenced in the Scenario. The resulting Message Sequence Chart is a scenario representing a single path through the graph. From release 4.0 UBET supports multilevel MSC generation which provides the ability to generate an MSC from a hierarchical scenario. As of Release 4.2, several scenarios can be generated at one time. Each MSC file represents a single path through the hierarchical UCGs. The way can achieve or avoid multiple scenarios in a single generation is described below.
The normal node property sheet will come up with an extra field (SubScenario). Click the browse on the Subscenario field to view the valid scenarios in the subgraph.

- The user can then double click on desired subscenario. This must be done for all nodes at all levels
.
RETURN TO TOP
Inlining allows user to view another UCE sub graph as part of the current graph by replacing the referencing node with the sub graph. Before you can inline a node containing a sub graph, the sub graph must contain a Start node and a Stop node to the sub graph.
In order to inline a sub graph, user must identify all the start nodes (nodes that the incoming edges of the parent node will be connected to) and terminating nodes in the sub graph. To do this:
Now that the start and stop nodes have been identified in the Sub graph and the parent node in the current graph has the sub graph file added in it's properties, you can do the following to inline the sub graph:
The sub graph is added to the current graph. Additional nodes can be inlined at the same time. Each sub graph cluster will be highlighted with a different color. If user inlines more than 10 graphs, the colors are recycled. If the mouse is placed over the sub graph's nodes, the name of the file is displayed. While a sub graph is inlined, editing is disabled. However, you can continue to do all other operations including context and path operations. To undo the inlining and return to the current graph, double click anywhere on the canvas.
The pictures below illustrates the results of inlining. The graph on the left is the original graph with 3 nodes that containing sub graphs: S4, S7 and S8. Note they are highlighted in yellow. The graph on the right shows the results of inlining S7 and S8.


The edge binding enhancement provides the users with the ability to inline subordinate graphs using methods that take into account the names of the edges in the upper and lower graph. This capability provides a useful diagnostic when trying to align edge names for the purpose of generating downstream driving outputs such as test generation and Spin and VFSM model generation. The discussion below shows how these methods work.
In the followng figure, the refer node contains a reference to the subordinate graph.
Egdes A and B in both upper and lower graphs are called as incoming edges while edges C
and D as outgoing edges. The
and
are known as start connector and stop connector for
inlining. During the inline operation, the nodes in the subordinate graph visually replace
the referencing node in the display. The following three methods are used: Map All, Strict
and Direct. The user can choose these methods
using the preference settings (see Edge
Mapping Preference Setting).
![]() |
![]() |
| Upper Level Graph | Lower Level Subgraph referenced by the Refer node |
Map All binds all the upper level incoming edges (edges going into the refer node, e.g., A and B in upper graph) to all the lower level incoming edges (those attached to the start node, e.g., A and B in sub graph) and all the upper level outgoing edges (those leaving the refer node, e.g., C and D in upper graph) with all the outgoing edges (attached to the stop node, e.g., C and Z in sub graph) of the subgraph. It does the binding by connecting the upper and lower level edges to the start and stop connectors. The first box in the figure below shows the results of inlining the "Refer" node using the Map All method.
![]() |
![]() |
![]() |
| Upper graph after inlining by Map All | Upper graph after inlining by Strict | Upper graph after inlining by Direct |
Strict binds only matching upper and lower level incoming and outgoing edges, essentially dropping unmatching upper level edges. The start and stop connectors will connect to any lower level edges that do not have matching upper level edges. If all edges match for the given connector, it will not be displayed.
The center box shows the results of inlining the "Refer" node in the previous
example. The upper level incoming edges A and B are bound with their matching lower level
incoming edges A and B. Upper level outgoing edge C is bound to the lower level outgoing
edge C. Upper level outgoing edge D is dropped because there is no matching outgoing edge
in subgraph. Note node four is now a floating node. Since lower level outgoing edge Z does
not have matching upper level outgoing edge, stop connector connects to it. As a part of
the Strict inlining, the following diagnostic was also produced.
The Direct method combines aspects of the Strict and Map All methods. It directly binds matching upper and lower level incoming and outgoing edges, but attaches all non-matching edges of both upper and sub graphs to enter and exit connectors. This basically wild-cards non-matching edges. If the user chooses to match upper and lower level edges, then connections to subgraphs are constrained and any generation activities (such as SPIN, VFSM, scenario, or test generation) generates the minimum correct connections. Users may start out and work with graphs with unmatching edges, but should try to match all upper and lower level edges as work on the use cases proceeds.
In the above illustration (right hand box) the upper level edges A, B and C directly connect to lower level nodes. Upper level outgoing edge D does not match to lower level outgoing edge Z, so both edges D and Z are attached to the stop node.
Edge Mapping Preference Settting:
RETURN TO TOP
Subgraphing is essentially the inverse of inlining. Subgraphing is the ability to select several nodes in a graph, then either view them as though they were a new graph or to actually create a new subgraph using the selected nodes. During subgraph creation takes place the following operations are performed.
Use these steps to subgraph a set of nodes.

RETURN TO TOP
After adding, deleting or moving nodes and edges, can redraw the graph:
RETURN TO TOP
To more easily see a section of a complicated graph:
To see more nodes of a large graph:
RETURN TO TOP
Note: you can be in any mode to view object attributes. The small popup resemble tool tips on Microsoft applications.
RETURN TO TOP
Printing is supported on the Solaris and PC platforms. TIP: use the new subgraph previewing capability to print a subset of complicated graphs.
It is now possible to print a drawing on Windows 95/NT directly from UCE. Two entries have been added to the file menu in support of this operation. Choosing File/Print prints the drawing directly to the user's default printer. Choosing File/Print Setup & Preview... brings up a view that allows the user to send the printout to another printer, set printer attributes, or preview the printout.
It is also possible to print a drawing on Solaris 2.5 directly from MSE. The user needs to set up the commands used to print and preview by choosing File/Print Setup... before printing for the first time. In the Print Setup dialog, do the following:
After the printing setup is completed, you can choose File/Print to print the UCE directly or choose File/Preview... to view the UCE any time.
The GIF image can be used in HTML pages and can be imported into MS Word. One can also produce at the same time a file containing a table with the list of reference tags used in the drawing that can be imported into Word. The file name has the same root as the GIF and a .csv suffix.
Generate GIF Dialog
| Option | Description |
| File name | It is the name that will be used for the generated GIF file. |
| Browse | Invokes the file browser to select the file you wish to generate the gif into. A relative path will be placed in the entry field. |
| OK Button | It makes all the changes performed at this window and closes the window. |
| Option Button | Invokes the Image Output Preferences dialog to set your output preferences. |
| Cancel Button | It cancels all the actions that were performed in this window and closes the window. |
Image Output Preferences
| Click on |
![]() |
| Click on |
| Option | Description |
| Dimensions | Allows the user to change the default WIdth and height of the GIF file. Default Width and Height have already been set to the same dimension as in the tool's canvas. The Width and Height are measured in pixels. |
| Hue | Selects either monochrome or color for the gif. |
| Orientation | Selects the output orientaion (Portrait or Landscape) |
| Show Reference Tag | If this option is set, a Reference Tag report will be generated. The Reference Tag item number [#] will be appended to the node label or edge label. |
| Apply Anti-aliasing | If the Black/White hue is selected, the Smooth option will be enabled. Click on the check box to set or unset this option. If this option is set, anti-aliasing technique will be applied to the gif which will blurr the image to make it appears to be smooth. This option can be used to remove the jaggies. |
| Set | The Set button stores the information into the user's preferences. These setting (except for the Dimension) will be reused in your next invocation of UBET. |
Several alternative export formats are supported by UCE. These are shown in File/Export dialog box as the following:

| Formats | Description |
| FrameMaker MIF | Imported format for FrameMaker |
| Postscript | Generate a Postscript file |
| Generated Test Cases | Generate Test Cases exercing all edges for the flattened use case |
| Spin Model | Generate a Promella model file for use in SPIN |
| VFSM Model | Generate VFSM model files for use in VFSM |
The GIF format can be used in HTML pages and can be imported into MS Word. One can also produce at the same time a file containing a table with the list of reference tags used in the drawing that can be imported into Word. The file name has the same root as the GIF and a .csv suffix.
RETURN TO TOP
MIF is a markup format that can be imported into FrameMaker documents or simply opened as a FrameMaker document.
RETURN TO TOP
Postscript is a format understood by many printers.
Note: to print postscript files on Windows 95, see the release notes.
Spin is a software system developed by Gerard Holzmann that supports the formal verification of distributed software. UBET generates Spin models in Promela, the native specification language used by Spin. General information about SPIN as well as stand-alone instructions for generating spin models is available.
RETURN TO TOP
Virtual Finite State Machines (VFSM) are extended finite state machines that support validation, simulation, and code generation. UBET generates the models from a use case with underlying MSCs. An individual model is generated for each process in the underlying MSCs. Information about generating VFSM from UBET including command line execution can be found in mkvfsm_readme.txt. General background information about VFSM can be found on the Virtual Finite State Machine (VFSM) Home Page (note: if you are not inside the Lucent firewall, you will not be able to access this url). To generate VFSM models from UCE:
A test case generation algorithm developed by Mihalis Yannakakis and David Lee can be used to generate test cases that exercise all choices in a hierachical Use Case. It first flattens the hierachy, then generates a set of scenarios that are then saved with the flattened graph. Because nodes must be named uniquely, the node names in the flattened graph will contain prefixes distinguishing them from each other.
The GIF and .csv formats can be imported into Microsoft Word documents. Export the drawing in GIF format. Choose the check box labeled show Reference Tags to produce a separate Word-importable file showing the reference tags. The following scenario shows how to export the files and then import them into MS Word.
TIP: Not all installations of MS Word have the ability to import .csv
files. The user may have to reinstall Word using the Custom install option to chose
the .csv filter.
WARNING: Word is not tolerant of import file anomalies. In tranfering the
.cvs file from UNIX to Windows, use binary mode in ftp. The GIF is also a binary
file. Use binary mode to transfer from UNIX to Windows in ftp. The following
scenario tells how to move the files without damage to the PC. It assumes you have
saved several drawings using the .gif and .csv suffixes and that you are using command
line ftp to move them to the PC.
RETURN TO TOP
Node context is an I/O view of a node, highlighting its incoming and outgoing edges.
RETURN TO TOP
Strongly connected components (Scc) refers to a set of nodes in which a path can be found from each node to all others in the set. To show the Node with its strongly connected components (Scc), do:
RETURN TO TOP
Similar to above, to show the Scc and all of its edges, do:
RETURN TO TOP
To show all the Sccs in the graph, do:
Note: It is easy to run out of colors if the graph contains many Sccs.
RETURN TO TOP
Root nodes are nodes from which all other nodes can be reached. Root nodes are not necessarily nodes without predecessors.:
RETURN TO TOP
To show all nodes that have no successors, do:
RETURN TO TOP