"Multiple" Multi-valued Attributes

llandale - Thu Aug 25 18:47:04 EDT 2011
You have a 'display' problem because you are not capturing the information you want to 'display'.

Perhaps you want 3 attributes with the same set of enumerations:
... Test
... Analysis
... Inspection
... Demonstration
The attributes could be called:
... Development Tests
... Qualification Tests
... Acceptance Tests

You could instead perhaps have 1 attibute called "Verification" with 4x3=12 enumerations
... Development Test
... Development Analysis
... Development Inspection
... Development Demonstration
... Qualification Test
... Qualification Analysis
... Qualification Inspection
... Qualification Demonstration
... Acceptance Test
... Acceptance Analysis
... Acceptance Inspection
... Acceptance Demonstration

• Louie

ZioAlfredo - Thu Aug 25 19:04:36 EDT 2011
Yes, I've thought of that, but the point is that I actually have 6 options for Verification Method and 5 options for Verification Stage, so I would need 5x6=30 options for the new Verification Attribute!
Is there a smarter solution?

Thanks Louie

ZioAlfredo - Thu Aug 25 19:04:36 EDT 2011
Yes, I've thought of that, but the point is that I actually have 6 options for Verification Method and 5 options for Verification Stage, so I would need 5x6=30 options for the new Verification Attribute!
Is there a smarter solution?

Thanks Louie

ZioAlfredo - Thu Aug 25 19:04:36 EDT 2011
Yes, I've thought of that, but the point is that I actually have 6 options for Verification Method and 5 options for Verification Stage, so I would need 5x6=30 options for the new Verification Attribute!
Is there a smarter solution?

Thanks Louie

SystemAdmin - Sun Aug 28 23:18:37 EDT 2011
How about one attribute (column) per Verification Stage where each attribute uses the same base enumerated data type that lists all of the Verification Methods - see attached screen grab taken from a module that I'm working on right now and uses this matrix approach.

Such a matrix makes it clear as to what verification method will be used at any one verification stage, it also makes it easier to see which requirements will be verified across more than one stage. We call this matrix a Verification Cross Reference Matrix (VCRM)

We used to also have a "Pass\Fail" attribute for each verification stage as well to record the status of testing against each assigned verification method within DOORS, but these days all of the verification results are handled in a Test Management tool like HP Quality Centre.

ZioAlfredo - Fri Sep 16 15:42:03 EDT 2011
Thank you very much Paul, it was very helpful.

Do you know how to set the background color according to the value assigned to a column?

I'd like to see red background for those stages in which verification failed and green for those that the verification passed.

Thanks

SystemAdmin - Mon Sep 26 03:55:33 EDT 2011
To be able to do this you will need to create a Results attribute for each verification stage e.g "Stage1 Results", Stage2 Results".....

This attribute will need to be defined to use a custom enumerated base data type that has at least two options, one for Pass and one for Fail, we just defined "P" or "F". These two choices should also be defined to be displayed in specific colors,e.g. Dark Green for Pass, Red for Fail. I assume that you know how to create enumerated base data types and define colors.

W.r.t. the view that displays the verification Stage attributes, insert the associated Results attributes after each Stage attribute - by using P & F as your two choices this allows these columns to be narrow.

For each column in the view that displays a verification Stage attribute, RH mouse click it's title cell, select properties and set the "Text Color" option to "By attribute", then select the associated Results attribute that will control which color will be used depending on whether P or F is chosen e.g when you select Pass in the Results attribute, it's corresponding Stage attribute should now display the verification method in the same color as defined for Pass. You may want to set the properties of each Results column in the same way - even though an attribute like the Results attribute has been defined to use colours, you still have to use the column properties feature to define it to use it's own colors.

Remember to save the view as these color properties are part of the view data.

We actually found managing test results like this to be a bit cumbersome, but in lieu of having a decent Test Management tool, then this might be the best way to visualise and track results status.