Design, develop, and test software systems using the MIM (Module - Infrastructure - Module) architecture and foundational modular design principles.
100
Quality
100%
Does it follow best practices?
Impact
100%
1.25xAverage score across 5 eval scenarios
{
"context": "Evaluates the implementation of the 'Infrastructure-Module' (IM) and its relationship with the 'Business-Module' (BM) according to the Dependency Inversion Principle and 'Wiring' instructions of MIM.",
"type": "weighted_checklist",
"checklist": [
{
"name": "IM/BM Folder Separation",
"description": "The Infrastructure and Business code is explicitly split into folders or namespaces named 'IM' and 'BM'.",
"max_score": 30
},
{
"name": "IM depends on BM",
"description": "The Infrastructure code (IM) depends on the Business code (BM). Specifically, the IM's repository implementation imports the BM's interface.",
"max_score": 30
},
{
"name": "DI Wiring outside BM",
"description": "Dependency Injection wiring (e.g., factory, DI container, manual wiring) happens in the IM or a module-level entry point, not inside the BM's service.",
"max_score": 20
},
{
"name": "Strict BM Technical Isolation",
"description": "The 'BM' section contains NO technical dependencies like database libraries or framework-specific controllers.",
"max_score": 20
}
]
}