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 ... 5 6 [7] 8 9
91
Uml Process / Sequence Instances vs Objects
« on: February 19, 2016, 09:32:51 pm »
Not the first time this question has been asked

What is the difference between a sequence instance and an object? This post asks the question perfectly (created in 2004!!!!!)

http://sparxsystems.com/forums/smf/index.php/topic,13340.msg155877.html#msg155877

92
General Board / Re: Relationship Matrix Notes
« on: January 30, 2016, 12:33:08 am »
Shame. I suspected as much!

Thanks for the tip on posting images! Been driving me crazy for ages!

93
General Board / Relationship Matrix Notes
« on: January 29, 2016, 10:50:06 pm »
Does anyone know if there is a way to construct a relationship matrix where the notes from the model elements are also visible. Say, for example, I had a matrix that maps requirements (shown as rows in the matrix) and use cases (shown as columns) together. It would be very useful if I could not only display the name of the requirements but also have an extra column next to the requirement name that displayed its notes

This would allow you to read the text of the requirement quickly and deduce which use case(s) it should be linked to



Also, how do you insert an image into these posts!!!! I can't work it out

94
Bugs and Issues / Call Behaviour Action Pins
« on: January 14, 2016, 03:26:42 am »
When I create a call behaviour action (EA 12.1, build 1224) and type it by an activity that
1. already exists in the model
2. has activity parameters

The call behaviour that is created shows the activity pins but does not show their type. If I double click on the activity pin and then click "OK" on the properties dialogue box, EA then updates the diagram and also shows the type of the action pin.

I've checked and the are no (obvious) display options that are hiding the types from the diagram

95
Uml Process / Re: Showing stereotyped action pins
« on: December 21, 2015, 06:51:47 pm »
From EA Support:

Unfortunately it's not currently possible to display the Actions Pin's stereotype as expected. Our developers have confirmed that this is a bug and it is logged to be fixed. We cannot yet say when (in which build) the fix will be implemented.
 
As a work-around, you can apply a shape script to your stereotype. For example:
 
shape label
{
 println("«#stereotype#»");
 println("#name#");
}
 
See the "Shape Scripts" help topic for more information.

96
+1

97
General Board / Interfaces, blocks and ports
« on: October 05, 2015, 09:17:14 am »
I am new to Enterprise Architect (Rhapsody user). If I create an interface block (in SysML 1.3) and then add a port to a block that implements that interface, I would expect to have access to these operations whenever I place this block on a sequence diagram.

However, when I do this and create a message between this block and an actor, I do not see the operations contained within the interface.

Is this possible?

98
Uml Process / Project Searches
« on: December 16, 2015, 08:15:56 pm »
I have some custom SQL searches. I wish to make them available to everyone that uses the model.

I am aware that it is possible to export the SQL to an XML file and then have each individual user re-import the search but is there any way to embed these searches within the project database itself?

Need: if I make changes to the search, I want these changes to affect everyone. I don't want each of my users to have to perform an import each and every time I change something.

99
Uml Process / Showing stereotyped action pins
« on: December 16, 2015, 04:30:01 am »
SysML action pins may be stereotyped with an «optional» keyword.

Does EA allow this stereotyping to be displayed on diagrams? I have tried various diagram and tool settings but so far have had no luck in getting this information to display

100
Uml Process / Re: Block elements and compartments in SysML
« on: November 26, 2015, 07:08:58 am »
Quote
Yes, but the referring compartment is just called "properties" in EA which I think is confusing because there are numbers of different properties such as reference properties, value properties,... So the "parts" compartment in SysML theory is equivalent to the "properties" compartment in EA?

In SysML there are part properties and value properties and they are slightly different things. Value properties are usually used to model slightly intangible characteristics of a block (e.g. an engine's mass, which is a characteristic of the "engine"). Whereas part properties are (typically) used to model slightly more tangible characteristics (e.g. a crank shaft, which is a part of the "engine"). These aren't rigid rules and I'm sure someone will agree to differ on this point!

Not only are they slightly different modelling concepts, they are also represented differently in EA. As I said, part properties are simply known as "properties" whilst value properties are known as "attributes"... Why? because EA is originally a UML modelling tool with a SysML profile on top. You will soon discover this often causes some divergence between what the SysML spec defines and what EA presents you... I have come from using Rhapsody and am often left scratching my head about the way certain things are displayed! What you must remember is this: EA is a UML tool. That is why EA calls them "attributes" rather than "parts"... because value properties are extensions to UML "attributes". This is just something you'll have to get used to!

Quote
a reference association, as you said, creates no property within the block (seen in the model browser) and there is no option to turn on "references" in the properties because no property is created from the connection. The connection itself does not have the option to turn on references.
Let’s say you have two blocks:  Block A and Block B… create an association between them on a BDD. Double click on the association, go to the roles tab and give the “source” and “target” ends role names… this is the “name” of the reference part. So for example you might give the association at the end near block A the name “a” and the role near block B the name “b”. Now, create an Internal Block Diagram for Block A and from it right click and go “Synchronise Properties”. EA will now add a part to this IBD with the name “b” (typed by the Block B). Now, any change you make to B (such as changing its name, adding operations etc) will be reflected. Why must you do this? Who knows!!!

Regarding the labelling of the operations compartment, I seem to remember there might be a way to do this but cannot recall how. EA support may be able to help more.

My advice - accept EA's quirky way of doing things! ;)
Hope this helps!

101
Uml Process / Re: Block elements and compartments in SysML
« on: November 24, 2015, 10:10:01 pm »
Quote
Is there an option inside a BDD respectively a block element where I can open all allowable compartments from SysML like part, reference, value, receptions etc

There are a few ways to control this:
1. On a case-by-case basis: Right click on block on BDD, from context menu: Features & Properties | Feature & Compartment Visibility. This dialogue box contains settings for element feature visibility, including operations (EA presently does not support receptions) and attributes (EA's name for value properties).
2. On a diagram level, press F5 to bring up the properties window. Go to the elements tab. EA shows a list of all the features owned by the elements on the current diagram. Note: this list will change depending on the features owned by the elements on it, so if you don't see the feature you're after listed then it is because that none of the elements on the diagram have this feature at present... create it first and then try again.

Option 2 is my preference as it is more intuitive and affects all elements on the diagram (and any new ones you later drop on)

Assuming you have created a reference assocation between two blocks on a BDD then you can turn on the "References" option from the dialogue properties window. However, EA will not display display this information if the two blocks are already on the same diagram (since that would be redundant information). If however you were to delete one of the two blocks from the diagram then EA will then add a reference compartment to the remaining block showing those things it is associated with...

Quote
it would be really helpful to know how to create an association that is equivalent to the part properties displayed in the part compartment.

To create part properties create a composite aggregation relationship from the block you wish to represent the type for the part to the block that represents the owner

Quote
On the other hand a shared association creates a property displayed in the reference compartment but the textbook says that reference properties belong to the reference association

I'm not quite sure what you mean when you say a "shared association". EA is different from other programs (such as Rhapsody). In other modellling programs the associations you create between elements are tangible model elements that you can see in the model browser... no so in EA.

102
Uml Process / Re: Using Connectors on IBDs
« on: November 20, 2015, 10:11:55 pm »
After some investigations I have concluded that it is possible to type connectors on an IBD (useful for interface modelling). The steps to do this are a little involved

1. Create a BDD and places the two blocks you wish to represent on an IBD. e.g. "Computer" and "Power Outlet"
2. Create an Association Block and use this to link up the first two blocks (or right click on an existing block, go Advanced | Association Class, and select the appropriate association). E.g. "Power Cable"
3. Add an IBD for the association class (Power Cable)
4. Right click on diagram and go "Synchornise Structural Elements". This creates to participant properties owned by the Association Block (Computer and Power Outlet) and connect the two together using a connector
5. Create an IBD for whatever system owns the computer and power outlet blocks (e.g. create a block called "House" and the create aggreation relationships to the Computer and Power Outlet blocks)
6. Synchronise Structural Elements (to quickly get all of the parts onto the diagram)
7. Create a connector between Computer and Power Outlet parts
8. select the connector and then Ctrl + L and a diaglogue box appears allowing you to specify the assocation to type the interface

It is important that the IBD you create for the Association block has the right participant properites at the end. For example, if you were to try and connect your computer and power outlet blocks via ports (which are themselves typed by some other block/interfaceBlock) then EA will not allow you to type this connector unless the participant properties  of the association class match the ports

Whilst it is rather unclear why EA is not letting you type the connector (it doesn't for example give you a warning) this behaviour what you want because it stops you acciendially specifying inconsistent interfaces

Request to Sparx: Adding some kind of message when attemping to type a connector when no suitable association class exists would help avoid a lot of head scratching by the user!

103
Uml Process / Re: Using Connectors on IBDs
« on: November 19, 2015, 09:49:04 am »
I'm using 12.1 Beta

Ctrl + L does not work, however I have been reading the SysML spec in more detail and Section 8.3.2.3 (of SysML version 1.3) talks about a "ConnectorProperty" which can "optionally be shown in an internal block diagram with a dotted line from the connector to the connector property". It goes on to state that this must be typed by "an association class stereotyped by a Block" (in other words an "Association Block")

Searching EA's help I found reference to a "Connector Property" in the IBD toolbox which "Creates an instance of an Association Block". What the EA help doesn't say is how I actually connect the connector and the connector property together (I'm guessing some kind of right-click?!?)

104
Uml Process / Using Connectors on IBDs
« on: November 19, 2015, 07:36:34 am »
I have two questions, one specific to EA and a more general one about modelling best-practice:

1. Specific: The SysML spec says that connectors on IBDs may be typed by associations. Does EA support this?

2. It is not always necessary to link two parts on an IBD via a port - you may legally join the parts directly together without using ports. Can anyone offer some "best practice" tips on when to use each approach?

Here's my thinking: connectors between parts represent purely general, structural relationships (e.g. a wheel is connected to an axle) whereas connectors between ports emphasise the specific behavioural features that are exposed between (e.g. a connection to a car via the diagnositics port reveals "diagnositic data")

Thoughts? Comments? Rotten Tomatoes?

Thanks in advance!

105
Uml Process / Display Action Pin Direction?
« on: November 10, 2015, 10:31:31 pm »
Is there any way to display the direction of an action pin on an activity diagram?

Pages: 1 ... 5 6 [7] 8 9