Practitioner research organized around four recurring problems in regulated, multi-vendor enterprise software delivery. Each theme is underpinned by an original framework — see the Frameworks page for full technical detail.
Examines how regulatory intent is translated — and frequently distorted — as it passes through multiple vendors, systems, and interpretation layers in enterprise software delivery.
In multi-vendor regulated environments, no single party owns the full chain from regulatory text to executable acceptance criteria. Each vendor interprets requirements independently, producing systems that individually pass testing but collectively diverge from regulatory intent.
Definition and characterization of the Regulatory Interpretation Gap (RIG) as a diagnostic construct; development of the Acceptance Translation Layer (ATL) as an operational mechanism to reduce interpretation drift across vendor boundaries.
IEEE Access manuscript — under review
PNSQC 2026 paper — selected through peer review
Zenodo preprint — publicly available (view)
Extension of the RIG/ATL model toward AI-assisted regulatory interpretation alignment.
Investigates why a fully passed UAT cycle does not guarantee a stable production release, and proposes governance structures to close that gap.
Release sign-off is typically based on test-pass rates rather than a structured assessment of readiness. Releases that "passed" still fail in production because passing tests do not verify the same thing as being ready to release.
A practitioner framework identifying recurring failure patterns between UAT completion and release stability, and a governance checklist for release-readiness assessment distinct from test completion.
"Why a UAT Pass Does Not Mean Release Readiness" — practitioner article submitted to Ministry of Testing
Formalizing the release-readiness governance checklist into a scored, reproducible assessment model.
Develops a measurable standard for testability — how much of a system's behavior can actually be verified — as distinct from test coverage or pass/fail metrics.
Existing coverage metrics measure what was tested, not what can be reliably tested. Systems can show high test-pass rates while significant portions of their behavior remain effectively unverifiable.
Introduction of Testability Coverage Rate (TCR), a metric and methodology for quantifying testability at the system level, presented as The Untestable Gap: Testability Coverage Rate as a Missing Release Readiness Metric in Multi-Vendor Regulated Systems.
"The Untestable Gap: Testability Coverage Rate as a Missing Release Readiness Metric in Multi-Vendor Regulated Systems" — accepted for presentation, QRS 2026 Industry Track
Validation of TCR against production incident data across multiple enterprise systems.
Addresses governance structure for User Acceptance Testing in multi-vendor, regulated enterprise programs — where UAT ownership, criteria, and sign-off authority are frequently fragmented.
Multi-vendor UAT programs commonly lack a single governing authority over acceptance criteria, producing inconsistent sign-off standards between vendors.
Governance model for UAT ownership and acceptance-criteria alignment across vendor boundaries, drawn from 13+ years of practitioner experience in healthcare, insurance, and government implementations.
Shares source material with Themes 01 and 02 above.
Development of a standalone UAT governance maturity model for regulated enterprise programs.