Philosophy of Software Quality Engineering

Is your organization relying on the passive illusion of "assurance" when it desperately requires the rigorous discipline of "engineering"?
In Philosophy of Software Quality Engineering, IT/IS architect and veteran engineer Martin J. Lammer delivers a groundbreaking philosophical treatise that dismantles traditional Software Quality Assurance (SQA) paradigms. Rebuilt from the ground up, this text establishes a new foundation based on rigorous engineering, ontology, and pragmatism.
The software industry is currently in an epistemological crisis. We build increasingly complex systems upon brittle methodologies, abstracting away the human cost of failure until catastrophe strikes. This is not another entry-level manual on testing automation or agile platitudes. Philosophy of Software Quality Engineering is a deep, socio-linguistic, and phenomenological analysis of technical success and failure. It is engineered specifically for software architects, engineering leaders, and "accidental" quality engineers who demand a more robust, intellectually rigorous framework.
Bridging the gap between high-level philosophical inquiry and the gritty reality of code deployment, Lammer exposes the empirical failure of mere assurance. Through meticulous analysis and real-world case studies, the text explores the catastrophic human and financial costs of engineering negligence, alongside the organizational dynamics of high-functioning teams.
Inside this comprehensive treatise, you will explore:

• The SQA vs. SQE Paradigm Shift: A rigorous breakdown of why the industry must abandon Software Quality Assurance in favor of the systematic engineering of quality.
• The Human Cost: A sobering, critical look at the real-world consequences of software failure, grounded in historical data.
• Ontological & Pragmatic Imperatives: Frameworks to align your software quality metrics with the fundamental, operational nature of your engineering reality.
• The Axiom Lifecycle: Actionable strategies for the "engineering of necessity" to overcome the current epistemological crisis of software development.
• Empirical Case Studies: Granular, uncompromising examinations of industry touchstones-from the catastrophic failures of the Therac-25 accidents and the Mars Climate Orbiter, to the methodological environments of the Linux Kernel, Cleanroom Software Engineering, Google's Project Aristotle, and the Uber (Kalanick) era.