Project Browser with a life of its own

[Doug Blake]

I am currently entering lots of requirements and diagramming them in groups and it is most convenient to CTL-Drag a requirement on the drawing to make a copy and then edit it. However the project browser tree decides to contract to the next package level for every requirement I add, and they are typicaly 2 or 3 levels down from a package.

Why does the project browser even get involved, apart from displaying the new element?

I am sure its not really a bug, but its really annoying....

[qwerty]

If you create a new instance EA creates that in the package where the diagram is located. Works as designed. Why do you create instances at all? Wouldn't it be more logical to use the original requirement?

q.

[Doug Blake]

If you create a new instance EA creates that in the package where the diagram is located. Works as designed. Why do you create instances at all? Wouldn't it be more logical to use the original requirement?

I am not sure you quite understand the way I am using EA.

In order to use the Level Numbering feature, I have shunned packages for holding Requirements in favour of Features. So I have a top level Package and then a tree of Features and ultimately Requirements leaves. Diagrams are scattered throughout the tree, not just at package level.

There are a couple of ways to copy requirements.

In the project browser, select Requirement, copy it and paste it - INTO A PACKAGE. EA wont allow me to paste it into a Feature, but once pasted into a Package I can move it (drag & drop) to the Feature of my choice (Dumb eh?)

Second way is the way I prefer to Ctl drag a copy in the diagram. But the Project Browser likes to close ranks when I do this.

In case you are wondering, the Level Numbering is replicated precisely in eaDocX documents with the proviso that I shuffle the elements within the project browser to enforce their numbering. Seems weird, but the order eaDocX takes the elements from the database isnt always the order you see in the Project Browser unless you shuffle them up and down the tree when new requirements added.

Looking forward to the release of EA10!!

[qwerty]

Indeed quite different from how I'd work with requirements. I'm sure you have reasons for doing it that way so I wouldn't start arguing. However, we have to live with EAUI...

q.