e-delos can be viewed as a permanent thinking process on application partitioning: the primary element is data.

Data

The whole e-delos philosophy relies on data, split into three categories:

As a result, each of these categories has its own set of data models and binary components.

Binary components directly leverage data models

Compiled building blocks make direct use of data models.

Component groups encapsulate each data category.

These are either system services, universal business modules, or application for the end-user, directly useable for integration within complete applications.

The goal is to be able to build new applications mostly by putting existing building blocks together. The e-delos suite provides numerous such modules.

KPM are the set of basic, application-independent functions. They were designed aiming at integration and use within any application.

KPM are system services:

They provide basic features (that are more or less system-level).

They are transverse components (complete binary building blocks, encapsulating services such as content indexing engine, email management, SQL servers).

They rely on a uniform data model, handle fundamental data (just a few tables, generally < 3 per KPM), that are unique and required to provide basic system features (hierarchy, security, localization, referencing...).

They allow developers to abstract system services required for their applications when building those.

UBM are the transverse business modules by which heterogeneous applications within the Information System exchange their data.

UBM are what transforms Information System from a repository of independent digital data into an Electronic Knowledge System.

They provide a comprehensive split of business information into simple elements.

Being business building blocks, they are designed to cover as much as possible of inter-application basic needs.

They rely on a uniform, simple data model, with no more than 5 tables. You can think of the business' fundamental data, without worrying about the architecture, database join tables, lookup tables, etc. (this is what KPM are for!)

UBM provide business-oriented Web-based interfaces that can be used directly by end-users.

They are the result of integrating UBM and KPM to address vertical feature needs for a business, corporate department... For instance, running the front desk or a legalities thesaurus.

Several examples are available at e-delos, and can be used as starting points to write your own specific applications.

The difference between applications and UBM is that an application sees its reach restricted to a specific performative kind (e.g. Sales, HelpDesk).