Term for errors-that-don't-look-like-errors?

Hello, I've found it useful in software design to distinguish between failure modes that will be obvious and those that may be confused with good behavior.  This is important for safety-related calculation-type software, in which the numbers may be taken and used to do something important.  I audited one organization that makes stress-analysis software, which classifies errors as follows:

Type A -- minor problems that dont affect results (ie warnings)
Type B -- major problems that cause results that are obviously wrong (eg crashes, or results in impossible values -- you discard the results)
Type C -- major problems that cause results that are not obviously wrong (eg a math error that adds 10 to the result, which user will use and causes a dangerous situation)

I think this was an organization-specific classification.  I'm looking for a handy or industry-standard term for their "Type C" issues.  I always find myself saying "errors that don't look like errors" or "non-obvious errors," which is a mouthful.  It seems like this is an obvious enough concept where I'd be surprised if there wasn't some industry standard that addresses, defines, and assigns terminology.

Anybody know of any standard terminology for this?

Who is Participating?
TommySzalapskiConnect With a Mentor Commented:
Maybe that's not really what you are going for though.
Perhaps something like
hidden error
discrete error
masked error
In programming we call those logic errors.
Type A - warning
Type B - runtime error
Type C - logic error

Note of course there is gray area with "obviously wrong"
RonMexicoAuthor Commented:
Yeah "logic error" isn't quite it, as some logic errors will be obvious and some not.

I like "hidden" and "masked" though.
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

TomRScottConnect With a Mentor Commented:
Unobserved error.

 - Tom
I meant discreet of course, not discrete.
Seaton007Connect With a Mentor Commented:
Semantic Error

Noun 1. semantic error - an error in logic or arithmetic that must be detected at run time
RonMexicoAuthor Commented:
A semantic error, I believe, is just not a syntax error and won't be caught by the compiler, correct?  That's different... a semantic error that causes a crash would be Type B, a semantic error that causes incorrect but plausible results would be Type C.

By the way also interested -- has nobody come across this distinction in any standard or text?  I'm surprised if not.  The (very big and successful) organization I visited spends ALL THEIR TIME on Type C errors... which makes perfect sense.  Bugs in math are very important, because buildings may fall down; bugs that might cause your program to not start are relatively insignificant.
RonMexicoAuthor Commented:
... in other words if they find a bug and the developer successfully argues that it is not Type C, it is deprioritized.
mccarlConnect With a Mentor IT Business Systems Analyst / Software DeveloperCommented:
I don't know of any official standards (or even any non-official but widely accepted standards), but the term that we use for these types of errors is:

latent error
RonMexicoAuthor Commented:
Thanks all!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.