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

Pages: 1 2 [3] 4
31
General Board / Re: Hide Stereotype for SysML 1.3 Ports
« on: September 22, 2014, 10:29:43 pm »
I think I have already sent a bug report about hiding port stereotypes. However, I think you should send another one, to put some more pressure on Sparx.

Omitting the stereotypes on SysML ports is fine, and perfectly valid SysML. However, it is not valid SysML to use the full stereotype on a port that is typed by an interface block, or to use the proxy stereotype on a port that is typed by a block. The type of a non-stereotyped port can be implicitly determined by the port type (block or interface blocks).

I agree, it is annoying that alignment of ports is not working.

(Another bug wrt SysML ports, is that multiplicity information is not displayed when ports are stereotyped either full or proxy. I have filed a bug report on this which has been accepted by Sparx.)

/Hans

32
General Board / Re: SysML connector types
« on: July 04, 2013, 11:01:00 pm »
Connectors (that can be runtime instances of associations) should be able to be 'typed' by the association that is its type, see section 9.3.6 in UML Spec issue 2.4.1. This is UML 2.0 (has been included in the standard for nearly 10 years) and not something which is specific to SysML. This is an important feature still missing in EA. Perhaps the need to specify a classname of an association that the connector represents is higher in SysML than in UML and that the need to include this feature into EA is greater than ever.

33
General Board / Support for Parameter Sets?
« on: February 05, 2013, 10:56:06 pm »
I have tried to find support for parameter sets in EA, but cannot find any information about it or how to accomplish this. In an interview with Geoffrey Sparks some years ago this was planned to go into EA 6. Does anyone know how to make parameter sets?

34
General Board / Re: SysML and allocations
« on: January 29, 2013, 02:09:18 am »
Relationsship based compartments is not supported yet. According to Sparx this feature will be added in the future. See this post:

http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1321607092

/Hans

35
General Board / Re: OOSEM Profile for EA?
« on: December 15, 2012, 01:34:13 am »
I have tried your recepie for creating profiles based on SysML 1.3, but it does not work. I.e. when I use the profile to create a logical block, the stereotype <<logical>> is not displayed.

I have attached a small example of my profile. What am I doing wrong?


/Hans

Code: [Select]
<?xml version="1.0" encoding="windows-1252"?>
<UMLProfile profiletype="uml2">
      <Documentation id="DC61E99A-5" name="OOSEMProfile" version="1.0" notes="OOSEMProfile"/>
      <Content>
            <Stereotypes>
                  <Stereotype name="logical" notes="" cx="90" cy="70" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0" generalizes="SysML1.3::block" baseStereotypes="SysML1.3::block"/>
            </Stereotypes>
            <TaggedValueTypes/>
      </Content>
</UMLProfile>

36
General Board / Re: OOSEM Profile for EA?
« on: November 28, 2012, 09:02:18 pm »
Pontus,

I have studied the OOSEM method extensively and agree that it is well thought out. In my opinion it is the best MBSE-method available at the moment.

An OOSEM-profile in EA would be great. But, as far as I know it is still not possible to create a profile in EA based on other profiles (such as SysML). Sparx has indicated that this feature can be expected in a future build, but I think it is still missing. Fortunately, most of the OOSEM stuff can be modelled in EA without a profile.

For me some obstacles were overcome by studying the actual model file which is provided by the publisher at this location. Unfortunately the model file is in MagicDraw format, which is not possible to import into EA. I got help to convert it to XMI and then imported this file to EA. The resulting diagrams were far from perfect, but the model organisation was retained and answered several of my questions.

/Hans

37
General Board / Re: SysML Association Blocks
« on: September 20, 2012, 08:42:42 pm »
In a SysML bdd-diagram, right-click on a Block and choose Advanced | Association Class... In the dialog that pops up you can select which association in the diagram the Block will be linked to.

38
General Board / Re: SysML and EA 9.2
« on: July 19, 2012, 07:42:28 pm »
Quote
We are planning to add relationship based compartments (including allocatedFrom and allocatedTo) and visibility options, expect to see them both relatively soon.

I hope that relationship based compartments are still in the roadmap. To be able to show allocation in compartments is a very important SysML feature. Any news on when we can expect to see this feature?

39
General Board / Re: SysML and EA 9.2
« on: November 22, 2011, 11:10:29 pm »
I'm also very happy to see that the SysML capabilities of EA are improving. I agree that the questions raised by philchudley must be addressed. The capability to control the visibility of different compartments must be provided (on both diagram and element level).

Also, the allocatedFrom and allocatedTo compartments is still missing.

I have found the hidden feature to add value properties to blocks: First you need to define your value types. Then try to drag a value type from the Project Broser and drop it on a Block, and choose 'Drop Class As Composite Part'. Voilą!

40
General Board / Reentrant, a missing property on activities?
« on: February 09, 2012, 08:03:53 pm »
There is a property on UML activities called Reentrant.

If an activity is reentrant, each complete set of inputs arriving at a usage will create a new concurrent execution of the activity. I.e. it tells whether the behavior can be invoked while it is still executing from a previous invocation.

Is this property missing in EA?

41
General Board / Re: SysML internal block diagram
« on: December 02, 2011, 10:21:59 pm »
Quote
However, it seems that flows from activity parameter nodes to actions cannot be displayed.
This statement was not correct. It is possible to specify an object flow from an activity parameter node to an action pin.

However, there is one remaining issue that is yet to be solved. It seems not to be possible to suppress the containing diagram frame from being saved on those diagrams that include a composite diagram notation with its on diagram frame used to display the activity parameter nodes on the border. (We get two diagram frames, one on top of the other.)

Is there a solution?

42
General Board / Re: SysML internal block diagram
« on: September 19, 2011, 04:12:31 pm »
Yes, thanks. This actually works. At first I didn't see the activity parameter nodes until I changed the visibility attribute in the element context meny | Embedded elements | Embedded Elements...

However, it seems that flows from activity parameter nodes to actions cannot be displayed.

43
General Board / Re: SysML internal block diagram
« on: September 17, 2011, 12:50:52 am »
It should be possible to display the activity parameter nodes on a diagram frame in SysML (and UML). I don't now about ports on the the Internal Block Diagram, but for the act diagram this is definitely true. If it is not possible, has anyone filed a "bug report" on this to Sparx?

44
General Board / Re: Configure Version Control on Separate EAP File
« on: July 29, 2009, 10:38:37 pm »
I have exactly the same problem, and would also like to have the script that you refer to in this post. How can I get it?

45
General Board / Preserve relationships from imported model element
« on: May 20, 2008, 12:17:21 am »
We are working with multiple models in parallel, using Enterprise Architect. Some which are general (framework) and used as building blocks in more project specific models. The framework model is used by importing it to the project specific model as a root model (from XMI). The model is made read-only to the staff working on a specific project. When an updated version of the framework is released it is imported again into the project specific model. Relationships that originate from elements outside the framework root model are retained during update, also if the relationships have framework elements as target elements. Now, here is my two questions:

1. Relationships may be created from the framework elements even though this model is write protected using the EA-security mechanism. Should EA security mechanism allow this relationship to be created? I think it should not.

2. The relationships created from the framework elements are discarded when framework model is imported again with a new update. How can they be retained?

One typical relationship that we would like to model this way is the SysML <<Satisfy>> relationship. We want to use this relationship from Blocks in the framework to requirements in the project to model that the specific requirements are fulfilled.

Any ideas?

Pages: 1 2 [3] 4