New visualisation of metadata, stereotypes, and links:

• In Eclipse: Help -> Software Updates -> Find and Install -> Search for new features to install -> New remote site:
  • Name: jUCMNav
  • URL: http://jucmnav.softwareengineering.ca/jucmnav/updatesite/
• See the animated InstallationDemo
• Important Notes
  • On Eclipse 3.4, select both the new jUCMNav update site and the Europa Discovery Site
  • On Eclipse 3.3, you might need to expand the Europa Discovery Site before clicking on "Select Required" (dependencies)
  • Using the update site is needed if you want the MSC Viewer plugin to be installed properly. Afterwards, the jUCMNav and MSC Viewer plugins can be updated manually from binaries.
  • Eclipse does not allow automatic upgrades between major revisions. jUCMNav v2.* will need to be uninstalled before proceeding with the installation of jUCMNav v3.*

• Download v3.2.1 here (jar).
  • <font color=red>Make sure your browser does not rename the .jar file to .zip or anything else.</font>
• Other files (src, javadoc)
• Download and install all prerequisites, then copy the jar file into your /eclipse/plugins/ directory. Restart Eclipse.
• If you've installed jUCMNav from a latest build instead of an official release, make sure you remove the latest builds.

• Windows XP (tested) :check:
• Linux (tested) :check:
• MacOS X (tested) :check:
• Any other O/S on which you can run Eclipse (currently untested - please report your success)

• J2SE 5.0 (1.5) or 6.0 (1.6) at http://java.sun.com/javase/downloads/index.jsp

• Version
  • jUCMNav 3.2 requires Eclipse 3.3 or Eclipse 3.4 or Eclipse 3.5
• Distributions
  • We recommend the installation of Eclipse Classic 3.5.x or Eclipse Modeling Tools available at http://www.eclipse.org/downloads/
• Plug-ins required for running jUCMNav
  • jUCMNav 3.2 requires the Eclipse EMF, GEF, JDT, RPC, OCL, and Platform plugins.
  • Users should use the jUCMNav update site to get these dependencies automatically.
  • Otherwise, they can be obtained from the Europa Update Site or from their respective projects
• [Optional] Additional plug-ins required for compiling jUCMNav
  • PDE and WTP 2.0

• GraphViz (dot) is required for the diagram autolayout feature.
• http://graphviz.org/Download.php

• For more in-depth information and a guide about installation of prerequisites, see DevDocDeployment.
• For complete notes and troubleshooting, see: JUCMNavDeployment

• End-user documentation is integrated with the Eclipse help system. Access Help > Help Contents from the Eclipse workbench, then select topic jUCMNav Online Help.
• The latest user documentation can also be accessed via HelpOnLine

• Send your bug reports to <a href="mailto:[email protected]">[email protected]</a>.
• Include reproduction steps, sample .jucm files and, if applicable, copy-paste the error log messages.
• If you're zealous enough, we'll create a BugZilla account for you :)

• Visualization of importance attributes (GRL), URN links (GRL) and metadata (GRL/UCM)
• URN link indicators for GRL elements, support for stereotypes, and tool tips for model elements that have descriptions, metadata and/or URN linkswith tool tips for descriptions, metadata, and stereotypes (URN)
• New colours for GRL evaluations, more pastel, which lead to better printouts. Also changed white to grey for Unknown evaluations.
• Scenario definitions in the scenario group named Init are now skipped when running all scenarios (including during MSC export). This Init group is hence a good candidate for defining partial scenarios that are included elsewhere but that are not meant to be run standalone.
• Partial support for user-defined metrics (in OCL) computed on URN models
• Various bugs and UI-related issues:

Bug	Description
<a href="http://jucmnav.softwareengineering.ca/bugzilla/show_bug.cgi?id=548">548</a>	Metadata indicator for URN elements
<a href="http://jucmnav.softwareengineering.ca/bugzilla/show_bug.cgi?id=637">637</a>	Display error in GRL qualitative/mixed evaluation
<a href="http://jucmnav.softwareengineering.ca/bugzilla/show_bug.cgi?id=638">638</a>	Deleting an unnamed start/end point creates exceptions
<a href="http://jucmnav.softwareengineering.ca/bugzilla/show_bug.cgi?id=466">466</a>	Some support for responsibility reference copy-paste (alpha)
?	Fixed GRL actor evaluation for quantitative/mixed algos (now just a simple weighted average based on importance of intentional elements).

• Three new GRL propagation algorithms (qualitative, qualitative and hybrid), and fixes to the existing one.
  • See Clause 11.1 and Appendix II.1 of draft Z.151 - URN
  • http://jucmnav.softwareengineering.ca/twiki/bin/viewfile/ProjetSEG/WebHome?rev=1;filename=GRLalgosPref.gif

• Verification of user-defined semantic rules
• PDF/RTF report generation
• Much improved HelpOnLine
• jUCMNav metamodel better aligned with the draft Z.151 (URN) metamodel
• Upgraded the French version of jUCMNav.
• Various bugs and UI-related issues:

Bug	Description
550	Error when undoing the deletion of a GRL element
554	Strategies export to .csv files do not handle commas in descriptions
556	In the Stub Bindings window, plug-in condition expressions' && are replaced with &
555	Belief descriptions not duplicated properly when duplicating a GRL diagram
551	Report when transforming a non-well-nested UCM
552	TOC links in the on-line help refer to the TWiki site
535	And/Or decomposition context menu item
559	Invalid thread access when exporting a URN model without scenario definitions
561	Invalid default value for Preferences under Linux
409	Export wizard + multi-map select
332	Image export: should try to trim exported images
329	Progress meters for wizards

• Reports generated, MSC Viewer, and user documentation only available in English.
• Reports do not include information on GRL elements or UCM scenario definitions (and MSCs)
• 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.
• Deleting a map whose start point is referenced in a scenario definition causes saving the file to complain.
• There are no extension points to give your own scenario/strategy algorithms and no UI to choose them.
• Memory leak. With very large diagrams (30+ complex maps), you might only be able to open it half a dozen times before you run out of memory. Restart Eclipse to clean memory or increase JVM heap space until we find the memory leak source.

-- Main.DanielAmyot - 21 Apr 2009