Architecture Radar · Regulated tier
Scoring tuned to the regimes your program runs under.
Architecture debt does not cost every program the same. On a certified program, a traceability gap is not untidiness — it is rework at the worst possible point in the schedule. The Regulated tier weights hot-spots against the regime you actually certify to, with extra sensitivity at the requirement and test intersection where verification risk concentrates.
Request a scoping callInterface boundary stress — illustrative
Supported regimes
Each regime, scored on its own terms.
Each regime carries its own hot-spot taxonomy and its own reason for elevated sensitivity. Select one to see what gets scored.
RTCA DO-178C Airborne software certification
What gets scored
- Bidirectional traceability between requirements, design and test cases
- Verification coverage by software level (DAL A–E)
- Structural coverage gaps and unmet MC/DC obligations
Where sensitivity is raised
Elevated weighting on verification gaps at higher design assurance levels, and extra sensitivity to coverage traces that fail to reach the requirement source.
AS9100 Aerospace quality management
What gets scored
- Configuration management drift across baselines
- Design and development record completeness
- Change-control traceability through the verification chain
Where sensitivity is raised
Weighting on record completeness at design review gates, where documentation debt tends to surface only during audit.
MIL-STD-882 System safety
What gets scored
- Hazard traceability from analysis through mitigation to verification
- Safety-critical function coupling across subsystem boundaries
- Residual risk documentation continuity
Where sensitivity is raised
Extra sensitivity where safety-critical functions cross interface boundaries — the coupling most likely to invalidate a prior hazard analysis.
ISO 26262 Automotive functional safety
What gets scored
- ASIL decomposition and freedom-from-interference claims
- Safety requirement traceability to verification evidence
- Interface coupling that undermines independence arguments
Where sensitivity is raised
Weighting on coupling that erodes freedom-from-interference, since independence claims are the argument most often broken by architectural drift.
IEC 62304 Medical device software
What gets scored
- Software safety classification consistency across items
- SOUP identification and integration coupling
- Requirement-to-verification traceability continuity
Where sensitivity is raised
Sensitivity to coupling between classified software items, where a class change in one propagates obligations across others.
What this is
Scored against — not accredited by.
Radar scores against these regimes. It reads the artifacts your teams already produce and flags where architectural coupling is creating traceability, coverage or verification exposure relative to the obligations you carry.
It is a measurement instrument, not a certification authority, and not a substitute for your DER, auditor, or safety assessor.
Stated plainly
ZOYA is not accredited by, approved under, or acting on behalf of any of these regimes. Scoring alignment means the hot-spot weighting reflects the obligations the standard imposes — it does not mean the output constitutes certification evidence. Any claim to the contrary would be worth less than nothing to a program that relies on it.
Handling of controlled material
Agreed before anything moves.
Regulated programs frequently involve technical data with handling restrictions. Scope, transfer method, retention period and destruction date are agreed in writing before any material moves, and applicable handling constraints are confirmed at scoping rather than assumed.
Where restrictions make document transfer impractical, the assessment can be scoped to operate on material that never leaves your environment. Raise it on the scoping call — it is a common constraint and shapes the engagement rather than blocking it.
Start with the assessment.
Three weeks, fixed fee. Radar continues the measurement afterward if it earns its place.
Request a scoping call