Skip to main content

Glossary

A collection of technical terms and their definitions based on Normalized Systems (NS) concepts.

A

Anchor (Anchor)
A marker within generated source code reserved for adding custom logic during re-expansion.
Related terms: Harvesting, Rejuvenation
Angular UI (AngularUI)
A front-end application architecture generated using Angular and MVVM patterns to integrate with the JEE stack.
Related terms: Angular App, Feature Module, Data Connector
Application (Application)
The overarching model container grouping all components, domain logic, and configurations for an enterprise solution.
Related terms: Component, Application Instance, Software Program
Application Instance (ApplicationInstance)
A target technology configuration defining how an application's architecture layers are built and executed.
Related terms: Application, System Architecture
Architectural Style
A specific high-level architecture describing the construction view (e.g., 'MIS – multi-tier information system').
Related terms: High-Level Architecture, Program Type, System Architecture
Artifact (Artifact)
A build or deployment result, such as a Docker container image or Java archive, produced by a software project.
Related terms: Software Project, Service, Docker Image

C

Client Library
A runtime library providing in-memory access to remote systems while encapsulating remoting technology.
Construction View
A core architectural perspective focusing on the how (physical structure and implementation).
Related terms: System, Functional View, Architectural Style

D

Data Command (DataCommand)
[Deprecated] A legacy mechanism used for data input and custom action execution on DataElements, replaced by DataOperations.
Related terms: Data Operation
Data Connector (DataConnector)
An Angular metamodel element linking front-end services to a back-end DataElement REST API for data retrieval and modification.
Related terms: Data Element, Data View, Feature Module
Data Element (DataElement)
A fundamental data concept or entity within an application's domain, acting as an anthropomorphic translation of a real-life object or concept.
Data Operation (DataOperation)
A type-safe action (e.g., Create, Update, Custom) executed on DataElement instances to modify data or trigger business logic.
Related terms: Data Command
Data Ref (DataRef)
An object encapsulating a reference (such as a database ID, name, or functional key) to a specific DataElement instance.
Related terms: Data Element, Projection
Data View (DataView)
An Angular metamodel element generating out-of-the-box CRUD interface screens (list, add, edit, detail) for a DataConnector.
Related terms: Data Connector, Feature Module, Data Element

E

Element Structure
The detailed construction design for implementing a functional element within a program type or layer.
Related terms: Program Type, Layer, Functional Element, Expander Beam
Engine Node (EngineNode)
A data element keeping track of the state, health, and assigned engine services of an individual deployment node or JVM instance.
Related terms: Workflow Component, Task Element
Enum Type (EnumType)
A specialized ValueType representing an enumerated list of fixed constant values defined within the model.
Related terms: Value Type, Field
Expander
A unit of generation that combines a data tree instance (functional M1 model) with a template to generate an artifact.
Related terms: Functional Model, M1 Model, Expander Bundle, Expander Beam
Expander Beam
A packaged set of expanders that generates element structures for a specific program layer type or an entire program type.
Related terms: Expander, Element Structure, Program Layer Type, Program Type, Expander Beam Aggregate
Expander Beam Aggregate
A collection of expander beams that aggregates complementary variants for different layers within a program type architecture.
Related terms: Expander Beam, Layer, Program Type
Expander Bundle
A set of expanders sharing a repository, packaged into an expansion resource or archive.
Related terms: Expander
Expansion Resource (ExpansionResource)
A reusable resource bundle containing expanders and features that provide specific application capabilities, defined in the expansion settings and added to the classpath during expansion.
Related terms: Expansion Settings, Expander, Capability
Expansion Settings (ExpansionSettings)
The core XML configuration file specifying model locations, target expansion output directories, and expansion resources.
Related terms: Expander, Expansion Resource
Expansion Technology Settings
Technology settings (utility frameworks) added to the functional model's data tree to drive expansion.
Related terms: Functional Model

F

Field (Field)
A property of a DataElement expanded to a database column and user interface input element.
Related terms: Data Element, Value Field, Link Field
Finder (Finder)
A search specification combining field-operator pairs to execute standard data queries on a DataElement.
Related terms: Data Element, Query Search
Flow Element (FlowElement)
[Deprecated ] A deprecated process modeling construct describing state transitions targeting a status field on a DataElement.
Related terms: Workflow
Functional Element
A node ('ElementClass') in the M2 ontology specifying the functional view (e.g., 'component').
Related terms: M2 Model, Functional View, Element Structure
Functional Model
An M1 model or instantiation of an ontology from the root element (e.g., 'E-Crystal').
Related terms: M1 Model, Functional Module, Expander, Expansion Technology Settings
Functional Module
An M1 model or instantiation from a specific node high enough in the hierarchy to be reusable (e.g., 'invoicing' component).
Related terms: M1 Model, Functional Model
Functional Type
The M2 ontology used to specify the functional view (e.g., 'Application').
Related terms: M2 Model, Functional View
Functional View
A core architectural perspective focusing on the what (operational behavior and functionality).
Related terms: System, Construction View, Functional Type, Functional Element

H

Harvesting (Harvesting)
The process of extracting and persisting custom code from anchors and ext directories back into source directories.
Related terms: Anchor, Rejuvenation, Expander
High-Level Architecture
The high-level specification of construction, including subsystems and their interconnections.
Related terms: High-Level Subsystem, Architectural Style
High-Level Subsystem
A subsystem identified in the high-level architecture with detailed interface and interaction specifications.
Related terms: High-Level Architecture, Program Layer Type

L

Layer
Logical separation of functionality within a single system/application, focused on code organization.
Related terms: Tier, Program Layer Type

M

M0 Model
Actual data that instantiates an M1 model in an information system.
Related terms: M1 Model
M1 Model
An actual model that instantiates an M2 meta-model or ontology.
Related terms: M2 Model, M0 Model, Functional Model, Functional Module, Expander, Software Program
M2 Model
A meta-model, ontology, or Domain Specific Language (DSL) specified in M3.
Related terms: M3 Model, M1 Model, Functional Type, Functional Element, System Architecture
M3 Model
A meta-meta-model used to define other meta-models or ontologies; it must be meta-circular (defined within itself).
Related terms: M2 Model
Micro Radiant (MicroRadiant)
The graphical modeling IDE and tooling environment used to design, edit, and maintain NS applications and project models.

N

NS Application (NSApplication)
A pre-built software stack that provides common enterprise application functionality such as CRUD, search, authentication, and business process modeling out of the box.

P

Program Layer Type
A high-level subsystem/layer with predefined technologies on top of a program type (e.g., 'JAX-RS Control Layer').
Related terms: Program Type, Layer, High-Level Subsystem, Expander Beam
Program Type
An architectural style with predefined technologies/standards (e.g., 'JEE Application').
Related terms: Architectural Style, Program Layer Type, Element Structure, System Architecture, Software Program
Projection (Projection)
A tailored subset of fields on a DataElement designed to encapsulate data for a specific technical or functional view.
Related terms: Data Element, DataRef

Q

R

Rejuvenation (Rejuvenation)
The core process of harvesting custom code from designated anchors and ext directories, updating model configurations, and re-expanding code artifacts to continuously evolve software without losing custom implementations.
Related terms: Harvesting, Anchor

S

Software Program
An instantiation of a system architecture (functional M1 model + program type instance).
Related terms: System Architecture, Functional Model, M1 Model, Program Type, Software Program Expansion, Software Project Composition
Software Program Expansion
A software program that has been expanded and is ready for build and deployment.
Related terms: Software Program
Software Project Composition
A collection of software programs that can be expanded, built, and deployed as an integrated system.
Related terms: Software Program
Standard API (stdAPI)
A fully generated JAX-RS REST API expanding JSON:API compliant endpoints directly from JEE element models.
Standard Types (StandardTypes)
A set of pre-built ValueTypes (e.g., EmailAddress, Iban, TelephoneNumber) providing validated data types out of the box.
Related terms: Value Type, Simple Value Type
System
A set of interconnected components that work together to achieve a specific purpose or function.
Related terms: Functional View, Construction View
System Architecture
The combined specification of an ontology (M2) and an architectural style/program type.
Related terms: M2 Model, Architectural Style, Program Type, Software Program

T

Tier
Physical or logical separation of components (e.g., across different servers), focused on deployment structure.
Related terms: Layer

V

Value Field Type (ValueFieldType)
[Deprecated] A deprecated specification defining how to store and represent the values of a ValueField, superseded by ValueTypes.
Related terms: Value Type, Field, Simple Value Type
Value Type (ValueType)
A specifier defining how data in a Field is rendered in the UI, stored in the database, and validated in business logic.
Related terms: Field, Simple Value Type

W

Workflow Component (WorkflowComponent)
A component for configuring automated process execution.
Related terms: Workflow, Task Element

Total terms: 58