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

Mammar, Amel

doi:10.1007/s10270-008-0098-8

Cited by 6 publications

(2 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Mammar [42] adopts a formal approach to generating relational databases from UML models. However, this requires the manual definition of appropriate guards for predefined update operations: the automatic derivation of guarded programs from arbitrary specifications is not supported.…”

Section: Discussionmentioning

confidence: 99%

Formal model-driven engineering of critical information systems

Davies

Milward

Wang

et al. 2015

Science of Computer Programming

View full text Add to dashboard Cite

Please cite this article in press as: J. Davies et al., Formal model-driven engineering of critical information systems, Sci. Comput. Program. (2015), http://dx. Highlights• Model-driven tools can reduce the cost of development and verification.• Information systems can be produced automatically from object oriented designs.• A formal, model-driven approach is proposed for use in safety critical systems.• A framework is provided for the correctness of model transformations. AbstractModel-driven engineering is the generation of software artefacts from abstract models. This is achieved through transformations that encode domain knowledge and implementation strategies. The same transformations can be used to produce quite different systems, or to produce successive versions of the same system. A model-driven approach can thus reduce the cost of development. It can also reduce the cost of verification: if the transformations are shown or assumed to be correct, each new system or version can be verified in terms of its model, rather than its implementation. This paper introduces an approach to model-driven engineering that is particularly suited to the development of critical information systems. The language of the models, and the language of the transformations, are amenable to formal analysis. The transformation strategy, and the associated development methodology, are designed to preserve systems integrity and availability.

show abstract

Section: Discussionmentioning

confidence: 99%

Formal model-driven engineering of critical information systems

Davies

Milward

Wang

et al. 2015

Science of Computer Programming

View full text Add to dashboard Cite

show abstract

“…Recent work on generating provably correct code, for example [22], is restricted to producing primitive getter and setter methods, as opposed to complex procedures. Mammar [14] adopts a formal approach to generating relational databases from UML models. However, this requires the manual definition of appropriate guards for predefined update methods: the automatic derivation of guards, and the automatic generation of methods from arbitrary constraint specifications, as demonstrated here, is not supported.…”

Section: Discussionmentioning

confidence: 99%

Formal Model-Driven Engineering: Generating Data and Behavioural Components

Wang

Davies

2012

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

Model-driven engineering is the automatic production of software artefacts from abstract models of structure and functionality. By targeting a specific class of system, it is possible to automate aspects of the development process, using model transformations and code generators that encode domain knowledge and implementation strategies. Using this approach, questions of correctness for a complex, software system may be answered through analysis of abstract models of lower complexity, under the assumption that the transformations and generators employed are themselves correct. This paper shows how formal techniques can be used to establish the correctness of model transformations used in the generation of software components from precise object models. The source language is based upon existing, formal techniques; the target language is the widely-used SQL notation for database programming. Correctness is established by giving comparable, relational semantics to both languages, and checking that the transformations are semantics-preserving

show abstract

A graph grammar-based formal validation of object-process diagrams

Bibliowicz

Dori

2011

Softw Syst Model

View full text Add to dashboard Cite

Two basic requirements from a system's conceptual model are correctness and comprehensibility. Most modeling methodologies satisfy only one of these apparently contradicting requirements, usually comprehensibility, leaving aside problems of correctness and ambiguousness that are associated with expressiveness. Some formal modeling languages do exist, but in these languages a complete model of a complex system is fairly complicated to understand. Objectprocess methodology (OPM) is a holistic systems modeling methodology that combines the two major aspects of a system-structure and behavior-in one model, providing mechanisms to manage the complexity of the model using refinement-abstraction operations, which divide a complex system into many interconnected diagrams. Although the basic syntax and semantics of an OPM model are defined, they are incomplete and leave room for incorrect or ambiguous models. This work advances the formal definition of OPM by providing a graph grammar for creating and checking OPM diagrams. The grammar provides a validation methodology of the semantic and syntactic correctness of a single object-process diagram.

show abstract

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

Cited by 6 publications

References 11 publications

Formal model-driven engineering of critical information systems

Formal model-driven engineering of critical information systems

Formal Model-Driven Engineering: Generating Data and Behavioural Components

A graph grammar-based formal validation of object-process diagrams

Contact Info

Product

Resources

About