Book a Demo

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - SebastienRoy

Pages: [1] 2
1
Suggestions and Requests / Re: generate tables from classes
« on: August 18, 2004, 06:49:11 am »
Did you try the "table" stereotype for your classes? Perhaps the behaviour of EA in this case is the one your looking for...

2
Suggestions and Requests / self-association limitation
« on: June 30, 2004, 08:53:41 am »
Hello,
I am currently evaluating EA for the purpose of generating database-creation scripts from a datamodel written in UML. The language of the generated script is specific of the project so I cannot use the buit-in generators. So, an interesting way to generate the scripts is to first create the model, export it into an Xmi file and then to transform it in the target script by using xslt stylesheets.
First I found EA very well designed for my purpose, especially because of features like constraints, tags on classes and attributs, which can be used to modelize some very specific needs, like meta-properties...
Unfortunately, I encountered a major limitation in Enterprise Architect : self-associations cannot be bi-directional (even tought there is no such a limitation in the UML standard). The datamodels I have to modelize contain a lot of self-associations.
Is there a plan to suppress this limitation in a future release of Enterprise Architect?

Thanks

Sebastien

3
General Board / Re: Visibility of Tagged values of Attribute
« on: February 12, 2009, 09:27:31 pm »
Well, the "feature visibility" can be used to display the tagged values associated to the classes directly. Unfortunately, this doesn't display the tagged values associated to attributes.

4
General Board / Visibility of Tagged values of Attribute
« on: February 12, 2009, 04:03:06 am »
Hello,
I would like to display on the class diagram the tagged values that  are associated to attributes.
Does someone know how can I do that ?

5
General Board / Re: Corba IDL Codegeneration
« on: March 30, 2006, 12:36:24 pm »
Hello Bruno,

The switching type of the union is generated according to the value of the "switchType" tag of the class.
The cases values are generated according to the "cases" tag of the Union attributes.

Example :
  • Create a class (named MyUnion for instance) and set the stereotype to "CORBAUnion".
  • Display the tagged values window ( View / Tagged Values )
  • Select the class in the diagram or in the project browser and create a new tagged value named "switchType" and having "long" as a value
  • add attributes to your class, choose a type or not (if not it will be generated as "any"
  • For each attribute, create a tagged value named "cases" having as a value "case 1 :" for instance.
  • Generate
  • Enjoy ;-)


I didn't found a documentation for that, but I deduced it from the IDL code templates (Settings / Code Generation template. Language IDL. Templates : Class Declaration and Attribute Declaration. Stereotype : CORBAUnion)

Sebastien

6
General Board / Re: C++ "friend" keyword
« on: March 29, 2006, 02:53:43 am »
Thank you for your help.
Finally, I will avoid using the "friend" C++ facility in my code. It is not really UML complient and breaks the class encapsulation (it is however usefull because there is no "package" specific visibility in C++).

For the "initializer" tagged value, it works fine. Was it written somewhere in the documentation? I didn't find it.

Sebastien

7
General Board / Re: C++ "friend" keyword
« on: March 24, 2006, 02:35:17 am »
I have another pb : The member initialization part of the constructors is removed by EA.
Example :
Code: [Select]

MyClass::MyClass()
: myAttribute(InitialValue)
{
// code...
}

is replaced with :
Code: [Select]

MyClass::MyClass()
{
// code...
}

when I regenerate my class.
This is really a blocking problem for using the code generator.

8
General Board / C++ "friend" keyword
« on: March 24, 2006, 12:38:25 am »
Hello,
When I make the reverse engineering of a C++ class which declares functions as "friends", these functions are generated in EA model as methods of the class.
This is a real problem for the round trip.
Does anyone has a workaround for that?

Seb

9
General Board / Association description in HTML reports
« on: June 16, 2005, 05:48:32 am »
Does anyone know how to write more information in the description of association in the HTML reports?
Those written by the default html template are a little short, and I would like to have for instance, the name of the association end, the constraints, ...

Best regards

Sebastien

10
General Board / Re: How to convince my boss?
« on: November 04, 2004, 01:59:09 am »
In order to convince your boss, with objective elements, you can take a look at the following paper, which compares EA to Rational Rose :
http://consulting.dthomas.co.uk/ooad_articles_resources/Comparison_of_UML_Modelling_Tools.pdf

Sebastien

11
General Board / Concurent modification of controlled package
« on: September 23, 2004, 03:01:56 am »
Hello everybody,

I have the following problem:
I have a very large project, available on a shared directory.
Many developpers work on it at the same time
The packages are version controlled, using Visual Source Safe. The local copies of the xmi files are on local directories. Each developper has his own copy of the controlled xmi file.
Everything is ok when the modifications made by separate developpers occurs on separated packages.

But two developpers cannot modify the same package at the same time. Indeed, in order to modify a package, it must be checked out (because it is version controlled). But when a package is already checked out by a user, the other users cannot check it out too (even if SourceSafe can perform multiple check out), so they cannot modify it.
That is a big problem, because when you add a dependency to a package A (for instance add a link from a class of package B to a class of the package A), even you do not really modify the package A, you have to check it out. This his hard to manage for package that many other depends on.

Does someone know how to resolve this problem? How can two developpers modify simultaneously or add simultaneously dependencies to the same package?

Thank you if you have a solution...

Sebastien



12
General Board / Association end documentation
« on: August 24, 2004, 02:55:51 am »
My team is using intensively the "role" of the association ends in class diagrams as the name of the relation from one class to another, even if the relation is monodirectional.
We use the role to modelise different parts of some scripts generated from the models. (it's like an attribute name).

Unfortunately, the name of the association ends (the role) does not appear in the EA documentation (rtf nor html). The name of the association end only appears in the diagrams where the association is displayed. This make difficult to retriew this information.
Does someone know if it is possible to display this information in the generated documentation?
Is it possible to customize the Project View, in order to display in the tree not only the attributes of the elements but also their relationships?

Sebastien

13
General Board / Re: Xmi import : pb with constraints on associatio
« on: July 05, 2004, 05:41:56 am »
I have performed some further import tests :
    [*]In a simple model composed with two classes and one association, I define a constraint on the association (like in the code of the previous msg). I export the model in Xmi format.
    [*]When I re-import the as-generated file, the constraint on the association is still present.
    [*]In the xmi file, I remove the documentation element of the header, in order to simulate a home-generated xmi.
    [*]When I import this second xmi file, the constraint in not present in the model.
    [/list]

    This behaviour is like if there were two different xmi import modules. One is used when a EA xmi is detected (according to the header content), the other is used in the generic import case. In this last case, the constraints on associations seam not be taken into account.

    The remove part of the file is the following:
    Code: [Select]

    <XMI.documentation>
     <XMI.exporter>Enterprise Architect</XMI.exporter>
     <XMI.exporterVersion>2.5</XMI.exporterVersion>
    </XMI.documentation>


    I hope this will help you

    Sebastien

    14
    General Board / Re: Xmi import : pb with constraints on associatio
    « on: July 05, 2004, 02:04:56 am »
    The version I am running is 4.1, build 730.
    Here follows a sample of the xmi I try to import :

    Code: [Select]


    <?xml version="1.0"?>
    <XMI xmi.version="1.1" xmlns:UML="omg.org/UML1.3">
         <XMI.header>
               <XMI.header>
                     <XMI.metamodel name="UML" version="1.3" href="UML.xml"/>
                     <XMI.model name="example" version="1" href="example.xml"/>
               </XMI.header>
         </XMI.header>
         <XMI.content>
               <UML:Model name="EA Model" xmi.id="MX_EAID_F0F1B9A0_3F79_4a82_8D1A_205E33BCB323">
                     <UML:Namespace.ownedElement>
                           <UML:Class name="EARootClass" isLeaf="false" xmi.id="EAID_11111111_5487_4080_A7F4_41526CB0AA00" isRoot="true" isAbstract="false"/>
                           <UML:Package name="AssocConstraintTest" visibility="public" isLeaf="false" isRoot="true" isAbstract="false" namespace="idD387F10">
                                 <UML:ModelElement.taggedValue>
                                       <UML:TaggedValue tag="created" value="2004-06-14 00:00:00"/>
                                       <UML:TaggedValue tag="modified" value="2004-06-14 00:00:00"/>
                                       <UML:TaggedValue tag="iscontrolled" value="FALSE"/>
                                       <UML:TaggedValue tag="version" value="1.0"/>
                                       <UML:TaggedValue tag="isprotected" value="FALSE"/>
                                       <UML:TaggedValue tag="usedtd" value="FALSE"/>
                                       <UML:TaggedValue tag="logxml" value="FALSE"/>
                                       <UML:TaggedValue tag="phase" value="1.0"/>
                                       <UML:TaggedValue tag="status" value="Proposed"/>
                                       <UML:TaggedValue tag="complexity" value="1"/>
                                       <UML:TaggedValue tag="ea_stype" value="Public"/>
                                 </UML:ModelElement.taggedValue>
                                 <UML:Namespace.ownedElement>
                                       <UML:Class name="Class1" visibility="public" isLeaf="false" xmi.id="idD35DCA0" isRoot="false" isAbstract="false" namespace="idD387F10" isActive="false">
                                             <UML:ModelElement.taggedValue>
                                                   <UML:TaggedValue tag="isSpecification" value="false"/>
                                                   <UML:TaggedValue tag="ea_stype" value="Class"/>
                                                   <UML:TaggedValue tag="ea_ntype" value="0"/>
                                                   <UML:TaggedValue tag="version" value="1.0"/>
                                                   <UML:TaggedValue tag="package" value="idD387F10"/>
                                                   <UML:TaggedValue tag="gentype" value="BDS"/>
                                                   <UML:TaggedValue tag="tagged" value="0"/>
                                                   <UML:TaggedValue tag="package_name" value="AssocConstraintTest"/>
                                                   <UML:TaggedValue tag="phase" value="1.0"/>
                                                   <UML:TaggedValue tag="complexity" value="1"/>
                                                   <UML:TaggedValue tag="status" value="Proposed"/>
                                             </UML:ModelElement.taggedValue>
                                       </UML:Class>
                                       <UML:Class name="Class2" visibility="public" isLeaf="false" xmi.id="idD3AE7E0" isRoot="false" isAbstract="false" namespace="idD387F10" isActive="false">
                                             <UML:ModelElement.taggedValue>
                                                   <UML:TaggedValue tag="isSpecification" value="false"/>
                                                   <UML:TaggedValue tag="ea_stype" value="Class"/>
                                                   <UML:TaggedValue tag="ea_ntype" value="0"/>
                                                   <UML:TaggedValue tag="version" value="1.0"/>
                                                   <UML:TaggedValue tag="package" value="idD387F10"/>
                                                   <UML:TaggedValue tag="gentype" value="BDS"/>
                                                   <UML:TaggedValue tag="tagged" value="0"/>
                                                   <UML:TaggedValue tag="package_name" value="AssocConstraintTest"/>
                                                   <UML:TaggedValue tag="phase" value="1.0"/>
                                                   <UML:TaggedValue tag="complexity" value="1"/>
                                                   <UML:TaggedValue tag="status" value="Proposed"/>
                                             </UML:ModelElement.taggedValue>
                                       </UML:Class>
                                       <UML:Association visibility="public" isLeaf="false" xmi.id="idD3A2610" isRoot="false" isAbstract="false">
                                             <UML:ModelElement.constraint>
                                                   <UML:Constraint name="indexed">
                                                         <UML:ModelElement.taggedValue>
                                                               <UML:TaggedValue tag="type" value="Invariant"/>
                                                               <UML:TaggedValue tag="description" value="true"/>
                                                         </UML:ModelElement.taggedValue>
                                                   </UML:Constraint>
                                             </UML:ModelElement.constraint>
                                             <UML:ModelElement.taggedValue>
                                                   <UML:TaggedValue tag="style" value="3"/>
                                                   <UML:TaggedValue tag="ea_type" value="Association"/>
                                                   <UML:TaggedValue tag="direction" value="Unspecified"/>
                                                   <UML:TaggedValue tag="linemode" value="3"/>
                                                   <UML:TaggedValue tag="seqno" value="0"/>
                                                   <UML:TaggedValue tag="headStyle" value="0"/>
                                                   <UML:TaggedValue tag="lineStyle" value="0"/>
                                                   <UML:TaggedValue tag="virtualInheritance" value="0"/>
                                             </UML:ModelElement.taggedValue>
                                             <UML:Association.connection>
                                                   <UML:AssociationEnd multiplicity="" isNavigable="true" name="the1_" visibility="public" isOrdered="false" aggregation="none" type="idD35DCA0">
                                                         <UML:ModelElement.taggedValue>
                                                               <UML:TaggedValue tag="containment" value="Unspecified"/>
                                                         </UML:ModelElement.taggedValue>
                                                   </UML:AssociationEnd>
                                                   <UML:AssociationEnd multiplicity="*" isNavigable="true" name="the2_" visibility="public" isOrdered="false" aggregation="none" type="idD3AE7E0">
                                                         <UML:ModelElement.taggedValue>
                                                               <UML:TaggedValue tag="containment" value="Unspecified"/>
                                                         </UML:ModelElement.taggedValue>
                                                   </UML:AssociationEnd>
                                             </UML:Association.connection>
                                       </UML:Association>
                                 </UML:Namespace.ownedElement>
                           </UML:Package>
                     </UML:Namespace.ownedElement>
               </UML:Model>
         </XMI.content>
    </XMI>

    15
    General Board / Xmi import : pb with constraints on associations
    « on: July 02, 2004, 07:40:29 am »
    Hello,

    I have trouble for importing a model from a xmi file (home generated) : all is imported fine in EA exepted for the constraints on associations. The constraints on classes, attributes and even associations ends are well imported but the ones on associations are not.
    However, when I re-import an Xmi file exported by EA, the import goes well, with all the associations constraints.
    Even though the constraint element format is exactely the same (I have checked it hundred times).
    Does anybody know why this strange behaviour occures and how to import my constraints ?

    Thanks a lot

    Sebastien

    Pages: [1] 2