Formal verification of static software models in MDE: A systematic review

González, Carlos A.; Cabot, Jordi

doi:10.1016/j.infsof.2014.03.003

Cited by 48 publications

(44 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To illustrate what the tightened bounds look like with respect the original ones, we discuss the tightening of the initial bounds [1,5] for classes and [1,10] for associations. For the sake of brevity, we do not discuss attribute bounds:…”

Section: Resultsmentioning

confidence: 99%

“…• Teams -2 of the 5 classes have improved bounds: Person to [2,5] and Team to [1,2]. With respect to associations, 2 of the 3 associations have improved bounds: TeamMember and MembersInTeam have bounds [2,5] and MeetingParticipants has bounds [2,10].…”

Section: Resultsmentioning

confidence: 99%

“…Checking the correctness of a UML/OCL model is a complex problem and, in general, undecidable [4]. This has forced existing tools for UML/OCL analysis [5] to accept a series of trade-offs: reducing the expressiveness of the modeling language [6]; performing an incomplete search [7]; requiring user guidance to conduct the verification [8]; or, finally, limiting the search space [9].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Smart Bound Selection for the Verification of UML/OCL Class Diagrams

Clarisó

González

Cabot

2019

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

Abstract-Correctness of UML class diagrams annotated with OCL constraints can be checked using bounded verification techniques, e.g., SAT or constraint programming (CP) solvers. Bounded verification detects faults efficiently but, on the other hand, the absence of faults does not guarantee a correct behavior outside the bounded domain. Hence, choosing suitable bounds is a non-trivial process as there is a trade-off between the verification time (faster for smaller domains) and the confidence in the result (better for larger domains). Unfortunately, bounded verification tools provide little support in the bound selection process. In this paper, we present a technique that can be used to (i) automatically infer verification bounds whenever possible, (ii) tighten a set of bounds proposed by the user and (iii) guide the user in the bound selection process. This approach may increase the usability of UML/OCL bounded verification tools and improve the efficiency of the verification process.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Resultsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Smart Bound Selection for the Verification of UML/OCL Class Diagrams

Clarisó

González

Cabot

2019

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

show abstract

“…[9] presents a systematic literature review on the formal verification of static software models. Most of the works make use of UML models, often enriched with OCL constraints, and only a part of them is fully supported by a tool implementing the model transformations and the verification process.…”

Section: Related Workmentioning

confidence: 99%

Formal verification of storm topologies through D-VerT

Marconi

Bersani

Rossi

2017

Proceedings of the Symposium on Applied Computing

View full text Add to dashboard Cite

Data-intensive applications (DIAs) based on so-called Big Data technologies are nowadays a common solution adopted by IT companies to face their growing computational needs. The need for highly reliable applications able to handle huge amounts of data and the availability of infrastructures for distributed computing rapidly led industries to develop frameworks for streaming and big-data processing, like Apache Storm and Spark. The definition of methodologies and principles for good software design is, therefore, fundamental to support the development of DIAs. This paper presents an approach for non-functional analysis of DIAs through DVerT, a tool for the architectural assessment of Storm applications. The verification is based on a translation of Storm topologies into the CLTLoc metric temporal logic. It allows the designer of a Storm application to check for the existence of components that cannot process their workload in a timely manner, typically due to an incorrect design of the topology. CCS Concepts•Theory of computation → Verification by model checking; •Software and its engineering → Model-driven software engineering;

show abstract

“…There is a general consensus about the MDE concept as the promotion of models as primary artifacts for software engineering activities (Di Ruscio et al, 2013) (González and Cabot, 2014), and as the presence of model transformations that refine abstract/concrete modelling levels. However, due to the generality of this consensus, an initiative may be model-driven without a strict fulfillment of the minimum aspects necessary for real applicability with technological support (e.g., notations without an associated abstract syntax, stereotyped elements of common modelling languages, or modelling proposals with specific intentions and poor adoption by model-driven practitioners).…”

Section: Assessing the Compliance Of Modelling Languages With Mde Primentioning

confidence: 99%

Considerations about quality in model-driven engineering

et al. 2016

View full text Add to dashboard Cite

Giraldo-Velásquez, FD.; España Cubillo, S.; Pastor López, O.; Giraldo, WJ. (2016). Considerations about quality in model-driven engineering. Software Quality Journal. 1-66. doi:10.1007/s11219-016-9350-6. Considerations about quality in model-driven engineeringCurrent state and challenges.Fáber D. Giraldo · Sergio España · Oscar Pastor · William J. GiraldoReceived: date / Accepted: date Abstract The virtue of quality is not itself a subject; it depends on a subject. In the software engineering field, quality means good software products that meet customer expectations, constraints, and requirements. Despite the numerous approaches, methods, descriptive models and tools, that have been developed, a level of consensus has been reached by software practitioners. However, in the modeldriven engineering (MDE) field, which has emerged from software engineering paradigms, quality continues to be a great challenge since the subject is not fully defined. The use of models alone is not enough to manage all of the quality issues at the modelling language level.In this work, we present the current state and some relevant considerations regarding quality in MDE, by identifying current categories in quality conception and by highlighting quality issues in real applications of the model-driven initiatives.We identified sixteen categories in the definition of quality in MDE. From this identification, by applying an adaptive sampling approach, we discovered the five most influential authors for the works that propose definitions of quality. These include (in order): the OMG standards (e.g., MDA, UML, MOF, OCL, SysML), the ISO standards for software quality models (e.g., 9126 and 25000), Krogstie, Lindland, and Moody. We also discovered families of works about quality, i.e., works that belong to the same author or topic.Seventy-three works were found with evidence of the mismatch between the academic/research field of quality evaluation of modelling languages and actual MDE practice in industry. We demonstrate that this field does not currently solve quality issues reported in industrial scenarios. The evidence of the mismatch was grouped in eight categories, four for academic/research evidence and four for industrial reports. These categories were detected based on the scope proposed in each one of the academic/research works and from the questions and issues raised by real practitioners.We then proposed a scenario to illustrate quality issues in a real information system project in which multiple modelling languages were used. For the evaluation of the quality of this MDE scenario, we chose one of the most cited and influential quality frameworks; it was detected from the information obtained in the identification of the categories about quality definition for MDE. We demonstrated that the selected framework falls short in addressing the quality issues. Finally, based on the findings, we derive eight challenges for quality evaluation in MDE projects that current quality initiatives do not address sufficiently.

show abstract

Formal verification of static software models in MDE: A systematic review

Cited by 48 publications

References 24 publications

Smart Bound Selection for the Verification of UML/OCL Class Diagrams

Smart Bound Selection for the Verification of UML/OCL Class Diagrams

Formal verification of storm topologies through D-VerT

Considerations about quality in model-driven engineering

Contact Info

Product

Resources

About