UCE WINDOWS LOOK & FEEL
Setting Up Environment Preferences
Users can set several preferences that help structure their environment and make working with UCE (and other parts of UBET) much easier. Use the UCE menu entry File/Preferences...to set them. The following is an example snap shot of the Preferences window.

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.
Location PreferencesThe 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. If the user opens a file that it is not in the Start Up directory the application will remember this new location when opening the next file. {}The most important fields for UCE are the Start Up Directory and the Reference Directory. Taking advantage of these will greatly reduce the user's need to browse through directories to find files. The Startup Directory allow to define the active directory for ucg and itu files and the Reference Directory allow to specify the directory for MS-Word documents referenced from UBET object.
Clicking on Browse... for the StartUp Directory or the Reference Directory will bring up the Directory dialog. With this window the user can browse through their computer or network to select the appropriate directory.

| 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. |
Inline MethodsRETURN TO TOP
The InLine Methods preference refers how the edges from the upper and lower level graph are connected while inlining subordinate graphs.
| Inline Methods | Description |
| Map All | It draws the subgraph (including start and stop nodes) inside the graph. No connection between edges with matching names are done. |
| Strict | Only matching edges are connected to the graph. Edges that does not match are presented as a different graph (with its start and stop node) and are located next to the principal graph inside the canvas. |
| Direct | Matching edges are directly connected and unmatching upper and lower level edges are connected to the start and stop connectors. If all edges match no start or stop node appear in the graph. |
Modify Environment Preferences
To change the values for these environment preferences, do:
- Click File/Preferences..., the preferences dialog will appear
- Click in the entry field of the preference and start typing in the new values
- Check or uncheck the non-standard character check boxes
- Click Set when done changing all the preferences
- Click Cancel if the changes are not desired.
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 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.
- MP_ENV=$HOME/.toolsdir/.ubet
- export MP_ENV

GIF Generation
The GIF image can be used in HTML pages, can be imported into MS Word or any tool that support that format. 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. This file name has the same root as the GIF and a .csv suffix.
Generate GIF Dialog

| Setting | Description |
| File name | It is the name that will be used for the generated GIF file. By default the active directory will be used. |
| 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

| Options | Description |
| Font | select the desired font and font size by clicking on the scrollists of fonts and size. |
| Output Dimension | Specify the width and height of the GIF image. User is notified of
the actual physical size.
If pagination is not set and the user specified width and height is not the same as he physical size, then the drawing (including the fonts) will be scaled to fit in the user specified dimension. Click on the Use Physical Dimension checkbox to default to physical dimension. |
| Paginate | Allow the user to specify paginated GIF images. This is only available for MSC GIF output. |
| Hue | Selects either monochrome or color for the gif. |
| Orientation | Selects the output orientaion (Portrait or Landscape) |
| Annotation | Generate Reference Tag report if this option is checked. The Reference
Tag item number
[#] will be appended to the node label or edge label. |
| Smooth | 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. |
| Cancel | Dismiss this dialog. No GIF will be generated. |
| Advanced | Select maximum Java Heap Size. From time to time, the JVM might not
have enough to create
the image you have requested with the default memory allocated. This is due to large image dimension selected or the system is running a lot of other applications. When this happen, you will get an OutOfMemoryError. You can try one of several things to remedy this problem:
Enter only the integer amount (e.g. 64 for 64MB) of the
desired memory to be allowed for the JVM.
|

| Setting | Description |
| File name | It is the name that will be used for the generated MIF file. By default the active directory will be used. |
| Browse | Invokes the file browser to select the file you wish to generate the mif into. A relative path will be placed in the entry field. |
| Annotation - 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. |
| Color | Selects either monochrome or color for the mif. |
| Orientation | Selects the output orientation (Portrait or Landscape) |
| Font size | Select font size among available sizes: 8, 10 or 12 |
| OK Button | It makes all the changes performed at this window and closes the window. |
| Cancel Button | It cancels all the actions that were performed in this window and closes the window. |

| Setting | Description |
| File name | It is the name that will be used for the generated ps file. By default the active directory will be used. |
| Browse | Invokes the file browser to select the file you wish to generate the ps into. A relative path will be placed in the entry field. |
| Annotation - Show Reference Tag | Places an identifier on each label
of tagged objects and produces a separate file containing the reference
tags that can be imported into MS Word. The file is generated as
an ASCII Comma Separated File (.csv suffix) that can be directly imported
into Word as a database file using the MS Word dialog obtained to choose
the Insert/Database menu selection. This .cvs file will have the
same name as the GIF file, but with a ".cvs" suffix.
WARNING: Word is not tolerant of import file anomalies. In transferring the .cvs file from UNIX to Windows, use ASCII mode in ftp. The GIF is a binary file. Use binary mode to transfer from UNIX to Windows in ftp. |
| Color | Selects either monochrome or color for the ps. |
| Orientation | Selects the output orientation (Portrait or Landscape) |
| Font size | Select font size among available sizes: 8, 10 or 12 |
| Postscript Pagination | It allows the user to choose between a single page or paginated, when Postcript format is selected. |
| Postscript Page Size | It allows the user to choose between 8.5"X11" and 8.27"X11.69 for the page size, when Postcript format is selected. |
| OK Button | It makes all the changes performed at this window and closes the window. |
| Cancel Button | It cancels all the actions that were performed in this window and closes the window. |
Starts a dialog window to save current data in a non-native format. The next example is a snap shot of the Export... window.
Export formats
| Export Format | Description |
| HTML Output | The HTML Export feature facilitate the sharing of UBET models online via the World Wide Web. This feature is accessible via the Html Export Dialog by clicking on File/Export/Html Output. See more details on html_export. |
| Spin Model
SPIN |
This generates an FSM model in Promela -- the specification language of the SPIN model checker. More information about Spin generation including how to run it from the command line is available in mkspin_readme.txt. Information about LTL Model checking with Spin is available on the Spin Home Page. |
| Test Cases | Exports test cases in the form of a flattened use case graph holding the minimum set of scenarios guaranteed to pass through all edges in the graph. The file is given a .tucg suffix. |
| VFSM Model | This converts use case graphs and their underlying MSCs into Virtual Finite State Machine models (Extended Finite State Machine models). An individual model is generated for each process in the underlying MSCs. For more information about the generation of VFSM including how to run generation from the command line see mkvfsm_readme.txt. For more information about VFSM see the Virtual Finite State Machine (VFSM) Home Page (Note: the url for the VFSM home page can not be accessed from outside the Lucent firewall.) |
| Testmaster model | Users can generate an equivalent TestMaster project by choosing this option, which creates a TestMaster import script (a ".tmi file") that can be opened in TestMaster. If the UBET model contains specification annotations, then this option will also create a .csv file containing them, which can be imported into TestMaster's requirements table after the .tmi file has been opened. See more details on this generation at TestMaster. |
RETURN TO TOP
Print Setup... (Solaris Only)

Node Properties Dialog
Use the menu button to bring up the property window while the cursor is over the node label. A dialog box appears to allow user to modify the node properties: Node Name, Node Number, Node Link, and Reference Tags and Associated Documents.Previously UBET had a MSC Link and a Subgraph Link, this has been modified with only one link, called Node Link. Node Link is either the MSC Link or the Subgraph link related to the current node.

| Setting | Description |
| Node Name | It is the node's name. The application gives a default
name that always starts "S_". No two nodes can be called the same
name.
Restrictions: Labels can not use any of the following symbols " , % \ [ ] |
| Node Number | It is the note number of the node. User can select the number or do an "Auto Number All Nodes" |
| Browse Button | Invokes the file browser to select the file you wish to select. A relative path will be placed in the entry field. |
| MSC Link | It links the current node to a Message Sequence Chart (itu file) that will be used when generating scenarios. |
| Subgraph File | It links the current node to another use case graph (ucg). It helps the user to increase the depth in the logic of the model. This file will be used when generating scenarios. |
| SubScenario | If the node is in the currently displayed scenario, the Properties... will bring up the node's property sheet with an extra field that allow the user to select a subscenario to be used for this subgraph during MSC generation. To learn about scenarios see Scenario's Window |
| Reference Tags | It links reference tags to this node. Reference Tags are pointers to bookmarks in Word documents. More information on Reference tags. |
| OK Button | It makes all the changes performed at this window and closes the window. |
| Edit MSC Button | It opens a new MSC editor displaying the graph chosen as the "MSC Link". |
| Edit Subgraph Button | It opens a new UCG editor displaying the graph chosen as the "Subgraph File". |
| Cancel Button | It cancels all the actions that were performed in this window and closes the window. |
Reference tags can be associated with the node by clicking the New button. New starts another dialog that permits the entry of a Reference Document and tag (Word bookmark). Use the browse button to find the referenced document. Browsing starts in the directory identified by the Reference Document Directory user preference. The following is an example snap shot of the dialog that starts when the user clicks the New button for Reference Tags & Associated Documents.

| Setting | Description |
| Doc | It has the path of the file that contains the tag (bookmark). |
| Browse Button | Invokes the file browser to select the file you wish to select. A relative path will be placed in the entry field. |
| Tag | It it the name given to the bookmark when created using MSWord. |
| Create Button | It creates the link between the tag and the object (node in this particular case). |
| Cancel Button | It cancels all the actions that were performed in this window and closes the window. |
Similarly, to edit a tag, select it first in the Node Properties dialog and then click the Select Button on the Edit button to modify it. To delete it, first select the tag and then click the Select Button on the Delete button. Note: you can also click Edit MSC in the Node properties sheet to bring up the MSE tool to edit the MSC named in the MSC Link field. Similarly, clicking on Edit Subgraph will bring up another instance of UCE to edit the associated UCE Subgraph.
Edge Properties Dialog
To change edge properties, use the Menu button to bring up the edge properties sheet. The user can change the Edge Label, Edge Number and enter Reference Tags.

| Options | Description |
| Edge Label | It is the edge's name. The application gives a default
name that always starts "A_".
Restrictions: Labels can not used any of the following symbols " , % \ [ ] |
| Edge Number | It is the note number of the edge. User can select the number or do an "Auto Number All Edges" |
| Match Any Label | When this attribute is set on the edge, the tool will match this edge with any label in the subgraph or vice versa during inlining. Both the Scenario Generation and Screen Inlining will use the Match Any Label attribute along with the Inlining Method selected to determine if the edge is a match or not. |
| Reference Tags | It links reference tags to this edge. Reference Tags are pointers to bookmarks in Word documents. More information on Reference tags. |
| OK Button | It makes all the changes performed at this window and closes the window. |
| "Hide all these" Button | "Hides" the edge. The edge is colored in a light gray color. |
| Cancel Button | It cancels all the actions that were performed in this window and closes the window. |
Open Scenario Window
It allows the user to select the scenario to be open.

Display Scenario Window
Delete Scenario Window
Delete Fragment Window
This is a new menu item under the Scenario menu. Delete fragment invokes the below dialog that allows the user to view the list of scenario fragments and their nodes currently shown on the screen. User can select the fragments and delete them from memory inside the dialog. This allows the user to discard unwanted excess scenario fragments that are not easily removed manually by selecting on the nodes.
Scenario Text Window

Parameterized Scenario Text Generation Window
"Parameterized Scenario Generation..." menu item allows the user to change parameters related to the scenario files without affecting his/hers preference settings.

| Buttons | Description |
| Add Node | Enters to add node mode. While in this mode each click on the canvas adds a new node. |
| Add Edge | Enters to add edge mode. While in this mode, clicking on one node (it will color the node in red), then another will create a new edge. |
| Delete Object | Enters to delete object mode. Clicking on a node deletes the node and all its edges. Clicking on an edge deletes the edge. Note: Before deleting a node move around any edges that need to be re-arranged. |
| Toggle Text | no functionality associated. |
| Redraw | Redraws the image. It positions the edges labels to the right of the edge. It does not means hat it will necessarily fit the image in the window. |
| Fit to Screen | Fits the drawing to the current window. Fits its typically used after resizing the window. |
| Larger | Allows the user to make the size of the drawing Larger (Zoom In). |
| Smaller | Allows the user to make the size of the drawing Smaller (Zoom Out). |
| Context of Node | Shows its (node selected) input edges in red and output edges in blue. Node context is an I/O view of a node, highlighting its incoming and outgoing edges. |
| Node + Scc | Shows the selected node and its strongly connected components. 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. |
| Node + Scc + Neighbors | Shows the context of the selected node and its strongly connected components. Node context is an I/O view of a node, highlighting its incoming and outgoing edges. 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. |
| New Scenario | Enters to scenario mode. Start to create a new scenario by defining the scenario path. The user can incrementally build a Path (scenario) through the graph -- clicking at nodes along the path one at a time. The nodes need not be adjacent, but they must be connected via zero or more intermediate nodes. |
| Show Leaves | Highlights all leaves (nodes without outgoing edges). |
| Show Roots | Highlights the root nodes. A root node is a node from which all other nodes can be reached. It is not necessarily a node without predecessors. |
| Show All Sccs | Highlights each strongly connected component set in a different color. 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. |
| Done | Closes the static menu. |
The TestMaster equivalent of any UBET model can be generated automatically by UBET in the form of a TestMaster import script (a ".tmi file") that can subsequently be opened by TestMaster. If the UBET model contains specification annotations, then a second file (a ".csv file") containing the specifications will also be created, in parallel with the .tmi file. The .csv file specifications can then be imported separately into TestMaster's requirements table after the basic .tmi file has been opened. Once these import steps are completed, it is recommended that users immediately save the project using TestMaster, and then delete the UBET-generated .tmi and .csv files that were used to create it. Reopening a .tmi file after it has been used to generate .tm files is likely to corrupt them, so a .tmi file should normally be used only once to create .tm files, and then discarded.
The TestMaster Dialog box is accessed via the Tools/TestMaster Model... menu item. The UBET utility that actually performs the conversion, mktm, can also be run from the command line.. The current use case graph (UCG) is always assumed by mktm to be the top level in the use case, and the utility recursively reads all subgraphs below the top level to generate a single, equivalent .tmi file representing a complete TestMaster "project."
mktm is implemented in Java 1.2. You must have JRE 1.2.2 or higher installed and your environment correctly set-up (see UBET Installation & Set-up for instructions on installing JRE). mktm enforces some restrictions on UBET models to ensure the validity of the generated TestMaster model.

The pop-up "Generate TestMaster Model" window is automatically populated with the name of the current ucg file using a .tmi extension for the output file. The user can search the directory structure and select an existing file. Alternatively, user can specify a file by typing path, file name and extension in the text box. If the file does not exist, it will be created. The Output file must be specified or an error will be generated.
The model name is a required parameter which specifies the name to be
used for the TestMaster project. When "Create Top-level Model with Test
Setup" is checked, the TestMaster project will contain two models: a top-level
empty model, "TestSetup," and a model named using the Model Call parameter.
Model Call thus becomes a required
parameter when "Create Top-level Model with Test Setup" is checked.
When "Include Script Generation Comments" is checked the .tmi file created will include comments documenting any required name aliasing and the names of the source files of the resulting TestMaster models.
For UBET variables to export correctly, UBET users must follow TestMaster type conventions. Only four data types are allowed in TestMaster: NUMBER, STRING, NUMBER ARRAY, and STRING ARRAY. Only these four types can be used within UBET if variables are to export correctly to TestMaster. TestMaster also requires that all SCOPE variables (UBET variables become SCOPE variables in TestMaster) be provided with an initial value. Variables that do not have an initial value, or that do not utilize TestMaster data types, cannot be exported to TestMaster.
An example is provided to demonstrate correct usage.