Messages

1

Suggestions and Requests / Re: Copy element "as new" should keep the li

« on: July 15, 2011, 10:21:03 pm »

Thanx a lot for the script.

I think this should be a feature included by default in EA user interface.

Cheers,
Davide

2

Suggestions and Requests / Copy element "as new" should keep the li

« on: July 15, 2011, 07:27:09 pm »

Hi
when copying a package with elements into a new one, all the newly created elements in the new package keep the original package's elements links.

Why not to do it also for a single element's copy (as new)? Or, at least, I would give the option to perform it and let the user decide.

Example:
I have a number of packages containing test cases; the test cases are linked to their requirements/use cases elements.

I decide to do a test run, so I create a new package for the test run and now I want to copy in it the test cases that will be tested in this run.

Unfortunately, the test cases in the run will loose the links to the requirements (because I have to do the paste as new), hence loosing the traceability reqs-tests.

Please let me know what you think.
Davide

3

Suggestions and Requests / Re: Sharing a user defined search with other EA Us

« on: June 15, 2011, 05:46:32 pm »

In addition, you can create your own MDG Technology file where you can add the exported custom searches.

Just add the line
<ModelSearches file="path\file.xml"/>
in the . mts file

Then the technology would have be used in your company, so you have to add it in all the users's EA installations.
Davide

4

Suggestions and Requests / Issues and changes management

« on: May 06, 2011, 06:03:28 pm »

Hi
right now, EA has a variegated way of managing issues and changes.

One can define them in the maintenance window of each element, or define them as external elements (issue, change) linked to the element(s) displaying the issue/change. Moreover, there is a project issues window where one can define issues at project level. To me it sounds quite confusing

I would like to propose a method to standardize the management of issues and changes, based on what is already done for requirements.

Reqs can be internal to an element (properties, rquirements) or externallly linked to the element through the realize relationship. They are anyway listed in the requirements tab of the element's properties.

I would like that issues and changes would be treated in the same way with dedicated tabs in the property window of an element; they should be listed either they are internal or external, and internal issues/changes could be moved external if required. In the same way, external issues/changes could be dragged on elements, thus linking them automatically to the element.

The issues/changes tabs in the elemen's property should be derived from the current maintanace window, thus displaying all the required infos for the issues management (status, initiated, resolved etc); I don't know exactly how to do it, but this is Sparx work.

An additional (very welcome) enhancement would be to list ALL the issues/changes (internal or external) in the project issues window (to be eventually renamed into project maintenance).

The same could be extended to defects and tasks.

What do you think about it?
Davide

5

Suggestions and Requests / Re: Parametric RTF report generation

« on: April 28, 2011, 05:04:26 pm »

I just make an example for requirements (since I'm doing reqs management with ea):

in the project specification, I list the requirements with few details (name, text, priority)

In the design documents, I list the reqs with more details, such as connections to other elements or derived requirements.

The template format is exactly the same in both situations, I just exclude the section in the rtf generation window.

By default, ea should enable all the defined sections of the template, so the behavior would be exactly the same as it is now, with no additional complications.

6

Suggestions and Requests / Parametric RTF report generation

« on: April 27, 2011, 09:45:32 pm »

Hi
I've searched in the forum but couldn't find anything about this...

Let's say I've created a template for the RTF report where I've specified lot's of infos to be generated for each element (tagged values, requirements, constraints and so on) with my custom formatting.

Now I have the need to create reports with different levels of details  (say for  the sales or the tech dept ) and I'd like to somehow enable/disable the sections of the template.

Now the only possibility is to copy the original template and to disable the sections in the new template, with clear disadvantages in terms of modifications impact (if I need to modify something, I have to run through all the affected copy templates).

The suggested solution would avoid this copy, allowing the user to select/deselect the sections in the report generation dialog, while using all the times the same report template.

What do you think?

Davide

7

Suggestions and Requests / Composite diagram on elements' instances

« on: April 28, 2011, 11:39:10 pm »

Hi

When I instantiate an activity through a call behavior action, or when I instantiate a block (SysML) through a propety(part) on a diagram, I would like to be able to show the composite diagram of the parent (activity or block) in the current diagram.

Moreover, if the activity has parameters or if the block has ports, I would like to be able to visually map the calll behavior action pin to the activity parameter; for the block , I'd like that the port of the block instance is directly mapped to the port of the block specification.

If you look in the help of EA, for activity diagrams, they show exactly this concept, but unfortunately the Contact Sales Staff diagram is not the composite diagram of the original activity, it has been drawn manually on the activity (or call behavior action ?) present in the current diagram. If they wanted to reuse the internal diagram of Contact Sales Staff in other diagrams, they would have to draw it again and again.

What do you think about it?

Davide

8

Suggestions and Requests / Line style shortcuts

« on: January 28, 2010, 02:13:03 am »

Hi

since I use it very often, I'd like to have a keyboard shortcut for all the line styles, not only the direct/auto/custom

Thanks
Davide

9

Suggestions and Requests / SysML Ports with ports

« on: January 28, 2010, 02:27:44 am »

Hi
as far  as I've understood, sysml ports can be typed by blocks, which in turn can have additional ports. The result is ports with nested ports.
See this image for an example.

It would be very beneficial for me to be able to do the same in EA.

Thanks
Davide

10

General Board / Re: SysML internal block diagram

« on: June 12, 2011, 04:34:15 am »

The only way is to drag the block (simple link)  into the ibd, enlarge it as required, and then add parts and ports.

Same for activities with their parameters.

Davide

11

General Board / RTF Property type

« on: October 24, 2011, 09:03:09 pm »

Hi
I'm using EA 8.0.856

I would like to document a port of a SysML block in a RTF report.
What I'm missing is the information regarding the port type (the one set with advanced/set property type); I've tried to select everything of the available fields of the embedded element, with no success.

Could you please give me a hint?
Thanks
Davide

12

General Board / Re: Traceability Output

« on: June 15, 2011, 05:18:29 pm »

How did you setup the export to CSV? I didn't even know it was possible (at least without scripting).

The only way I know is to list the element's connectors in the rtf report, then you could also exclude all the connectors but the dependencies in the rtf generator options.

Davide

13

General Board / Re: Show contents of package diagrams

« on: June 12, 2011, 04:39:26 am »

The small icons are displayed because you have the option "Package contents" enabled in the diagram properties (right-click on the diagram, Elements tab).

For what you want to do, you have to disable this option, then pull your sleeves up, enlarge the packages as required and drag the classes (simple link) on them...  :-/

EA doesn't do it automatically...

Then draw associations between classes and so on.
Davide

14

General Board / Re: Document generation for linked elements

« on: May 27, 2011, 11:41:02 pm »

If the link is a realization (UC->req), they can be listed with the "external requirements" section. If the link is a dependency, the can be listed with the "connector" section of the template.

See the "use case scenario template" under the System Document templates in the resources window.

Davide

15

General Board / Re: SysML <<copy>> relationship for Reqiurements

« on: May 16, 2011, 04:20:31 pm »

hi, see this
http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1303285984/5#5