Fundamental principles
There are some basic / fundamental principles that was considered in all PMO producs design and architecture. These priciples give the major feaures, security, flexibility and scalability of components. So:
- (FP-1) independence of operating systems for all what mean "client module" (being it a desktop application or browser, for example). More than that, as a usaility rule, the system must have, provide and ptresent the same look and feel (from functional point of view).
- (FP-2) moduarity which means that parts which are not absolutely required from components ca be segregated to be used from other systems or third party, those provided in PMO or other REN products. All of these can be installed / uninstalled as needed at any time at cliet disposal.
- (FP-3) standardization; each "part of the system" respects as much as possible the common public standards. Where there are only proprietary standards, rhe user is notifyied and system will apply then only with the customer's consent. Highly usage of standards give a maximum of of compatibility and flexibility in interconnecting the system especially regarding internet practices and data exchange, but not limited to.
The BIG picture
In the following picture there can be seen almost all architectural design artifacts of the PMS editions and components. It is visible that
most components are reused (not exactly but the core is the same).vThere are some aspects that must be clarifyied because they changed
along development.
NLE was renamed to NOE. The IKS component is part of DEV (which is normal, having no usage without DEV edition), IKS being an acronym
for Integration Kits Suite and being a set of "in-house software tools" for "pre-defined / already built" integration modules (for example an integration
already built add-on with a well known commercial ERP system has its own integration features and rules, so you'll take it AS-IS).
Already built IKS are for mostly used Document Management Systems (DMS), Project-based Manufacturing Systems and Accounting and Cost Control Systems.
What is not shown in picture is the data storage used by DLE / SLE component which is not visible because is not necesarly a database,
but in 99% of cases is just a locat "human readable" file (JSON format). This component (i.e., DLE) use "Import / Export / Sync" techniques
and functionalities to integrate with a NOE or EE edition.
Screenshots
