Tagged Values - Question

[jedwards]

I have a number of use cases that have been created via analysis of a large legacy system.  I need to go back and assign complexity, priority, size and a few other  data points to each use case.

I'm thinking I should add them to the use case objects as tags.  Is this an appropriate use of tags?  

As an alternative I could store this information in the use case objects' note field, but then it's not very accessible (through SQL queries, this is the corp. edition w/ a DBMS repository) unless I write a small script to parse the notes...

Any advice is welcome!

Jon

[MichaelHanson]

I would say it is an appropriate use of Tags, that you are suggesting.  Although it is worth mentioning that Use Cases already have some of the properties you are looking for such as Complexity.

I mention this because as far as I am aware the Estimation features of EA can't use Tags so you would need to use the provided properties if you plan to use this feature.

Mike Hanson

[jedwards]

Thanks Michael, that's what I was hoping.  I've already written a SQL script to insert the necessary t_objectproperties records into the SQL Server repository, just to make entering the data a bit easier.  I suppose I can always go back and write a few more scripts to populate the appropriate complexity, etc properties.

Speaking of the Complexity property, I was going to use it but there are only three values and I need to be a little more specific than that.  Is there a way to manage the default complexity levels?

Jon