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

Pages: [1] 2 3
1
I strongly endorse this suggestion.

We (CSIRO) are involved in a number of collaborations within the geospatial community, using EA for model design.
These typically involve several organizations, sometimes in several countries. I'm trying to get all the projects to build on the same base model.
This requires that any tweaks made in the base are easily propagated into several different derived models.
We host the TWiki and code repository for these, and already use Subversion.
"Controlled packages" and subversion would seem to be the right solution.

2
General Board / [HELP] - Run-time association-class?
« on: February 15, 2011, 08:26:27 pm »
"An Association Class connector is a UML construct that enables an Associate connector to have attributes and operations (features). "

So in the object model that is a run-time instantiation of such a model, on the Associate connector between two objects classified appropriately either (a) it should support the assignment of attributes and operations or (b) it should allow an object classified by the association class to be connected.

I can't find a way to do this in the EA interface. Any suggestions?  :-?

3
General Board / Association-end navigability in XMI export
« on: November 24, 2008, 04:41:52 pm »
We are generating XML Schemas from UML which depend critically on the "navigability" status of association ends.
We have a test model that shows all combinations of end navigability status - see https://www.seegrid.csiro.au/twiki/bin/view/AppSchemas/FullMoonTestModels#Test_25.
However, looking in the XMI exported for this model https://www.seegrid.csiro.au/subversion/FullMoon/trunk/resources/xmi-samples/TestAS25.xml, we find

(a) every UML:AssociationEnd/@isNavigable="true" regardless of status

(b) the correct navigability is hidden as a substring in the @value attribute of UML:TaggedValue[@tag="sourcestyle"] or  UML:TaggedValue[@tag="deststyle"]

Obviously the latter is harder to use, but the former appears to be redundant/pointless.
Comments anyone?

4
General Board / Can I show connector tagged-values on a diagram?
« on: November 24, 2008, 12:45:16 pm »
By judicious use of linked diagram notes, and application of diagram settings it is possible to get most model information to show automatically on a diagram. But I am stumped on this one:

we use tagged values on association-ends and on attributes, but I can't find how to get them displayed on a diagram. Any suggestions?

5
General Board / Re: Exported model includes dependants, but should
« on: November 23, 2008, 12:41:01 pm »
Frank - yes, I agree with your analysis. But I find that stubs for the dependants are included when I export the dependancy - though only when the dependant packages are present in the model cache when I run the export operation on the dependancy. If I remove them from the model cache then the exported document is as expected. That doesn't make sense to me. \-.

6
General Board / Exported model includes dependants, but shouldn't?
« on: November 21, 2008, 12:32:00 pm »
When I run "Export package to XMI file", the exported document also includes UML: Dependency, UML: Generalization and UML: Association links that involve dependant packages and classes that are in my model cache (.eap file) but are _not_ in the package being exported. These associations are owned by the dependant, not the elements in package being exported, so surely they should not be exported as part of the XMI representation of the package of interest?

This causes us trouble because we are processing the XMI representation, and we run conformance tests on the EAStub elements to check that dependencies are known to the processor. We don't care about dependants, so if they are also present in the EAStub list our conformance checking gets much harder.  :(

7
General Board / Tagged values on diagrams
« on: October 17, 2008, 02:26:07 pm »
To support a documentation generator application, we'd like to be able to tag diagrams so the right ones are selected for the right documentation page. EA does not appear to provide an interface to set/change diagram tagged values - is this correct?

8
General Board / Attribute type identified by name, not EAID?
« on: May 15, 2008, 05:54:20 pm »
We are using EA's DDL transform to generate table schemas from a class model. In the model we use a mixture of class attributes and associations. Some attributes have complex types corresponding to other classes in the model. When the table schema is generated, these appear as table columns, where we expected to see links.

Inspection of the XMI representation of the model shows that an attribute type is given by its name, with no EAID link to the class. This is surprising. Are class attributes really not meant to link to the class definition of their type?

(We had also come across these previously in XMI processing.)

9
General Board / Resolved - Re: How to "unlock" a connector
« on: October 16, 2007, 07:19:36 pm »
Issue resolved with some assistance from Sparx.

The "source" of the connector was a locked class (as shown in the connector properties).
This was clearly an error, which must have snuck in before we more clearly separated the governance of the packages.
It was also confused by the fact that the navigability of the association was target->source, which gave a misleading hint on the diagram.  

10
General Board / Re: How to "unlock" a connector
« on: October 15, 2007, 11:21:43 pm »
More information:
notwithstanding the fact that the target class is "locked" (it is in a Controlled Package which is not checked out) I can make a new association that points to it, and I can also add tags to the target end.

Its just that an existing association is "locked", so can't be modified, and I can't figure out how (in the EA interface) to unlock it.

11
General Board / Re: How to "unlock" a connector
« on: October 15, 2007, 09:06:02 pm »
Yes, the class that is the target of the association is locked - it is in an external package (not checked-out).

But a navigable association-end is "owned" by the originating class, so it should be possible to set properties on an inbound association.
Just like it is OK to create an inbound association ...

Is this something that changed in EA recently?
We point to a *lot* of classes that are in locked packages, and have had no trouble creating/deleting/modifying the associations until now...

12
General Board / Re: How to "unlock" a connector
« on: October 15, 2007, 08:57:14 pm »
Yes - but where in the UI is the required dialogue?
Connector properties doesn't seem to have an option.
Where else?

13
General Board / How to "unlock" a connector
« on: October 15, 2007, 08:06:47 pm »
I have a model in which I need to modify the properties of a connector (specifically: add a tagged value to one end).
The required buttons in the Tags pane are not active.
Investigating further, I cannot even delete the connector - the error message says it is "locked against modification".
So this seems to the be the underlying problem.

So now I'm trying to find out how to "unlock" a connector.
I can't find this in the interface or documentation.
Any advice?


14
General Board / Convert profile to XMI (Exporting to UML profile?)
« on: July 11, 2005, 06:41:50 pm »
I have manually created a UML Profile following the documentation of the XML document format for UML profiles.
However, some of my collaborators don't want to be messing with raw XML, so it would be convenient to be able to convert the profile to XMI so that it can be imported as a model and then tweaked using a diagram view.

EA help gives the instructions how to export a package as a UML profile, but not the reverse direction.
Is this possible?

Pages: [1] 2 3