Author Topic: SysML: BDD context menu of a block in Project Browser shall allow adding propert  (Read 1899 times)

PeterHeintz

  • EA User
  • **
  • Posts: 811
  • Karma: +47/-17
    • View Profile
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”.
Best regards,

Peter Heintz

philchudley

  • EA User
  • **
  • Posts: 569
  • Karma: +11/-0
  • UML/EA Principal Consultant / Trainer
    • View Profile
Hmm Interesting

To add Properties to a Block in a BDD, what I do is

1) Add two blocks to a BDD
2) Create a "whole-part" relationship between them using a Part Association (Composition) or a Shared Association (Aggregation)

EA then creates a Property typed to the "Part" Block as a direct child to the "Whole" block

You may have to hide the Properties compartment for the Blocks on the BDD

To add a Value Property to a Block on a BDD what I do is

1) Drag a Property from the Toolbox onto a Block on a BDD
2) Type the Property to a ValueType
3) Delete (Using the Delete Key) the Property from the diagram

EA then creates an entry in the values compartment

Oddly, the above only appears to work correctly if the Block is in the same package as the BDD, otherwise its back to drag and drop within the Project browser.

Cheers

Phil

follow me on Twitter

@SparxEAGuru

PeterHeintz

  • EA User
  • **
  • Posts: 811
  • Karma: +47/-17
    • View Profile
Assuming a new keen EA user ask you, how to add a child package under a parent package.

You advise him to add a diagram, drag in the parent package and drag in a new package from tool bar to create the child package and draw a special line between both to achieve his goal (new child package under a parent package).
The keen new user would argue that a diagram is for communication with stockholders, but  the diagram needed to be created provides no value to stockholders at all.  :(
Ok, you could suggest deleting the diagram afterwards, but for sure the feedback of new user will be to have in the project tree the possibility to add a child package, by selection the parent package and selecting a menu item to get the job done (as it works for any kind of application within this globe).

You mention to him that such possibility is there, by creating a child package of stereotype w,x,y,z, but a stereotype with z Package should be chosen, because for that the stereotype can be deleted afterwards. Or the user can add a child package under a Class which can be dragged under the parent package afterwards.
What a wonderful world!!!! :o
At this point most of the new keen EA user will come to the point, that in EA some user goals need some very indirect and somehow senseless ways to be achieved. ::)

Fortunately EA provides a sense making and direct way to achieve that goal (new child package under a parent package). 8)

But if you substitute:
  • Parent Package by Block
  • Child Package by Property
  • w,x,y,z by Port, Full Port, Proxy Port, Flow Property
  • and Class by Package
You see that the curious very indirect and senseless user interaction as described above is required in EA. :o :o :o :o
Best regards,

Peter Heintz