Messages

1

Suggestions and Requests / Re: Local Paths support for any type

« on: May 23, 2008, 03:37:09 pm »

I want to second your request for this functionality. It will be very useful to  have the possibility to use local paths everywhere not just for generated code files.

2

Suggestions and Requests / Re: Show requirements priority in the diagram

« on: May 19, 2008, 04:12:47 pm »

Priority is not listed in Display "Element and Connector Properties" help page. Is it possible to use priority in shapescripts?

3

Suggestions and Requests / Re: Joined up models and notes/descriptions

« on: May 13, 2008, 02:02:14 am »

This feature would be extremely useful. There is an EA addin EA Object Editor which adds this feature to EA (page is in czech language).
But it is an addin with its limitations. It would be much more nicer to see it as a build in feature.

4

Suggestions and Requests / Re: "copy diagram" feature

« on: April 24, 2008, 07:32:36 pm »

When copying a diagram it could be nice to have these possibilities:
- shallow
- package
- deep

The new option "package" should work in such way that for every element on the copied diagram it will
- duplicate it, if it's in the same branch in the project as the copied diagram (all links to to this element will be also duplicated)
- display it on the new diagram as link to the original element
Visibility of all links will be the same as in original diagram.

There could be other ways how to specify which elements should be deep copied and which shallow copied. I think the package criterion is simple and would be useful.

5

Suggestions and Requests / Re: "copy diagram" feature

« on: April 17, 2008, 01:50:11 am »

Read this. I think it will help you with copying the whole diagram.

It's not possible to achieve a copy of diagram in the usual manner - Ctrl+A Ctrl+C Ctrl+V. But there is a way to achieve it.

6

Suggestions and Requests / Re: EA Beta 7.1.825 - Text Sizing

« on: March 04, 2008, 06:47:57 pm »

It works, but I've to use the mouse wheel in the Notes window every time I changed focus in the main window.

It wpould be much more useful if the   text size in the Notes window remain the same while changing focus in the main window.

7

Suggestions and Requests / Re: Packages, Namespaces & groupings

« on: November 07, 2007, 12:27:58 am »

It's even worse, because you have to checkout every package levele up to your namespace root, even if the pakages above your node where you want to reverse engineer are not affected.

This blocks team collaboration.

If the option "Save nested version controlled packages to stubs only" is set, then it's not necessary to check out parent controlled package if you want to check out child controlled package.

...

And add my vote to the "grouping only packages" feature.

8

Suggestions and Requests / Re: Diagram element marking

« on: December 14, 2007, 06:24:11 am »

I have to open EVERY use case and switch to Scenarios

You can open the "Rules and Scenarios" window. It can save you a little time, when searching for scenarios.

9

Suggestions and Requests / Re: API support for Export/Import Reference Data

« on: November 22, 2007, 12:00:45 am »

And it will be very nice to Version control Reference data from EA.

It has a
 big   + nice control in the same way as packages
 small - necessity to check out Reference data before modifying them.

10

Suggestions and Requests / Re: Reference Data Import needs "Delete"

« on: October 20, 2007, 12:19:46 pm »

Consider you have a package with some elements. You can
- export it, and import to another project (strip GUIDs or not, as you want)
- version control this package, check it out, delete some elements, check in, somebody else can get the latest version of this package.

I think this is exactly what you want to do with reference data.
- export it, and import to another project (as new, or replace existing set of ref data)
- version control reference data, check it out, delete some data, check in, somebody else can get the latest version of this "reference data package".

Now it's possible only to
- export reference data
- import them as new
You can version control the exported xml file on your own. But it's not possible to import this xml file and replace the complet set of ref. data. The possibility to delete ref data not in the imported xml file is missing.

Some examples:
1. it's possible to work offline on a Requirements package and check in this package lately, when online. This is not possible with Project glossary because glossary items are not elements in a package, but reference data.
2. it's possible to work offline on a GUI package and check in this package lately, when online. But new images used in GUI diagrams will be lost unless exported/imported as ref data. Images are not elements in a package, but reference data.

Is it clear, what I mean by "Version control Reference data"?

I mean the possibility to make a table with reference data "version controlled table" just as it is possible to make a package "controlled package with version control".
When somebody wants to update such version controlled table, it's necessary first to check it out, update it and then check it in.
"Get all latest" will work together with controlled packages and tables.

The ability to delete ref data, that are not in the imported package is built in the idea to control tables with ref data. It's not possible to implement "controlled tables" without this ability.

11

Suggestions and Requests / Re: Reference Data Import needs "Delete"

« on: October 19, 2007, 01:00:22 pm »

What about Version control Reference data such as Images, Project Glossary etc. ?

12

Suggestions and Requests / Re: Newbie Questions

« on: October 19, 2007, 01:10:27 pm »

2) see help on copy

13

Suggestions and Requests / Re: Template generator: filter connected elements

« on: October 10, 2007, 10:17:40 pm »

Seconded.

This can be added to the general requirement - add filter ability to the report generator.

14

Suggestions and Requests / Re: Attribute to attribute traceability

« on: October 04, 2007, 11:05:21 pm »

See this reply from Simon in a related topic:

It is possible to reference an attribute with a tagged value.  Create a predefined tagged value with the following.

Type=RefGUID;
Values=Attribute;

15

Suggestions and Requests / "X" Close Diagram Button on the Tab

« on: September 06, 2007, 08:58:16 pm »

I'm used to have diagram tabs on the top. It would be nice to have the Close Diagram Button (little "x") situated on the tab, like Mozilla Firefox or Internet Explorer.

It could be be implemented by an option
[] Close Diagram Button is on the Tab
  which will be active when
[] Main Diagram Tabs at Bottom
  is unchecked.