The Business must be able to modify the Model


The Solutions are often well suited to the current needs, but struggle to evolve.

The baker would like to develop his solutions by himself.

Separate in a model what is stable from what is often modified: make the elements that are often modified configurable.

The baker acquires configurable solutions.

  1. Identify what often changes in the Model

    A Model changes over time.
    Certain elements of the Model are rarely modified. For example, the definition of the Business Objects and their relations: if we defined that a Contract is only linked to one Customer, it is unlikely that it will change.
    But other elements change more frequently: pricing, conditions of eligibility, allocation of tasks between Actors, adding data to the Objects... that is to say the rules (or Functions), the sequencing of Processes and Information.
    Identifying what is often modified helps to select a Solution that can easily support these modifications.

  2. Acquire a configurable Solution

    One of the main qualities of a Solution is to let us modify the elements that change often by "Configuration".
    The idea is a simple one: we isolate the elements that change frequently and provide tools that can be used by non-IT workers to modify these elements. It is a modification of the Model, but it is perfectly limited and does not require complex Functions of programming, integration, non-regression testing...
    Among the techniques used: parameterization, rules engine, workflow engine, dynamic data (see the white paper on Software packages).

    Not only is it a technique that enables the Enterprise to evolve rapidly, but it is also a means of differentiating oneself from the competition.

  3. Personalize the single Model to adapt it to different Organizational units

    As we have just seen, configuration techniques allow us to modify the elements that often change quickly.
    There is also another use for configuration: personalize the single Model for different Organizational units.
    When a Group is looking to rationalize its Solutions, it still has to respect the specificities of each of its Organizational units (or subsidiaries): language, currency, regulation, tax system, commissioning,...
    Configuration techniques allow us to maintain different implementations of the same Model: the common Model can evolve through successive versions because the personalization of each Organizational unit has been isolated.

  4. And tomorrow, Customers will configure their Products

    Customers like to buy Products that are specific to them. Some enterprises have devised Offers that can be personalized.
    As an example, the shoe "One Many" from Newfeel, distributed by Decathlon, gives you an infinite number of combinations of patterns, material and colors: a Customer creates a single Model him- or herself!
    This is also a case of configuration: the Product architecture is the same, but what "often changes" in customer tastes has been isolated so that the Product Model can be configured.
    The icing on the cake: the Model configured by a Customer can be proposed to other customers: one way of staying close to the market, as it is the Customers themselves who guide the Enterprise in Modeling the Products that are aimed at them.

Licence Creative Commons
The story of George the Baker is made available under the terms of the
Creative Commons Attribution - NoDerivatives 4.0 International license.
Table of Contents

Comments

comments powered by Disqus