A passed acceptance test is a snapshot of a sample: it holds for the section that was checked and for the moment it was checked. What was never observed has not been tested — it simply did not come up. Changing that needs not only a reference but a rule by which it is built the same way everywhere.
Structure, naming and operating concept are created anew per project. Whoever takes over the second line first reads into a handwriting — not into a task. That is not a reproach to those involved; it follows from there being nothing for them to follow.
One special case can be mastered. Twenty can only be administered.States are named alike, transitions follow the same logic, messages carry the same structure. That makes the Behavior Reference (BR) not only checkable but readable by someone who was not there when it was created.
WhiteBox does not mean you can see the code. WhiteBox means conformity becomes decidable instead of a matter of judgment. Verification asks: was it built right? Validation asks: was the right thing built?It governs the structure, not the line. What your machine should do is still your decision; how it is described so that it stays checkable is the standard's.
Introduction to the Selmo Standard. If you cannot play the video: it shows the structure of the rule set on an example — the same four points are written out below. German soundtrack.
Rules for states, transitions, interlocks, signals and messages. Not as a recommendation but as the condition for two lines being comparable.
How a model is built so that a unit module can be reused in a larger line without its behavior being renegotiated.
A concept by which the states of the model are found again on the interface — instead of a second interpretation of the same behavior.
Rules for when a block enters the library, who releases it, and how a change to it affects the lines that use it.
Openness here is not a concession to the market but a condition of the method: what cannot be applied independently cannot be checked independently either.
The standard is written down. It can be learned, applied and checked — including by companies that do not work with us.
The exchange format. The reference and what is derived from it stay readable outside our tools.
The Behavior Reference (BR) belongs to the operator. It is handed over as an object — even to someone not called Selmo.
Behavioral knowledge is not outsourced, it is made transferable. Whoever knows the line is still needed — only no longer as the only source.
A handover is not a training course and not a folder. It is the question of whether the successor can check against the same document as the predecessor.
The Behavior Reference (BR) is not after-the-fact documentation of the code. It exists before the code — which makes it the only thing in a handover that does not age while you read it.
The standard sets the structure, Selmo Studio makes the derivation practicable. Neither replaces the reference — that is what is being produced.
The environment in which you model and derive — and in which the rules of this standard are applied.
A model on which the whole path is played through: from BlackBox to decidable conformity.
The defined behavioral space is the checked space. What is not modeled is not covered — the boundary moves, it does not disappear.
The question a rule set has to answer
15–30 minutes. We bring the answer, not the presentation.