Diamonds. They’re so beautiful. Women are fascinated and this fascination could never fade away. This is one reason why every woman, no matter what she comes from, must at least have one.
Software Bugs are important for the testing team like diamonds for the women.
Let’s see how we can map the 4 C’s which are four attributes that are used to calculate the value of a diamond to be used to evaluate bugs, “Clarity, Color, Cut, and Carat”.
But first, let’s define the term bug which will be used here, A human being can make mistakes which produce bugs in the work product. If a bug in the work product is executed, the system will fail to do what it should do or do something it shouldn’t, and causing a failure.
We’ll use the term Bug instead of failure.
Software Bug Clarity describes the clearness or purity of a bug. This is measured by how your bug is clearly scripted.
Software Bug Color describes the type of the bug, and its classification, this varies from calculations, workflows, UI, business process, etc…
Software Bug Cut describes the severity of the bug; severity relates to “how bad” a bug is to the business, usually determined by the technical behavior of the system, this can range from cosmetics to showstoppers.
Software Bug Carat describes the priority of the bugs, priority relates to how soon this problem should be fixed, usually determined by the business impact of the failure and this leads to priorities the bugs to deal with the highly weighted bugs first.
Written by: Samer Desouky