Metadata-Driven Systems
Metadata-Driven Systems have structures and behaviour substantially defined through metadata. The 3D Federated Software Architecture uses definitions that go beyond database tables and columns.
Metadata can define relationships, validation, temporal behaviour, auditing, forms, commands, navigation, security, and data exchange behaviour.
The same metadata drives multiple system layers. Generated artifacts include database structures, constraints, interfaces, forms, navigation, audit mechanisms, and other application components.
Metadata at the Core
Generation in the 3D Platform
Requirements → Concepts → Shared Structures → Local Structures → Validated Metadata → Generation
-
Begin with business-unit requirements and identify business concepts.
-
Reuse applicable shared structures and add business-unit-specific structures.
-
Use AI where interpretation of requirements is required.
-
Use deterministic processing where results can be derived mechanically.
-
Validate the resulting metadata before generation.
Why it matters
A common set of definitions can drive coordinated structures and behaviour across the system. System generation has already been implemented and exercised in the 3D Platform, the implemented software/reference platform demonstrating the architecture.
Boundary
The implemented requirements-to-generation pipeline is distinct from reverse engineering existing systems or metadata. Other proposed automation capabilities remain planned work unless implemented and demonstrated. Generated environments provide implementation evidence, not proof of production readiness at organizational scale.