Eclipse Community Forums: Epsilon » Check consistency

Help

Home

Home » Modeling » Epsilon » Check consistency - multi domain

Show: Today's Messages :: Show Polls :: Message Navigator

Check consistency - multi domain [message #1827750]

Fri, 22 May 2020 13:40

Weslley Torres

Messages: 6
Registered: May 2020

Junior Member

Dear all,

My name is Weslley Torres and I am a Phd Student at Eindhoven University of Technology. My supervisors are Mark van den Brand and Alexander Serebrenik, both from the same University. I am writting a paper about tools/frameworks used to manage models. I have a few questions about Epsilon (EVL).

Can you please clarify whether this tool can check consistency between models? In case the answer is positive, does the consistency checking is performed between models from different domains or only between the same domain?

I have checked the Epsilon Book ( https://www.eclipse.org/epsilon/doc/book/ ) but it is not clear. It says that it does inter-intra model consistency checking but it doesn't specify if it is between model from different domains or only in the same domain.

Finally, in case this tool can check consistency between models from different domains. Can you please specify what kind of consistency these tools provide? Bellow you can find some kind of consistency to help you answering this last question:

Behavioral inconsistencies - occur between components that request and provide services whose names and interfaces match, but whose behaviors do not.

Information Consistency - It checks if the data that can be presented on different media, remain the same regardless of how they are presented. Example of Information inconsistency would be when the distance is presented in different units without respecting the conversion calculation

Interaction inconsistencies - occur when a component's provided operations are accessed in a manner that violates certain interaction constraints, such as the order in which the component's operations are to be accessed.

Interface inconsistencies - happen when connected interface elements have mismatching values, terminologies or schemes.

Name inconsistencies - happen when components, connectors or services have the same name.

Refinement inconsistencies - occur between models of different abstraction levels due to the fact the some elements are suppressed/inserted to fit the corresponding abstraction level.

Requirement Consistency - It checks whether the requirements from a requirement list are related to some model element and if this relationship is valid.

Thank you in advance,

Report message to a moderator

Re: Check consistency - multi domain [message #1827751 is a reply to message #1827750]

Fri, 22 May 2020 14:05

Dimitris Kolovos

Messages: 2163
Registered: July 2009
Location: York, UK

Senior Member

Hi Weslley,

EVL constraints can be executed against an arbitrary combination of models conforming to different metamodels/domains and even modelling technologies (e.g. you could validate an EMF model against a Simulink model [1], using additional information coming from an XML document [2]). As EVL is a Turing-complete language, it can be used to check for all of the types of inconsistencies you listed. Does this answer your question?

Thanks,
Dimitris

[1] https://www.eclipse.org/epsilon/doc/articles/simulink/
[2] https://www.eclipse.org/epsilon/doc/articles/plain-xml/

Report message to a moderator