As a technical term quality is not a description but the concept of meeting the specification. Outside of the comparison with the spec it is meaningless. High or low quality more so.
Describing the spec you can/do work to will give a more accurate idea of what can be expected and be more useful to a potential customer than lofty, vacuous phrases. A high or stringent spec is the business.
I was an aero-engine Quality Engineer for 24 years and slept through many presentions of consulants brought in to describe/reorganise quality. The name got changed a few times, Quality Assurance, Product Assurance and back to Quality. And back to the simple fact that:
"It's the spec, stupid!"
I remember my boss ransacking the reference library for a definition of chrome. It included the phrase "beautiful sheen". Sadly, that never made it to the Quality Manual.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.