Book a Demo

Author Topic: Different auto name counters behaviour per package  (Read 3594 times)

Shadow

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Different auto name counters behaviour per package
« on: March 30, 2011, 04:14:17 pm »
Is it possible to have different auto name counters behaviours for different packages?

E.g. Say i set the Requirement type name to REQ (prefix) 001 (counter) in the Settings-->Auto Name Counters dialog box.

Each time i had a new requirement it will increment (REQ001, REQ002, etc...)

I currently have 2 packages that represent 2 different projects.
As i add requirements to both projects i would like the prefix to be related to the actual package.

Project 1 (package)
L-- REQ001
L-- REQ002

Project 2 (package)
L-- REQ001
L-- REQ002
L-- REQ003

At the moment i get something like this

Project 1 (package)
L-- REQ001
L-- REQ005

Project 2 (package)
L-- REQ002
L-- REQ003
L-- REQ004
« Last Edit: March 30, 2011, 04:15:55 pm by michael.wojtaszak »

«Midnight»

  • EA Guru
  • *****
  • Posts: 5651
  • Karma: +0/-0
  • That nice Mister Grey
    • View Profile
Re: Different auto name counters behaviour per pac
« Reply #1 on: April 01, 2011, 11:38:00 pm »
In this case you seem to be using "project" to refer to your work, not to an EA "project" repository. It appears you are using a package to contain each such "project" in your (single) EA repository.

If you are doing so I think you are out of luck. AFAIK the only way to achieve this is to list all your requirements in advance and insert them in order. Of course this kind of defeats any attempt to use EA as an exploratory requirements tool; you would be reduced to documenting the end result after the fact. Not too useful.

You could write an automation tool to go through the model and sort out the requirement names (and any other sequences you want). You could then run the tool whenever things changed, or before generating public documentation. Any such tool would also have to ensure that auto name parameters were correctly tweaked after each run. You would have to either turn off auto naming entirely, or set it to use some 'safe' values. This would prevent it from reusing any names already in the model (perhaps in some other package), which could trash work to date if you were not expecting it.

Not the best news, but that is all that comes to mind.

HTH,
David
No, you can't have it!

Shadow

  • EA Novice
  • *
  • Posts: 12
  • Karma: +0/-0
    • View Profile
Re: Different auto name counters behaviour per pac
« Reply #2 on: April 04, 2011, 07:52:28 am »
Quote
If you are doing so I think you are out of luck.
Thanks David... I thought that might be the case.  Appreciate your help on this one.

Michael.