When referring to software, what does a "QA Environment" mean?

I believe it has something to do with security, but I'm clueless. Please advise.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Quality assurance (QA) refers to the engineering activities implemented in a quality system so that requirements for a product or service will be fulfilled. It is the systematic measurement, comparison with a standard, monitoring of processes and an associated feedback loop that seeks error prevention. This is in contrast with quality control, which is focused on process outputs.

Two principles included in QA are:
-"Fit for purpose":the product should be suitable for the intended purpose
-"Right first time", mistakes should be eliminated.

QA includes management of the quality of raw materials, assemblies, products and components, services related to production, and management, production and inspection processes
sheana11Author Commented:
I am not a programmer(I should have mentioned that). That means you took the trouble to explain in elegant, but technical language, what QA means.

Unfortunately, most of it is over my head.....perhaps you could explain in terms of an analogy, pretending you are speaking to someone in elementary school. That would be helpful. Thanks in advance.
Hmmm, how to put it kindly? Basically, if you're not a system engineer or programmer, then QA is just techspeak. It's the process of designing software without mistakes. I'm not a programmer, either, and this sort of BS is what you'll see in an ad for a programmer or system engineer position:
"Large enterprise seeks system engineer to work in a QA environment, must have 3 years of design experience, etc."
It just puts a label on the systematic design of software: Design it right, don't make mistakes. Managers love that sort of BS. To most technicians, it's just BS.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sheana11Author Commented:
Now that you've explained it, I believe this comment was for the IT people attending the webinar for our software that is being updated. He probably should have said "THIS IS FOR THE IT PEOPLE.....EVERYONE ELSE COVER YOUR EARS!!!!!!!!!!!!!!!!!"
sheana11Author Commented:
Answered it as best he could, given my level of understanding.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.