Autonumber quircks with requirements

[colinc]

There seem to be some quircks with autonumber and requirements.

When an internal requirement is created for an object autonumber does not seem to operate.

And when the requirement is moved external autonumber doesn't apply then either.

Thanks, Colin

[Paolo F Cantoni]

There seem to be some quirks with autonumber and requirements.

When an internal requirement is created for an object autonumber does not seem to operate.

And when the requirement is moved external autonumber doesn't apply then either.

Thanks, Colin

Colin,

You'll find this is by design.  Search for "responsibilities" and you'll get some hints as to why...

I think it's part of EA's unique UI.

HTH,
Paolo

[colinc]

Thanks Paolo, c'est la vie !

I guess in that case a different question is how people handle this problem?

I have a few hundred requirements that I need to publish into a tender document. They relate back to use cases/scenarios and have a priority determined by the scenarios they relate to.

I would like to put them into a spreadsheet format, which is easy enough using CSV export, but numbering would facilitate referencing. While I could just autonumber on the spreadsheet itself that obviously leads to risks of requirements order being changed etc.

Has anyone come up with a a better practice for handling requirement lists ?

ps. On a side note any way to get the package name included on a CSV dump ? I realise I may have to resort to an XMI dump and then do a XSL translation on it, but I'm trying to avoid it.

[colinc]

I've jumped directly to the DB instead; turns out is a very simple self join with the _t_object table...

Colin

[Paolo F Cantoni]

I've jumped directly to the DB instead; turns out is a very simple self join with the _t_object table...

Colin

Hi Colin,

I was going to suggest that but:

1) I got diverted by my "day job"
2) I felt I should leave it as an "exercise for the reader..."

Anyway - glad to see you "got it"!

Paolo

[colinc]

If anyone is interested I have uploaded a perl script onto the EA user group site that adds numbering to existing elements in a Requirements model.  It works by adding a tagged value of ID then setting it to an incrementing value. The tag ID values from the packages to get to the element are prepended to the tag.  

eg. The structure   is   tag   ID=2.1.1

Full documentation is within the script.

The script is at;

http://sharepoint.knowledgerecovery.com/external/eaug/Tools/autoNumber.pl

Hopefully someone will find it useful!
Colin

[thomaskilian]

That IS useful. I'm currently creating a Perl Add-In which works quite nice. You can place several Perl scripts in a directory and EA will automatically add them to a list of add-ins. Hopefully I'll upload that next week.