Object-oriented software engineering
Object-oriented software engineering
The B-book: assigning programs to meanings
The B-book: assigning programs to meanings
Problem frames: analyzing and structuring software development problems
Problem frames: analyzing and structuring software development problems
Supplementing a UML Development Process with B
FME '02 Proceedings of the International Symposium of Formal Methods Europe on Formal Methods - Getting IT Right
Proceedings of the 25th International Conference on Software Engineering
An Overview of a Method and its Support Tool for Generating B Specifications from UML Notations
ASE '00 Proceedings of the 15th IEEE international conference on Automated software engineering
Automatic Translation from UML Specifications to B
Proceedings of the 16th IEEE international conference on Automated software engineering
UML-B: Formal modeling and design aided by UML
ACM Transactions on Software Engineering and Methodology (TOSEM)
Refinement, Decomposition, and Instantiation of Discrete Models: Application to Event-B
Fundamenta Informaticae - This is a SPECIAL ISSUE ON ASM'05
COMPSAC '08 Proceedings of the 2008 32nd Annual IEEE International Computer Software and Applications Conference
Precise specification of use case scenarios
FASE'07 Proceedings of the 10th international conference on Fundamental approaches to software engineering
Modeling in Event-B: System and Software Engineering
Modeling in Event-B: System and Software Engineering
FMCO'05 Proceedings of the 4th international conference on Formal Methods for Components and Objects
An open extensible tool environment for event-b
ICFEM'06 Proceedings of the 8th international conference on Formal Methods and Software Engineering
Hi-index | 0.00 |
UML-B is a development process framework for Event-B based on a "UML-like" graphical formal notation that provides support for object-oriented modelling concepts, in particular, for class and state machine diagrams. However, this methodology has a gap for mapping requirements to formal specifications. To overcome this issue, we present a proposal for extending UML-B to support a conceptual model to provide an easier starting point for the actual development process. More precisely, we propose two diagrams to facilitate the passing from requirements to the initial formal model: a first one to represent system behavior based on UML 2 interaction overview diagram (IOD) and a second one for system structure based on boundary-control-entity stereotyped class diagram (BCE). We show how to translate the former into an Event-B specification and explain how to link the latter to the original UML-B using a simple ATM example as proof of concept.