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

Pages: 1 2 3 [4] 5 6 ... 39
Bugs and Issues / RTF Template Selectors based on package stereotypes
« on: October 24, 2017, 09:14:55 pm »
Does anyone know if this should/is work.

Package:review session:KB-SfS ESC ReviewSessionPackages
Package::KB-SfS ESC Packages

Currently I assume that this is just another issue, where package elements are constraint without reasons.

Bugs and Issues / Re: Case Sensitive Problem with Searches
« on: October 24, 2017, 06:04:02 pm »
This is now confirmed to be a bug (with enquiry no 17107268) by Sparx and will be fixed eventually.

I am with qwerty, and I use the profile helper whenever I am able to.

In this case I just was not able to, because I was looking for a way to define with the profile helper a tag using a Tagged Value Type Format. This I found by adding strings like <memo>,  <data> in Default Value.
But what on earth is the difference in putting a string in the Default Value field of the profile helper in comparison to put the string in the Initial Value field of an attribute?

At the end I can say that there is no feature at all in the profile helper to define a tag with a tagged value type of type <time> and most others, as defined here:

You have to go outside, defining uml tagged value types and afterwards, when using the profile helper again you have to know the “Predefined” does not refer to the major content you find here
but more to the content here:

I have a "not so simple MDG" and I maintain that for years. I know and sometimes forget most pitfalls and sources of errors and there are a lot, even when using the helpers.
It is far away from beeing such simple as "Use the helpers and all works fine".

Anyhow, I am absolutely sure, that with not much effort the power of MDG could be made much handier for creation.

Bugs and Issues / Re: Test, Issue, Defect,… Requirement dependencies
« on: October 20, 2017, 06:15:53 pm »
Yes, there is a lot of power in EA, but too often it cannot be used just because of some unnecessary constraints implemented, some very small stuff not implemented, some inconsistency and so on.
If e.g. 10% of the efforts spend for releases would focus in such stuff, it would help a lot.

Examples for me are:
Remove the blocking to handle Packages like other elements where not needed (e.g. Specification View, Kanban,..)
Show really the SQL results in Matrix rows and columns
Remove the poor (almost useless) element selection dialogs e.g. Add/Create Link… by the existing useful  once you find when setting a classifier or a property type.
Solve design shortcuts choosen years ago like this forum topic.

Bugs and Issues / Re: Case Sensitive Problem with Searches
« on: October 20, 2017, 12:00:53 am »
I have personally no problem with that issue.
However it is a bug, I reported to Sparx and I typically report the bug here and create a “Sparx Bug Report” linking to that forum issue.

Bugs and Issues / Re: Test, Issue, Defect,… Requirement dependencies
« on: October 19, 2017, 11:31:09 pm »
Hi Uffe,
Do you know a way that I can have stereotyped "Defects" and "Requirements" where the Properties/Type list is independent from each other. I remember somehow that I added in General Types/Requirements some entries (stereotype names) to be able to switch my requirement stereotypes with the Properties/Type field. And I know, that I got it managed to show not all what is defined General Types/Requirements.

Bugs and Issues / Re: Case Sensitive Problem with Searches
« on: October 19, 2017, 11:11:25 pm »
That probably depends on the case sensitivity of the underlying DB
I do not think so, because in the Model Views dialog I saw both and in fact it is the same DB.

Bugs and Issues / Case Sensitive Problem with Searches
« on: October 19, 2017, 10:54:29 pm »
I realized the problem by doing the following:

I had a search let say with name My_search and I wanted to have MY_search
So I copied My_search and named the copy MY_search
However afterwards I found only MY_search in the list when trying to delete My_search.
When trying to assign a search to a Model View I found both
After returning to Model Search, selecting MY_search and pressing delete, My_search was deleted but MY_search was still there.

Well finally what I wanted to achieve at the end, but not what I sad EA to do.

This works for time and maybe for some else, may be for date and memo as well, but for date and memo you can do something else.

-for date and memo you can put <date>/<meme> in the Attribute Initial Value field.
-for using other predefined tags you have to define a Tagged Value Type for each and you have to put the name of that Tagged Value Type as Attribute Name
If you what to use Enums you have to put that in the Attribute Type

So if your goal is to entirely confuse the users, I recommend to use the Stereotype and Alias field as well to come to end. ;)

Hi Geet,
SfSTime is my own type I defined with 2Detail" Type=Time;.
I thought that was what you suggested.

Hello Markus,
To bring you to the right track.
The API seems to have no method, that allows you to make an action a call behavior action or at least to define by API what it calls by that action.

So, if you do not have an API, you have to change your model by changing DB content directly.

By doing so, you will see some ugly things in the EA DB design like the stuff above, what shows that the relevant data for your issue is stored as some kind of structured text in a description field of a db table.

Now I added under UML Types/Tagged Value Types a tag with name SfSTime having a Detail Type=Time;.

In my stereotype definition I tried to use that by:
Initial Value = SfSTime
Initial Value = <SfSTime>
Type= SfSTime

Nothing is working in my project using that mdg.
What works is using SfSTime in my project for manual created tags. :'(

Bugs and Issues / Re: Test, Issue, Defect,… Requirement dependencies
« on: October 18, 2017, 09:55:39 pm »
Making sense would make sense!

Bugs and Issues / Test, Issue, Defect,… Requirement dependencies
« on: October 18, 2017, 09:29:06 pm »
Test, Issue, Defect, Requirement are some EA build in elements.

The major difference in comparison to other stuff like classes is that you can set a Type rather than a Stereotype when opening the property dialog. However the type is somehow a stereotype.  :-\  So far so good.

However there is some stereotype dependency looking strange to me.
In my MDG I have define some stereotyped requirements and when I create a requirement I can select one of those stereotypes as type of my requirement. Apart of thinking why it is called type and not stereotype it is good for me.

However, when I create other stuff like Defect, Issue I see the same Types/Stereotypes I have created for requirements only.

So it seems to me that Test, Issue, Defect is regarded as a kind of Requirement by EA.
What is the sense of that? Any idea?
From my perspective it is just nonsense!

Ok! I will give it a try and come back!

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