B System or B Event
Method B for the specification and realization of proven software and mission-critical systems
Article REF: SE2525 V1
B System or B Event
Method B for the specification and realization of proven software and mission-critical systems

Author : Jacques valancogne

Publication date: January 10, 2012 | Lire en français

Logo Techniques de l'Ingenieur You do not have access to this resource.
Request your free trial access! Free trial

Already subscribed?

7. B System or B Event

7.1 B extensions at system level

In order to be able to work on systems that are not as small as software, it is necessary to model the environment in addition to the strictly software part, which is not done by B software or B "classic", which works in a closed way. B event-driven or B system-driven (we'll use both terms interchangeably) responds to the problem of systems by taking into account the reactive aspect, where the environment acts on the system and vice versa. To this end, the concepts of software B or classical B have been generalized. State/transition modeling is proposed (as for automata), with a static part and a dynamic part. In static mode, i.e. at a given moment in time, the state of the system is presented in two aspects: on the one hand, the state of the software...

You do not have access to this resource.
Logo Techniques de l'Ingenieur

Exclusive to subscribers. 97% yet to be discovered!

You do not have access to this resource. Click here to request your free trial access!

Already subscribed?


Article included in this offer

"Safety and risk management"

( 461 articles )

Complete knowledge base

Updated and enriched with articles validated by our scientific committees

Services

A set of exclusive tools to complement the resources

View offer details
Contact us