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.


Topics - Shegit Brahm

Pages: [1]
1
Hi there,

I have a question about documenation generation:

I have a package and there a diagram that contains some requirements. These requirements are linked to several use cases.

I want to generate a document that lists me the package with the diagram and afterwards each requirement with description and a table with use case to which this requirement is linked (source-target relationship is shown in relationships window).

circumstances: the requirements and the use cases are located inside project browser somewhere else, they are not stored inside the package of the diagram.

from section package I chose:
- package
-- package element
--- external requirements
--- tagged value
-- child packages
-- diagram
--- element
--- connector
-- element
--- extension points
--- tagged value
--- connector
---- source
----- element
----- linked feature
--- attribute
--- child elements
-- connector
--- source
---- element
---- linked feature
--- target
---- element
---- linked feature

so the template looks like:
Code: [Select]
{ReportName}


 

package >

{Pkg.Name}
{Pkg.Notes}
package element >
external requirements >
< external requirements
tagged value >
Member Company- department
{ElementTagVal.Value} {ElementTagVal.Notes}

< tagged value

< package element

child packages >
< child packages

diagram >
{Diagram.DiagramImg}

image {Diagram.Figure}: {Diagram.Name}
{Diagram.Notes}
element >
{Element.Name}
state: {Element.Status}    release: {Element.Phase}  version: {Element.Version}  modified: {Element.DateModified}
author: {Element.Author}

description:
{Element.Notes}

Type Name Version Release
{Element.IsSpec} {Element.IsLeaf} {Element.Owner} {Element.Phase}
< element
connector >
SourceColumns
{Connector.SourceColumns}
TargetColumns
{Connector.TargetColumns}
Notes
{Connector.Notes}
IsRoot
{Connector.IsRoot}
< connector
< diagram

element >
extension points >
{ElemExtPoints.ExtensionPoint}
< extension points
tagged value >

< tagged value
connector >
source >
element >
[Package/Element/Connector/Source/Element]
Element-Name
{Element.Name}
< element
linked feature >
[Package/Element/Connector/Source/Linked Feature]
Linked Feature
{LinkedSourceFeature.Type}
< linked feature
< source
< connector
attribute >
[right-click-to-insert-Attribute-field(s)]
< attribute


child elements >
< child elements
< element

connector >
[right-click-to-insert-Connector-field(s)]
source >
element >
Connector/Source/Element - Type:
{Element.Type}

Connector/Source/Element - Name:
{Element.Name}

Connector/Source/Element - Notes:
{Element.Notes}
< element
linked feature >
Connector/Source/LinkedFeature - Stereotype:
{LinkedSourceFeature.StereotypeEx}
< linked feature
< source

target >
[right-click-to-insert-Target-field(s)]
element >
Connector / Target / Element - Type:
{Element.Type}

Connector / Target / Element - Name (full):
{Element.FullName}

Connector / Target / Element - Notes:
{Element.Notes}
< element
linked feature >
Connector / Target / Linked Feature - Type:
{LinkedTargetFeature.Name}

Connector / Target / Linked Feature - Type:
{LinkedTargetFeature.Type}
< linked feature
< target
< connector
< package


property setting for this diagram: "add each contained element in documenation"

After prompt for document generation comes up, I choose "include all diagram elements in report" and set all exclude filters to "none".

What do I miss - in explanation here and in generation there?
Bug, feature, wrong concept of documentation?

Thanks

PS: If the requirement is stored in the same package as the diagram then it works. But that is not useful as I need seperate packages for documents and for the model itself.

2
I digged into MDG and created several technology exports.

Now I realize: the dropdown of "open an existing mts file" is filled - and denies any new ones. And the existing ones occur in random order.

My question: how to get rid of these entries?

If I delete one in windows file explorer, EA does (obviuosly) not know and just tells me: oops, this is unknown and has no information stored.
But it persists as dropdown entry.

http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/user_interface/configurelocaloptions.html
is quite quiet about.

Thanks, Shegit

3
Using EA 13.0

If I define a stereotype extending metaclass "ActivityInitial" with some attributes,
create myToolbox with it and export all as MDG,
import it to other eap.

In activity diagram I
- have to drag'n'drop from myToolbox to receive my customization (see http://sparxsystems.com/forums/smf/index.php/topic,38479.0.html for my observation)
- if I whyever delete any tagged value (originally attributes) from this node, I'm unable to restore them.
- neither sync nor "apply" again works.

Looking for a workaround I tried to define Tagged Values in UML1-style: using "UML Types"

But "AppliesTo" is fully ignored on ActivityInitial:

- e.g. for Decision works fine:
Type=RefGUID;
Metatype=Decision;
AppliesTo=Decision;

- for ActivitiyInitial doesn't show up:
Type=RefGUID;
Metatype=Decision;
AppliesTo=ActivityInitial;

"AppliesTo=Action" works as well, but not these nodes.

Any ideas how I can workaround this bug set a "model" Tagged Value that only applies to ActivityInitial?

4
To define a stereotype with specific tagged values for a specific element type I define an UML profile.

Now I'd like to have some tagged values of this stereotype to apply depending to which element type the stereotype was added.

Is that possible?

E.g:
- ActionTV = my stereotype
- extends Action, ActivityInitial, ActivityFinal, Decision
- has attributes attribute1, attribute2, attribute3, ActionOnly, InitOnly, FinalOnly, DecisionOnly

-> visualization

importing the UML profile (or MDG technology to have toolbox) I want to create (inside activity diagram):
- stereotype "ActionTV":
- an action with tagged values            attribute1, attribute2, attribute3, ActionOnly
- an initial node with tagged values     attribute1, attribute2, attribute3, InitOnly
- an final node with tagged values       attribute1, attribute2, attribute3, FinalOnly
- an decision node with tagged values attribute1, attribute2, attribute3, DecisionOnly

- stereotype "Together"
- an action with tagged values      together1, together2, ActOnly
- an decision with tagged values   together1, together2, DecOnly


Question: is that possible?

The option "first stereotypes from each metaclass, later specialization from these to one stereotype" results in elements, that have all time all tagged values from all classes, just grouped by their original stereotype. And synchronizing one element updates all :-)
Here stereotype "Together" specializes from ActionFirst and DecisionFirst.
See

files:
- https://www.dropbox.com/s/2nlgkdb7teg58e0/ShegitTvOnClass.xml?dl=1  UML Profile
- https://www.dropbox.com/s/iq5s6003uyvdjhl/Toolbox1TvOnClass.xml?dl=1 Toolbox defintion for profile
- https://www.dropbox.com/s/5jd7rvsv5wkrg1g/TvOnClass_MDG.xml?dl=1 MDG of profile and toolbox
- https://www.dropbox.com/s/5bjd6ndvk89tg4l/TVDef_ApplySomeTVOnClass.eap?dl=1 eap where everything was defined
- https://www.dropbox.com/s/rk5dxeq02vz7xmz/TvOnClass.png?dl=1 picture of profile
- https://www.dropbox.com/s/9id05ovrh707f2r/TvOnClass_tags.png?dl=1 picture of tagged values as result

thanks, Shegit

5
I created an UML Profile for individual stereotypes and a Toolbox based on that.
- create in ToolboxBase.eap, use in TboxUse.eap

need sync for full definitions from myProfile:
- constraints will be added only after syncing the element (User Guide already says so: http://www.sparxsystems.com/enterprise_architect_user_guide/13.0/model_domains/synchronizetagsandconstrain.html)

my problem with ActivityInitial:
- creating an element from original UML and adding stereotype myInit does nothing: neither tagged Values nor constraints added. And stereotype is visually wrong: instead of "<<myInit>> it shows <<myProfile::myInit>>
- syncing the stereotype from myToolbox: does nothing
- adding stereotype using drag'n'drop from myToolbox: impossible, creates always new node
- only solution so far: creating ActivityInitial from myToolbox, sync it, re-connecting & transferring everything from now-old node, delete now-old node.

my problem with Decision:
- creating element from original UML: adding stereotype myDec using properties page is impossible, myProfile is not offered for selection
- solution: drag'n'drop from myToolbox, adds everything or create from myToolbox

my problem with CallBehavior:
- defining toolbox needs "special skill": the metaclass is called "BehaviorCall", the toolbox attributes need full qualifier with "myProfileTB::myCallBehavior(UML::BehaviorCall)" (other stereotypes need only myProfileTB::myAction, guess it is because of CB vs BC)
- drag'n'drop from myToolbox on empty activity diagram does nothing
- drag'n'drop from myToolbox on default action does nothing
- creating action from default toolbox, changing kind to CallBehavior, drag'n'drop myCall from myToolbox: I get choice "apply myCall/ add myCall" - but nothing happens.
- only solution: create action from default, change kind to CB, select stereotype in properties


So all in all everywhere a different kind of workaround exists - but is there nothing to achieve a consistent work flow?

files for example:
https://www.dropbox.com/s/rr0z7btay6lcnq8/myProfileTB.xml?dl=1  profile definition as UML profile
https://www.dropbox.com/s/irgqc8f87a7dd2a/myToolb_MDG.xml?dl=1  entire stuff as MDG technology
https://www.dropbox.com/s/zs9tz7gd9orx56r/myToolbox.xml?dl=1  toolbox definition as UML profile
https://www.dropbox.com/s/8mt338nhrcyyske/TboxUse.eap?dl=1   eap where MDG is used
https://www.dropbox.com/s/ou1gvo94lo6xr6l/ToolboxBase.eap?dl=1 eap where profiles got defined

Thanks, Shegit

6
I created UML profiles and usually set all exporting and importing options, including "Element Size".
In detail, I set stereotypes extending several metaclasses.

I use these to ways:
- right click on package and using "Advanced -> Save package as UML profile"
- click on package and then "Layout-> (Diagram) Manage -> Save as Profile" (works only after one diagram was opened in advance but exports entire package)

My question is:
- Where is the "Element size" stored, when I export the UML profile?
- Should I dig into "Shape Script", to ensure any sizing? (Because appearance like "grey merge node" works fine)
- and can this Shape Script be exported together with UML profile or at least MDG, because there is inclusion of "Other -> Scripts"?

In the beginning, I had only one diagram and "accidentially" did diagram export
-> that way "imported" ActivityInitial got the size of the stereotype that defines it in the base eap.
like stated here
http://sparxsystems.com/enterprise_architect_user_guide/13.0/modeling_tools/save_profile_options.html

But
http://sparxsystems.com/enterprise_architect_user_guide/13.0/modeling_tools/exportprofile_2.html
is silent about size.

Thanks in advance, Shegit

7
Base eap to define a UML profile with
- stereotype "myStereo" extending metaclass Action (myStereo1 for only one per attribute, myStereo2 for more than one)
- several attributes for this stereotype
- connector "taggedValue" between metaclass Action, ActivityInitial and Decision
- connector role specified as attributes names intend

exporting as MDG Technology or UML profile

Use eap to have tagged values depending on stereotype
- creating activity diagram with at least one element for each type of metaclass in base eap
- importing MDG Technology/ UML profile
- creating Action "useStereo1" and Action "useStereo2" in Activity diagram
- setting "myStereo1" and "myStereo2" as stereotype for this action.
- defining entries for each tagged value of both actions

what is:
- every tv is limited to only one metaclass

what should:
- every tv is limited to each metaclass as defined in base eap

source of problem:
- generated xml selected one metaclass by random

"workaround":
- editing xml so that 'notes="Type=RefGUID;Metatype=Action,Decision,...;"

With the XML I can achieve almost any limitation.
But that's what the generated xml should do as well.

example files:
https://www.dropbox.com/s/500b4as78dw3vfy/RefGUID_difference_GUI_XML_Base.eap?dl=1 eap used to define stereotypes with tagged values
https://www.dropbox.com/s/a7rhs8o0hhpnjmo/RefGUIDandRefGUIDs.xml?dl=1 MDG generated by EA
https://www.dropbox.com/s/0pr3ve1e7vauwj8/RefGUIDandRefGUIDs_Edited.xml?dl=1 MDG edited to achieve aimed behavior
https://www.dropbox.com/s/1zknc7cyi9ypmtz/RefGUID.xml?dl=1 UML profile for single tagged value connectors
https://www.dropbox.com/s/d9s2hzeivtwooh0/RefGUIDs.xml?dl=1  UML profile for multiple tagged value connectors
https://www.dropbox.com/s/tnzom6j02zh20vt/RefGUIDs_AllTargetSet.png?dl=1 diagram RefGUIDs with multiple connectors
(edit: changed dropbox links to start download directly (dl=1) instead opening dropbox page (dl=0))

general discussion took place here:
http://sparxsystems.com/forums/smf/index.php/topic,38459.0.html

8
Hi,

I tried to do the following:
- creating a definition eap where I set my UML profile
- creating a usage eap where I will use defined profile
- extending Action with stereotype and attributes so I will have Tagged Values after import of Profile

what works:
- Setting any enum works fine (->"WithEnum")
- defining Memo works only with <memo> as "Initial value" of corresponding attribute (-> "WithMemo")

my problem:
- how to enforce "Integer"?
- how to enforce "RefGUID"?

my workaround:
- creating profile as intended
- exporting as MDG as well
- editing MDG-XML with an editor:
Code: [Select]
</UMLProfiles>
<TaggedValueTypes>
<RefData version="1.0" exporter="EA.25">
<DataSet name="Property Types" table="t_propertytypes" filter="Property='#Property#'">
<DataRow>
<Column name="Property" value="WithInteger"/>
<Column name="Notes" value="Type=Integer"/>
</DataRow>
<DataRow>
<Column name="Property" value="WithRefGUID"/>
<Column name="Notes" value="Type=RefGUID;Metatype=Decision;"/>
</DataRow>
</DataSet>
</RefData>
</TaggedValueTypes>
</MDG.Technology>

See files if you like:
https://www.dropbox.com/s/7t9jh5agbyas8zn/Shegit_MDG.xml?dl=0
https://www.dropbox.com/s/tfeo43ju3y7l25r/Shegit_MDG_edited.xml?dl=0
https://www.dropbox.com/s/d6tezhto74yeayw/TVDefinition.eap?dl=0
(Edit: changed to dropbox)

For Memo I did it that way to, but found out that "initialValue" takes it as well.

I prefer to include the Tag-Definition inside eap because otherwise I need to take care for every change of Profile whil updating mdg-xml.

Thanks,
Shegit

9
I have similar problems like these ones:
- http://sparxsystems.com/forums/smf/index.php/topic,23145.msg192681.html
- http://sparxsystems.com/forums/smf/index.php/topic,26723.msg207736.html

Here feature has been requested, but I don't see valid fulfilment so far.
- http://sparxsystems.com/forums/smf/index.php/topic,28678.msg214620.html

As I can say:
current EA 12.1 exports still conflicts with (almost) current HP ALM 12.2

My core question:
EA mistake or HP error?

Whenever I create a sample BPMN in EA and export the model, all I get is
- export as BPMN 2.0 XML
Code: [Select]
<?xml version="1.0" encoding="windows-1252"?>
<bpmn:definitions xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" id="EAPK_E444FEBD_8B92_4fe2_87B3_83154728E814" targetNamespace="www.sparxsystems.com.au/bpmn20" xmlns:ssbp="www.sparxsystems.com.au/bpmn20" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" exporter="Enterprise Architect" exporterVersion="12.1.1224"></bpmn:definitions>
- export as XPDL 2.2
Code: [Select]
<?xml version="1.0" encoding="windows-1252"?>
<Package xmlns="http://www.wfmc.org/2010/XPDL3.0alpha" Id="EAPK_E444FEBD_8B92_4fe2_87B3_83154728E814">
<PackageHeader>
<XPDLVersion>2.2</XPDLVersion>
<Vendor>SparxSystems</Vendor>
<Created>2016-06-08 09:56:55</Created>
</PackageHeader>
<TypeDeclarations/>
</Package>

I could export the package with the diagram only and got a bigger export file, but it failed with any of file names .xml, .xmi, xpdl.

I can't upload attachment here directly, can I?

Thanks,
Shegit

10
Hi there,

I realized, that EA 12.1 creates a much bigger model output if I use "export to XMI": from 92 MB .eap it builds 280 MB .xml.
Taking old EA 9.x it produces only 110 MB.

Any idea what the reason might be?
Any effects beside bigger size? (I didn't do any kind of file comparison)

I choose XMi 2.1 in both cases, all checked options are same.

Thanks,
Shegit

11
Hi,

I have a question / topic I don't understand fully. I'm using EA 12.1, the model has been developed since EA 7.

Situation:
I have a class, create an UML object diagram and drag it into there.
Then transforming that class to an instance and rename it.

In another package I have modeled a webservice with some operations.

Now I'd like to show connection (dependencies) between the object and the operations.

Context: the class represents authorization and some operations of this webservice just requires them, some not.

My problem:

As soon as I drag the operations into my UML object diagram, the EA creates actions.
And additionally as I take all at once, hangs one action under the other - resulting in a long diagonal line.

If I check GUID from action: it is different to the operation of spoken webservice.
But if I check either action and operation with "find in all diagrams", it gets located in created UML object diagram.

The core problem here is that I want to ensure to keep the operation linked to the class instance.

I'm used to use "Strg + G" for locating element in project browser and I see - it goes anywhere instead to the webservice.

My question finally is:
- Do I need other diagram type to prevent this action creating? Which one?
- Is it impossible to link class instances to webservice operations by UML or by EA?

Because I can't use the relationship matrix to show it. At least because I can't even get a matrix by choosing the package with webservice and package with obejcts.
Works like a charm with UseCases and objects.

Thank you very much.

Pages: [1]