Parameterized Systems

In the 3D Framework, we describe the system’s structure and supported behavior in metadata. We do not have to write application code for each definition.

Metadata can describe tables, columns, relationships, validation, forms, navigation, commands, security, auditing, history, and data exchange. The shared application framework reads those definitions and presents the system to the user.

We can change a system’s definitions while keeping the framework that runs them.

Why This Matters

Build common framework functions once and use them across systems.
Concentrate quality and security work on the shared framework.
Update framework technology without rewriting every system’s business definitions.
Make framework improvements available through controlled releases.
Distribute modules through metadata to compatible systems that support their behavior.
Add local requirements while continuing to use shared definitions.
Generate systems from metadata.
Translate labels, menus, forms, and other text through metadata.
Manage development, UAT, and production configurations through versioning.
Track changes to system definitions.
Compile and cache parameters to reduce repeated metadata assembly.