Quality should be considered from different perspectives:

• Customer perspective.
• Developer perspective.
• Support Analyst perspective.
• Sales and Marketing perspective.

You need to find a balance between these different views of quality before releasing a product.

How much time and money you spend on quality and testing depends essentially on economics. When failure is unthinkable, you spend a lot more. For example:

• Formal verification. That is, mathematically prove that software meets its specification. This is very expensive to do, but is performed today in a number of areas, verifying secure microkernels, for instance.
• How they ensure quality of the space shuttle software. An interesting example of how a CMM level 5 organisation operates.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.