In the Root Cause Analysis process, we categorize by application. However, we live in a world, with hundreds of .

So, for our website, it is easy to categorize if it is .com. However, if it is a supporting service, there are about 180.

In Rally (CA Agile Central), we have a custom field with our list of applications. However, this will triple in size (or more) if we add each service by name.

What is your recommendation(s) to ? Should we perhaps group services by Engine, Broker, External Integration, Internal Integrations, etc? Or should we just list all (and maintain that list), or just put ‘Services’, OR, just do something else?

Thanks in advance…



Source link https://sqa.stackexchange.com/questions/34516/categorizing-defects-in-web-services

LEAVE A REPLY

Please enter your comment!
Please enter your name here