Book a Demo

Author Topic: Auto Counting for Requirements  (Read 3050 times)

JohnnieMo

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Auto Counting for Requirements
« on: July 01, 2004, 01:03:16 pm »
I am using EA as a requirements management tool.  I am using the auto counter to create unique identifiers for each requirement.  The only issue is that I cannot use the requirements tracker within the element itself because it will not apply the auto counter.

For instance - each GUI element contains a requirements tab.  I want to enter my requirements and type within this tab, but when I "move external" I want to apply the counter.  Does anyone know how to do this???

Is there any other way to "tag" requirements with a unique identifier?

I am relatively new to this but am already pleased with EA.

John

thomaskilian

  • Guest
Re: Auto Counting for Requirements
« Reply #1 on: July 01, 2004, 05:26:56 pm »
John,
you have to apply the autocounter when you create the requirement. Actually the autocounter configuration is a bit clumsy (see also http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.cgi?board=suggestions;action=display;num=1087330707;start=0#0)

JohnnieMo

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Auto Counting for Requirements
« Reply #2 on: July 02, 2004, 08:23:55 am »
Thanks Thomas....

However - I am creating the requirements using the supplied tab within the GUI Elements dialog.  So I'm not creating a new element each time.  It makes sense for the auto-counter to leave these alone, but when I "move external" I want the identifier to appear.  It does not.  

Also - it would be nice if the "move external" button would allow more than one requirement at a time and would default to the current directory of the given element.

John

thomaskilian

  • Guest
Re: Auto Counting for Requirements
« Reply #3 on: July 05, 2004, 08:07:47 am »
John,
the way I work with requirements is the following. In the very beginning I start with an Custom (Extended Class) Diagram where I put all requirement (already external). I also place the actors (stakeholders) here in order to connect them with their requirements (helps tracking a lot in a later phase). Having gathered these requirement I start sorting them out.  Later I connect requirements and Use Cases via a Realize relationship. Working in that way you get the autocounters working as desired.

What you want to do should be feasible via the automation interface (place autocounter text in front of the existing heading and move it to a desired place likely nearby the object where it stems from).