Release Notes: Astah Professional 6.0 (October 19, 2009)

  • Model Version:31
    Astah files (.asta) are upward compatible. If the files have been edited by the newer model version of Astah, they cannot be opened in the older model version ones.

What's new

  • Astah Professional
    • The product name has been changed from JUDE/Professional to Astah Professional
    • The setup files are moved from \.jude\Professional to \.astah\Professional
      • The Astah setup files are copied from User Home Directory\.jude\Professional to User Home Directory\.astah\Professional when starting Astah.
    • To all the JUDE/Professional Users
      • JUDE/Professional license is valid for Astah Professional if the license support period is not expired
        • The Astah setup files are copied from User Home Directory\.jude\Professional to User Home Directory\.astah\Professional when starting Astah.
          The JUDE license file (JUDE_License_User_Professional.xml) is also copied in the new directory.
      • The extension of project files is changed from .jude to .asta
        • .jude files can be opened in Astah
      • Astah log file
        • Log file is moved from User Home Directory\jude.log to User Home Directory\.astah\Professional\astah_pro.log.
  • Requirement Analysis Support
    • New model "Requirement" is added
      • Requirement can hold information such as its name, ID and Text.
      • Establish a relationship between Requirements and define the type of relationship out of Derive Requirements, Copy, Satisfy, Verify, Refine or Trace in the [Client]/[Supplier] Tab of Requirement's Property View.
      • How to create a Requirement
        • Select [Create Model] - [Add Requirement] from the Pop-up menu of Project, Model, Subsystem, Package and Requirement
        • Select [Add Child Requirement]/[Add Brother Requirement] from Pop-up menu of Requirement Table
        • Select [Add Requirement] from Pop-up menu of Requirement Table (Only when there is no Requirements on it)
    • New model "TestCase" is added
      • TestCase can hold information such as its name, ID and Definition to it.
      • Establish a relationship between TestCase and Requirements and define the type of relationship out of Satisfy, Verify or Refine in the [Supplier] Tab of TestCase's Property View.
      • How to create a TestCase
        • Select [Create Model] - [Add TestCase] from the Pop-up menu of Project, Model, Subsystem, Package and TestCase
    • Requirement Table is implemented
      • Requirement Tables show the list of Requirements with their names, IDs and texts hierarchically.
      • How to create a Requirement Table
        • Select [Create Diagram] - [Add Requirement Table] from the Pop-up menu of Project, Model, Subsystem, Package and Requirement
      • Setup of Requirement Table
        • Format of Requirement Table can be setup in [Edit Requirement Table] dialog. This dialog opens when new Requirement Table is created, by selecting [Edit Requirement Table] button from either Pop-up menu of Requirement Table in the Structure Tree or in the Property view of Requirement Table
          • Display Model :
            • Display the top parent if the requirement table is created under a requirement [Default: ON]
            • Display requirements under sub packages [Default: ON]
          • Hierarchy :
            • All Hierarchies [Default: ON]
            • Hierarchy Range (1 to 20)
              • Default : 2
          • Sort Order :
            • ID (ASC)
            • ID (DESC)
            • Name (ASC)
            • Name (DESC)
            • Text (ASC)
            • Text (DESC)
          • Display Items :
            • ID [Default: ON]
            • Name [Default: ON]
            • Text [Default: ON]
      • Edit ID, Name and Text of Requirements on the Requirement Table directly.
      • Pop-up menu of Requirements on the Requirement Table
        • Add Child Requirement
          • Add a new Requirement under selected Requirement
        • Add Brother Requirement
          • Add a new Requirement in the same level where the selected Requirement is
        • Edit Source Dependency
          • Specify source models of selected Requirement. The relationship type from Derive Reqt, Copy, Satisfy, Verify, Refine or Trace can be defined.
        • Edit Target Dependency
          • Specify target models of selected Requirement. The relationship type from Derive Reqt, Copy, Satisfy, Verify, Refine or Trace can be defined.
        • Convert to UseCase
        • Reference from Requirement Table
          • Jump to the selected Requirement on other Requirement Tables
        • Show in Structure Tree
      • Export Requirement Table to Excel
        • Export Requirement Tables to Excel using a template by selecting
          • [Export Requirement Table to Excel] from Pop-up menu of Requirement Table in the Structure Tree
          • [Tool] - [Requirement] - [Export Requirement Table to Excel] from Main Menu
      • Import Requirement Table from Excel
        • Import Requirement Tables from Excel by selecting
          • [Tool] - [Requirement] - [Import Requirement Table from Excel] from Main Menu
        • If there are Requirements that have same ID or name, ones in Excel file will overwrite ones that already exist in project
        • If there are Requirement Tables that have same name, the setting of one in project will apply
      • Print Setup(Project), Print Setup(Diagram)
        • New tab [Requirement Table] is added which contains [Print to Multi-Page] option
    • Convert to Mind Map Topics
      • Requirements, TestCases and Requirements Tables can be converted to Mind Map topics by doing drag & drop onto Mind map from Structure Tree
    • Exporting Requirements and TestCases to RTF Document
      • Exporting list of Requirements and TestCases
        • Check on following options in [Export RTF Document Option]
          • [Basic] - [Requirement List] (Default: ON)
          • [Basic] - [TestCase List] (Default: ON)
      • Exporting Requirement Tables
        • Check on following options in [Export RTF Document Option]
          • [Diagram] - [Requirement Table] (Default: ON)
      • Exporting Requirements and TestCases
        • Check on following options in [Export RTF Document Option]
          • [Model] - [Requirement] (Default: ON)
          • [Model] - [TestCase] (Default: ON)
  • Traceability Map
    • Traceability Map visualizes the traceability of selected models on a map
      • Create a Traceability Map to each model and it represents all the models, diagrams, hyperlinks that the model is related to. The traceability of the model can be seen at a glance in this traceability map.
    • How to create a Traceability Map
      • Select [Open Traceability Map] from Pop-up Menu of target model in the Structure Tree
      • Select [Tool] - [Traceability Map] - [Open Traceability] from Main Menu
    • Traceability Maps are available under following models:
      • Package, Model, Subsystem
      • Requirement, TestCase, Class, UseCase, Component, Artifact, Node, External Entity, Datastore and ER Entity
    • Traceability Map
      • Traceability Map is generated by all the models in project and is not available to modify directly
      • Updating Traceability Map is available by
        • selecting [Update] button on Traceability Map tool bar
        • selecting [Update Traceability Map] from Pop-up Menu of target Traceability Map in the Structure Tree
      • Updating all the Traceability Maps in project is available by
        • selecting [Update All Traceability Maps] from Project's Pop-up Menu in the Structure Tree
        • selecting [Tool] - [Traceability Map] - [Update All Traceability Maps] from Main Menu
      • Deleting all the Traceability Maps in project is available by
        • selecting [Delete All Traceability Maps] from Project's Pop-up Menu in the Structure Tree
        • selecting [Tool] - [Traceability Map] - [Delete All Traceability Maps] from Main Menu
    • Topics on Traceability Map
      • By selecting a topic,
        • property of selected model will appear in the Property View
      • By double-clicking a topic,
        • a Traceability Map of selected model will appear in the Diagram Editor if the topic is a model
        • the diagram will open in the Diagram Editor, if the topic is a diagram
    • Convert to Mind Map Topics
      • Traceability Map topics can be converted to Mind Map topics by doing drag & drop onto Mind map from Structure Tree
    • Export to RTF Document
      • Exporting Traceability Map
        • Check on following options in [Export RTF Document Option]
          • [Diagram] - [Traceability Map] (Default: ON)
        • Select [Tool] - [Traceability Map] - [Export RTF Document]
  • astah API enhancement
    • "DiagramEditor" is added to modify diagrams by using astah API
    • ClassDiagramEditor Interface (Modification of Class/Object diagrams)
      InterfaceMethodDescription
      ClassDiagramEditorcreateClassDiagram()Create Class Diagram / Object Diagram
      StructureDiagramEditor, parent interface of Editor ClassDiagramEditorcreateNodePresentation()Create Package Presentation and Class Presentation
      createLinkPresentation()Create Presentation of following models:
      Association, Generalization, Realization, Dependency and TemplateBinding
      ClassDiagramEditorcreateAssociationClassPresentation()Create Association Class presentation
      createInstanceSpecification()Create InstanceSpecification Presentation
      createInstanceSpecificationLink()Create Link Presentation

    • UseCaseDiagramEditor Interface (Modification of UseCase diagrams)
      InterfaceMethodDescription
      UseCaseDiagramEditorcreateUseCaseDiagram()Create UseCase Diagram
      StructureDiagramEditor, parent interface of UseCaseDiagramEditorcreateNodePresentation()Create UseCase Presentation
      createLinkPresentation()Create an Extend Presentation and Include Presentation
    • StateMachineDiagramEditor Interface (Modification of Statemachine Diagram)
      InterfaceMethodDescription
      StateMachineDiagramEditorcreateStatemachineDiagram()Create a Statemachine Diagram
      createInitialPseudostate()Create a InitialPseudostate Presentation
      createState()Create a State Presentation
      createFinalState()Create a Final State Presentation
      createTransition()Create a Transition Presentation
      StateMachineDiagramEditor's each methodCreate each model's Presentation
    • ERDiagramEditor Interface (Modification of ER Diagram)
      InterfaceMethodDescription
      ERDiagramEditorcreateERDiagram()Create an ER Diagram
      createNodePresentation()Create an ER Entity Presentation
      createLinkPresentation()Create Presentation of following models:
      Create an Identifying Relationship, Non-Identifying Relationship and Subtype Presentations
    • MindmapEditor Interface (Modification of Mind Map)
      InterfaceMethodDescription
      MindmapEditorcreateMindmapDiagram()Create a Mind Map
      createTopic()Create a Child Topic Presentation under selected topic
      moveTo()Move selected topic to selected spot
      deleteChildren()Delete all the Child topics under selected topic
      createMMLinkPresentation()Create a link between topics
    • BehaviorDiagramEditor Interface (Creating/Deleting Behavior Diagrams)
      InterfaceMethodDescription
      BehaviorDiagramEditor-Create/Delete behavior diagrams
    • StructureDiagramEditor Interface (Creating/Deleting structure diagrams)
      InterfaceMethodDescription
      StructureDiagramEditorcreateNodePresentation()Create a rectangle presentation (INodePresentation)
      createLinkPresentation()Create a line presentation (ILinkPresentation)
    • BasicDiagramEditor Interface (Creating/Deleting basic diagrams)
      InterfaceMethodDescription
      BasicDiagramEditorcreateNote()Create a Note Presentation
      createNoteAnchor()Create a Note Anchor Presentation
    • DiagramEditor Interface (Creating/Deleting Interface)
      InterfaceMethodDescription
      DiagramEditordeleteDiagram()Delete diagram from Project
      deletePresentation()Delete presentation from Project
      createText()Create a Text presentation
      createImage()Create an image presentation
      createRect()Create a rectangle presentation
      createLine()Create a line presentation
    • Interface that composes diagram information (presentations)
      InterfaceDescription
      INodePresentationInterfaces for rectangle presentations:
      - Refer to arrays of diagram, ID, label, property, element type, plot, width, height, parent, child, rectangle and line presentations
      - Specify label, property, plot, width and heights
      (e.g) Package, Frame, Note, Class, InstanceSpecification, UseCase, State, Partition, Action, Lifeline, Execution Occurrence, External Entity, ER Entity, Topic and boundary presentations
      ILinkPresentationInterfaces for line presentations:
      - Refer to diagram, ID, label, property, element type, array of dots, source and target
      - Specify label, property and array of plots
      (e.g.) Noteanchor, Association, Generalization, Realization, Usage, Dependency, TemplateBinding, Link, Extend, Include, Transition, Control Flow/ Object Flow, Message, Anchor, Dataflow, Identifying Relationship, Non-Identifying Relationship, Many-to-many Relationship, Subtype edge and link line between topics presentations
    • New methods to get presentation information
      InterfaceMethodDescription
      IDiagramgetPresentations()Get all the located presentations and each cells of CRUD including values and header in cells
      IElementgetPresentations()Get array of presentations
    • New Util methods
      InterfaceMethodDescription
      ProjectAccssorfindElements(Class elementKind, String name)Get models by specifying model type and name
      findElements(Class elementKind)Get models by specifying model type
      findElements(ModelFinder picker)Search model by ModelFinder
      IElementgetContainer()Get parent of model
      getContainers()Get parent of model
    • Operation's body condition, Precondition and Post condition
      InterfaceMethodDescription
      IOperationgetBodycondition()Get Body condition of Operation
      getPreconditions()Get Precondition of Operation
      getPostconditions()Get Post condition of Operation
      setBodycondtion()Specify body condition to Operation
      addPrecondtion()Add Precondition to Operation
      removePrecondition()Remove Precondition from Operation
      addPostcondtion()Add Precondition to Operation
      removePostcondition()Remove Post condition from Operation
    • Attribute's Navigability
      InterfaceMethodDescription
      IAttributegetNavigability()Get Navigability
      setNavigability()Set Navigability
    • New Interfaces
      InterfaceModel
      ICompositeStructureDiagramComposite Structure Diagram
      IPortPort
      IConnectorConnector
      IInstanceSpecificationInstanceSpecification
      ILinkLink
      ILinkEndLinkEnd
      ITerminationTermination
    • DataFlow Diagram
      InterfaceMethodDescription
      IDataFlowDiagramgetNotation()Get notation of DataFlow Diagram
      setNotation()Set notation of DataFlow Diagram
    • ER Diagram
      InterfaceMethodDescription
      IERDiagramgetNotation()Get Notation of ER Diagram
      getModelType()Get Model type of ER Diagram
      getInitialDisplayLevel()Get initial display level
      isAlignAttributeItems()Get array information of Attributes
      setNotation()Set Notation of ER Diagram
      setModelType()Set model type of ER Diagram
      setInitialDisplayLevel()Set Initial display level
      setAlignAttributeItems()Specify array of Attributes
    • Cardinality of ER Relationship
      InterfaceMethodDescription
      IERRelationshipgetCardinality()Get Cardinality
      setCardinality()Set Cardinality
    • Some Classes have been changed to @deprecated
      InterfaceMethodDescription
      ITopicPresentation-Interface for topics. INodePresentation is recommended.
      IMindMapDiagramgetRootTopic()Get Mind Map's root topic. IMindMapDiagram.getRoot() is recommended.
      MindmapDiagramEditor-Interface for Mindmap. MindmapEditor is recommended.
      IModelEditorFactorygetMindmapDiagramEditor()Create a MindmapDiagramEditor. IDiagramEditorFactory.getMindmapEditor() is recommended.
      IDiagramgetText()Get Text that is drawn on diagram. IDiagram.getPresentations() is recommended.
      IAttributeisEnable()Check if it is navigable or not. Using IAttribute.getNavigability() to get the navigability is recommended.
      setEnable()Specify the navigability. Using IAttribute.setNavigability() to specify it is recommended.

    • Astah API is not applicable for Requirements, TestCases, Traceability Maps and Requirement tables
    • Reference/Edit presentations by astah API is available in Astah Professional and Astah UML.
  • API sample
    • Following API samples are added.
      • Sample of getting diagram presentation information
      • Sample of creating a diagram presentation
  • Creating models through Text of Clipboard
    • Create models by pasting text through Clipboard on Diagram Editor. If there are line breaks in the text, multiple models can be created for each line of text.() indicates a default model that text can be converted to each diagram.
      • Class Diagram (Class)
      • UseCase Diagram (UseCase)
      • Statemachine Diagram (State)
      • Activity Diagram (Action)
      • Sequence Diagram (Lifeline)
      • Communication Diagram (Lifeline)
      • Component Diagram (Component)
      • Deployment Diagram (Node)
      • CompositeStructure Diagram (Structured Class)
      • Flowchart (Flow element)
      • DataFlow Diagram(DFD) (Process)
      • ER Diagram (ER Entity)
      • Mind Map (Topic)
  • Improvements on converting MindMap to UML
    • When converting a Mind Map Topic back to UML model, the original UML model type appear in the [Convert to UML model] dialog.
  • Improvements on converting UML to MindMap
    • Show UML Icons on Mind Map topics that are converted from UML model
    • [Tool] - [System Properties] - [Mindmap] - [Show UML icon when converting UML Model to Topic] (Default: ON)
  • Export Mind Map to PowerPoint file
    • Export Mind Map to PowerPoint file (.PPT) by selecting:
      • [Tool] - [Mindmap] - [Export PowerPoint] from Main Menu
      • [Save as Document] - [Export PowerPoint] from Mind Map's Pop-up menu in Structure Tree or Mind Map's in Diagram Editor
  • Show all the relations
    • Make all the relations visible on following diagram by selecting [Show Hidden Relationships] from its Pop-up Menu
      • Class Diagram
      • UseCase Diagram
      • Component Diagram
      • Deployment Diagram
      • CompositeStructure Diagram
  • Improvements on Sequence Diagram
    • Make Lifeline names visible by enabling following option.
    • [Tool] - [System Properties] - [Diagram Editor] - [Show temp name for Lifeline in Sequence Diagram] (Default: ON)
  • Adjust Lifeline's length
    • Adjust Lifeline's length
      • Select [Adjust Lifeline Length] from Lifeline's Pop-up Menu
    • Adjust the length of plural Lifelines
      • Select [Adjust Lifeline Length] from Pop-up menu of Sequence Diagram in the Diagram Editor or of selected multiple Lifeline's Default, Align to Minimum or Align to Maximum
  • Adjust ExecutionSpecification's length
    • Adjust ExecutionSpecification's length
      • Select [Adjust ExecutionSpecification] from ExecutionSpecification's Pop-up Menu
    • Adjust the length of plural ExecutionSpecifications
      • Select [Adjust ExecutionSpecification] from Pop-up menu of Sequence Diagram in the Diagram Editor or of selected multiple ExecutionSpecifications
  • Improvement on InteractionUse
    • Creating another sequence diagram through InteractionUse
      • If InteractionUse does not have a Sequence Diagram created in, double-click on InteractionUse or select [Create Sequence Diagram] from InteractionUse's Pop-Up Menu to create a sequence diagram
    • Opening a sequence diagram under InteractionUse
      • Double-click on InteractionUse or select [Open Nested Diagram] from InteractionUse's Pop-Up Menu to open the diagram
  • Improvement on Partition (Activity Diagram) and Lane (Flowchart)
    • Names of Partitions and Lanes are visible by enabling the option of
    • [Tool] - [System Properties] - [Diagram Editor] - [Show temp name for Partition/Lane] (Default: ON)
  • Improvement on Callbehavior Action
    • Creating another activity diagram through Callbehavior Action
      • If Callbehavior Action does not have an Activity Diagram created in, double-click on Callbehavior action or select [Create Nested Diagram] from Callbehavior action's Pop-Up Menu to create an activity diagram
    • Opening an activity diagram under Callbehavior Action
      • Double-click on Callbehavior Action or select [Open Nested Diagram] from Callbehavior Action's Pop-Up Menu to open the diagram
  • Improvement on Activity Diagram's option
    • Default setting of this option has been changed to OFF, [Tool] - [System Properties] - [Basic] - [Allow only one InitialNode in Activity Diagram]
  • Improvement on Submachine state
    • SubmachineState is now added in Statemachine diagram's toolbar
    • Creating another statemachine diagram through SubmachineState
      • If SubmachineState does not have a statemachine diagram created in, double-click on SubmachineState or select [Create Nested Diagram] from SubmachineState's Pop-Up Menu to create a Statemachine diagram
    • Opening a Statemachine diagram under SubmachineState
      • Double-click on SubmachineState or select [Open Nested Diagram] from SubmachineState's Pop-up Menu to open the diagram
    • Creating new Statemachine and modification of it is available from [Submachine] tab of SubmachineState
  • Improvement on crating lines on Line (Right Angle) mode
    • Association lines and Relationship lines won't overlap each other
  • Specifying resolution of copying diagram elements as an image or exporting diagram images
    • Specify resolution when diagram images are copied onto Clipboard or exported as diagram images.
    • [Tool] - [System Properties] - [Image] - [Expansion rate to copy a diagram as a bitmap image (%)] (Default: 140)
    • [Tool] - [System Properties] - [Image] - [Use the zoom level of the screen for copy (Minimum 100%)] (Default:None)
    • [Tool] - [System Properties] - [Image] - [Resolution to export a diagram as a bitmap image (DPI)] (Default: 96)
  • Setting Body Condition, Post Condition and Precondition to Operation
    • New tabs [Body Condition], [Post Condition] and [Precondition] are implemented to Operation's Property View.
  • Adding Stereotype with Shortcut key (Ctrl+Alt+S)
    • Shortcut key [Ctrl+Alt+S] adds stereotypes to selected model
  • Export properties as C#3.0 automatic properties
    • New option is added in [C# Option] that includes [Export properties as C# 3.0 automatic properties] option
  • New option for Text and Note
    • New option has been added in System Properties regarding Text and Note
    • [Tool] - [System Properties] - [Diagram Editor] - [Show Text and Note at the forefront of the elements] (Default: ON)
  • New option to display/non-display Collaboration menu
    • [Tool] - [System Properties] - [Management view] - [Show Collaboration menu on the main menu (Restart Astah)] (Default: OFF)
  • Minimum size of Frame has been smaller
  • Opening ".juth" file from Command-line is available
  • "Astah Support Site" has been added to Help Menu to directly receive Astah support

Fixed Bugs

  • [3800]The view of the UseCese Description template may not be updated promptly after importing the new template.
  • [3794]Port is out of Structure Class after changing the notation from the customized icon to the normal icon.
  • [3793]Icons are not displayed in the conflict list in Flexible Merge dialog.
  • [3792]Popup menus on the conflict list are not working in Flexible Merge dialog.
  • [3789]An exception may occur when exporting a project with Data Store by csvexporter in API samples.
  • [3788]Class definition is not exported by csvexporter in API samples.
  • [3782]Association End Name and multiplicity cannot be moved on Class Diagram by key operation.
  • [3781]Destroy Message may be placed on the StateInvariant in Sequence Diagram.
  • [3780]Mind Maps may not be saved after inserting images.
  • [3777]Inputted characters may blink on the diagram if the UseCase Description is opened at the same time.
  • [3776][Correct Invalid Models] may not correct some models.
  • [3773]New lines may be added in UseCase Description in some cases.
  • [3769][MacOS] .juth files is not selected in the file chooser.
  • [3767]Source code can not be imported by Import Java if the annotation type and default value is set to the annotation parameter.
  • [3761]MultiplicityRange is added to a Part in the Composite Structure Diagram after exporting to XMI.
  • [3760]Background color is not displayed correctly in Compare Project dialog.
  • [3759]Composite setting disappears by exporting or importing XMI.
  • [3757]Auto Resize menu is not working in Mindmap plural popup menu.
  • [3755]An exception occurs when moving the Usage of Required Interface on diagram.
  • [3754]Attributes and Operations of Class can be moved to UseCase on diagram.
  • [3751]StackOverFlow may occur when saving a project with JUDE API.
  • [3750]An exception occurs after setting the proxy server in the system properties and restart the program.
  • [3746]Navigation of the AssociationEnd may be set to non navigable when creating an Association with BasicModelEditor.createAssociation() (API).
  • [3744]Action/Flow element can be created by drag and drop of Topic from the structure tree to the outside of the Partition/Lane.
  • [3743]An exception occurs when showing an Association Class by using popup menu of Class diagram.
  • [3742]The logical name of ER Entity is not used when converting ER Diagram to Class Diagram.
  • [3738]A project cannot be saved if the image is inserted into the diagram and the name is changed.
  • [3736]A message is displayed after installing the program into the non-writable folder and running it at the first time.
  • [3735]Doing UNDO while selecting Process after cloning a Package may cause an exception error.
  • [3733]Cloning a Package clears the setting of diagram under Process in DataFlow Diagram.
  • [3732]Cloning a Class changes its nest class name
  • [3731]Cloning a Package clears the setting of Port type (Component's, Part of Component's and StructuredClass's).
  • [3730]"Operation Return Type Visibility" as missing in the [System Properties] - [Visibility1 (Initial)].
  • [3729]Cloning a Package contains an Association Class that self-association may cause an exception error.
  • [3728]Cloning a Package may create invalid models if there was an Association Class that has a BoundClass.
  • [3727]Cloning a Class does not clone any diagrams under its Operation.
  • [3726]Cloning a Class does not clone any diagrams under the Class.
  • [3724]Cloned Attributes and Operations font colors are not the same as original ones after cloning Package that contains Association Class has Attributes and Operations.
  • [3723]Doing Copy&Paste of InteractionUse causes an exception error if the InteractionUse has a Sequence Diagram setup.
  • [3717]Cloning Component, Node and Artifact makes stereotype duplicated.
  • [3711]Messages get out of ExecutionSpecification when moving ExecutionSpecification on CreateMessage.
  • [3673]After cloning a Package, BaseClass in cloned model (InstanceSpecification in Class Diagram/ObjectNode in Activity Diagram/Lifeline in Sequence Diagram/Lifeline in Communication Diagram/Part in CompositeStructure Diagram) is not correctly set.

Attention

  • XMI files generated by JUDE/Professional3.0 or older cannot be loaded. Project files (.jude) generated by older versions can be loaded.

Existing Bugs

  • [3765] Spaces are not displayed correctly when printing a UseCase Description (Java6).
  • [3049] After ungrouping the EMF images of diagrams from JUDE(Astah), the EMF image falls apart in other tools.
  • Depend on the running environment, images in EMF format cannot be pasted directly in Word, Excel or PowerPoint. This happens in Office 2000 after applying Windows update KB896424. To paste, go to [Edit] - [Paste special] - [Enhanced Metafile] in Word, Excel and PowerPoint. If you use Office 2003, you do not encounter this problem.
  • In the RTF document export function, the size of images becomes too large or too small depending on the option or the size of diagrams.
  • Some of Japanese characters cannot be input in the Mind Map.
  • A curve line in Mind Map will become a dashed line when you copy & paste an EMF file.
  • Boundaries, Icons and Images in Mind Map are not displayed in the EMF format.
  • There are some bugs upon on editing subtypes.
  • Objects lose gradations on exported EMF images. (By [Export Image]-[Save Diagram as EMF]/[Save Multiple Diagrams as EMF]/[Copy to Clipboard]-[EMF])

JUDE/Professional 5.5.2 (August 28, 2009)

  • Model Version: 30
    JUDE files (.jude) are upward compatible. If the files have been edited by the newer model version of JUDE, they cannot be opened in older model version.

Fixed Bugs

  • [3734]An error occurs when adding a Parameter to operation directly in Diagram Editor.

Attention

  • XMI files generated by JUDE/Professional3.0 or older cannot be loaded. Project files (.jude) generated by older versions can be loaded.

Existing Bugs

  • After ungrouping the EMF images of diagrams from JUDE, the EMF image falls apart in other tools. [3049]
  • Depend on the running environment, images in EMF format cannot be pasted directly in Word, Excel and PowerPoint.
    This happens in Office 2000 after applying Windows update KB896424. To paste, go to [Edit] - [Paste special] - [Enhanced Metafile] in Word, Excel and PowerPoint. If you use Office 2003, you do not encounter this problem.
  • In the RTF document export function, the size of images becomes too large or too small depending on the option or the size of diagrams.
  • Some of Japanese characters cannot be input in the Mind Map.
  • A curve line in Mind Map will become a dashed line when you copy & paste an EMF file.
  • Boundaries, Icons and Images in Mind Map are not displayed in the EMF format.
  • There are some bugs upon on editing subtypes.
  • Objects lose gradations on exported EMF images. (By [Export Image]-[Save Diagram as EMF]/[Save Multiple Diagrams as EMF]/[Copy to Clipboard]-[EMF])

JUDE/Professional 5.5.1 (August 11, 2009)

  • Model Version: 30
    JUDE files (.jude) are upward compatible. If the files have been edited by the newer model version of JUDE, they cannot be opened in older model version.

Fixed Bugs

  • [3722]An invalid model is created by cloning the Package which includes an AssociationClass with Template Parameters.
  • [3721]An AssociationClass is not cloned under the Package by cloning the Package.
  • [3716]Realizations and Usage Dependencies are not cloned correctly by cloning Package when they are connected to a Part and an Interface under the Package.
  • [3715]A Port on the Part is deleted after changing the Part name in the Composite Structure Diagram.
  • [3707]By clicking a root of message, it could break the indenting of Execution Specifications in Sequence Diagrams.
  • [3706]A cloned Part refers to the original Part when cloning a Package with a Component Diagram.
  • [3705]An relationship remains when selecting "Show as Class" popup menu on the Structure Class with Part and relationship, and an exception occurs by dragging the relationship.
  • [3703]Set ON to [System Properties] - [Basic] - [Set Unknown Type for Part when deleting its type from model], then delete a Class related with an AssociationClass. The AssociationClass is not deleted.
  • [3702]Improvements regarding to Foreign keys of ER Diagrams
    • Now you are able to modify Foreign keys of Attributes such as Domain, Data Type and Length/Precision.
    • Now you are able to set all Attributes in Child Entity for targets in [Child] Key of [Key] Tab of Relationships.
    • Models that contain Parent and Child that have different Type is now applicable in importing with [JUDE DB Reverse Tool (Sample)].
  • [3700]By dragging and dropping a unnamed Association end to Mind Map, it creates a topic without name.
  • [3699]There is no respond while doing merge sometimes.
  • [3698]An error occurs sometimes after changing the Diagram Type in CRUD.
  • [3695]Anonymous bound classes are not included in IAttribute.getTypeExpression(), IOperation.getTypeExpression(), IParameter.getTypeExpression()
  • [3693]It is unable to set "int*[]" for Attribute type directly in the Diagram Editor.
  • [3692]It is unable to set IAttribute.setTypeExpression("int[]") by JUDE API.
  • [3691]It is unable to specify Type Modifier in IAttribute.setTypeExpression(), IOperation.setTypeExpression() and IParameter.setTypeExpression().
  • [3690][Import Java] fails when the parameter is relational operation in the Attribute initial value = method (Parameter).
  • [3685][Set color] applies to Messages in Communication Diagram.
  • [3684]It is unable to set the minus value for Precision for ER Attribute.
  • [3683]Type Modifiers are not included in IAttribute.getTypeExpression(), IOperation.getReturnTypeExpression(), IParameter.getTypeExpression()
  • [3681][Import Java] fails if namespace of import statement includes enum.
  • [2716][3675][3680]"Execution Specifications" get out of lifeline sometimes in Sequence Diagram.
  • [3678]A.jude opens instead of A.juth, when you type in the file name on [File chooser] when opening a project and the file type is already set as ".juth".
  • [3679]An exception occurs when double-clicking a hyperlink on [Hyperlink Information] dialog.
  • [3677]It is unable to specify shared file on network for hyperlink.
  • [3674][3676]Moving messages in Sequence Diagram makes indenting of "Execution Specifications" wrong sometimes.
  • [3672][Print Preview Multi-UseCase Description] menu does not export Usecase Description in multiple pages correctly.
  • [3671]Modifying operation name creates invalid models when allocating a Class operation to messages in Sequence Diagram.
  • [3670]Modification you made for Return value of operation, Type modifier of Parameter when allocation a Class operation to messages in Sequence Diagram would not apply.
  • [3666]When you are running JUDE on Linux, files and directories appear in random order in the file chooser dialog when doing [Import Java].
  • [3665]Hyperlink from diagram image to package definition does not work sometimes in exported HTML.
  • [3664]Dragging and dropping Required/Provided Interfaces to another breaks the shape of model elements.
  • [3663]getOwner() of both IExternalEntity and IDataStore always return NULL.
  • [3662]When drawing a Component/Structured Class that has a part from Structure Tree, Usage/Realization that is related to the part do not appear in the Diagram.
  • [3661]When deleting a Component/Structured Class that has a part from Model, Interfaces that are related to a part still stay.
  • [3660]An exception occurs and wrong part appears in the diagram when selecting [Show Related Classes] in Component Diagram or Composite Structure Diagram.
  • [3659]When deleting a Structured Class that has a part in Composite Structure Diagram, Interfaces/Realizations/Usages that are related to a part still stay.
  • [3654]Interface icons do not appear correctly sometimes when drawing them by dragging from the Structure Tree.
  • [3653]Interface icons are still showing in a diagram sometimes even after deleting Realizations/Usages of Interfaces from the Property View.
  • [3650]Hyperlinks to model definitions from diagram image do not work sometimes on exported HTML if the project has two classes that have the exact same name.
  • [3649](AK) letters sometime stick out of the ER Entity.
  • [3647]When selecting more than one Stateinvariant at the same time, you can drag them onto a lifeline.
  • [3646]If the operation's abstract is set as "true", it gets exported into C++ incorrectly. (It says "abstract" in front of C++ member functions where it should be "virtual".)
  • [3645]Renaming lifeline could get CombinedFragment, InteractionUse and Stateinvariants out off the lifeline.
  • [3641]While [System Properties] - [Basic] - [Set Unknown Type for Part when deleting its type from model] option is ON and there is an Identifying Relationship, if you delete an ER Entity from Model, unnecessary relationship is automatically added (Same as UseCase, Node and Artifact)
  • [3640]Moving an Activation of CreateMessage could get an Activation out of the message.
  • [3637]After resizing lifelines and creating Createmessages, a Stateinvariant moves to wrong spot.
  • [3633]Modifying a Primary key that has FK, unnecessary Attribute is automatically added to Child Entity.
  • [3628]Sometimes messages are not attached to Lifelines.
  • [3630]We have improved to show an alert when invalid Create messages are made.
  • [3626]ER Model appears in the tree view on [Export Java], [Export C#] and [Export C++]
  • Relating to [3624][3623][3620], Child keys Attributes in different two relationships could switch to each other easily.
  • Relating to [3623][3620], specifying Child key(new) of Relationship [Key] may not apply properly.
  • [3620]If there is a parent entity that has a Primary key and Identifying/Non-identifying Relationship to Child Entity, modifying Child Entity's FK Attribute name may get reset after creating another Identifying/Non-identifying relationship.
  • [3611]Moving CreateMessages could make other messages appear strangely.
  • [3375]If you create an Identifying relationship to two Entities that already have Non-identifying relationship, the Non-identifying relationship may turn into Identifying one automatically.

Attention

  • XMI files generated by JUDE/Professional3.0 or older cannot be loaded. Project files (.jude) generated by older versions can be loaded.

Existing Bugs

  • After ungrouping the EMF images of diagrams from JUDE, the EMF image falls apart in other tools. [3049]
  • Depend on the running environment, images in EMF format cannot be pasted directly in Word, Excel and PowerPoint.
    This happens in Office 2000 after applying Windows update KB896424. To paste, go to [Edit] - [Paste special] - [Enhanced Metafile] in Word, Excel and PowerPoint. If you use Office 2003, you do not encounter this problem.
  • In the RTF document export function, the size of images becomes too large or too small depending on the option or the size of diagrams.
  • Some of Japanese characters cannot be input in the Mind Map.
  • A curve line in Mind Map will become a dashed line when you copy & paste an EMF file.
  • Boundaries, Icons and Images in Mind Map are not displayed in the EMF format.
  • There are some bugs upon on editing subtypes.
  • Objects lose gradations on exported EMF images. (By [Export Image]-[Save Diagram as EMF]/[Save Multiple Diagrams as EMF]/[Copy to Clipboard]-[EMF])

JUDE/Professional 5.5 (April 8, 2009)

  • Model Version: 30
    JUDE files (.jude) are upward compatible. If the files have been edited by the newer model version of JUDE, they cannot be opened in older model version.

New Functions

  • C++ Support
    • C++ language information can be set to project.
      • [Project Setting] tab of Project's property
        • C++
      • [Tool] - [System Properties] - [File] - [New Project Language]
        • C++
    • C++ Default Model
      • C++ Default model (C++.jude file) with classes extracted from C++ standard library, is provided.
        (Stored in JUDE/Professional Install folder\template\project)
        • There are two ways to read this C++ model when creating a new project.
          • [File] - [New By Template] and select C++.jude.
          • [Tool] - [System Properties] - [File] - [Create New Project By] and select "JUDE Build-in Template", and then specify [C++.jude] at the [Template File:], and then create a new project.
    • Type modifier support (Pointer information such as *, &..etc)
      • Specifying Type modifier is available in the Property view of models listed below.
        • [Attribute] and [Operation] tabs of Classes
        • [Base] tab of Attributes
        • [Base] and [Parameters] tabs of Operations
        • [Association End A] and [Association End B] tabs of Associations and Parts
        • [Base] tab of Ports
        • [Template Parameter] tab of Template Parameters and Template Bindings
      • Defined Type modifiers are displayed on Diagram Editor for models listed below.
        • Classes
        • Attributes*
        • Operations
        • Parts
        • Ports
        • Anonymous bound classes*
        • Template Bindings
        • *Type modifiers defined for Attributes and Anonymous bound classes are displayed in the Structure Tree.
      • HTML Export of Type modifiers
        • Classes
        • Attributes
        • Operations (Including Associations and Parts)
      • RTF Document Export of Type modifiers
        • Classes
        • Attributes
        • Operations
        • Associations (Including Parts and Template Bindings)
        • Template Parameters
    • C++ Primitive Type Support
      • bool
      • char
      • signed char
      • unsigned char
      • short
      • unsigned short
      • short int
      • signed short int
      • unsigned short int
      • int
      • signed int
      • unsigned int
      • long
      • unsigned long
      • long int
      • signed long int
      • unsigned long int
      • float
      • double
      • long double
      • wchar_t
    • Particular setting of C++ language is available in the property view of Classes, Attributes and Operations.
      • [Language] Tab of Class
        • <>
        • <>
        • <>
      • [Language] Tab of Attribute
        • <>
        • const
        • mutable
        • volatile
      • [Language] Tab of Operation
        • const
        • explicit
        • friend
        • inline
        • virtual
    • Export C++ Code ([Tool] - [C++] - [Export C++])
      • The following setting is available when exporting C++ Code.
        • Export #ifndef, #define, #endif in header file
        • include list
        • Header file extension
        • Source file extension
    • Remarks
      • Programming language setting isunspecified for project files that are created with ver 5.2.x or earlier.
      • Java Primitive Types can be set to projects that don't have programming language set up.
      • Programming language can be set to use for a project by simply checking on checkbox of language on the [Project Setting] tab of Project's property.
  • API Sample tool
    • JUDE C++ Reverse program
      • The following issues have been resolved.
        • Pointers included in Class names
        • C++ Primitive Type was created as a class
        • C++ setting toward JUDE project was not applicable since C++ project setting was not supported yet in JUDE/Professional
        • C++ particular setting (i.e. virtual) were not applied for models since it was not supported yet in JUDE/Professional
      • This tool imports C++ source code to JUDE by using the Doxygen and the edit function of JUDE API.
        Please see the detail at JUDE Install folder\api\sample\sample_doxygen_c_plus\sample_doxygen_c_plus.html .
      • *Technical support is not provided for this sample tool.
  • Improvements on Export HTML
    • The tools.jar of J2SE5.0 or 6.0 is required to export HTML.
      • Note: The tools.jar of J2SE1.4 is NOT applicable to export HTML since ver 5.5.
    • Template Classes are included in exported HTML.
    • Exporting Associations as Attributes
      • Associations that fit both conditions as below are exported as Attributes.
        ・They have names for Association Ends.
        ・They are not Non-Navigable.
  • Java5 Build
    • JUDE/Professional installer is built with J2SE5.0 since ver 5.5.
    • NOTE :JUDE/Professional no longer launches with J2SE1.4 since ver 5.5.
  • Show differences between diagrams in [Compare Project]/[Merge Project]
    • Show conflicts between diagrams graphically
      • Double-click on a diagram or select a diagram and press [Show Diagram Difference] button on [Compare Project] dialog. It opens a [Compare Diagram] dialog with two diagram images.
    • Export images of diagram differences
      • To export two diagram images with conflicts into an image (png, jpg), press the [Export Image] button on [Compare Diagram] dialog.
    • Open diagrams in order
      • To open diagrams in the project in order, press the [Previous Diagram Difference] / [Next Diagram Difference] button.
    • Zoom
      • All kinds of zooming （Zoom to Default, Zoom-in, Zoom-out and Fit in window) are available on [Diagram Compare] dialog.
    • Synchronize scroll
      • To synchronize both sides of diagrams to scroll, check on [Synchronize scroll] box on [Diagram Compare] dialog.
  • Change font color of model names
    • Changing font color of model names is available from Toolbar or Pop-up menu of model elements listed as below.
      • Classes (Attributes and Operations)
      • Packages
      • Subsystems (Operations)
      • Association Classes（Attributes and Operations）
      • Associations (Association Ends)
      • Generalizations
      • Realizations
      • Dependencies
      • Usages
      • Interfaces
      • Entities
      • Boundaries
      • Controls
      • Instance Specifications
      • Slots
      • Links (Link Ends)
      • Actors
      • UseCases
      • Extends
      • Includes
      • States
      • Event, Guard and Action of Transitions
      • Submachine states
      • StubState of Submachines
      • Partitions
      • Actions
      • CallBehavior Actions
      • Flow Final Nodes
      • SendSignal Actions
      • AcceptEvent Actions
      • Control Flows/Object Flows
      • Object Nodes
      • Processes
      • Connectors
      • Lifelines
      • Messages（Argument, Guard, Return Value Variable, Return Value and Operation)
      • Asynchronous Messages（Argument, Guard, Return Value Variable, Return Value and Operation)
      • Create Messages（Argument, Guard, Return Value Variable, Return Value and Operation)
      • Destroy Messages（Argument, Guard, Return Value Variable, Return Value and Operation)
      • Reply Messages
      • CombinedFragments
      • InteractionUses
      • StateInvariants
      • Components
      • Parts
      • External Parts
      • Ports (Multiplicity and Type)
      • Classifiers
      • Artifacts
      • Nodes
      • NodeInstances
      • Components
      • ComponentInstances
      • Structured Classes
      • Processes
      • Transition Conditions
      • External Entities
      • Processes
      • Data Stores
      • Data Flows
      • ER Entities (ER Attributes)
    • [Tool]-[System Properties]-[Basic]-[Set font color to element's title individually when selecting a frame of the element] (Default : OFF)
  • Improvement on Statemachine Diagram
    • When creating a new Transition, Events and Guards are defined in recommended cases.
  • Improvements on [Export Entity Definition Report]
    • A Domain List can be exported. It includes:
      • Project
      • Number
      • Logical Name
      • Physical Name
      • Alias1
      • Alias2
      • Type
      • Length&Precision
      • Not Null
      • Parent Domain
      • Definition
    • Select documents to export
      • Select which documents to export by checking on [Export] checkbox of [New Entity Report Template] dialog.
        • Domain List
        • Entity List
        • Entity Definition
  • Improvement on [Export Image]
    • Now the following images can be exported:
      • UseCase Descriptions
      • CRUDs
  • Show namespace in the Diagram Editor title
    • Show a namespace of diagram's in Diagram Editor's title bar.
      • [Tool] - [System Properties] - [Diagram Editor] - [Show namespace in the Diagram Editor title (Restart JUDE)] (Default : ON)
  • Support Constraint for Classes
    • Specifying constraint for Classes is available in [Constraint] tab of Classes in the Property View.
    • Constraints of Classes are exported into RTF document.
  • Object diagram models have been changed into UML2.0 names.
    • Instance Specification (Former name: Object)
    • Slot (Former name: Attribute)
  • Improvement on Sequence/Communication Diagrams
    • The following selections have been added in Drop-down button of Lifeline in Toolbar.
      • Actor
      • Entity
      • Boundary
      • Control
  • Improvement on Object/Deployment Diagrams
    • The following selections have been added in Drop-down button of InstanceSpecification in Toolbar.
      • Actor
      • Entity
      • Boundary
      • Control
  • Improvement on partition size (Activity Diagram)
    • Default size of partition has been adjusted, so it fits in Diagram Editor when you create the first partition.
  • Improvement on [Show in Structure Tree] and [All Related diagrams] menu.
    • [Show in Structure Tree] and [All Related diagrams] menu include the models listed below as target.
      • Type of Template Parameter that is referring a target class
      • Default Value of Template Parameter that is referring a target class
      • Actual Parameters of Template Binding that is referring a target class
  • Improvement on cloning
    • Cloned diagram will be open in Diagram Editor when cloning a diagram.
  • Improvements on API
    • Get Return Value variable from a message by adding getReturnValueVariable() to IMessage.
    • Specify Type expression from Operations/parameters
      • Specify a Type expression from Operations by adding setReturnTypeExpression() to IOperation.
      • Specify a Type expression from Parameters by adding setTypeExpression() to IParameter.
    • Set C++ language
      • Specify C++ language information to project by adding to BasicModelEditor.
    • Specify/Get Type Modifier
      • Get Type Modifier from IElement by adding getTypeModifier() to IElement.
      • Specify Type Modifier from IElement by adding setTypeModifier(String typeModifier) to IElement.
      • Get Type Modifier of actual parameter by adding getActualParameterTypeModifier(IClassifierTemplateParameter param) to ITemplateBinding.
      • Specify Type Modifier of actual parameter from ITemplateBinding by adding setActualParameterTypeModifier(IClassifierTemplateParameter param, String typeModifier) to ITemplateBinding
      • INVALID_TYPE_MODIFIER_MODEL_ERROR_KEY,INVALID_TYPE_MODIFIER_MODEL_ERROR_MESSAGE is added to InvalidEditingException.

Fixed Bugs

  • [3610]An exception happens sometimes when changing the end of Message in Sequence Diagram
  • [3605]By double-clicking a slot of Instance Specification that has a base class with Attribute more than once, the Attribute's string appears and you are able to modify it.
  • [3604]An exception happens when converting a Class Diagram to ER Diagram if there are Class and Subsystem and the Subsystem is used for Class's Attribute type.
  • [3603]It is unable to open Class's Pop-up menu in Structure Tree,in the list of [Search] pane, in the Diagram Editor if the Class is used for Type of Qualifier.
  • [3602]Initial Hight setting of [Tool] - [Set Template] - [UseCaseDescription] does not apply sometimes.
  • [3600][Import Java] may fail if the Java contains an Attribute that is using a Template and also is initialized by Method that is using the template.
  • [3597]An exception occurs when cloning a package in some cases.
  • [3596]Strange letters appear when double-clicking the name of line between topics.
  • [3595]Classes under a Model don't appear in the [Convert UML Model to ER Model] dialog.
  • [3584]When exporting a model to XMI, it doesn't keep the model name and it becomes "no_title".
  • [3581]We should not add "_x" at the end of operations when we copy them if they had the same name but had different parameters.
  • [3578]Logical name appears on the sheet of Entity Definition Report where it should appear Physical name.
  • [3576]ER Model and Domain should not be allowed to move under UseCase Description in the Structure Tree.
  • [3573]Properties are not exported properly upon Export C#.
  • [3572]Class name gets exported unnecessary into using statement upon Export C#.
  • [3569]A confirm dialog now indicates which version of JUDE last modified the .jude file when opening it.
  • [3559]A Height field of ProcessBox in [Tool] - [System Properties] - [Default Size (Initial)] is now put together with "Width".
  • [3568] When you copy and paste Attributes/Operations, an order of them will change from an original order.
  • [3567] Unable to delete Stereotypes/Constraints of Attributes/Operations directly from Diagram Editor.
  • [3566] An exception happens when you select [Paste] from Menu on CRUD which contains no diagrams.
  • [3564]The using phrase is not correct in a class which references a class in a different namespace when exporting C#.
  • [3557]Invalid icon appears for Class’s property on following areas (Class’s Property View [Property] Tab [Depend Type] / Class’s Pop-Up Menu [Show Part] dialog [Depend Type].)
  • [3555]Inner classes cannot be imported properly by [Import Java] if they have deep class hierarchy.
  • [3553][SQL Export] does not export constraints of some foreign keys properly if a child key has been changed in the [Tab] key of Relationship's property.
  • [3552]Entity title does not appear correctly when exporting an Entity Definition using Excel 2007.
  • [3550]When restarting JUDE, external tool history may not appear on the menu. Since ver5.5, all registered external tools should appear on menu of [Tool] - [External Tool] - [Customize External Tool].
  • [3547]Base class of Instance Specification is cleared after modifying the object name in Alias view.
  • [3542][Set Line Color] menu is missing from [Template Binding] Line 's Pop-Up Menu
  • [3540][Correct Invalid Models] does not work for some invalid models properly.
  • [3539]While the [System Properties] - [Project View] - [Show navigable Association End (Role) only on the structure tree] option is on, the structure tree expands every time a model is modified.
  • [3535]Javadoc files cannot be opened after Export HTML.
  • [3534]It is unable to click on anything in the Structure Tree after changing [Look and Feel] on JUDE that is running upon on Java6.
  • [3494]It fails to print out a Mind Map if any line feed code is included in Mind Map's name.
  • [3532][Version Information] dialog box is modeless.
  • [3531]After changing Look & Feel, an arrow to open a split pane in the top of [Structure] and [Alias] tabs moves to left.
  • [3530]Target models are missing on [Show in Structure Tree] menu of CRUD's Pop-up menu.
  • [3528]It is unable to create anonymous bound classes with ? by modifying Attributes/Operations directly.
  • [3527]It is unable to create anonymous bound classes with Primitive type by modifying Attributes/Operations directly.
  • [3525]There is a difficulty in scrolling with right-drag on Diagram Editor.
  • [3524]Unable to get namespace by using JUDE API getOwner() method toward Activity Diagram, Statemachine Diagram, Sequence Diagram, Flowchart and Data Flow Diagram.
  • [3522][Correct Invalid Models] menu does not work sometimes for invalid models in Sequence Diagram.
  • [3521][Software Update Information] menu does not work.
  • [3518]A hyperlink is not applicable if the target file name contains "+".
  • [3517]An exception could occur when converting a Class into an Association Class.
  • [3515]It is unable to transfer BoundClasses to another package.
  • [3514]It is unable to delete Parameters from Operations on the Diagram Editor.
  • [3513]Multiplicity for Attribute Type, Operation Return Value, and Parameter Type is not exported to RTF Documents.
  • [3464]When you adjust size of a Class with ports on, a Class size changes and leaves ports out off the Class.
  • [3510]Unnecessary comma is sometimes attached at last column definition in exported SQL.
  • [3509]If "String - java.lang" is applied to System Properties's [Basic] - [Default Type of Attribute], deleting java package could call an invalid message dialog and generate invalid models.
  • [3506]Improved on SQL export option dialog labels.
  • [3504]Cloned classes lose its individual visibility setting of Attributes/Operations. (When cloning a Package that contain a Class Diagram that has a Class with Attributes/Operations with individual visibility setting)
  • [3503]An exception happens by clicking Frame with holding CTRL key down if frame and other objects are selected in diagram.
  • [3500]Length/Precision field of referenced Domain's in the property view should be grayed out.
  • [3499]Length/Precision of Domain's in referenced ER Entities attribute won't be updated in the property view.
  • [3498]When you select two Notes in Communication Diagram, [Set Font Color] menu is not showing on its Pop-Up Menu.
  • [3496][Show in Structure Tree] in Pop-Up Menu of ExternalEntity and DataStore does not work.
  • [3495]An error occurs in parser when importing Java files.
  • [3493]An exception occurs when cloning a folder containing an Activity diagram.
  • [3491]ER Entity names are always exported in logical name to CREATE UNIQUE INDEX by executing Export sql.
  • [3490]Setting of Comment in [Export SQL Option] dialog does not apply if ER Entities do not have any definitions.
  • [3489]When you copy a State containing an Internal event in Statemachine diagram, copied state will have duplicated Interval events.
  • [3488]Alias do not show in the Diagram Editor properly.
  • [3485]Color of model elements changes automatically when adding another model to diagram from structure tree.
  • [3484]Sequence Diagrams should not be able to have the same name under package.
  • [3480]Merging could create multiple classes that have same name.
  • [3479]When a state is inside another state, it is unable to create a Transition from one to another.
  • [3478]Adding a reference project could create multiple classes that have same name.
  • [3475]Interface Icon does not show right sometimes when adding it from the Structure Tree.
  • [3474]Deleting a model after cloning packages could create invalid models.
  • [3473]An exception happens when exporting HTML of models if the models contain C# Primitive type.
  • [3472]When creating more than one Template Parameter by BasicModelEditor.createTemplateParameter(), a wrong error message appears.
  • [3471]An error occurs when specifying null for Class and initial value for Template Parameter's type by BasicModelEditor.creaetTemplateParamenter().
  • [3470]An invalid error message comes up when specifying "" (setName("")) for a Class by JUDE API.
  • [3467]Attributes are shown in logical name always on [Edit Index] dialog of ER Diagram.
  • [3466]An exception happens when creating Provided/Required Interface while the [Create relation in original direction] option is ON.
  • [3462]It is difficult to change a direction of messages in Communication Diagram.
  • [3461]An exception occurs when adding or updating files as reference models that are created or updated with newer model version.
  • [3460]Invalid menu name is used on [Compare Project] dialog.
  • [3458]AssociationClasses are not included in [Java Parse Chooser] list when importing Java.
  • [3456][Java Parse Chooser] does not show up when importing .java with associations that have static definitions.
  • [3455]An exception happens when importing the same .java files several times.
  • [3454]Anonymous bound class does not show properly on exported text by [Compare Project].
  • [3454]Anonymous bound class does not show properly on exported Class CSV.
  • [3451]Scrolling up/down (with mouse wheel) enlarges a diagram without any limit.
  • [3450]Unnecessary space is included when printing Mind Map or exporting image of Mind Map.
  • [3448]Alias for base class of Lifeline do not show properly in Sequence and Communication Diagram.
  • [3447]Alias do not appear properly on diagram.
  • [3445]JUDE freezes when opening a file if it contains invalid models.
  • [3444]An exception occurs when doing UNDO after deleting Lifeline in Sequence Diagram.
  • [3428]An exception occurs if jude-pro.jar is in front of jude-api.jar in CLASSPATH of Java projects that use JUDE API.

Attention

  • XMI files generated by JUDE/Professional3.0 or older cannot be loaded. Project files (.jude) generated by older versions can be loaded.

Existing Bugs

  • After ungrouping the EMF images of diagrams from JUDE, the EMF image falls apart in other tools. [3049]
  • Depend on the running environment, images in EMF format cannot be pasted directly in Word, Excel and PowerPoint.
    This happens in Office 2000 after applying Windows update KB896424. To paste, go to [Edit] - [Paste special] - [Enhanced Metafile] in Word, Excel and PowerPoint. If you use Office 2003, you do not encounter this problem.
  • In the RTF document export function, the size of images becomes too large or too small depending on the option or the size of diagrams.
  • Some of Japanese characters cannot be input in the Mind Map.
  • A curve line in Mind Map will become a dashed line when you copy & paste an EMF file.
  • Boundaries, Icons and Images in Mind Map are not displayed in the EMF format.
  • There are some bugs upon on editing subtypes.
  • Objects lose gradations on exported EMF images. (By [Export Image]-[Save Diagram as EMF]/[Save Multiple Diagrams as EMF]/[Copy to Clipboard]-[EMF])
  • Release Notes for JUDE/Professional5.4.x or older versions have been omitted.