maister:problem-classifier

Classifying business requirements into domain-driven design modeling problem classes is done by scanning natural language descriptions to categorize them as CRUD, Transformation, Integration, or Resource Contention. The classification process applies targeted clarifying questions to resolve ambiguity and outputs structured reasoning with implementation guidance.

Concurrency analysis for software architecture is needed when business requirements involve Resource Contention, where multiple actors compete for limited resources. The classification process detects this problem class from requirement descriptions and flags the need for aggregate-based concurrency controls to prevent underengineering.

CRUD problem classes involve simple database operations without complex state conflicts, while Resource Contention requires aggregate-based concurrency control to manage competing access. The classification process distinguishes them by asking high-discrimination questions to ensure you apply the correct implementation strategy and avoid overengineering or underengineering.

Natural language feature descriptions can be used to determine integration design patterns through signal scanning, which detects the Integration problem class when cross-module orchestration is required. The classification process outputs class-aligned implementation approaches with rationale and flags common anti-patterns for integration failure handling.

Avoiding overengineering software architecture with unnecessary service layers is achieved by accurately classifying requirements into modeling problem classes. By distinguishing simple CRUD operations from complex Integration or Resource Contention scenarios, the classification process ensures you only add service layers or aggregates when truly needed.

The problem classifier supports UI mockup text as input for modeling classification, scanning it for signals to identify initial problem class candidates. It processes this text alongside natural language requirement descriptions to determine whether the feature needs CRUD, Transformation, Integration, or Resource Contention building blocks.