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
16
General Board / Re: Separating ActivityParameters in Action Pin
« on: March 01, 2016, 04:41:07 pm »
When you call an Activity from an action you can use the structural element dialog to get the  Activity Parameters as action pins (each activity parameter you select will be an action pin).
This is not the preferred way to do this. Instead you should right click on the call behaviour action and choose 'Properties...'. Then press the 'Call' tab. Finally press the button 'Synchronize with Parameters'.

However, what's happening is that only one action pin is being made and under behavior it has ALL of the ActivityParameters listed. This would be OK if it at least split up the inputs and the outputs, but it's not, and anytime I try to add an action pin myself it still crams all of the ActivityParameters into one action pin.

Is there a way for me to split these up?
I can also not understand how you make this happen. Are you are referring to the problem where all pins are stacked on top of each other in a diagram when first created? An improvement would be to make EA distribute them evenly around the action. However, you need to move them around yourself for now.

17
General Board / Re: Allocate
« on: January 18, 2016, 06:18:16 am »
No, EA does not support relationships between connectors even though it has been part of the UML spec at least since UML 2.0. For UML modeling this feature is probably not so important, but with the introduction of SysML it is really important. In my opinion this shortcoming of EA is by far the most severe. Sparx have logged this as a bug to be fixed, but have not revealed when the fix will be implemented.

18
General Board / Re: Viewing instance when deleting a classifier
« on: December 24, 2015, 07:22:23 am »
It is not common to make an (extra and redundant) relation between instances and their classifier.

Of course not, and you don't have to. To see the relationship between the instance and its classifier in the traceability windows as I suggested you need to tell EA to show it. To do that you need to select 'Classifier' in the Traceability filter list (fourth icon from left in top row of the Traceability window).

19
Suggestions and Requests / Re: SysML Compartment notation
« on: January 23, 2012, 01:42:04 am »
A property with stereotype <<valueType>> will show up in the values compartment.

The references compartment is also not supported in current version of EA (922). And what about the flow properties, and operations compartments? Will they also be supported in future releases of EA?

Another related feature that is still missing is the option to hide SysML compartments. As a result, many block definition diagrams will be cluttered with ambigous information. If you use embedded parts/properties in your blocks you should think twice before upgrading to EA version 921 or 922.

20
Suggestions and Requests / Re: Element List improvements
« on: November 25, 2007, 11:50:06 pm »
Quote
1. Possibility to update any field on multiple selected elements, e.g. to change status on several elements at once.

I would like to select several rows in the Element List, then right-click and choose properties, and then change any property on the selected elements all at once. As an alternative, a right click on a specific column would allow me to change that particular column on all all selected elements at once.

Quote

2. Possibility to add additional columns from any given tagged value.

When dealing with e.g. requirements we use Tagged values to deal with requirement attributes. Then is is desirable to be able to change also these values on multiple requirements at once, in analogy with my first issue above. So the suggestion is to allow for additional columns to be displayed, from tagged values or e.g. the element stereotype  field.

/Hans

21
Suggestions and Requests / Element List improvements
« on: October 26, 2007, 04:39:15 am »
I would suggest two improvements to the element list feature:

1. Possibility to update any field on multiple selected elements, e.g. to change status on several elements at once.

2. Possibility to add additional columns from any given tagged value.


22
Suggestions and Requests / Re: More RTF Generate Options
« on: October 25, 2007, 08:30:15 pm »
To clarify: I would be very happy if the present possibility to filter based on element Status could be extended to filter based on any element tagged value.

The tag could e.g. reflect a configuration (slightly different requirements for different configurations of a system).


23
Suggestions and Requests / More RTF Generate Options
« on: October 25, 2007, 08:18:55 pm »
We need to filter out not only Packages but also Elements during RFT output. We therefore suggest that another option should be available in the Generate RTF Documentation -> Generate Options dialog box where the user is allowed to filter by:

Element tag <input tagged value name> <input tag value>

This feature is useful e.g. when the requirements are nested in Packages based on their type (Performance, Functional, etc) but requirements within packages need to be filtered based on other characteristics such as Phase or custom tagged value on element level.

24
Suggestions and Requests / Re: Requirements Hierarchy
« on: October 17, 2007, 11:12:27 am »
Yes, I'm well aware of the Hierarchy tab which I use frequently.

However, it does not solve my problem with preserving the hierarchy and the parent elements when doing a search. My suggestion is therefore to add an option to the search function that allows the user to optionally select parent items for a matching element, also when the parent items does not match the search criteria. The function will e.g. allow nested requirements to print correctly (together with its parent) in a report where only a subset of the requirements are required.


25
Suggestions and Requests / Requirements Hierarchy
« on: October 16, 2007, 08:33:26 pm »
I would like to see a feature where the requirements hierarchy (or any element hierarchy) optionally could be preserved when doing a model search.

This is useful if you wish to make a selection among requirements based on some attribute (tagged value) but need to keep the hierarchical nesting as well. (The result would be that requirements without match on attribute still should be selected if it owns an element with matching attribute.) Obviously, the resulting selection can then be used to create reports.

This is a feature that is available in other requirements management tools e.g. ReqPro/SoDA.

26
General Board / Re: Viewing instance when deleting a classifier
« on: November 30, 2015, 04:36:18 pm »
I use the Traceability windows (Ctrl+Shit+4) to find instances of a classifier. You can jump to each instance of a classifier by right clicking an instance in the Traceability window and choose Switch to Related Element. Make sure you have Classifier selected in the selection list at the top of the Traceability window.

27
General Board / Re: EA12.1 beta builds
« on: November 27, 2015, 09:44:06 pm »
But where are the release notes for the Beta builds? I cannot find them anywhere.

/Hans

28
General Board / Re: Using EA to make a instance of a block in SysM
« on: July 11, 2015, 11:08:07 pm »
I believe that in previous versions of EA it was possible to create an instance specification by just dropping a block from the project browser (while holding down ctrl and choose instance). However, in recent versions of EA this is unfortunately no longer possible. Instead a only a link or a part property can be chosen.

In EA 12 I think you need to create instance specifications from the Toolbox -> UML -> Object. Then when element is created you can specify the instance classifier and choose a block of your choice.

In my opinion Sparx should revert their profile to generate an instance specification instead. The reason is that many people use SysML the wrong way because of this feature. Modelers create internal block diagrams by dragging in blocks directly into the diagram, without first defining the block in an internal block diagram. (If associations are done properly, then part/reference properties are created automatically.) As a result, ending up with a model that is not consistent with respect to properties. Also, a property should never go inte a bdd which is also something that EA should prevent a user from doing. An instance specification however is fine on a bdd.

To Sparx: The best way forward would be to give three options for the modeller when dropping a block into a diagram.

1. Drop as Link
2. Drop as Instance Specification
3. Drop as Property (should not be an option on a bdd)

If it is not possible to have both instance specification and property then the instance specification is the one that should be the default. If you need to create properties within an internal block diagram you can right click on a Linked element and choose Advanced -> Convert to Property.

29
General Board / Create RTF based on search
« on: June 24, 2015, 03:13:56 am »
Hi,

I have created an RTF document based on a predefined search. (Instead of dragging packages onto model documents, a search is defined with a search value in tagged values of the model document.) The search looks like this:

Code: [Select]
SELECT Element.ea_guid AS CLASSGUID, Element.Object_Type AS CLASSTYPE
FROM ((t_object AS Element
LEFT JOIN t_connector AS fp ON Element.Object_ID = fp.End_Object_ID AND fp.Connector_Type = 'Dependency')
LEFT JOIN t_object AS product ON product.Object_ID = fp.Start_Object_ID)
WHERE
Element.Stereotype = 'Function'
AND (fp.Stereotype = 'Performs' OR fp.Stereotype = 'FunctionProvision')
AND product.Object_ID = <Search Term>
ORDER BY Element.Name ASC;

As you can see, only the CLASSGUID and CLASSTYPE are selected. Still EA is capable of reporting on any element attribute as well as any diagram embedded within the element. However, embedded elements are not reported.

Questions:

1. Is there a way to use the embedded elements Section in your RTF template when using RTF searches as a basis for populating the document?
2. EA ignores/overrides the sorting order in my search. Is it possible to make EA honor the search order?

/Hans

30
General Board / Re: SysML ways to add blocks to diagrams
« on: November 12, 2014, 06:24:59 pm »
You should use the last option to create properties in IBDs. Actually, I seldom create the properties explicitly as EA does it for me when creating the associations in the BDDs. But sometimes you do want to create the properties manually, and in these cases you should use the last option called Property.

Instances of blocks (instance specifications) should be created on BDDs not on IBDs.

Also, I cannot understand why you are having difficulties to "turn on" structural elements such as ports on your properties. Right-click on the property in a diagram and choose Structural Elements. You may need to check the Show Owned/Inherited checkbox to see them.

Pages: 1 [2] 3 4