Meta Models and Meta Execution Models

Kamalakar Karlapalem, IIIT – Hyderabad, India
Radha Krishna Pisipati, Infosys Labs, Infosys Limited, India

Tutorial Abstract:
The topic of meta modeling is important for many areas in information systems such as conceptual modeling, business processes and workflow management. Meta modeling conceptualizes data models and provides the functionality required for adapting a data model to new requirements. These meta models are useful for describing the data, relationships and the associated information such as rules and exceptions to model complex applications such as workflows, e-contracts and e-services. The supporting features for meta models help in modeling the complexities across many applications to instantiate appropriate (or customizable) model for a specific application.

The concept of meta-execution introduces an innovative aspect that facilitates flexible execution environment without much re-design of application engines such as workflow engine. Processes get executed by the execution model, which dictate how the models are executed, and the specification of this execution model as a process using the concepts of execution model is the meta execution model. Meta execution models are specific to conceptualizing and representing the execution logic for executing processes. For example, Meta Execution Workflows describe the execution logic of workflow management engine that drives specification and execution of workflows. Meta Model along with Meta Execution Model provides a powerful construct to manage the data and processing capabilities of changing reality in a seamless manner. Further, it helps connect conceptual layer to actual physical layer by using constructs, their implicit semantics and constraints to cater to dynamic and evolving reality. This kind of framework can seamlessly model data and processes.

This tutorial presents a class of meta models and meta execution models by promoting active conceptual modeling and meta execution models. In this tutorial, we introduce meta models and meta- execution models and show how they help in orchestrating the complex application design and development, and deployment. We present our concepts through a case study on e-contracts enactment and describe meta models and meta execution models (through meta-execution workflows) to support their enactment.


How to make Requirements Modelling Languages?

Ivan Jureta
Fonds de la Recherche Scientifique – FNRS, Brussels, Belgium and Department of Business Administration, University of Namur, Belgium

Tutorial abstract:
This is a tutorial on how to make Requirements Modelling Languages (RMLs), formalisms used to facilitate problem-solving in Requirements Engineering (RE).

RE focuses on how to elicit, model, and analyse the requirements and the environment of a system-to-be, in order to produce its specification. The tutorial shows how to make new RMLs, in a progression from simpler to more complicated ones, reviews and illustrates major topics and challenges in RML design, and discusses the designs of oft-cited RMLs in RE research.

This is a tutorial for professionals and researchers who need to select among existing, or make new rules for documenting the inputs, decisions, and outcomes of early phases of system design. The rules are usually made for interdisciplinary teams who do system design. Teams can include such disparate groups as investors in the system-to-be, product designers, future users, business analysts, domain experts, engineers from relevant fields (construction, software, hardware, and so on, depending on the purpose of the system-to-be), government representatives, legal professionals.

The rules are applied in order to facilitate problem-solving during design, by clearly representing the information relevant for design, the design options, relative merits of the options, and in order to produce documentation of the chosen design, which is used for, for example, selecting subcontractors, engineering and implementing the system, quality evaluation and assurance, evaluation of regulatory and standards compliance. The rules are applied in early phases of system design, in that they usually do not produce a system design specification which is sufficiently complete and detailed to serve as a blueprint to make the system. Instead, they result in a clear definition of the system’s purpose, of the main constraints it has to live with, and of (some) constraints on how it should achieve its purpose, all of which are inputs for engineers who are responsible for producing the specification of the system’s detailed design.

Participants do not need to have specific knowledge of RE.