Note: You are invited to add your own requirements
to this list. Please contact Daniel
Amyot.
High priority
DONE. Ability to add the current map to any predefined UCM set.
DONE. Ability for quick switching between
parent and submaps.
DONE. Provision of an autosave function with user specified interval with the
ability to revert to previous saved versions.
DONE. Ability to vary the interpolation detail of the UCM paths from high to
low definition splines and the possibility of straight line segments.
DONE. Ability to delete single and multiple path elements and components using
the Delete key.
DONE. Provision of an import option where conflicting components and responsibilities
are not duplicated.
Ability to export and import the global list of component definitions between
designs.
Ability to specify and selectively highlight end-to-end scenarios across
entire designs.
Ability to cut and paste between maps and provide ability to undo cuts.
Enhanced control over the positioning of labels. Labels could be dragged
to new locations while remaining anchored to their parent element.
Ability to put textual comments on a map within a comment box. For instance,
Ability to specify timeout paths on a synchronization with timers.
DONEAbility to produce Computer Graphics Metafile (CGM) files of map graphics
Ability to vary the size and fill colours of stubs for visual effect.
Low priority
New disposition of main panel (more windowish), with separate windows for
the UCM, comments, pre/post conditions, responsibility list, and decomposition
level.
Decomposition Level window: we currently have a the current map and its
parent maps, up to the root. A separate window (or drop down menu as with
file manager tools ) would be more appropriate. Root maps could be enumerated
(at the very least), or everything could be displayed as a tree-like structure
(with subtrees that can be collapsed à la Acrobat Reader)
Undo operation in which transformations on maps can be undone.
Free rotation of forks and joins.
Implementation of exceptions: need a RAISE responsibility on one path,
and a HANDLE responsibility on another path connected by an abort symbol.
Improvement of the spline path drawing functions in which interior path
elements which are not endpoints or multipath elements can be specified
by the user to be slave points in that their position will not need to
be set by the user but will follow the path resulting in much smoother
curves with less user effort.
Implementation of an incremental drawing mechanism for the display in which
only changed elements are redrawn as opposed to the whole display.
Possibility to edit/view multiple maps simultaneously.
Cardinality attached to synchronizations. For instance: 1:N, 2:2, etc.
Instance values for plug-ins that include formal components.
Colors, shadings, textures for lines, components and path elements.
Achieved in Wish List Version 5 (UCMNav versions 1.02
to 1.12)
DONE. Use of XML for loading/saving maps.
DONE. Scrollable, resizeable, and zoomable
workspace.
DONE. Tags for goals boundaries (like timestamp
points), and relations between these tags such as Goal name, Precondition,
Postcondition, Description.
DONE. “Forest” of UCMs in a file (multiple
root maps)
DONE. Selection of map elements should be
more noticeable and have a larger selection range. (US)
DONE. Creation of forks and joins should allow
selection of two path end points. (US)
DONE. Separate definition of responsibilities
from inclusion along paths allowing a single definition for an entire design
to be placed at an arbitrary number of path points and in an arbitrary
number of different maps.
DONE. Could we have forks (OR, AND) oriented
to any of four main directions? We have 0 and 180 degrees, could we also
have 90 and 270 degrees?
DONE. A short Help window (with key shortcuts
and essential basic explanations) in the About menu would be appreciated.
DONE. Possibility to save/load a plug-in to/from
an external file. In the File menu, “Export Current Map” would save the
current (plug-in or root) map as well as its sub-maps, and “Import Plugin
From File” would be a transformation in the stub popup menu.
DONE. Ability to specify graphical path direction
arrows.
DONE. Ability to generate complete detailed
reports in PostScript and PDF formats containing map graphics and all textual
annotations requested by users including responsibility descriptions, pre/post
conditions and events lists, goal descriptions and all map, map element,
and component descriptions. The PostScript file will include indexes for
PDF generation.
DONE. Ability to move entire sections of maps
across editing area by multiply selecting path elements and components
by dragging out a rectangle with the select tool chosen.
DONE. Ability to specify timeout paths for
waiting places cast as timers.
DONE. Ability to select multiple map elements
(either path points or components ) and perform either horizontal or vertical
alignment operations such as align top, align bottom or center or distribution
operations such as distribute horizontal/vertical.
DONE. Ability to highlight path elements with
missing performance annotations.
DONE. Port to Windows NT environment using
GnuWin32.
DONE. Selection policies associated to dynamic
stubs. This is a description of how plug-in(s) will be selected at run-time.
DONE. Implementation of enforced bindings
for stubs allowing input and output paths of a stub to be selected from
lists in the stub attributes dialog and bound together for the purpose
of recording valid end-to-end paths. The verification will be done at run-time
(not via the tool).
DONE. Allow user the option of displaying
unavailable transformations. (US)
DONE. Ability to save the map as a MIF file.
DONE. Selected components should be coloured
the same as selected path elements. (US)
DONE. Handles should not be shown for components
that are fixed in position. (US)
(US) Denotes recommendation from the UCM Navigator usability study.
![[Comment Image]](wishcomment.gif)