B complements conventional management procedures put in place to
control the Software Process.

In the early stages of the software process, the specification, which
constitutes a model of the requirements of a system, is verified for
consistency and validated against the user's expectations by testing,
using typical usage scenarios. However during the development stages
each design description is verified to be consistent with the
requirements documented in its specification.

The lowest level of each design component is build on a reliable
library of pre-specified components, and is translated into executable
code. The B software design itself can be established as Zero Defect
and the reliability of the pre-specified components are established
through testing and re-use (many have actually been used in the
implementation of the B-Toolkit).

New low level components can be added, and these are either tested in
order to determine their properties, or formally developed using
existing reliable components.

The reliability of the operational system comes from the re-use of
the translators and the compilers used within the process and the
reliability of the run-time system which supports it. These latter
aspects of the system's reliability, though supported by the B, lie
outside the scope of mathematics which are used to establish a Zero
Defect B design.