Aiming for the Right Target
Most software is designed for the development lab or the testers in the Quality Assurance (QA) department. It is designed and built to pass tests such as, “The customer’s first and last names are required, but the middle initial is optional.” It aims to survive the artificial realm of QA, not the real world of production.
When my system passes QA, can I say with confidence that it is ready for production? Simply passing QA tells me little about the system’s suitability for the next three to ten years of life. It could be the Toyota Camry of software, racking up thousands of hours of continuous uptime. It could be the Chevy Vega (a car whose front end broke off on the company’s own test track) or a Ford Pinto, prone ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access