Business Modeling

Business Component

It can be associated a micro and dedicated information system called business component to each activity done by an actor of the firm. We find in it the essential functions that are following:

The component beholds the modeling of the atomic activity for what can be automated. This abstraction is described at the IT level by the business interface, which is independent of:

Business Interface

The business interface describes in an exhaustive way the part of the activity to automate:

Business Modeling

While the function conception stage of an application, the business interfaces of atomic activities that are entering into the perimeter are defined. From time to time, while running the processes, it is possible to build the business modeling of the enterprise of the public service, through the clustering and the completude of different business interfaces.

The interconnections of applications, what are translated in the day-to-day work into information system as data flows and service calls, are characterized by shared business interfaces.

Here is an example:

A shared business interface may be too rich for an application. In this case, in order to simplify the local modeling, it is possible to use a business view by only keeping information, the relations and the actions that are just necessary.

Building an information system around a business modeling designed with business interfaces is offering two major benefits for the firm:

Business Expertise Rules

The business modeling conceptualizes information kept and exchanged inside the firm and also the actions that are impacting their life cycle - creating, modifying, reading, transferring and deleting.

The business modeling is however not concerned by the state of art and the know how of the firm, coming from year experience feed by numerous competencies, that have contributed to its positioning and its culture.

The purpose of the business expertise rules is to fill this lack by making explicit this expertise, which is mostly proper to the firm. They act as triggers on the business modeling.

Here is an example that could apply to a business interface describing a client in the telecom business line:

If the invoice of the client is lower that one Euro then do not claim for payment.
The reason is not to have bank fees upper than the turnover.

If the consumption of the client is 25% upper than his average consumption, then ask for an advance on consumption.
The reason is to manage the non-payment risk.

If the client risk is strong, then settle his account from the Société Générale's one.
The reason is that non-payment fees are lower in Société Générale in regard with other banks.

If the client is using the "Souplessismo" offer, then register him into the statistics.
The reason is that the offer "Souplessimo" is in the launching stage. We must keep an eye on the conquest curve.