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 ... 22 23 [24] 25 26 ... 50
General Board / Re: Common Text Element
« on: November 24, 2016, 08:32:46 pm »
Does that occur in any toolbox or in a specific toolbox?

General Board / Re: Common Text Element
« on: November 24, 2016, 07:54:18 pm »
Do you mean "Note"?

Hi Simon,
I have neither seen a server db nor a eap corruption as well (most of the time I work on a server db).
Now I have it again and this makes we wary about that.

My EAP is on local drive, and in this second case it happens when checking out data from subversion. By opening the eap with ms-access I could repair it.
After repairing the checkout worked!?!?

However I still have the suspicion that these issues have something to do with my redefining of structural element (I mean this which behaves somehow odd.

Due to the fact that I have more work in this area I will see if I can find out something more concrete.

Yes, I have gone to my backup.
In this case my data is in SVN so it is easy for me to start from a working point.

But the model data contain assets and will be distributed to a MS SQL DB later.

Up to now over several years I did not manage to make my DB corrupt (stop the world) just by doing modeling. However when distributing those stuff to the MSSQL DB I see some risks that the same happens maybe very frequently on that DB later ("mystic area").
MSSQL restores in my company takes hours or even days. Having this scenario frequently will make my users crazy.
So I would be interested to know if somebody knows similar cases were just doing modeling causes such disaster.

I did some modelling in the “mystic EA area” by refining some properties (structural elements).

By doing so I got an error message “ Unrecognized database format xyz.eap”. When opening the model anew this error remains.
So my database I corrupted by modelling. Any idea to fix that?

Bugs and Issues / Re: How to reference a diagram in documentation
« on: November 22, 2016, 01:43:17 am »
Well, when I need a document I do entirely generate that from EA, so I have no experience about that, but maybe this can help you:

Bugs and Issues / Re: How to reference a diagram in documentation
« on: November 22, 2016, 01:14:09 am »
What is a document for you?
E.g. just a MS-Word file you edit manually or a WS-Word file you generated from EA or a ...????

Bugs and Issues / Re: How to reference a diagram in documentation
« on: November 21, 2016, 09:58:12 pm »
What exactly do you mean about this?
And what do you expect from the reference?

In text you have in EA, you can add a link within the text to any element, including diagrams.

General Board / Re: Communicating State Machines
« on: November 18, 2016, 10:57:38 pm »
"Send" represents an event (wording in EA is somehow confusing).

What you need is the thing that sends the signal.
To do that drag and drop an action into you diagram. After dropping you have to select the type of action. Choose "Send Signal" and add the signal to the action in the properties afterwards.

General Board / Re: Communicating State Machines
« on: November 18, 2016, 07:58:30 pm »
Hi Michielper,
to communicate you need some kind of Event (Message, Change, Time) and someone who causes (behavior) those events. The behavior you specify in the state operations or in the state transitions. This you can do either pure textual (tend to become more easily inconsistent) or by a model (e.g. an Activity).
In you case I would define an Activitiy which sends a signal and assigning this Activitxy to the right behavioral place (see above) of your sending state machine. For the receiving state machine I would define a trigger using the signal to be used on a transition.

On a SysML BDD or an IBD you can add properties to a block with some but not all allowed stereotypes (just prop, connector prop, distributed prop, flow prop,…). However you can set the right stereotype afterwards.
On the process browser you can only add a flow prop. But again you can change the stereotype afterwards again.

A more consistent solution would be, to allow adding the same subset of stereotyped properties or even just an “unstereotyped” property for both diagrams and project browser.

Even trickier e.g. it goes, when you want to have a “ClassifierBeaviourProperty” classified with a State Machine. If you have already a property and you want to classify it with a state machine you are not able to, because StateMachines are not shown as possible Property Types (presumably a bug). The only way by achieving that is by dragging and dropping the state machine to the block in the diagram and by selection “Property” in the dialog.

What programming language did you use for your application?
Does it mean you did not write any programming language code at all, or did you put the code just in Rhapsody?

Are you saying with Rhapsody you created "full applications"?

What gives your query back when you use it in „Search“ rather than in GetElementsByQuery?

See e.g. this:,37427.msg234453.html#msg234453

I would not spend to much effort in trying to go in this direction.
UML is a specification language, not a programming language.

Pages: 1 ... 22 23 [24] 25 26 ... 50