Messages

1

Bugs and Issues / Document Generation - Fragment in Diagram Element section

« on: March 03, 2017, 03:11:41 am »

Hello,

To able to deal with the AS-IS and TO-BE architecture, we wanted the TO-BE in some diagrams stacked at the same place in the project browser, while the objects shown in these diagrams are elsewhere in the project browser. To be able to do that and generate a document showing all of our changes and the TO-BE architecture, we used a trick to call fragment from the "Diagram Element" section like you can see here :



We have some down side of using this, but this is highly manageable compared to the benefits we have by doing this. Since calling Fragment from "Diagram Element" section seems to be disabled, I want to know if its a bug or its a feature. Then, I want to know if I should do a feature request so our template will be forward compatible with the next version of EA.

We are using EA 12.1229 at the moment.

Thanks for your help,

Janic

2

Suggestions and Requests / Database Builder and Scaling

« on: January 27, 2017, 09:04:22 am »

Hi,

We tried to see if we could replace ER/Studio Enterprise Team Edition with Enterprise Architect (v12.1.1229) using the Database Builder.

We had two issues I couldn't resolve :

First issue, scaling. ER is a Business Intelligence Tool so it got a lot of tables in one BD (it might be the cause of our problem, of well). We were able to create sub packages in the Project Browser to make logical group of tables, but we couldnt use that package hierarchy in the Database Builder. So we had the 700ish tables flat lined in the builder view, we couldn't use the hierarchy we just created. For example : show the differences on a group of tables nested under a package created in the project browser ans such. In ER studio, you can create multiple views or packages to bundle your table.

Second issue, when we trying to show differences for one Table only, using ODBC for Oracle, EA couldn't resume. Not sure why, it was only one table...

Unfortunately, we won't be able to replace ER Studio this year...

Anyway, thanks for this great tool by the way, your doing a great job!

Janic

3

Bugs and Issues / Re: BPMN Links Geometry - Strange Behavior between two versions

« on: May 26, 2016, 05:57:02 am »

Ok, we might try a shot at your suggestion. Thank you qwerty.

4

Bugs and Issues / BPMN Links Geometry - Strange Behavior between two versions

« on: May 26, 2016, 12:43:56 am »

Hello guys,

First of all, we made a ticket to Sparx to get some help and Sparxians don't have an explanation nor a solution to provide.

We are making a major version upgrade from 9.3.931 to 12.1.1229.

We found in about half of our 3200 BPMN diagrams strange behavior of the BPMN links geometry. Everything was fine in EA9 and now we got that. Here is a few screenshots EA9/EA12.

EA9vsEA12
EA12 examples

Do you guys have any ideas how to :
-What is causing this to happen? (Options, etc)
-If we can detect that behavior by query or by a script?
-If we can correct that beside doing them one by one manually (like the Sparxians told us to do sadly)

We did estimate that it would take one persone about 15 days to do the job manually.

Thanks for your time and your help.

5

General Board / Re: Wrong Stereotype applied to an element

« on: January 12, 2016, 08:25:42 am »

Yeah, I did test that. Even if the good profile and stereotype are selected, in the DB, the reference in the t_xref is on the wrong stereotype. So the tagged values aren't synced. I believe that selecting the good profile and stereotype in the element's stereotype dropdownlist only put the good spelling of the stereotype in the textbox. Then, EA tries to match it with a known stereotype and I get the same problem as above.

Thanks,

Janic

6

General Board / Re: Wrong Stereotype applied to an element

« on: January 12, 2016, 02:15:43 am »

Ok, thanks for the reply KP.

That might explain a lot of things that we are experiencing with an UML Profil. So manually typing new objects' stereotype is not a good idea, because EA can apply a much larger range of meta class than the one used in the UML Profile.

We always got to use the UML Profil Toolbox (or the ressource view, or ...) to create elements associated to the UML Profile.

Thanks again, it is much appreciated.

Janic

7

General Board / Re: Wrong Stereotype applied to an element

« on: January 09, 2016, 08:56:41 am »

Yeah well, I think it will be much simpler to just clean the unwanted stereotypes.

Thanks for your time q.

Janic

8

General Board / Re: Wrong Stereotype applied to an element

« on: January 09, 2016, 06:59:54 am »

Hi there, thanks for the reply q.

I just ran into a strange behavior that is similar to my previous post. Lets say we still have the same two stereotypes in the t_stereotypes table :
Stereotype name|AppliesTo (BaseElement or metaClass)
librairie|component
librairie|class

When I create a new "component" and type in the stereotype "librairie", it gives the group "librairie*class" instead of "librairie*component". Why would it match the wrong stereotype with the wrong object's base class?

Any hints on this? I know I could get rid of the undesired stereotypes, but i got 60 users, so there will always be undesired stereotypes created until we enable the built-in security feature.

So, in this case, is it a bug or a feature?

Thanks,

Janic

9

General Board / Wrong Stereotype applied to an element

« on: January 09, 2016, 04:11:08 am »

Hi there,

I need your input please. I want to know if its a feature or a bug. I tested it in EA 12 and this is the behavior that I got. I browsed the web and this forums and couldn't find anything. Here it goes :

We have an UML profile (without MDG technology for some reasons) and I was wondering why some of our elements weren't getting theirs taggeds values synchronized with the desired stereotype. I found why : They had the good stereotype with the correct spelling, but the metaclass (BaseElement in EA) related to the stereotype isn't the good one. Here is some explanations :

When you look into the t_stereotype table (or in Project>Settings>UML Types from the EA UI), you know that a stereotype is a group of a stereotype applied to a metaclass (BaseElement in EA). We happen to have some groups of the same stereotype with different BaseElement. For example :
Stereotype name|AppliesTo (BaseElement or metaClass)
application|component
application|class

So when an user drag a new "Class" in a diagram and type in "application". EA gives the group of "application*class" to this element. But using a class to define an application is wrong. It has to be a component. So you got to change the type to Component. (Element>Advanced>Change Type)

The "Change type" doesn't seem to change the stereotype group "application*class" to "application*component". Since the first combination is not related to the UML profile, these objects won't get theirs tagged values synchronized.

So it is a feature or a bug?

Thank you for your help,

Janic

10

General Board / Re: Viewing instance when deleting a classifier

« on: December 24, 2015, 08:13:09 am »

Wow, that just made my day.

Didn't know that option existed!!

Thank you very much!! No SQL needed!!

Janic

11

General Board / Re: Viewing instance when deleting a classifier

« on: December 24, 2015, 06:30:48 am »

Well, it works on SQL Server. You are right, the JET engine probably do not support temporary table. I would have to edit it so it would work on JET engine. That will be next year

Thanks,

Janic

12

General Board / Re: Viewing instance when deleting a classifier

« on: December 24, 2015, 05:31:29 am »

Hi there,

Thanks a lot for the info Geert. I upgraded your SQL search query. A lot simpler to sort by package hierarchy (Model root to children package) when it is in a column. I drill down to 11 packages. It is really useful when you want to show objects that are under a certain package. You can add few "like" clauses with package name to specify what you want to get.

Give it a try

Thank you

Code: [Select]

select * from
(select 
instance.ea_guid as CLASSGUID, instance.Object_Type as CLASSTYPE, instance.name as InstanceName, classifier.name as ClassifierName ,
case when package_p11.name is null then '' else package_p11.name + ' > '  end +
case when package_p10.name is null then '' else package_p10.name + ' > '  end +
case when package_p9.name is null then '' else package_p9.name + ' > '  end +
case when package_p8.name is null then '' else package_p8.name + ' > '  end +
case when package_p7.name is null then '' else package_p7.name + ' > '  end +
case when package_p6.name is null then '' else package_p6.name + ' > '  end +
case when package_p5.name is null then '' else package_p5.name + ' > '  end +
case when package_p4.name is null then '' else package_p4.name + ' > '  end +
case when package_p3.name is null then '' else package_p3.name + ' > '  end +
case when package_p2.name is null then '' else package_p2.name + ' > '  end +
case when package_p1.name is null then '' else package_p1.name + ' > '  end +
case when package.name is null then '' else package.name end
as 'Package'
from (((((((((((((t_object instance
inner join t_object classifier on instance.classifier = classifier.object_id )
inner join t_package package on instance.package_id = package.package_id)
left join t_package package_p1 on package_p1.package_id = package.parent_id)
left join t_package package_p2 on package_p2.package_id = package_p1.parent_id)
left join t_package package_p3 on package_p3.package_id = package_p2.parent_id)
left join t_package package_p4 on package_p4.package_id = package_p3.parent_id)
left join t_package package_p5 on package_p5.package_id = package_p4.parent_id)
left join t_package package_p6 on package_p6.package_id = package_p5.parent_id)
left join t_package package_p7 on package_p7.package_id = package_p6.parent_id)
left join t_package package_p8 on package_p8.package_id = package_p7.parent_id)
left join t_package package_p9 on package_p9.package_id = package_p8.parent_id)
left join t_package package_p10 on package_p10.package_id = package_p9.parent_id)
left join t_package package_p11 on package_p11.package_id = package_p10.parent_id)) t1
where
t1.Package not like '#WC#obsolete#WC#'
and t1.ClassifierName like '#WC#<Search Term>#WC#'

13

General Board / Re: Viewing instance when deleting a classifier

« on: December 24, 2015, 04:01:25 am »

I use the Traceability windows (Ctrl+Shit+4) to find instances of a classifier. You can jump to each instance of a classifier by right clicking an instance in the Traceability window and choose Switch to Related Element. Make sure you have Classifier selected in the selection list at the top of the Traceability window.

Hi there, thanks for your response. From what I understand, you see see your instances in Tracability view because you do make a relationship between your classifier and your newly created instance?

Since we dont make that relationship, I dont see any of my classifier in Tracability view. So, I got to run some sql query to get the list of my instances for a given classifier.

I got a question for the community, it is common to make a relationship between the instances and the classifiers? I dont find anything on the UML stating that explicitly.

Thanks for your time,

Janic

14

General Board / Re: Viewing instance when deleting a classifier

« on: November 27, 2015, 05:30:29 am »

Thank you for your answer. Am I the only one that would need that feature?

Janic

15

General Board / Viewing instance when deleting a classifier

« on: November 24, 2015, 12:21:13 pm »

Hi there,

Is there a way to view the instances of a classifier using the UI? (beside doing a "find in all diagrams" on the classifier or doing a sql query on the ClassifierID on the t_object)?

I want to be sure that I don't delete a classifier that has multiples instances that might not appear in diagrams...

If you ask me why I need to do that, its because we have a large project with a lot of users and there is sometimes duplication between classifier. So from times to times, we need to merge (manually because we are using 9.3) these classifiers and instances.

Thanks for your time,

Janic