Statistics

Last updated 1 day ago

Depth is not a promise here, it is something you can watch. Statistics shows what feeds your Domain Contexts, how much of your code is mapped, and what your connected tools report. Every document you add and every tool you connect moves those numbers, so you always know what to add next.

Where

On a project, from the project bar: the picture across all its Domain Contexts.

On a Domain Context, from its toolbar: the detail, readable against MAIN, the working state, or against any of your versions.

Every figure can be shown as a raw count or a percentage, with the # and % toggle.

How to read the panel

The panel follows the path your data takes, from raw material to mapped code, in three stages.

Polarization data to semantic. What comes in, and how much of it is usable. Contents counts the documents feeding the Domain Context. Integrations counts connectors, split between endogenous and exogenous. Semantic data mapping tells you what share of it all actually lands on the model.

Semantic definition from ontologies. What the model holds. Domain Contexts and Context Objects count the structure built from your ontologies.

Mapping. How far the model reaches into your code. Parcels counts your Code Parcels, with the lines of code they cover and their overlap rate. Line of code mapped and Files mapped show how much of the codebase is connected.

Legend

Some labels on the panel are Mobioos terms. Here is what they mean.

Label on the panel

What it means

Polarization

Retrieving data from your tools, filtering out the noise, and projecting what matters onto the semantic structure of your ontologies.

Semantic data mapping quality

Of all the data collected, the percentage that is mapped onto the model. A low figure means a lot of what you supplied is not being used yet.

Endogenous connectors

Sources whose information describes the implementation, such as a diagnostic tied to a code location.

Exogenous connectors

Sources whose information describes usage and intent, such as a customer ticket or a functional rule.

Semantic definition from ontologies

The structure of your Domain Contexts, derived from the ontologies they instantiate.

Context Objects

The elements of a Domain Context, each one a meeting point between a business concept and its code.

Parcels

Your Code Parcels: the code associated with each context object, from a single word to entire folders, across repositories and branches.

LOC Mapped

Lines of code covered by at least one Code Parcel.

Code overlap rate

The share of your code that several context objects point at. Some overlap is normal, since a shared component serves several features. A high rate shows where the boundaries of your model and of your code do not line up.

Statistics or the graph overlay?

Two readings of the same material.

Statistics answers how much: coverage, volumes and ratios, for a project or a Domain Context.

The overlay on the graph, driven from the Service Connections panel, answers where: which parts of your product carry the problems. See Domain Context.

What fills in when

Figures derived from your code appear as soon as a scan completes. Figures derived from a connector fill in as soon as that connector is attached, so each tool you add lights up its own part of the picture.

Every term is also defined in the Glossary.