Overriding default toolboxes in an MDG

[contrem]

I'm so close!!

I have created a version of the requirements toolbox with our stereotyped versions of the elements and connectors. As the last step I wanted to override the default UML requirements toolbox with our own tailored version. I followed the instructions in the user guide and added the redefinedtoolbox instruction in the notes for the diagram scoped to the toolbox profile, but when I generate the MDG and use it it doesn't override the default requirements toolbox!! I'm using a class diagram for the toolbox profile (not sure if this is relevant or not)!

This is what I put in the diagram notes:

RedefinedToolbox=Extended::Requirements;Alias=Requirements;Notes=Structural elements for requirements diagrams;

I added the MDG by adding a path in Settings|MDG Technology to the MDG XML file.

The toolbox appears in the More Tools... list, but doesn't override the default requirements toolbox when I open a requirements diagram.

I also did a bit of digging into the MDG XML and noticed that the ICONIX MDG technology XML contains the following elements in the definition of the UI Toolbox section:

<Options>
  <Option name="RedefinedToolbox" value="Extended::Analysis"/>
</Options>

When I generate my MDG this doesn't appear in the XML.

Any help would be very much appreciated.

[contrem]

I have also tried manually editing the XML and adding the <Options> bit, but that didn't seem to work either.

I'm using 7.0 build 818.

[Eve]

What you've put in looks about right.

Just make sure that you have set your technology as active.  The redefined toolboxes only take effect for an active technology.

[contrem]

The technology is definitely active becasuse the toolbox is available.

I've had to make them common toolboxes at the moment, so that our BAs don't have to reselect the toolbox everytime they open a reqts diagram.

I really hope someone can help. I'm trying to get this organisation to take on EA and I need it to be as easy as possible or people will start to finbd excuses to produce diagrams in Visio or requirements catalogues in Word!!

[Eve]

The toolbox pages will be available as long as the technology is enabled.  However, only one technology can be active at a time, and that means that EA should be modelling primarily in the domain specified by the technology instead of UML.  Open the MDG Technology Manager (Settings | MDG Technologies) select your technology and press Set Active.

Alternatively select your technology from the Standard Tools toolbar.

[contrem]

The toolbox is available already, that's no the problem.

The problem is that when I open a requirements diagram the default UML toolbox opens instead of the new one that I've defined.

As I described before, even though I've added the relevant commands to the notes section of the toolbox diagram nothing appears in the XML generated.

Is this a bug?

Below is the xml generated (if that's any help):

Code: [Select]

<MDG.Technology version="1.0"><Documentation id="phl-reqts" name="Platform Requirements" version="1.0" notes="MDG Technology for Platform Requirements"/><UMLProfiles><UMLProfile profiletype="uml2">



<Documentation id="D322AEC0-9" name="Requirements_Stereotype" version="1.0" notes="MDG Technology for Platform"/>



<Content>




<Stereotypes>





<Stereotype name="Aggregate" notes="">






<AppliesTo>







<Apply type="Aggregation">








<Property name="direction" value="Source -> Destination"/>







</Apply>






</AppliesTo>





</Stereotype>





<Stereotype name="Associate" notes="">






<AppliesTo>







<Apply type="Association">








<Property name="direction" value="Source -> Destination"/>







</Apply>






</AppliesTo>





</Stereotype>





<Stereotype name="Feature" notes="">






<AppliesTo>







<Apply type="Feature">








<Property name="isStatic" value="false"/>







</Apply>






</AppliesTo>





</Stereotype>





<Stereotype name="Functional" notes="" generalizes="Requirement"/>





<Stereotype name="Implement" notes="">






<AppliesTo>







<Apply type="Realisation">








<Property name="direction" value="Source -> Destination"/>







</Apply>






</AppliesTo>





</Stereotype>





<Stereotype name="Inheritance" notes="">






<AppliesTo>







<Apply type="Generalization">








<Property name="direction" value="Source -> Destination"/>








<Property name="isSubstitutable" value=""/>







</Apply>






</AppliesTo>





</Stereotype>





<Stereotype name="Non-functional" notes="" generalizes="Requirement"/>





<Stereotype name="Package" notes="">






<AppliesTo>







<Apply type="Package"/>






</AppliesTo>





</Stereotype>





<Stereotype name="Requirement" notes="">






<AppliesTo>







<Apply type="Requirement"/>






</AppliesTo>






<TaggedValues>







<Tag name="Source" type="String256" description="" unit="" values="" default=""/>







<Tag name="DeviateFromLowCost" type="boolean" description="" unit="" values="true,false" default=""/>






</TaggedValues>





</Stereotype>




</Stereotypes>




<TaggedValueTypes/>



</Content>


</UMLProfile>

</UMLProfiles><UIToolboxes><UMLProfile profiletype="uml2">



<Documentation id="B11E0FDC-8" name="Requirements_Toolbox" version="1.0" alias="Requirements (PHL)" notes="Elements and Relationships for Platform requirements diagrams"/>



<Content>




<Stereotypes>





<Stereotype name="RequirementElements" alias="Requirement Elements (PHL)" notes="Elements for Requirements Diagrams">






<AppliesTo>







<Apply type="ToolboxPage"/>






</AppliesTo>






<TaggedValues>







<Tag name="Requirements_Stereotype::Package(UML::Package)" type="" description="" unit="" values="" default="Package"/>







<Tag name="Requirements_Stereotype::Requirement(UML::Requirement)" type="" description="" unit="" values="" default="Requirement"/>







<Tag name="Requirements_Stereotype::Functional(UML::Requirement)" type="" description="" unit="" values="" default="Functional"/>







<Tag name="Requirements_Stereotype::Non-functional(UML::Requirement)" type="" description="" unit="" values="" default="Non-functional"/>







<Tag name="Requirements_Stereotype::Feature(UML::Feature)" type="" description="" unit="" values="" default="Feature"/>







<Tag name="IsCommon" type="boolean" description="" unit="" values="true,false" default="true"/>






</TaggedValues>





</Stereotype>





<Stereotype name="RequirementRelationships" alias="Requirement Relationships (PHL)" notes="Relationships for Requirements Diagrams">






<AppliesTo>







<Apply type="ToolboxPage"/>






</AppliesTo>






<TaggedValues>







<Tag name="Requirements_Stereotype::Aggregate(UML::Aggregation)" type="" description="" unit="" values="" default="Aggregate"/>







<Tag name="Requirements_Stereotype::Inheritance(UML::Generalization)" type="" description="" unit="" values="" default="Inheritance"/>







<Tag name="Requirements_Stereotype::Associate(UML::Association)" type="" description="" unit="" values="" default="Associate"/>







<Tag name="Requirements_Stereotype::Implement(UML::Realisation)" type="" description="" unit="" values="" default="Implement"/>







<Tag name="IsCommon" type="boolean" description="" unit="" values="true,false" default="true"/>






</TaggedValues>





</Stereotype>




</Stereotypes>




<TaggedValueTypes/>



</Content>


</UMLProfile>

</UIToolboxes></MDG.Technology>


[Eve]

Adding

Code: [Select]


<Options>
   <Option name="RedefinedToolbox" value="Extended::Requirements"/>
</Options>
between </Content> and </UMLProfile> (as is done when you follow http://www.sparxsystems.com/EAUserGuide/index.html?overriding_default_toolboxes.htm) and setting your technology as active will get the behaviour you want.

[contrem]

I'd already tried that. I'd also tried overriding it for another diagram type (analysis).

The other problem I've found is that If I make them common menus then even if I remove the attribute from the toolbox the menus continue to appear as common!

When I'm making changes to the MDG xml I close and re-open EA as I'd assumed that this would reload the MDG. Is this assumption correct?

Any other ideas??

[«Midnight»]

I'd already tried that. I'd also tried overriding it for another diagram type (analysis).

The other problem I've found is that If I make them common menus then even if I remove the attribute from the toolbox the menus continue to appear as common!
...

I think at this point you need to raise a formal bug report. Search my recent posts (past day or so) for a best practice we use. Please also attach to your bug report compressed versions of your MDG project as well as the XML file you are using, with your edits as described above.

Please also remember to get back to us (the forum community) with whatever you learn from Sparx.

David

[Eve]

By all means, raise a bug report.  Although that worked properly for me, maybe something is going wrong for you and this forum isn't really the place to try to track down your problems.

[contrem]

I've submitted a bug report and I'll keep this thread updated!