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.

Messages - Polymorph

Pages: 1 ... 3 4 [5] 6 7 ... 9
Uml Process / Extending non-UML diagram types
« on: August 09, 2016, 01:48:55 am »
I am creating an MDG Technology following and as guides

I have read that it is only possible to extend EA's basic built-in diagram types (see,30151.msg220401.html#msg220401) - so, if I want to extend SysML Block Definition Diagram (BDD), I must start with a class diagram and modify it as necessary

Having defined a new diagram type, I want to specify a toolbox to use with it.

The help describes how you can include elements from other MDG technologies:

(Optional) Define a Toolbox item that will create an item from an external MDG Technology. For example, adding a Toolbox item that creates a SysML1.3 Block element.
Click on the down-arrow on the right of the Add button.
Select the 'Add New Item' option.
The 'Create new Toolbox Item' dialog displays.
In the 'Alias' field, type the label to appear on the Toolbox item, and click on the OK button.
The Toolbox item will be added to the 'Toolbox Items' list.
In the 'Stereotype' field for this Toolbox item, type:
     -  Profile is the name of the Profile that the Stereotype is defined in
     -  Stereotype is the name of the Stereotype/Metatype that this toolbox item will create
     -  BaseUMLType is the base UML type of the non-UML object
For example, to include a SysML Block in a Toolbox you would type:
To identify the Profile::Stereotype string, create an element of the type to include in your Toolbox (for example; a SysML 1.3 Block), then select the element and display the Tagged Values window.
Any predefined tags for this element will be grouped under the Profile::Stereotype heading; for example, a SysML 1.3 Block's tags are grouped under SysML1.3::Block.
All non-UML objects in Enterprise Architect are an extension of a UML Type. You can reveal an element's base UML type by deleting its Stereotypes. For example, create a SysML1.3 Block and then, using the Properties Window, delete the Block element's Stereotype. The element type will change from Block to Class.

Does anyone know if you can re-use an entire toolbox from another MDG, rather than individually listing the elements to include within it? For example, can I re-use the SysML Block Definition Diagram toolbox in my custom toolbox?

Uml Process / Re: Object flow from ObjectNode to Action
« on: August 03, 2016, 10:51:30 pm »
If you have a copy, take a look at SysML Distilled by Lenny Delligatti, pp 96-97, 2014

Pins mean exactly what object nodes mean; pins are simply alternative notations that you can choose case-by-case to meet the specific needs of your target audience. Each has strengths and weaknesses

The object node notation lets you display compartments to convey the internal properties of the object tokens it holds. However, it takes up more real estate on an activity diagram than the pin notation. The pin notation does not allow you to display the compartments but it's a more space-efficient notation. As a rule, I recommend that you adopt the pin notation as your default option and switch to the object node notation only on those rare occasions when you need to show the internal properties of an object token.

Based on this advice, there's nothing to stop you showing an activity pin connecting to an object node, but to do so is to introduce redundant information... so it is best avoided.

EA is rather inconsistent in when it adds action pins to actions and when it does not. I'm not sure the behaviour is based on either the SysML or UML specs.

Uml Process / Re: Using Model Searches with the Model Views browser
« on: August 03, 2016, 05:18:48 pm »
I suspect you need to replace 'As' with 'AS'. (case sensitive)

That seems to have done the trick - the search now appears!


Uml Process / Using Model Searches with the Model Views browser
« on: August 02, 2016, 11:26:21 pm »
I am trying to write SQL searches and use these to create Model Views. Here is an example (simple) search

Code: [Select]
  t_object.ea_guid As CLASSGUID,
  t_object.Object_Type As CLASSTYPE
  t_object.Name Like "System"

I have saved this search under the name "My Test Search" and it is accessible from the drop-down list of user-defined searches

This search just looks for any model elements with the term "system" in their name - obviously my actual search is WAY more complex than this...

This code returns model elements exactly as expected...

Then, I have created a Model View search

Then I hit a problem... when I try to add the search that I created previously, the list of available searches does not include my newly created search  ???

What have I done wrong? I can see other custom searches in the list

When I click on the ... button the Manage Search dialogue window opens and I can see my search (yay!)

But there doesn't seem to be any "OK" button on it and once I hit "close" then I am returned back to the previous dialogue box again and my new search is one again not listed in the available choices!

This is driving me crazy!!!!!!!!!!

Uml Process / SysML Viewpoints
« on: August 02, 2016, 08:46:44 pm »
It seems I am not the only one that is wondering if Model Views EA's answer to the SysML specification of Viewpoint,3315.msg116105.html#msg116105

Does anyone have experience of creating viewpoints and views in EA? Just like the original poster, I can't help thinking that there must be a smarter way to do it!

Uml Process / Highlighting Glossary Terms in EA document export
« on: July 06, 2016, 11:27:38 pm »
We are making use of EA's built in document generator to export SysML requirements into a Word Requirements Specification. These requirements have a number of technical terms within them and these are defined in the Project Glossary, which we have also exported to the same requirements specification.

When terms are defined in the project glossary, EA will helpfully underline them in the GUI. However, when we export the model elements to the document, the underlining is not retained. This is a problem because many of the people reviewing the documents don't know what terms are included in the glossary - and which ones are not.

What I want is some way to visually indicate to any reader that certain terms within the requirement text are also glossary terms.

Is it possible to, for example, use italics and/or underlining to indicate this? That way, the reviewer would know that the term is defined in the glossary and they could turn to that section of the document to fine the definition.

It would be even better if there was a way to include a hyperlink from the text the glossary term... but one thing at a time!

Uml Process / Re: Action Effects - text wrapping
« on: July 05, 2016, 10:28:42 pm »
Thanks for that... unfortunately, the link to element feature option does not include the Action Effect so it looks like I'll just use the notes instead.

Uml Process / Re: Controlling the order of exported model elements
« on: June 30, 2016, 10:54:48 pm »
Yes - tree order does the trick. Thanks everyone  :)

Uml Process / Re: Controlling the order of exported model elements
« on: June 30, 2016, 05:13:23 pm »
We use the standard EA document generator

Uml Process / Controlling the order of exported model elements
« on: June 30, 2016, 05:32:12 am »
I have a package containing multiple requirements that I need to export.

EA allows me to change the order of the model elements in the browser but what do I need to do in the template to ensure that this order is respected in the document?

I want to do this because some requirements are related and I don't want them to simply them to be placed in alphabetical order. Rather, I want a measure of control

Thanks all!

Uml Process / Re: Connector Highlighting on Internal Block Diagrams
« on: June 30, 2016, 05:26:26 am »
I would never have guessed that! Thanks

Uml Process / Connector Highlighting on Internal Block Diagrams
« on: June 29, 2016, 06:15:29 pm »
I have an Internal Block Diagram (SysML) that shows a number of parts connected together via ports. These ports are typed by blocks, many of which themselves own flow properties (indicating the types of matter/data/energy that flows in/out of them).

I have noticed that when I select a port on the diagram and press Ctrl + L, EA highlights the connector(s) that connect to the port. However, sometimes EA highlights the connector in a green colour. Sometimes it highlights the connector in red. I am wondering if anyone knows the significance of these colours? I have looked through the documentation and can't find any mention about this functionality!

I wondered if it might somehow be indicating there was a mismatch between the types of ports at each end of the connector but I can't see anything obviously wrong ???

(I have also typed the connectors between these ports by using Association Classes - but I'm not sure that is relevant to my question...)

Uml Process / Action Effects - text wrapping
« on: June 17, 2016, 06:35:40 pm »
You can add an "effect" to an action and optionally display this on the diagram (Action Properties dialogue | Effect Tab)

EA seems to ignore any line feeds and puts the entire expression on one line ???

Does anyone know if there's some kind of text wrapping function that needs to be turned on?

Thanks everyone!

Suggestions and Requests / Lifeline Head sizing
« on: June 15, 2016, 01:06:44 am »
It would be useful to be able to adjust the height of Sequence Diagram Lifeline Heads (the rectangle at the top of the lifeline).

Alternatively, please sort out the text-wrapping behaviour when placing nested structural elements on a sequence diagram

See,30990.0.html for a description of the problem...

Uml Process / Lifeline Head sizing
« on: June 14, 2016, 08:47:01 pm »
Does anyone know if there is a way to control the height of the rectangle that forms the head of a lifeline on a sequence diagram?

I have a (SysML) block that contains several part properties. When I drop (an instance of) the block onto a sequence diagram EA brings up the Structural Features dialogue box and asks me if I want to display any of these on the diagram too - very helpful  :)

However, these "nested" parts take up a lot of real-estate on diagram. If I make then very narrow then the text within the nested part overflows outside the bounding rectangle since EA seems to keep them at a fixed height, and there seems no way to change this! ??? This makes the diagram look rather messy (and doesn't do my OCD any favours!)

The other option would be to suppress the name of the part on the diagram. Unfortunately, EA seems to only let me suppress the type - which I am not keen to do as we name our part properties using acronyms - which makes the diagram rather hard to interpret

Any suggestions?

Pages: 1 ... 3 4 [5] 6 7 ... 9