MERODE[1] is an Object Oriented Enterprise Modeling method developed at KU Leuven (Belgium). Its name is the abbreviation of Model driven, Existence dependency Relation, Object oriented DEvelopment. MERODE is a method for creating domain models (also called conceptual models) as basis for building information systems making use of two prominent UML diagramming techniques - class diagram and state diagrams. Starting from a high-level PIM (close to a Computational Independent Model (CIM)) allows removing or hiding details irrelevant for a conceptual modelling view which makes the approach easier to understand. The method is grounded in process algebra, which enables mathematical reasoning on models. Thanks to this, models can be checked for internal consistency and mutual completeness, i.e. inter/intra model consistency and syntactical quality. The automated reasoning ("consistency by construction") [2] also caters for autocomplete functionality, which allows creating correct models faster.

A typical MERODE analysis or conceptualisation consists of three views or diagrams: a so-called existence dependency graph (EDG) similar to a UML class diagram, a proprietary concept namely an object event table (OET) and a group of finite state machines.

MERODE fosters a model-driven engineering approach to software development. It targets platform independent domain models that are sufficiently complete for execution, i.e. transformation to platform-specific models and to code. In order to achieve automated transformation of models, MERODE limits the use of UML to a number of well-defined constructs with clear semantics and complements this with the notion of "existence dependency" [3] and a proprietary approach to object interaction modelling.

MERODE-models can be created with the opensource case tool JMermaid.[4] The tool also allows checking the models for consistency and readiness for transformation.

A companion code generator[5][6][7] allows to generate a fully working prototype. One-click prototype production lowers the required skill-set for its useful application. By embedding the models into the application, the behaviour of the prototype can be traced back to the models, i.e. making it possible to validate the semantic quality of models. MERODE prototypes are augmented with feedback (textual and graphical) [8] that links the test results to their causes in the model.

References

  1. ↑ Snoeck, M. (2014). Enterprise Information Systems Engineering: The MERODE approach: Springer.
  2. ↑ Snoeck, M., Michiels, C., & Dedene, G. (2003). Consistency by construction: The case of MERODE. In M. A. Jeusfeld, Pastor, Oscar (Ed.), Conceptual modeling for novel application domains, LNCS (Vol. 2814, pp. 105-117).
  3. ↑ Snoeck M, Dedene G (1998) Existence Dependency: the key to semantic integrity between structural and behavioral aspects of object types. IEEE Trans Softw Eng 24(24):233–251
  4. ↑ "JMermaid: Java MERode Modelling AID".
  5. ↑ "Code Generation with MERODE-tools".
  6. ↑ Sedrakyan, G., Snoeck, M. Lightweight semantic prototyper for conceptual modeling, In Advances in Conceptual Modeling, LNCS (Vol. 8823, pp. 298-302), Proceedings of International Conference on Conceptual Modeling, ER'14. Atlanta, GA (US), Springer Switzerland
  7. ↑ Sedrakyan, G., & Snoeck, M. (2013). A PIM-to-Code requirements engineering framework. In Proceedings of Modelsward 2013-1st International Conference on Model-driven Engineering and Software Development-Proceedings, 163-169.
  8. ↑ Sedrakyan, G., Snoeck, M., & Poelmans, S. (2014). Assessing the effectiveness of feedback enabled simulation in teaching conceptual modeling. Computers & Education, 367-382, 367 - 382.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.