Sharing Principle

Principle according to which the business objects that concern several actors, activities or processes in the system are pooled in “repositories” accessible to all

Introduction to the notion


At the semantic level, the system is structured in “object domains” so that everything that can be shared is: information, objects, rules, associated documentation, requirements, etc. The sharing principle allows:

  • major concepts (in the existing system, a single concept can be processed by several applications) to be unified and system redundancy to be reduced;
  • the exploiting of information to be increased.

This principle is reinforced by the precept that a single term appears only once in the whole model. The sharing principle is applied, without derogation, on the semantic plane. It does not prejudge in any way, the denormalization decisions that will be taken in the logical architecture or at a later stage.

Practical Consequences

  1. Each local model (produced by a project) flows into the enterprise repository. Here, the structure and articulations will be checked with the rest, as specified by the urbanization target.
  2. In return, projects draw on the modeling repository for part of their models and all the interface notions. They evolve these models to meet their specific requirements.
  3. In this way, the repository is progressively consolidated to reflect the business reality, with all its details, even if the applications cannot yet be structured according to the same sharing principle: what is feasible on paper, in upstream models, takes longer to filter into the reality of the IT system.

Related - items

Bookmark the permalink.

Comments are closed.