Recently in this space I’ve described the SEI’s recent research in architecture support for testing (AST), with which we are striving to understand how architecture can be used to lead to better testing outcomes. I also described a testing practitioner’s workshop we held at the SEI in February, which resulted in a set of 29 model problems in AST. These are problems that, if solved, would make a substantial difference in the testing of software. I invited readers of this blog to add their votes to those of our workshop participants to produce a ranking of the model problems in terms of importance, using the following scale:
- VH (Very High) = 5 (meaning that the respondent places a very high value on this capability)
- H (High) = 4
- M (Medium) = 3
- L (Low) = 2
- VL (Very Low) = 1 (meaning that this is a capability that is not at all valuable to the respondent)
As promised, here are the results.







