A verification and validation process for model-driven engineering

Delmas, Rémi; Pires, Anthony Fernandes; Polacsek, Thomas

doi:10.1051/eucass/201306455

Cited by 5 publications

(5 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In 2013, Delmas et al defined a generic process of validation and verification for the design of the model and creation of the instance which has been centered on the class diagrams of the UML and its declarative constraints. this study illustrates the way by which the formal approaches may be utilized during the variety of the phases of the typical MDE (Model-Driven Engineering) procedure, from problem formalizations to solution syntheses, and verification of the solution [30].…”

Section: Tools and Approaches Of Vandvmentioning

confidence: 99%

Verification and Validation of a Software: a Review of the Literature

Altaie

Alsarraj

Al-Bayati

2020

ijci

View full text Add to dashboard Cite

With the development of the Internet, making software is often essential, also it is complicated to succeed in the project’s development. There is a necessity in delivering software of top quality. It might be accomplished through using the procedures of Verification and Validation (V&V) via development processes. The main aim of the V&V has been checking if the created software is meeting the needs and specifications of clients. V&V has been considered as collections related to testing as well as analysis activities across the software’s full life cycle. Quick developments in software V&V were of high importance in developing approaches and tools for identifying possible concurrent bugs and therefore verifying the correctness of software. It has been reflecting the modern software V&V concerning efficiency. The main aim of this study has been retrospective review related to various researches in software V&V and conduct a comparison between them. In the modern competitive world related to the software, the developers of software must be delivering on-time quality products, also the developers should be verifying that the software has been properly functioning and validating the product for each one of the client’s requirements. The significance of V&V in the development of software has been maintaining the quality of software. The approaches of V&V have been utilized in all stages of the System Development Life Cycle. Furthermore, the presented study also provides objectives of V&V and describes V&V tools that can be used in the process of software development, the way of improving the software’s quality.

show abstract

Section: Tools and Approaches Of Vandvmentioning

confidence: 99%

Verification and Validation of a Software: a Review of the Literature

Altaie

Alsarraj

Al-Bayati

2020

ijci

View full text Add to dashboard Cite

show abstract

“…Regarding the use of OCL to check or analyze a model, we can find several examples of its adaptation to industrial context and needs, offering technical solutions [16]. Some, such as [17] include OCL as a V&V solution in a process for models and instances design. In this paper, we focus on its use in a much broader context, that is a system development process including many kind of models and taking into account the work of several modeling teams across different projects.…”

Section: State Of the Artmentioning

confidence: 99%

SysML Models Verification and Validation in an Industrial Context: Challenges and Experimentation

Baduel

Chami

Bruel

et al. 2018

Lecture Notes in Computer Science

View full text Add to dashboard Cite

This paper presents a solution for SysML model verification and validation, with a return of experience from its implementation in an industrial context. We present this solution as a way to overcome issues regarding the use of SysML in an industrial context. We contribute by providing a method and a list of the existing challenges and experimentation results. We advocate the need to have semantics for SysML models without having to define a full domain-specific modeling language. We highlight the work, requirements and benefits that arise from the application of existing technical solutions, and hint at new perspectives and future development in system verification and validation.

show abstract

“…Mappings onto formal process specification languages have been performed for UML sequence diagrams (Dan, 2010), activity diagrams (Elmansouri et al, 2011) and state charts (Ng and Butler, 2003;Delmas, R. et al, 2013). The formal process specifications are then verified by a model checker to confirm the absence of a set of process design flaws.…”

Section: Related Workmentioning

confidence: 99%

“…Model validation and verification are extensively used to assess model quality within MDE (Malgouyres and Motet, 2006;Delmas, R. et al, 2013). In model validation one establishes that the requirements model correctly reflects the stakeholder needs and the design model correctly addresses those needs.…”

Section: Introductionmentioning

confidence: 99%

“…that they are free from undesirable engineering characteristics. To reduce the risk and cost introduced by model quality concerns it is vital that model quality assessment and management is done early and continuously (Delmas, R. et al, 2013). To this end one generally aims to integrate model verification within model editing and model transformation tools.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Constraints-based URDAD Model Verification

Solms

Hammond

Marshall

2016

Proceedings of the 11th International Conference on Evaluation of Novel Software Approaches to Software Engineering

View full text Add to dashboard Cite

In Model-Driven Engineering the primary artifact is a technology and architecture neutral model called a Platform Independent Model (PIM). The Use-Case, Responsibility Driven Analysis and Design (URDAD) is a service-oriented method which is used to construct a PIM commonly specified in the URDAD Domain-Specific Language (DSL). In this paper we show that model quality can be verified by specifying a set of quality constraints at metamodel level which are used to verify certain consistency, completeness, traceability and simplicity qualities of URDAD models. The set of constraints has been mapped onto the Object Constraint Language (OCL) and a tool used to verify these constraints has been developed. The set of constraints is also used by an URDAD model editor to verify aspects of model quality as it is being developed.

show abstract

A verification and validation process for model-driven engineering

Cited by 5 publications

References 9 publications

Verification and Validation of a Software: a Review of the Literature

Verification and Validation of a Software: a Review of the Literature

SysML Models Verification and Validation in an Industrial Context: Challenges and Experimentation

Constraints-based URDAD Model Verification

Contact Info

Product

Resources

About