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.

Topics - RIL

Pages: 1 2 [3]
I have a problem with TaggedValues associated with Roles. The TVs which I defined for my own extended stereotype role (bold.role) doesn't "attach" to the roles, only to the association. See screenshot far below.

I defined the stereotype (called <<bold.role>>) and added the TVs in the same manner as I did successfully with Classes, Attributes and Associations, (that is, Stereotype(bold.role)--extends-->MetaClass(Association) ), but for some reason the TVs doesn't show up as one set of TVs for each role.

I manually ensured that the roles has the correct stereotype, then I updated the model with "Sync Tagged Values and Constraints...", as usual, but the result is still as shown in the screenshot below.  If TVs can't be attached to individual Roles via the stereotype, then this is a show-stopper for me.

Q: What am I doing wrong?

// Rolf Lampa

Fig. The down-arrow indicates that the TaggedValues for roles should show up under respective role, not under the association:

I can't find any code substitution for the property "Advanced \ isDerived" in the association dialog.

Q: Am I missing something?

What I do find though is that association Roles has a code substitution for derive (%connectorSourceDerived% and %connectorDestDerived%), but the the association itself doesn't seem to have any.

I can derive the status for the association itself, like so:
    $isDerived = %connectorSourceDerived=="T" or connectorDestDerived=="T"%
    [/list]... but this may confuse the modeller user which can explicitly set the derived status to True/False in the dialog.

    And furthermore, if only the Role(s) are set do Derived (and the association is indirectly interpreted by the Code Gen as being Derived) that is not displayed in the diagram with a slash prefixing the /association name.

    This seems to me like something that needs to be fixed.

    // Rolf Lampa

    Hi again all,

    When I try generate a special code format I need to collect all associations in the model into a collection outside the context of classes, but how do I use the list macro to retrieve the "Linked Attributes" when in the scope of the File

                  %list="Class" @separator="\n" @indent="            "%
                 %list="Attribute"... linkAttAccess!=""%  // <- only associations

    // Rolf Lampa

    Hi all,

    I've searched the help but fail to find the answer to the following question:

    1. Is it possible - using only a Profile* - to configure my own stereotyped class to instruct the attribute dialog to automatically set only a specific <<stereotype>> for the attribute instead of the std (un-stereotyped) ones when adding new attributes?

    1.b. Same Q for operations and associations.

    1.c. Same Q for right-click menus when adding from the diagram view.

    // Rolf Lampa

    * (Yes, I plan to make a MDG Technology later)

    Hi all EA experts,

    Coming from Rational Rose I'm trying to learn some new EA terms (I'm reading the ea docs but I haven't read through all of it yet), I would like to make a "set of tools" consisting of different sets of Tagged Values, even following a naming convention with a prefix for each TV. Like so "ToolName.TaggedValueName=Value".

    My questions:
    • 1. What term - In Rose such a set of TVs would be named a "Tool". Is the EA equivalent a Profile?

      2. Predfined TV values - Is it possible to define enumerations, that is, predefined value lists, for individual specific TaggedValues (enums associated with a list of TV names)?

      3. Multiple ToolSets - I would like to "bundle" both such a TV-tool-set and a specific code gen template (a customized Delphi template). Could all that be achieved through defining a Profile, which can be used /activated only demand for new models?
    // Rolf Lampa

    Hi again,

    1. Is it possible to somehow export a CodeGen Template to disk?
    2. Is it possible to copy an existing CodeGen Template (as to start from when customizing my own)?
    3. Is a "Profile" the way to go to make any custom CodeGen Templates available at any time ? (It looks like it stores my CodeGen Templates only in the model in which I created them. Is that correct?)

    // Rolf Lampa

    Diagram Image Generator - Is it possible to (via API) fill in scenario lists and from the scenario autogenerate a flowmodel (this should be possible) and then - and this is my Q - fetch an image of the flow diagram to be used outside of EA?

     - Has someone already tried anything like that? That is, an EADI Server.  ::)

    What for? - What I'd like to achieve is using EA to provide with some diagrams based on legacy excel data, where it would make sense to let Excel export and populate Steps for Scenarios and get back the autogenerated flow diagrams. Or, of course, the images of the diagrams.

    // Rolf Lampa

    After reading and trying for many hours (doing well with most other elements) I still have difficulties retrieving constraints from classes and attributes.

    From the documentation i gather that constraints can be listed. But the following %list% expression returns nothing but empty strings (although I defined "test constraints" within the context, both pre- and post-process and OCL constraints):

    $sConstraints = %list="Constraint" @separator="\n"%

    What am I doing wrong?

    // Rolf Lampa


    Summary: I fail to be able to retrive Tagged Values from Attributes. Why?

    I tried to retrieve TaggedValeus from an Attribute in my SoonToBe CodeGenerator, but it seems like the macros doesn't return any (existing) TV data from my Attributes.

    I found the following macros in the help section "Macros, Code Template Syntax" with the title "Tagged Value Substitution Macros":
    Code: [Select]

    These were all called in the "Attribute Declaration" template, but I get only empty strings as the result. What am I missing? :( :

    Code: [Select]
    Any hints?

    // Rolf Lampa

    Pages: 1 2 [3]