Book a Demo

Author Topic: Autonumbering / Autonaming and Relationship Matrix  (Read 3340 times)

Emilio

  • EA User
  • **
  • Posts: 78
  • Karma: +0/-0
    • View Profile
Autonumbering / Autonaming and Relationship Matrix
« on: July 08, 2008, 07:27:04 pm »
The auto-numbering feature is quite handy for Requirements and Use Cases. It has however a drawback in that it is only limited for single sequences (0, 1, 2, 3... N).

The autonumbering allows you to specify the type (Requirement, Use case, etc.), Prefix, Counter initial value and Suffix.

In our organization we follow a slightly different numbering scheme which I have also seen in other organizations. In this scheme rather than using a single-path sequence, we use a "book" or "hierarchycal" numbering such as 1, 2, 2.1, 2.2, 2.2.1, 2.2.2, etc.

This hierarchy is quite often used for aggregation/composition of requirements (or use cases). This numbering system is not supported by EA.

Actually it kind of does but not for the auto-number. In the Requirements one can use the Show Numbering feature that autoasigns numbers and if you drag a requirement INTO another one then the number the dragged requirement becomes something like 1.1 (like I described above).

So, it would be nice if there was a feature to auto-number the requirements (or use cases) according to that same hierarchycal number given by EA when the uses chooses "Show Numbering".  So EA already has the logic to do it but misses adding the feature to the Auto Element Naming.

In that case it would also be handy if this auto-element-numbering/naming can be used as a prefix. For example, say my requirement was autonumbered GEN-FR-1.1 I would like its name to become "GEN-FR-1.1.1 Friendly name here" rather than just "GEN-FR-1.1.1". Main reason here being that it is easier to read at least one set with names in the relationship matrix.

And speaking of features let say the actual REQ/UC full name is composed of <Auto-Naming-Number> <Friendly Name> that in the Relationship Matrix the user has the possibility to select either of the following for the relationship axis labels:
  a) Use Auto-Naming-Number  (GEN-FR-1.1 -> UC-1.5)
  b) Use Friendly Name (Generic Requirement -> General use Case)
  c) Both (GEN-FR-1.1 Generic requirement -> UC-1.5 General use case)

Wow, that is 3 useful features in one.