Messages

1

General Board / Re: Overriding default toolboxes in an MDG

« on: November 14, 2007, 06:44:43 am »

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

2

General Board / Re: Overriding default toolboxes in an MDG

« on: November 13, 2007, 01:33:06 am »

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??

3

General Board / Re: Overriding default toolboxes in an MDG

« on: November 12, 2007, 01:19:37 am »

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>


4

General Board / Re: Overriding default toolboxes in an MDG

« on: November 09, 2007, 02:34:55 am »

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!!

5

General Board / Re: Overriding default toolboxes in an MDG

« on: November 08, 2007, 03:11:52 am »

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.

6

General Board / Overriding default toolboxes in an MDG

« on: November 08, 2007, 03:02:50 am »

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.

7

Automation Interface, Add-Ins and Tools / Re: Does the EA BPMN MDG fully support BPMN 1.0??

« on: October 31, 2007, 09:20:20 am »

Thanks for your replies. It all makes perfect sense now! All I need now is for EA to import/export BPMN diagrams as BPMN rather then XMI and I'll be able to convince this organisation to use it for all our modelling!

8

Automation Interface, Add-Ins and Tools / Does the EA BPMN MDG fully support BPMN 1.0??

« on: October 26, 2007, 03:13:34 am »

I've got the latest version of EA (7.0.817) and have just started to look at the BPMN profile. Comparing what seems to be available with the BPMN 1.0 spec there seem to be some things missing from EA, the omissions seem to be mainly around the stereotypes for the different objects.

For example, in BPMN, EA supports the three Flow Dimensions for an Event (Start, Intermediate, End), but doesn't seem to support the Tyep Dimension (Message, Timer, Error, etc).

Am I missing something?

9

Automation Interface, Add-Ins and Tools / XMI and BPMN

« on: October 26, 2007, 03:32:55 am »

My organisation would like to perform all of the design activities going forward within EA.

We are also currently looking at BPM tools.

Ideally we would like to be able to design the processes in EA and be able to export them to the BPM tool. It would also be good if we could make changes to the process in the BPM tool and import those changes back into EA. (The BPM tools that we are looking at both support BPMN, but not XMI)

Would I be right to assume that the standard XMI export/import mechanism will not be able to handle either creating BPMN or consuming it? If this is the case, could I run a transformation from XMI to BPMN and vice-versa? Finally, if it is possible to transform between the two formats, how do I work out how to do it!!!!