From a B formal specification to an executable code: application to the relational database domain

A systematic approach to generate B preconditions: application to the database domain

“…The paper focuses on the last phase since the first two ones are largely described and compared with the relevant related work in our previous publications [12,14]. We just sum them up in the next section; the aim is to point out the generic features of the B specification obtained by translating the UML notations.…”

“…The problem addressed in this paper concerns the consistency of the B specification that is generated in the first step as described in [13,14]. In fact, as the UML notations are not sufficient to express all the business rules, some of them are directly expressed as B invariants.…”

A formal approach based on UML and B for the specification and development of database applications

“…4. From the last refinement step, the definition of the database schema is automatically derived (Mammar and Laleau, 2006;Mammar, 2002). We plan to extend this automation to derive the programs corresponding to the transactions.…”

“…Moreover, the variables which the transitions may refer to are refined by the variables defined in the imported SQL machines. In Mammar and Laleau (2006), we have defined a generic and automatic process to refine transactions. The refinement of transactions consists hence of the following points:…”

“…Since by construction S 1 and S 2 do not modify the same variables, two solutions are possible: either (S 1 ; S 2 ) or (S 2 ; S 1 ). In Mammar and Laleau (2006), we described a formal approach that provides the best solution. The approach is based on the set of modified and read variables of S 1 and S 2 .…”