Parameterized Systems
In the 3D Framework, parameterization means defining system structure and behaviour as metadata rather than embedding it directly in application code.
Metadata can define tables, columns, relationships, validation, forms, navigation, commands, security, auditing, temporal behaviour, and data exchange. The shared application framework interprets this metadata and presents the resulting system to the user.
This separates what a system does from how the application framework is implemented.
Why This Matters
-
Reduces duplication — common application framework functionality is developed once rather than rebuilt for every system.
-
Improves quality and security — development effort can be concentrated on one shared framework.
-
Simplifies technology changes — the framework can evolve without rewriting every system.
-
Distributes improvements broadly — new framework capabilities can immediately become available to many systems.
-
Makes functionality portable — modules can be distributed between systems using metadata.
-
Supports local extension — shared modules can be adapted without losing the benefits of the common core.
-
Enables system generation — systems can be generated from metadata definitions.
-
Supports multilingual interfaces — labels, menus, forms, and other literals can be translated through metadata.
-
Supports controlled deployment — versioning can manage development, UAT, and production configurations.
-
Improves auditability — changes to system parameterization can be tracked.
-
Optimal Performance - Parameters are compiled and cached for optimal performance.