Deriving operational software specifications from system goals
Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering
An Abstract Model for Scheduling Real-Time Programs
ICFEM '02 Proceedings of the 4th International Conference on Formal Engineering Methods: Formal Methods and Software Engineering
Introducing Dynamic Constraints in B
B '98 Proceedings of the Second International B Conference on Recent Advances in the Development and Use of the B Method
Specification and Proof of Liveness Properties under Fairness Assumptions in B Event Systems
IFM '02 Proceedings of the Third International Conference on Integrated Formal Methods
Goal-Oriented Requirements Engineering: A Guided Tour
RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering
Managing Conflicts of Interest in Virtual Organisations
Electronic Notes in Theoretical Computer Science (ENTCS)
Duration calculus: a real-time semantic for B
ICTAC'04 Proceedings of the First international conference on Theoretical Aspects of Computing
Augmenting b with control annotations
B'07 Proceedings of the 7th international conference on Formal Specification and Development in B
Time constraint patterns for event b development
B'07 Proceedings of the 7th international conference on Formal Specification and Development in B
An event-B approach to data sharing agreements
IFM'10 Proceedings of the 8th international conference on Integrated formal methods
A design phase for data sharing agreements
DPM'11 Proceedings of the 6th international conference, and 4th international conference on Data Privacy Management and Autonomous Spontaneus Security
| Hi-index | 0.00 |
We propose a syntactic extension of Event-B incorporating a limited notion of obligation described by triggers. The trigger of an event is the dual of the guard: when a guard is not true, an event must not occur, whereas when a trigger is true, the event must occur. The obligation imposed by a trigger is interpreted as a constraint on when the other events are permitted. For example, the simplest trigger next, which states that the event must be the next one to be executed when the trigger becomes true, is modelled as an extra guard on each of the other events which prohibits their execution at this time. In this paper we describe the modelling of triggers in Event-B, and analyse refinement and abstract scheduling of triggered events.