Level Numbering

[Doug Blake]

In the days before EA we used to create Word docs full of requirements all nicley numbered in an hierarchical way.

Level numbering would seem to be the answer, but it only goes half way to being the solution I need. Packages are not included in level numbering so there is no field to insert into the RTF generated document called Pkg.LevelNumber.

Is this something that Sparx could accommodate?

Currently I use Packages in the early days of a project and when the package details have firmed up, I create a Feature of the same name at the same level and move the contents of the Package into the Feature, then delete the Package. This continues till I have a single top level package full of nicely numbered Features.

It doesnt matter that this is now a single package because changes to the package are now few and far between (hopefully)