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

Pages: 1 2 3 [4] 5 6 ... 34
Found using the diagram legend -> Apply auto color, works just fine so don't use a script anymore as  its a lot faster on the larger diagrams.

Vaguely remember having the same problem about  6 or 7 years ago. Might be able to do it via jscript/vbscript and the API. Some things to try;
a) Re-synch the stereotypes or
b) Set the stereotype value using stereotypeex using jscript/vbscript and the API.
c) Export to CSV then import guid, name, object_type and stereotype fields preserving the hierarchy.
d) Try making copy of respository and change the column(s) via SQL.  Usually I create a new object to see what the columns are populated so I have a half decent chance  of making mods to the DB correctly.

Sorry can't remember the details of how I fixed it- too long ago. Hope that provides some ideas you can try.

Possible because its .NET and the API can be accessed by it but not a good idea. ASP.Net is meant to run on a server. The Sparx EA API is part of the client that is designed to run on desktop/laptop. You could install Sparx EA on a server to make the API available to the ASP.Net. Just because you could doesn't mean you should. If you did you are like to have some performance or scaleability issues.

You might have to wait for Sparx Systems to release the pro cloud and web EA products.

He want's them to appear in the "Insert Related Elements" dialog. This is a valid request and I'd suggest to ask for a new feature.


Right. So a work around would be to create a Project browser JScript/VBScript that goes through the project tree and creates real composite relationships between the child and parent packages/objects.  Then you'd would see them in the insert related elements. You'd have to put a check in to make sure you don't duplicate the relationship when the script is run again later.
Simple aye?

General Board / Re: Adding Memos as a MDG
« on: May 03, 2017, 09:21:45 am »
No. That only works for <memo>. You can try it manually (type <memo> in the TV value).


Well that's just typical inconsistency isn't it?

Shame that by setting the type on attribute in the stereotype in the MDG you can't specify date, memo, spin etc just to be consistent.

General Board / Re: Adding Memos as a MDG
« on: May 02, 2017, 08:04:35 pm »
@KP Now thats interesting to know. Does it work for dates too? For example just set the initial value to '<date>'

When the objects, packages or diagrams are created the parent relationship is created automatically and stored in parent_id in the relevant table. If you need to change where the object, package or diagram is located its simple to drag and drop to another location in the project explorer.  Users don't have to fiddle with SQL just drag and drop just like they do with windows file explorer. Kind of confused about what you are trying to do or what your problem is.  ???
May start at the beginning and state what you think the problem is and what you are trying to achieve.

Suggestions and Requests / Re: Status for connectors
« on: May 02, 2017, 07:32:43 pm »
Sounds like a good idea. Theres been a couple of times I've needed that status on connectors too.

General Board / Re: Adding Memos as a MDG
« on: May 02, 2017, 07:13:36 am »
Here is how I do it.
1) Create tagged value type via config tab>Reference Data>UML Types like so
Name: MemoField
Details: Type=Memo; BaseStereotype=Class;

2) In your MDG stereotype add attribute with these details
Type: MemoField

Where <MDG_ID> should be the ID you have for your MDG.
Note the the name has to match the UML Type name for this to work. The type doesn't seem to have any effect but I set it so I can figure out what it was.

3) When generating MDG select the UML Type MemoField to export into the MDG file.

Its a bit of a pain that you have to define a tagged value type for each attribute even though they may be all of type memo but that's how Sparx EA works. Hope that helps.

If you are finding the direction of certain connector are pointing the wrong way and you need to change them in bulk the following options are available to you depending on your skill set.
a) write a jscript/vbscript to change the direction
b) write SQL to change the direction
c) providing you use Jet4 database you can open with MS Access and do a search and replace on the connector table

Note if you have a repository using native eap file (MS Access 97 aka jet 3.5) you'll need to download the jet4 (MS Access 2000+) from sparx site and transfer your project to it before you can open with MS Access 2000 or later to do option c)
 The eabase_jet4.eap file can be downloaded from here

One thing you could try is creating a classes with the attributes you want and inheriting them from your stereotype for your MDG rather than just putting them as attributes in your stereotype. I think it might provided a mechanism to get around your problem. In addition you get your attributes grouped together in the tag window with some context as a bonus which makes it more usable.

Hi, I cannot imagine that this has not been asked before, but I cannot find a corresponding thread.
(1) EA builds a hierarchy in the Project Browser by default if I move an element into another. But it does no reflect this via any kind of relation. For exampe the "reference" is not shown "Insert Releated Elements".

??? Kind of confused about what you are asking but you mention "hierarchy in the Project Browser" so I'm interpreting you are asking about the hierarchical relationships represented in the project browser. If you look in the t_object or t_diagram tables you'll find Package_ID and Parent_ID which are used to point to the  package and the parent.

(2) The same is happens for "Composite Diagram" resp. "Child Diagram".
Is there a way to find out the relations (without database-queries)? Many thanks in advance, V.

Other than looking at the project browser I can't think of any ways of finding out those hierarchy relationships unless using SQL. I've found books like SQL hacks, and recipes good for helping with SQL if thats your area of concern.

Hope that helps  :)

I use a model to generate my MDG and looking at the xml where I've added attributes to stereotypes they come out as tag values
Something like this
Code: [Select]
<Stereotype name="Application Component" metatype="Application Component" ...>
<Tag name="Pace Layer" type="enumeration" description="State the pace layer. Reference Gartner Pace layering" unit="" values="Record,Differentiation,Innovation" default=""/>
<Tag name="COTS name" type="String" description="If the app is a Commercial Off-the-Shelf (COTS) product state the common name for it." unit="" values="" default=""/>

Not sure how Sparx EA will store the data in its database as defined in your stereotype. Its uncharted territory doing it that way to me I'm afraid.

Any particular reason why you don't use a Sparx EA model to generate the MDG? Its so much more easier than messing around down at the XML level.

Uml Process / Re: ControlFlow not bi-directional
« on: April 26, 2017, 08:08:25 pm »
The OMG amateurs don't build airplanes. But airplane engineers use those amateur's spec to build airplanes. I'm flying less frequent these days.


Just to be clear I was talking about ArchiMate Standard by the Open Group and how it lacks robustness and consistency. Nothing to do with OMG or its specs. Point was there was a lack of quality that wouldn't be tolerated in some areas.

FYI  - Aircraft engineers use ISO/ IEEE /AS/ MIL-Q etc standards to build aircraft so rest assured air travel is still the safest form of travel and they ARE PROFESSIONAL ENGINEERS who design and build them.

Notations like UML, SysML etc may be used to design along with some formal methods to meet safety critical needs as well as comprehensive testing to validate.

Worked in aviation industry for 9 years where I designed and built avionic systems so had first hand knowledge of it all.

But alas we drift off topic so lets call it a day.

Uml Process / Re: ControlFlow not bi-directional
« on: April 25, 2017, 02:46:36 pm »
Whom are you talking of? Oh My God? Their error-prone PDF spec is based on "models" which merely are used to create diagrams. Amateurs? Yes, professional amateurs.

Just keep those professional amateurs away from designing and building aircraft. Just imagine if an aircraft manufacturer built a plane with the same lack of professional integrity as those guys wrote those Archimate Specs. Would you fly in it?

Pages: 1 2 3 [4] 5 6 ... 34