USPs
Continuous improvement is the quality that distinguishes Pluriform the most from other complex informationsystems: not only build a system fast and in an evolutionairy manner, but also able to continously (for decades) improve the system quickly (daily). Therefore the following points are essential:
- Insight in use. The Where-used relations of each modelobject show the modeler directly where and how it is (re)used; the Execution logs count how often model objects are called in (which) productionsystems.
- Development speed. Pluriform is a RAD-tool with which modelers can build applications in a very short period of time. Yhe most important tool for the Pluriform modeler is the strongly typed, grafical Scripting editor to very accurately and quickly define and refine business logic. All changes are recorded in Change logs so all involved colleagues can see what is changed, when and by whom. The integration of Data and metadata in the develop system and a tight, fast link to the test / production system keep the cycles short, in which modelers together with users build /change and test the system.
- Automatic carrying through of changes: Changes in a business model can be carried through almost always automaticly in the develop and production systems derived from it. The Conversion Framework guides the modeler in writing conversions and executes these automaticly in the derived systems, Schema evolution takes care of automatic adapting the database schema and the Object lifecycle indicates and whther and when a model object may be deleted.
- Signaling problems. Before a change leads to errors Pluriform signals the problem. The Model checker checks all upgrades on possible conflicts with the model present locally. Moreover the modeler can and must add Testing for each aspect of a model to verify and guard automaticly adn systematicly the compliance between models or between model and data.