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

Pages: 1 ... 9 10 [11] 12
I have a SysML Super Block (interfaceBlock) defining a Flow Property with direction “out”. From this Super Block I derive a Sub Block by Generalization. For the Sub Block I called Structural Elements… to get the Flow Property in the Sub Block as well.
This works, but the direction of the Flow Property of the Sub Block is set to “inout” rather than to “out” as defined in the Super Block. Due to the fact that the Flow Property in the Sub Block is read only the direction cannot be changed.
EA Version 12.0.1250

When you have a nested port and you add more than one interface to the owning port, all interfaces are graphically placed on the same position (overlap) and cannot be moved to another place to solve the overlapping problem.

Bugs and Issues / SysML: Full Ports shall allow adding properties
« on: March 23, 2016, 04:23:36 am »
According SysML 1.4 Chapter full ports can have own parts/properties not only Flow Properties.

When typing a port (A) with a block (B) containing properties and ports, and calling the menu item Structural Elements only the ports of block (B) will be added to port (A) but no properties of block (B).
However adding a property under a package and dragging it under a port is possible in EA, but leads to stage effects in a diagram.
The menu item Structural Elements should also allow to add any kind of properties under a port when the property belongs to the typing block.

According SysML 1.4 Chapter ValueTypes may have its own properties and operations just as for a UML DataType.
Features to add properties under a ValueType on a diagram and in project browser shall be added.

Currently within the context menus on a SysML Block in Project Browser it is only possible to add Port,Full Port, Flow Property.
To add a properties the following workarounds can be applied:
  • Adding a Flow Property and deleting the FlowProperty stereotype afterwards
    Adding a property (although according SysML packages do not have properties at all) under a package and dragging/dropping it under a block.
Instead of these workarounds the context Add menu shall have item “Property”.


SysML 1.3 says this
A property can represent a role or usage in the context of its enclosing block. A property has a type that supplies its definition. A part belonging to a block, for example, may be typed by another block. The part defines a local usage of its defining block within the specific context to which the part belongs. For example, a block that represents the definition of a wheel can be used in different ways. The front wheel and rear wheel can represent different usages of the same wheel definition. SysML also allows each usage to define context-specific values and constraints associated with the individual usage, such as 25 psi for the front tires and 30 psi for the rear tires.

When I add a property typed e.g. with a ValueType to a SysML block (A) I can set the initial value (initial) in the properties dialog. But when is type a property in another Block (B) with Block (A) I cannot change the initial value of the property of type (A) in (B) anymore because the property dialog is somehow read only.

My idea is to define a Block with some ValueType properties in which I want to use as whole to type properties in various scenarios just by changing the values.
Car Data
   Speed ValueType(km/h)
   Power ValueType (kW)

Lamborghini  Huracan
cd:Car Data

Is it just a bug that properties of properties are read only?
Any idea to meet my goal?

Don’t be afraid! I do not intent to leave the club!

I need to transfer EA model data to eclipse papyrus to use some safety analysis features there.
I tried several kinds of exports without success. I am interested only is the data of the model (not in the diagrams).

Any hint?

I have a ConditionalNode in an activity diagram with some Clauses.

As long as no actions are in that node I can resize the node in the diagram by dragging as I expect.

However after adding some actions in, my resizing gets out of control and  the node get each time I try to resize it longer and longer (vertically).
Do I just miss to press some magic key when resizing or is that a bug?
I remember, I had similar problems with sequence diagrams where I found a magic key some time ago in V11.
Now I am using V12.

General Board / Usage of document Meta Data in document templates
« on: February 27, 2016, 04:27:12 am »
I work in an environment where nice pretty and formal documents are required.

These documents need some meta data (project name, project number, document number,….). These data is either project specific or document specific and must go to the cover page or header/footer.
All my project specific data I put in Project Constants. When defining document templates I can use those constants on cover page or header and footer (all fine).

The problem I have is with the document specific data. This data I could hold as tagged values in a package. But I find no way how to access those tagged values because I need to be in the package or I would need a custom query, but none of both I can use in cover page nor in header/footer.
Any idea?

I have some kind of model library that is intended to be used in other EA repositories.

Basically several user will create content for this model libraries.

The users who use the libraries will import those libraries somehow to their model and use the library more or less as read only elements.

I think it would be good, when the users would be able to quickly find out (e.g. when looking on their diagrams) whether an element belongs to their own work or when it just is a library element or is classified by an element coming from the library.

Currently I belief I should stereotype all that library elements manually or by a script before distribution. So I would be able to define in addition, some visual effects on those elements.
Do any of you, have some better ideas how to achieve such an indication with low effort, maybe even working when the library element is used as an classifier in a project using the library?

My document templates work as I expect as long I do not have more than one diagram under an element.

Example: When I have one SysML IBD under a Block all works fine, but when I have two IBD diagrams, both diagrams are rendered twice.
Any idea about a workaround?

I have several potential use cases that would fit to the Decision Table feature.
However I do not use it, because it is so limited by just allowing appending rows.

Adding the possibility to insert rows before existing rows or move existing row, is really a basic feature, which is from my point of view the minimum the make Decision Tables usable at all.

As an example I have use cases which are made more precise e.g. by activities, sequences or state machines.

To maintain the relation between the use cases the concretization I use the traceability matrix feature, but I need several of those, depending on the modeling language I have chosen for the concretization.

The specification manager is a good feature to enrich the model with explaining text.
Currently either one specific item type or any item type can be edited.

However it would be more useful if it would be possible to select several but not any item type to be shown. Further on also packages can have textual descriptions and currently there is no way to maintain this package notes by using the specification manager.

In a template fragment I call a custom script method and after generating a document all works fine.

When I use the templates and scripts in a published MDG, the script seems to be not called at all.

What I realized (when using the MDG) is, that in the “Custom Query” tab of the template fragment the method call is there but the script containing the file is not selected in the form.

Any idea to get this problem solved?

Pages: 1 ... 9 10 [11] 12