How Can i create a Sub Requirment in EA?

[eyalg]

I would like to create a hirarchy of requirments like:
Req1 bla
- Req1.1 Bla X
   - Req1.1.1 bla X Y

Today i am just using the packages to drill into requirments.

Thanks,
Eyal

[thomaskilian]

Auto-numbering is not supported, although many times requested. You have to do that on your own.
What you can do is to connect the requirements via associations (composite). That should reflect what you need.

[bmioch]

Hey guys

EA does support auto-numbering of any elements. I have attached a section from the Requirements whitepaper regarding auto-element naming at the end of this post. If you're interested in requirements modeling, make sure you check it out:
http://sparxsystems.com.au/downloads/whitepapers/Requirements_Management_in_Enterprise_Architect.pdf

However, hierarchical auto-numbering is not supported, but it will likely show up in a future version.

This feature allows you to configure Enterprise Architect to automatically name and number
requirements as they are created. (It can be used with almost any UML element such as Use Case and
Classes etc.). It is particularly useful with requirements since these are often required to have a unique
reference for external checking.
To enable Auto Element Naming, use the following instructions:
1. Select Settings | Auto Counters… from the menu to open the Auto Element Naming window.
2. Change the Type to Requirement.
3. Set the Prefix or Suffix. Both are optional. Eg. “REQ”
4. Type in the value for your first requirement in the Counter box. Eg. “0002” or “99”
5. Check the Active Checkbox to enable the Auto Naming.
6. Click Save to save your changes.
7. Click Close to exit the window.
The first Requirement will take the value entered into the Counter box, and Enterprise Architect will
then increase the value by one for every new Requirement. Eg. “0003” or “100”

[thomaskilian]

I was not precise with my first answer. Of course EA can auto-number, but only very limited. That is, it can not create a numbering structure like 1.1 and 1.1.2 or even 1.a or the like. It's just natural numbers with pre-/postfix.

[Rob_M]

One way to create a hierarchy of requirements is to drag a sub requirement onto the main requirement using the project browser (i.e. the project view.)

The numbering is not automatic, but it does create a hierarchy.

Rob M