Intel, via UST · 2017 - 2018
Processor Validation Frameworks
ATMS and UDL: Python and AWS frameworks that use compiler-style models to generate every feature combination a processor must pass before release, so coverage is designed, not guessed.
The problem
Before a processor ships, every feature has to be validated in every meaningful combination. Writing those cases by hand does not scale, and a missed combination is expensive.
Key decisions
- Model each feature as a grammar, so combinations are generated rather than hand-written.
- Explore the full combination space first, then prune with explicit rules.
- Keep the frameworks reusable across processor programs and feature areas, such as Bluetooth.
- Run suites on AWS so coverage scales with compute, not headcount.
Outcome
Validation teams could generate complete, repeatable coverage for each feature area before release. I led a team of seven on the program, and the work earned a Certificate of Appreciation from the Intel engagement.
Architecture flow
- Feature specifications
- Compiler-style models: grammar and rules
- Combination generator
- Generated test suites
- Execution on AWS
- Results and coverage reporting
More architecture work
Book a conversationEnterprise Data Foundation
A reusable data foundation for risk, products, analytics and AI, not one-off pipelines. Ingestion, medallion warehouse layers, domain marts and operational distribution from a single architectural spine.
Read case studyGlobal Risk Data Platform
Large-scale company risk-data architecture that ingests, enriches, normalizes and distributes company-level intelligence across countries. Built as a reusable risk pool for underwriting, products, analytics and intelligent systems, and today the data foundation beneath Cowbell's OMNI AI agents.
Read case studyGlueFlux
Metadata-driven processing framework. Pipelines defined in YAML so teams onboard Spark, Python and dbt workloads without rebuilding orchestration, deployment and operational patterns every time.
Read case study