|
Rules for bug level
Why are there Bugs in Software?
(Continued from previous question...)
Rules for bug level
Rules for bug level will be determined by the project goals and
the project stakeholders. For example, a software product's
graphical user interface is very important in the market competition,
so inconsistencies in the GUI more important than missing functionality
Critical: Error that make the program can't run.
High: Important functional can be completed, but bad
output when good data is input.
Medium: Important functional can be completed and good output
when good data is input, but bad output when
bad data is input.
Low: Function is working, but there is some little bit problem
UI problem, like wrong color, wrong text fond
Rules for bug level will be determined by the project goals and
the project stakeholders. For example, a software product's
graphical user interface is very important in the market competition,
so inconsistencies in the GUI more important than missing functionality
Customer impact as the single way to rank a bug because it eliminates different
defintions among different folks. Customer impact is customer impact. There isn't an "impact to testing",
a "marketing priority", a "customer support" priority. There is merely a customer impact.
Since all of us produce software for a customer, that is really the only field needed.
It eliminates confusion in our profession as well as within the companies that each of us work for.
(Continued on next question...)
Other Interview Questions
| 