You can define your own metadata on any path node, intentional element, etc. These string / value pairs are intended to be used when writing your own custom plug-in to jUCMNav that needs extra information to do its job. An example would be a test case exporter which would require a few setup parameters to drive the output.
Many thanks to Pengfei Chen for this addition!
Traversal algorithm is now more robust, supports multiple threads, knows about the component context in which a path node is being run.
Hit count no longer algorithm dependant.
Created infrastructure to support:
Scenario Traversal Listeners
Other scenario traversal algorithms (strategy design pattern)
Added export to MSC plug-in to jUCMNav.
Based on the work done by Daniel Amyot and Ali Echihabi for UCMNav.
Actually exports to *.jucmscenarios, the XML serialization of an EMF-based meta-model which clean-ups up the XSLT-related elements required by UCMExporter
It can also export its intermediate steps as a *.jucm file representing a flattened UCM and another *.jucm file representing the well-formed (in terms of concurrency) linear representation.
User documentation only partially reflects integration of GRL and scenarios.
Duplicate map / grl diagram does not set IDs for the new elements.
There are no extension points to give your own scenario/stategy algorithms and no UI to choose them.
Visibility of GRL contribution icons and text now can be set via jUCMNav's main preference page, but open editors are not automatically updated. You need to reload the model.
Bug in export to MSC: If none of your scenario elements are not contained inside a component reference, the exported MSC will fail to open. Workaround: associate at least one of your responsibilities to a component reference.
The generated "Environment" component dissapeared if it did not communicate with another component, even if it contained elements such as responsibilities.