jopirx

[jopirx]

…
So, reluctantly, we’re making a change to eaDocX so that any EA element can have attributes or operations. Should be in 3.8.4, which is being tested now.
Do you think this will solve your problem ?

First – no
Second – yes.

[jopirx]

1. What condition of the solution of this problem?
2. The similar situation is observed with “signals”. From the point of view of EA – a signal in fact the class, so may contain attributes and methods. But in dialogue of a profile of a signal in EADocx attributes / methods aren’t available to the choice neither among standard attributes, nor among “sub-elements”. The choice in “sub-elements” of children option also doesn’t allow to unload attributes/methods in the document.In general is a fundamental problem.

[jopirx]

Word ‘eaDocXSection’ style has been created successfully. But he had no in a configuration of a font of the established option “hidden”. I have established manually – everything became normal.

• This reply was modified 8 years, 8 months ago by jopirx.

[jopirx]

This is a very strange situation, and may be a bug in EA.
I have submitted a question to the EA forum, and I’m waiting for a reply.
Please see http://sparxsystems.com/forums/smf/index.php/topic,30338.0.html%5B/quote%5D

EA considers that everything is OK and Object – the legacy concept (literally: “It’s mostly legacy reasons why classes have object instead.”)
http://sparxsystems.com/forums/smf/index.php/topic,30338.msg221274.html#msg221274
Whether I don’t know you will be helped by it, but I have nothing to tell EA in that topic more.

I think it is necessary to correct in eadocx. In other words Instances not only Objects. As Instances in model of data of EA are identified – I don’t know.

PS> nevertheless I added a question – whether how to define the element a instance is: http://sparxsystems.com/forums/smf/index.php/topic,30338.msg221354.html#msg221354

• This reply was modified 8 years, 10 months ago by jopirx.

[jopirx]

If I understand you correctly, the your first screen-shot shows two different ways of saying the same (similar?) thing:
– one where you have an Actor, linked to a Process, linked to a use case
– one where the Actor is linked to the Use Case, and the Process is a ‘conveyed item’ of that link.
…

Not some things.I described a difference as could. I, of course, will try to make an example of model and the document. But it will demand some time.

[jopirx]

Up topic. 🙂

[jopirx]

Good afternoon,

I will repeat, I not really well know English. At the heart of the text the tool translation. Therefore some phrases, perhaps, will seem to you strange or not clear.

10 days ago I finished the trial period for eadocx. I needed to make the decision will be – whether our company to buy and use it or not.
There were questions which are strongly influencing it. And therefore I transferred the decision before I don’t receive final answers at least to the first of them. Within a week of “eaDocX Support” didn’t log in. Ok, everyone happens in life. But here week passed “eaDocX Support” is active, but answers aren’t present. No answers are present, even “we can’t do it”.
We nevertheless will buy it. But now only in volume of one personal license. It is rather from a hopelessness as a lot of things aren’t clear and clear only that partially this tool will close our requirements in case it is possible to combine it with built in in the EA generator of documents.
However to consider it seriously and to use as the tool in the processes of design it won’t turn out until feedback of the developer isn’t adequate.
I assume that other channels of support offered for the users who already bought the license are more effective. We will look. But the buyer still it is necessary to become. While it didn’t happen – everything looks not really beautifully.

[jopirx]

1. there is an additional attribute, available only for Objects, which is RunState Variable Summary, which prints the attribute, operator and value, for all the run state variables.

Ok, im see.

if the <> is also an Object, then you can use the same approach
If not an object, then what is your <> a stereotype of?

It isn’t my stereotype. :dry: If you create “deployment specificaton instance” by drop “deployment specification” element from project browser with Ctrl – you will get “deployment specification instance” with visual stereotype “deployment specification”. I don’t know what this is in Enterprise Architect information object model.

I thought that only Objects can have run states?

Why? Not only “objects” – instances, not only “class” – classifier.
For example. Deployment specification – are a classifier that define specification for setup parameters for artefact deployment (as list of classifier attributes definitions). Deployment specification instance – are the instance that define values (as run states) for setup parameters for conrete artefact instance deployment.

To create a profile for a <>(thing) just go to the ‘profile’ tab in eaDocX and choose ‘add element’. You can create profiles for any element+stereotype, but there has to be an instance of it in your model somewhere.

Ок. But “deployment specification” instance not avaible in list for choose. Instance (element) “deployment specification instance” are exist in model.

Or, do it the easy way, and create an eaDocX “quick document” on the package which contains the elements/objects, and eaDocX will create profiles for all types+stereotypes.

Im do test this. eadocx create only one profile for “deployment specification” and applied it as to “deployment specification” model element, as to “deployment specification instance” model element.
“object” profile was’t created.
And not avaible also to create profile for “deployment specification” with some stereotype for “deployment specification instance”.

[jopirx]

Thanks, I found. There was other question.

1)
I created the class “A”, I added to it the A123 attribute. I created a instance of a class “A” with the name “test”. I established value through “Set run state” in the A123 attribute. Result in an attachment 10.png

I created the document and in a template for “object” added “Run state variables” sub-elements. I made unloading of section for the test:A element. Result in attachment 11.png

The question – that needs to be made, that in the table “Run state variables” unloading also “Operator” and “Value” values for each variable?

2)
Repeate this for “deployment specification” (model 20.png).
2.1) But in template for “deployment specification” sub-elements “attributes” or “Run state variables” – not avaible (21.png) :blink:
2.2) How define template/profile for instance of “deployment specification”? It not found in list of avaible element types and not specialize as “object” and common “object” profile not applicated for it.

• This reply was modified 8 years, 11 months ago by jopirx.

[jopirx]

It isn’t difficult to explain (but, my English isn’t really good, sorry :blush: ).

In our case in model it is necessary to define references between a business process step, the participant (actors) of this step and “use cases” of system which is applied by the participant (actor) within this step.
In an attachment simple, but not absolutely typical Use Cases diagramm (2.png). The problem that as the triple connector isn’t possible in EA (as well as in UML), sense of binding “operation” – “participant/actor” – “use options” exists only in the context of concrete the diagramm.
Any attempt to unload from rather big model the description of UseCase in a look “use case” – “actors”- “operations in which actors participate” won’t be correct as not in all operations the actor uses this option of use.
Unloading on logic of a chain “use case” – “operations in which it is used” – “actors who participate in operation” also isn’t correct as not all participants of operation use this “use case”.

It turns out it is necessary to bring use context in at least one of scheme connectors. An example in attachment (1.png). As besides in EA there is no universal opportunity to link an element to a context of connector (of course noa as connector source or target) (well or I don’t know it), the good candidate is Information Flow Realize which in fact ties to a connector practically any type essence with sense “is transferred on this connector”. Application of course not really beautiful, however what to do?

Now a question if I want to construct unloading in the document of use case by means of “attributes of related elements” – as I am able to do it? Information Flow Realize not avaible for “association” type connector (4.png).

[jopirx]

But “conveyed items” can be defined not only for connectors with the InformationFlow type. At least actually in EA so. How to be in this case?

[Author]

Posts