Messages

1

General Board / Re: EA Standard Security - Corporate version

« on: February 03, 2010, 12:20:38 am »

Thanks Geert... I think I have this working now.  Based on some experimentation and your comments, I locked the root nodes that I had, all of them and it appears one can't create new ones - unless you are of the group that I checked those out to.  Which suits me fine.

I hadn't thought about the import, but will tackle that if/when I get sophisticated enough users and provide guidance on where I'd like their models to go.

Ultimately I don't want to be too autocratic, and we are a small group.  Just trying to help organize!

thanks - cwt

2

General Board / EA Standard Security - Corporate version

« on: February 02, 2010, 02:54:14 am »

Is there a way to manage the creation of a root node using the permissions and security model in standard mode?

I can manage packages simply by having an "admin" user set a group lock on packages, and adding users to that group giving them access to that package (and all of its children).  I think that requires Manage Elements permission (which the group has) which I also think gives you the permission to create Root Nodes - which I don't want...

I have set up a number of root nodes myself - checked out to admin only so that I can partition the model "appropriately," and want to manage those - managing existing ones is easy, not allowing new ones seems tougher.

Any ideas?

cwt

3

General Board / Re: Applying Auto Names to Elements

« on: February 03, 2010, 12:17:52 am »

Good work - I may borrow this as I would love to assign auto-names based on my stereotypes of Requirements, like Assumptions or other categorizations

Since the auto-number is only using an already supported field that's not a key (as in DB FK), I think you are good to go!  In fact, one downside is you can change these in the Properties...

cwt

4

General Board / Re: Applying Auto Names to Elements

« on: February 02, 2010, 02:49:48 am »

You can try export to CSV, add the numbers through Excel or whatever, then import back to your model - preserving the GUIDs per this.

http://www.sparxsystems.com/uml_tool_guide/uml_model_management/csvimport.html

Then turn auto-name on and set the number to +1 from your highest one to date.

5

General Board / Re: List of values for TaggedValue and Stereotypes

« on: December 04, 2007, 02:47:21 pm »

I have tried this, and other techniques today and am stuck.  I have a profile that I import (Resources) into a model.  I can create my new element (in my case from the profile a Business Process) and I can see the associated tagged value (Process Level; values = One, Two; default=One).  however, I don't get a drop down list, in fact I can't even edit the value of the tagged value.  If I set the type of the attribute to string, I can enter whatever I want.

My profile has a a Business Process stereotype, extended from a metaclass with an attribute Process Level.  This attribute is of type: pTypes; Initial Value: one; no stereotype; Scope: public.  pTypes is an enumeration with the attributes of One and Two.

What did I miss?

thanks

cwt

6

Bugs and Issues / HTML Template problem

« on: December 14, 2012, 01:14:57 am »

I am trying to modify a new template (from the default) and noticed that for operations parameters, the #STEREOTYPE# tag doesn't appear to get any value.  I have stereotyped operations parameters (path, query) and they can be reported on via RTF, but not in HTML Report.  Any ideas what I might be doing wrong?  In fact, even in the default HTML Report this doesn't work - see "Content - Operations Parameters Items" which has this:

Code: [Select]

<tr id="param#GUID#02" style="display: none;">
      <td width="50"><strong>Stereotype: </strong></td>
      <td>#STEREOTYPE#</td>
</tr>
There never is a value displayed...

cwt

7

Bugs and Issues / Re: Javascript error in Generated HTML report

« on: December 14, 2012, 01:09:22 am »

I get the same error(s), but have found if I select a link (right click) and open in new tab, it all 'works.'  Not an answer, just a work around and confusing.  I have also found it seems to work better if I have an initial diagram in my report.

I use Firefox 14.0.1 on Windows 7...

8

Automation Interface, Add-Ins and Tools / Re: Access to element->advanced->Parent in SDK

« on: April 25, 2013, 02:49:01 am »

That's it!  Thank you.

Chris

9

Automation Interface, Add-Ins and Tools / Re: Access to element->advanced->Parent in SDK

« on: April 24, 2013, 02:06:05 am »

This seems to be true if the Generalization/Realization is an actual Element, if it's not an element, there don't appear to be "real" connectors (as Elements).  This happens when the "Accept classifier if not in model" is checked/set.

Curious as to where that string (in my example normalizedString) is stored.  In both cases, that string (classifier name) appears in the element on the diagram - so it's there somewhere!

cwt

10

Automation Interface, Add-Ins and Tools / Access to element->advanced->Parent in SDK

« on: April 24, 2013, 12:36:32 am »

I am trying to access the value/type of a relation that I can see from a model element that is in a diagram.  If I right click on that element->advanced-Parent, I get a dialog "Set Parents and Interfaces."  In this dialog there is a list of Relations under the heading Type Details.  There is also a check box that says to "Accept classifier if not in model."

I have elements that have a 'row' there, but through the SDK I can't seem to find this information... the row values are:
Classifier: normalizedString
Type: generalizes
Owned: No
Package: <none>
So I assume (and confirmed) that normalizedString is not an element in my model.

This got populated via an import of a WSDL, and the element is stereotyped as <XSDtopLevelElement> if that matters (I have removed the stereotype and the parent relation remains). The XSDtopLevelElement properties (double click on the element) show 'normalizedString' as the XSD elment type.

I've tried things like connectors (there are none), RelationSets, classifierType/Name all to no avail.  Any ideas?  (Note: I can't seem to find this from EA using the the UML view of the elements properties either...)

cwt

11

Automation Interface, Add-Ins and Tools / Create a Bi-Directional Association (Profile)?

« on: July 12, 2012, 11:58:32 pm »

I'm trying to create a profile stereotype of an Association (or Connector) that I would like the initial Direction to be Bi-Directional, the default on the metaclass is "Source -> Destination."  I have extended the metaclass with my stereotype and tried setting the attribute initializer (which doesn't show the metaclass attribute direction) and that didn't work.  I tried setting the attribute initial value in the metaclass and that didn't work.

Is there a way to set the direction for my stereotype?

Thanks
Chris

12

Automation Interface, Add-Ins and Tools / TOGAF MDG Add In doesn't install

« on: May 04, 2012, 10:05:06 pm »

I'm not sure if this is the correct forum for this, so please advise.

We have purchased the TOGAF add-in for the latest EA.  We have installed EA on a Windows 7 machine (requires administrator rights to do so) to be shared by all users on the machine.  We also installed the TOGAF add-in.  All seems to work fine from the user account with local admin rights.  Logging into a user account we can run EA (at least start it, create a project, not an exhaustive test yet) however the TOGAF add-in capabilities are not available.  Attempts to run the add-in installer-either run as administrator or run and prompted for credentials just does not run.

How can we install the TOGAF for a user?

Thanks
Chris

Windows 7 Enterprise, EA 9.3 (932), MDG Technology for Togaf v2.0

13

Automation Interface, Add-Ins and Tools / Using RTF for AssociationClass Properties

« on: September 24, 2010, 04:00:01 am »

I have set up a number of associationClasses in my model.  For example there is Class A and Class B, and an associationClass C on the connector (association) between them (created using the Class Relationships icon for associationClasses).  I'd like to be able to report on the source/target of the connector "with" Class C - I can't seem to make the RTF generator understand that - in fact, the properties of Class C has no links (which probably explains why I can't report on them).  So... how can I report the fact that Class C is an Association Class on the Association connecting Class A to Class B?

Class A's links include the association to Class B (and vice versa), but nothing at all about Class C.  The connector doesn't have a way (in reporting) to duplicate the information that it displays via the (right click) AssociationClassProperties - which is what I'm after.

What am I missing?

thanks

Chris

14

Automation Interface, Add-Ins and Tools / Generate RTF - linked element feature

« on: July 28, 2010, 11:08:40 pm »

I have created a set of Classes.  I have created associations between them and am using the linked element feature on the connections to specify an Attribute on one end of the connection.  That all seems to work fine, at least in the diagram.  It's interesting to note that I can find "anywhere" the details for this connection.  The Class Links (tab) shows the class to class connection, the association properties is plain - no mention of the linked element.

While I can live with that, I am trying to generate "a report" that would listen these connections, using the RTF Generator.  It sort of works, however IF there is lined element on one end of the connector, I can't seem to get the Element Name to display, just the linked element name.  For example, Class1 -> Class2.linked element to Attribute1... the report writer will generate:
Connector / (source element) Class1 / (target element) (linked element) Attribute1, the Class2 is not there.  If there is no connection to a linked element, you would get Connector / (source element) Class1 / (target element) Class2.

What am I doing wrong?

here is the section of the template
element >
{Element.ParentPackage}.{Element.Name[ch25981]
connector >
 connects {Connector.Direction} {Connector.Stereotype} {Connector.Name[ch26237]
source >
element >
from {Element.ParentPackage}.{Element.Name}
< element
linked feature >
({LinkedSourceFeature.Name})
< linked feature
< source
target >
element >
 to {Element.ParentPackage}.{Element.Name[ch8317]
< element
linked feature >
({LinkedTargetFeature.Name})
< linked feature
< target
< connector
child elements >
< child elements
< element

Chris

15

Automation Interface, Add-Ins and Tools / Assocation Properties in a Profile

« on: June 12, 2010, 02:11:30 am »

Is there a way, and if so how, to set properties of a Source Role and/or Target Role in a stereotyped association?  I have a stereotype class extending the meta-class Association, working just fine.

Specifically I'm trying to create a <has one> and a <may have> association with appropriate source and target role multiplicities.

I'm sensing it may be some attribute of the stereotyped association in my profile?  perhaps _SourceRole.Multiplicity = 0 or something?

thanks

cwt