Throughout this process, we're going to have to deal with problem management. Now, problem management in this context is defined as defects in product that is being produced. And in that, we have flaws and these would be characterized as errors in design. We have behavioral anomalies which can produce things that are operational issues or a strangeness, which if we think carefully about that, it is something that may not appear blatantly obvious and wrong, but it is something that seems odd in comparison to the results we've gotten from previous tests. A certain odd kind of behavior, possibly due to a combination of things or other characteristics.

We also of course have errors and faults. These are typically outcome-based issues and these can be derived from other sources as well, impacts from other modules or other elements within the code. Then of course, we have our vulnerabilities and these would prove to be targets of hostile manipulation, exploitation. And these would be things like weak controls, poor coding practices and choices that would be prone to exploitation, bad implementation, and other elements.

We have, of course, the infamous bug which are defined as errors in coding. Now, when bugs are found, we need to develop a method for both detecting and tracking them. Because what we need to look at is how to elaborate when we find a bug. And that means, looking at it in greater and greater detail, getting better and deeper knowledge about how it works or how it fails so that we can do a better job of prioritization, and thus repair. We, of course, want to try to remove the bug but history tells us that removing the bug may in fact be very costly. That means that we're going to have to change our focus to instead of removing it, mitigating by perhaps to put it one way, writing a rounded.

We either have to correct the bug itself or we have to compensate in that way. We could, of course, if the bug itself is harmless in what it does truly harmless not perceived as that, we might be able to ignore it. We're always gonna have consider the cost-benefit analysis in determining things like prioritization, repair, correction, compensation, mitigation, removal, and other related issues. Because we must determine the most efficient course and that means what is the impact that it will have on the schedule or cost to produce the final product. And also in the process, as is well-known trying to remove bugs often times instead of removing alone. It also introduces the possibility of more bugs.