archetype-scanner

To match domain requirements to architectural archetypes, scan your domain specifications against a registry of known patterns in parallel. This generates individual fit reports for matching archetypes and a merged summary documenting mapped concepts, overlaps, and uncovered domain gaps.

Archetype scanning in domain-driven design workflows is the parallel process of checking domain requirements against multiple architectural archetypes simultaneously. It eliminates manual checking to ensure no relevant domain patterns are overlooked during early modeling, requirements review, or training workshops.

Yes, you can use parallel pattern matching for a SaaS domain modeling requirements review. It simultaneously evaluates your requirements against all registered archetype mappers to quickly identify if accounting, pricing, or party archetypes apply without running each mapper manually.

To identify unmapped domain concepts and overlapping mappings, scan your domain requirements against known architectural archetypes. The generated consolidated fit report highlights uncovered domain gaps and overlapping mappings across archetypes to guide your next modeling steps.

A limitation of automated archetype scanning is that it only matches requirements against registered architectural archetypes. Domain concepts falling outside the known registry will be flagged as uncovered gaps, requiring manual domain modeling to define new architectural patterns.