Messages

1

Bugs and Issues / Re: Activity Parameter Direction and Action Pin Kind

« on: July 30, 2021, 11:54:06 pm »

This is a bug in EA's synchronise.  The Parameter (from Behavior) can be inout, but the ActivityParameterNode in the Activity cannot have two directions.  The ActivityParameterNodes are converted to ActionPins when you create an invocation Action. 

UML states:
1.  A Parameter with direction other than inout must have exactly one ActivityParameterNode in an Activity.
2.  A Parameter with direction inout must have exactly two ActivityParameterNodes in an Activity, at most one with incoming ActivityEdges and at most one with outgoing ActivityEdges.

This makes sense as getting a token from the node and putting a token to the node would cause a loop if you think about it.  In essence the inout parameter have two different nodes, the input and the output.  The fact that you write it to the same memory position in code (inout parameter), just not modify the fact that you hav an input and a different output.

EA only allows you to specify parameters (which can be inout), but it does not create two ActivityParameterNodes for the parameter if it is inout.

2

Suggestions and Requests / Re: SysML Activity BDD and Synchronize structural elements

« on: October 10, 2019, 11:30:23 pm »

Are there any plans to correct this functioning? 

3

Automation Interface, Add-Ins and Tools / Re: EA's implementation of UAF

« on: July 25, 2018, 06:48:12 pm »

I am also struggling to use EA with UAF.  EA still has serious bugs with it's UAF implementation which makes it nearly unusable, unless you disable validation and not use Quicklinks and not try to use UAF::Dictionaries and...

That being said, UAF recommends the Operational structure be implemented in SysML BDD or SysML IBD.  One way to do this is to create a HighLevelOperationalConcept and add an IBD to it, or a Composite Diagram.  The BDD describes the composition and the IBD the exchanges.  Don't know if this helps?

4

General Board / Re: Error: Unknown Package Connector Source or Target

« on: March 15, 2017, 12:02:54 am »

Thank you for the effort. 

I am actually trying to import the OMG UAF 1.0 profile, as the support which Enterprise Architect gives for it is very (extremely) poor.  As it's import failed, I then tried all the others. 

I have come to the conclusion that Enterprise Architect:
1.  Cannot import standard .xmi files as released by OMG without logging errors,
2.  Cannot maintain an ownedComment on a packagedElement but moves it to the containing Package when importing,
3.  Cannot import ownedRule even when written in OCL and throws it away,
... etc ...

5

General Board / Re: Error: Unknown Package Connector Source or Target

« on: March 14, 2017, 08:53:54 pm »

Yes.  This is what I am trying to resolve.  For starters I cannot import directly from the URL, Enterprise Architect just hangs if I try this and I have to kill it off.

Copying all the related .xmi files from OMG and importing them in order does not solve the problem either.

6

General Board / Re: Error: Unknown Package Connector Source or Target

« on: March 14, 2017, 06:35:24 pm »

When importing, I get the following in the import log file:

Importing Model from XMI
Root Package: SysML
Add Classifier: FlowDirection
Add Classifier: FullPort
Add Classifier: ProxyPort
Add Classifier: FlowProperty
Add Classifier: ItemFlow
Add Classifier: InterfaceBlock
Add Classifier: InvocationOnNestedPortAction
Add Classifier: TriggerOnNestedPort
Add Classifier: AcceptChangeStructuralFeatureEventAction
Add Classifier: ChangeStructuralFeatureEvent
Add Classifier: DirectedFeature
Add Classifier: FeatureDirection
Add Classifier: FlowPort
Add Classifier: FlowSpecification
Add Classifier: AllocateActivityPartition
Add Classifier: Allocate
Add Classifier: Allocated
Add Classifier: DistributedProperty
Add Classifier: PropertySpecificType
Add Classifier: ParticipantProperty
Add Classifier: ValueType
Add Classifier: QuantityKind
Add Classifier: Block
Add Classifier: ConnectorProperty
Add Classifier: Unit
Add Classifier: NestedConnectorEnd
Add Classifier: BindingConnector
Add Classifier: ConstraintBlock
Add Classifier: ConstraintProperty
Add Classifier: Requirement
Add Classifier: Verify
Add Classifier: TestCase
Add Classifier: Satisfy
Add Classifier: VerdictKind
Add Classifier: RequirementRelated
Add Classifier: DeriveReqt
Add Classifier: Copy
Add Classifier: Probability
Add Classifier: Optional
Add Classifier: NoBuffer
Add Classifier: Rate
Add Classifier: ControlOperator
Add Classifier: Continuous
Add Classifier: Overwrite
Add Classifier: Discrete
Add Classifier: Viewpoint
Add Classifier: Rationale
Add Classifier: Conform
Add Classifier: View
Add Classifier: Problem
Add Classifier: Real
Add Classifier: Number
Add Classifier: Boolean
Add Classifier: Integer
Add Classifier: String
Add Classifier: Complex
Add Classifier: ControlValue
Resolving Classifiers
Resolving Owners
Resolving Attribute Types
Resolving Parameter Types
Error: Unknown Package Connector Source or Target
Error: Unknown Generalization Source or Target
Error: Unknown Generalization Source or Target
Error: Unknown Generalization Source or Target
Error: Unknown Generalization Source or Target
Error: Unknown Package Connector Source or Target
Error: Unknown Package Connector Source or Target
Resolving Association-Classes
Resolving Properties for Association Ends
Resolving InteractionOccurences
Fixup external references
Import Complete!

7

General Board / Re: Error: Unknown Package Connector Source or Target

« on: March 14, 2017, 06:15:04 pm »

http://www.omg.org/spec/SysML/20150709/SysML.xmi][url]http://www.omg.org/spec/SysML/20150709/SysML.xmi
http://www.omg.org/spec/UML/20131001/StandardProfile.xmi[/url]

8

General Board / Re: Error: Unknown Package Connector Source or Target

« on: March 09, 2017, 10:06:15 pm »

I have tried importing a whole range of .xmi files from OMG and I get one these errors for each OMG file that is referenced in the .xmi using the <importedPackage href=.... .   

This includes (but are not limited to) uml.xml, StandardProfile.xmi, UAFP_Profile.xmi, mof.xmi, SysML.xmi,...

The only one that does not throw the error is PrimitiveTypes.xmi as it does not reference any other files.
 

9

General Board / Error: Unknown Package Connector Source or Target

« on: March 09, 2017, 08:49:39 pm »

I have browsed all the references to the above error when importing .xmi which stretch over more than 11 years now.  Everywhere the answer is that there are some connectors dangling.

Unfortunately I cannot find any solutions to this problem which has now become a serious problem.

Using .xmi files from OMG, I have narrowed the error down to references to external packages in a packageImport which is located on the web.  You get exactly one error for each of these "importedPackage href=" entries.  Here is an example causing the error.

      <packageImport xmi:type="uml:PackageImport" xmi:id="_packageImport.0">
         <importedPackage href="http://www.omg.org/spec/UML/20131001/PrimitiveTypes.xmi#_0"/>
      </packageImport>

Is there anybody who can point me to what I should do to fix the problem?  Obviously the importer cannot find the external packages on the web (even though they are there).  Should I copy all the imported files to a local disk and modify the OMG .xmi files?