Issues for Discussion on MFI-9 Jian Wang, Keqing He, Chong Wang, Peng Liang, Zaiwen Feng SKLSE, Wuhan Univ.

The basic idea and content of MFI-9 have been reported several times in WG2 meeting. We hope we can get a consensus on the scope and basic contents of MFI-9, so that we can prepare our CD draft ASAP.

Scope of MFI-9 Specify a technical guideline on how to use R, G, P, and S metamodels to select appropriate combinations of models and/or services to meet users' goals. Specify how to use the RGPS infrastructure to support operational harmonization and interoperability within and between industries. From resolution of Wuhan Meeting, September, 2008

Basic Idea of MFI-9 Faced with the personalized and diverse requests of users, how to select appropriate services/models from abundant and heterogeneous model resources These models registered in MFI registries can be semantically annotated by Ontologies and connected by RGPS According to the matching between users' requests and registration information of models, appropriate models can be selected to satisfy users' requests

Contents to be covered in MFI-9 The relationship of the RGPS models Specify the different kinds of users’ requests Define model selection strategy Based on RGPS relationship Model selection evaluation Basic principle to evaluate the selection result from the view of the user and the registry

Several Problems

Model selection or Service selection We think that services registered in MFI-7 can be viewed as a service model. MFI-9 can help users select service models, as well as role&goal models, process models. Depends on different usage scenario Depends on different user type: end user or developer. E.g., A developer might use service as an input, and wish to find its goal model An end user might input a goal, and wish to find a service model

Shall we need to define the model selection template The model selection template may consist of Mandatory part Input type (RGPS) Expected result type (RGPS) Optional part Priority or amount of the result Precision of selection result … The recognition of user’s request can be based on domain ontology

The interaction procedure during model selection Should the interaction procedure during model selection be defined in MFI-9? We think that users should be tightly involved during model selection. User’s feedback on confirming requests can contribute to the satisfied selection result

About the Cardinality and Registration Status According to the discussion with Masao san, we think that: The multiplicity constraints in MFI-5,7,8 should be maintained. These constraints can be used in checking whether the registration info is in the “Approved” or “Recorded” status. For example, we define a service should have one and only one goal. Although the corresponding goal instance doesn't exist, the service instance can be registered in MFI registry with a "Unapproved" status. Only after it has a corresponding goal instance, it can be in the “Approved” or “Recorded” status.

How to store the relations in RGPS Each part will maintain its relations with others all the relations should be defined according to RGPS When the cardinality constrain is satisfied, the status can be in an “Approved”status

The cache of the users' selection result The users' selection history should be recorded so as to recommended for the similar request. The selection results such as the composite service composed according to users request can be cached for reuse.

Architecture of ODMS ① ⑦ Model Selection Engine ⑥ ② ④ ③ ⑤ P ① ⑦ Model Selection Engine ⑥ ② ④ ③ This figure shows the architecture of ODMS, which consists of three parts. Selection engine, selection record registry, and MFI registries. When a user wants to select models. First he may submit his request to the selection Engine. Then the request will be sent to a selection record registry to search history record. If there is a similar request, the models will be returned to users. Otherwise, the selection Engine will make a selection from MFI Registries. Based on the relationships in RGPS and annotation provided by domain Ontology, the models related to the request will be found and returned to users. Meanwhile, the selection record will be registered in the selection record Registry. ⑤ Role&Goal Registry Service Registry … Process Registry Ontology Registry Selection Record Registry MFI Model Registries

Thank You!