Compliance checks
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
show compliance with principles and standards in a way a board can verify.
Planned topics
- Map each architecture principle and standard to the design element that satisfies it, with a link to evidence.
- Mark each line: compliant, compliant with condition, or non-compliant (exception needed).
- Be honest: a self-assessment that is all green with no evidence loses credibility.
- Evidence can be an ADR, a diagram, a test result, or a policy reference.
Draft outline details
Demonstration
a compliance table with columns principle or standard, status, design element, evidence link, for Larkspur lines such as "prefer SaaS for non-differentiating capability" and "no direct database access between systems".
Check your understanding
What makes a compliance table credible?
Show answer
Evidence links for each line and honest statuses, not all green.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.