Advantages for developers
A dia$par model engineer operates a reality representation model.
Objects of the real world, their attributes and interactions are described in the model.
Over 85% of routine works carried out by developers of traditional systems can be automated by outsourcing them to high-level smart tools of mmizer.
A business logic of dia$par.Matrix, a cybernetic model of the managed organization is written in the C# 6.0 language using its most advanced possibilities — LINQ and Asynchronous features.
By independently varying meta data, the distributed version control subsystem can support several functional dia$par.Matrix models of the same enterprise and run them online simultaneously.
For each model, a separate team of developers can be assigned, while built-in validation tools of mmizer ensure avoidance of conflicts.
Besides, the Structured Diff Viewer for model objects, integration with change request management systems, reviewing the history of model changes directly from the developer workstation and conflict resolution for model objects are available for developers.
Built-in tools for continuous integration along with the version control subsystem encourage engineers to apply Agile techniques.
The Continuous Integration is the native method for developing dia$par.
Oracle Database EE (or a very similar Enterprise DB) is literally implanted in the mmizer core.
dia$par makes the maximum use of its special features and tools for access, access control, analysis and other operations with data ultimately ensuring the highest conciseness, clarity and efficiency of applications.
The graphic editor for modeling system objects (sort of a wizard) ensures rapid prototyping of interfaces for dia$par manned applications.
For example, after an object is created, the dia$par development tools will automatically generate required visual interfaces for bidirectional replication of changes.
There are embedded integration tools which use the REST protocol with serialization to XML or JSON.
Serialization/deserialization and routing details completely concealed under the hood.
In contrast to the traditional approach, the multi-language string support is implemented at the core level.
Names for cybernetic model attributes, string data and user's messages can be written by developers in any languages, while their values are stored structured along with the code and attributes and can be controlled via the graphic interface.
The mmizer tools ensure correct output of the required model version depending on individual language settings of each user.
There is a built-in editor to design forms of any complexity that supports all popular functions like exporting to PDF, Excel, HTML, cross-sectional bands, tables, watermarks, barcodes (including 2D barcodes).
There is an embedded centralized subsystem for sending tasks to printing devices that ensures delivery and collects printer usage statistics.
Automated business processes testing framework for a managed enterprise, first ever implemented in dia$par.
Business logic of the digital twin, implemented by a application developers in dia$par.Matrix, is tested by the mmizer engine, starting from enter point services and web services ending with storage of data into the dia$par infocontainer.
Entire vertical interaction between application components and business logic is checked.
dia$par Integration Tests Framework is the ideal platform for test-driven development.
Yet for the classical development approach, covering critical business processes with integration tests dramatically reduce number of errors in a production environment, and make a significant contribution to the unprecedented performance of applied development in dia$par.
This is a dia$par.Mirror processor unit preventing wrong transactions which is run in fully automated mode.
This component ensures dia$par mmizer reliability and efficiency required for bidirectional replication of changes in real time.
This is an mmizer unit for centralized control over the saving, viewing and change data analyzing functions and determining the status of the meta-system.
In contrast to the traditional approach of recording individual logs for each application server, all dia$par meta-system messages are stored in the centralized data storage of the meta-system.
There are a structured analysis, view and diagnostic functions which can be performed from the developer workstation.
Outdated data is archived automatically by Big Brother Center tools.