MFI-9: On Demand Model Selection

WANG Jian, HE Keqing, WANG Chong, LIANG Peng, FENG Zaiwen

State Key Lab of Software Engineering (SKLSE),

Wuhan University, China

2010-05-26

1

Motivation of ODMS

2

Objectives of RGPS

RGPS provides a framework for the management, discovery and sharing of service-related models. RGPS can be used to describe services in different

views(Role, Goal, Process,Service), and it can also be used to express users’ needs.

According to the mappings between users’ needs and registration information of models, appropriate models can be selected to satisfy users’ needs.

Semantic annotation: some elements in these models can be annotated by registered domain ontologies.

3

4

Difficulty of Model Selection

B8

A1A4 A1 A2

A4

B3

A1A4 A6

A5

A4 A1A1

A4A1 A4 A1 A2

A1 A1A1

A1

B3

A1

B3

A1

A2A1

B3

A1A4 A1 A2

A1B3

A1A4 A1 A2

A1

B3

A1

A1

B3

A1A4 A1 A2

A1

B3

A1A4

A2

A1

B3 A1A4

A1 A2

B3A1 A1

B3

A1A4 A1 A2

A1

B3

A1A4 A1

A2A1

B3 A1A4 A1

A2

A1B3

A1A4 A1 A2

A1

A1A4 A1

A1A4 A1 A2B3

A1A4

A1A2

A1B3

A1 A4A1 A2

A1

B3

A1A4 A1

A2

B3A1

A4

A1 A2

A1

B3

A1A4 A1 A2

A1B3

A1A4 A1 A2

A1

A4

A4

A1

A4

A1

A1 A4 A1 A2

B3

A1A4 A1

A2

A1

B3

A1 A4

A1

A2B3

A1

A4 A1 A2A1

A4

A1

A4 A1

A1A4

A1 A2

A1

A1 A4 A1 A2A1

A1A4

A1

B3A1

A1

A1

B3

A1A4 A1 A2

A1B3

A1A4 A1 A2

A1

A1 A2

A1

A4 A2 A4 A2A2

A1

A1

B3

A1A4 A1 A2

A1

Why On Demand Model Selection is important? Personalized and diverse requests Abundant and heterogeneous model resources

?Role&GoalRole&Goal

ProcessProcess

ServiceService

Basic idea of ODMS

Faced with the personalized and diverse requests of users, how to select appropriate service/models from abundant and heterogeneous model resources Register these models in MFI registries Annotate the models based on registered ontology According to users’ request, select appropriate

models based on the relationships among the models

5

Role of RGPS in ODMS

66

ServiceService

UserUser

RGPSRGPS

RGPSRGPS

Top-Down

Matching Role

Matching Goal

Matching Process

Matching Service

Matching Role

Matching Goal

Matching Process

Matching Service

Who

What to do

How to do

Which service is needed

For Whom

What can do

How to do

How to use

Bottom-Up

ScopeScope

This ISO/IEC Technical Report specifies 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.

It also specifies how to use the RGPS infrastructure to support operational harmonization and interoperability within and between industries.

From resolution of Wuhan Meeting, September, 2008From resolution of Wuhan Meeting, September, 2008

7

Scope of MFI-9

Content of ODMS

8

Relationships in RGPSAn actor can play zero to many roles.

A role can take charge of at least one role goal.

An actor can prefer zero to many personal goals.

A role can involve at least one process.

A service can serve at least one role.

A process can achieve one goal.

A process can be realized by zero to many services.

A service can accomplish one goal.

P

S

R

G

&

The relationships are the foundation for model selection in MFI-9 9

Semantic annotation of models

R&G

S

Service

Goal

Process

P

Domain Ontology

Object

hasOperation

Input

hasInput

Output

Semantic Annotation

Operation

Contribute to• mapping between models• semantic discovery of models

Resource

10

hasObject

hasOutput

hasResource

MFI-3MFI-8

MFI-5

MFI-7

Role

plays

Architecture of ODMS

11

MFI Model RegistriesMFI Model Registries

Selection Selection RecordRecordRegistryRegistry

S

RG

P

Role&Goal Role&Goal RegistryRegistry Process Process

RegistryRegistry

Service Service RegistryRegistry Ontology Ontology

RegistryRegistry

①

②

⑦

③

⑤

④

⑥Model Model Selection Selection EngineEngine

……

Model Selection Strategies (1/5)

Users’ request can be expressed as role/goal/process/service.

The whole model selection process consists of many steps Each step may follow the relationships in

RGPS When there is no model/service that satisfies

users, the registries will be revisited to find some possibly useful models/services.

12

Model Selection Strategy (2/5) Role

Role->Role Role->Goal Role->Process Role->Service

13

Role Goal Process Service

Role interaction takesCharge involves servedBy

Model Selection Strategy (3/5) Goal

Goal->Role Goal->Goal Goal->Process Goal->Service

14

Role Goal Process Service

Goal takenChargeBy decomposes achievedBy accomplishedBy

Model Selection Strategy (4/5) Process

Process->Role Process->Goal Process->Process Process->Service

15

Role Goal Process Service

Process involvedBy achieves composedBy realizedBy

Model Selection Strategy (5/5) Service

Service->Role Service->Goal Service->Process

16

Role Goal Process Service

Service serves accomplishes realizes

Template of Model Selection

Model Selection Input Expected Output Criterion

Similarity Stopping criterion

17

Typical Model Selection Typical Model Selection Process (Case 1)Process (Case 1)

S

RG

P

Role

Goal

Process

ServiceUserUser

Input ： GoalExpected Output ： Service

18

Input ： GoalExpected Output ： Process

19

S

RG

P

Typical Model Selection Typical Model Selection Process (Case 2)Process (Case 2)

Role

Goal

Process

ServiceUserUser

S

RG

P

Role

Goal

Process

Service User

Input ： RoleExpected Output ： Service

20

Typical Model Selection Typical Model Selection Process (Case 3)Process (Case 3)

An example

21

Functional Goal

Operational GoalRole

bbbbbbbbbbbbbbb

22

Service01: QueryWeather_InfoURI http://www.daml.org/services/owl-s/1.2/

Service.owl#WeatherInforService Provider Wuhan weather stationDescription_Language

OWL-S

Composite Process

Atomic Process

Service02: QueryHotelURI http://www.daml.org/services/WSMO/

QueryHotelervice Provider …Description_Language

WSML

Example

User’s Input: Goal(Arrange Travel Plan) User’s Expected Output: Process

Step1: Match users’ input with the Goal in registry

23

Role_Goal00

id RG00

name ArrangeTravel_Plan

goal_type Functional Goal

is_operational false

hasOperation Arrange

hasObject Travel_Plan

hasManner

Process01

ID 1

name ArrangeTravel_Plan

administration_Record

#

achieves ArrangeTravel_Plan

type C

describedBy Process_Model01:ArrangeTravel_Plan_ProcessMod

el

creates Resource01: Audio_TravelRout/ Resource02: Vedio_TravelRout/Resource03: Map_TravelRout/Resource04: Text_TravelRout

restrictedBy Sequence01

Sequence01

constructType Sequence

nodeSet Process02: SearchDestination

Process03: QueryTavelInfo

Process04: PlanTravel_Rout

Process05: DispayTravel_Rout

• Step2: Search for the process achieve that goal.• Step3: Find the processes that compose the process• Step4: Return the process to the user.

MFI-9 vs. the other parts of MFI

Basic Interoperation PatternBasic Interoperation Pattern

((MFI-1,2,3,4,6))

Basic Interoperation PatternBasic Interoperation Pattern

((MFI-1,2,3,4,6))

Service Oriented InteroperationService Oriented Interoperation

((MFI-5,7,8,9)

Service Oriented InteroperationService Oriented Interoperation

((MFI-5,7,8,9)

Based onBased on

25

Relationship between ODMS and the other parts of MFI

Personalized Needs

Models Role/Goal Models, Process Models, Service Models…

Role&goalRegistry

…… Process Registry

On Demand Model Selection MFI-9

Federated Registry

MFI-3 MFI-5

MFI-7

MFI-8

MFI-9

Serive Registry

OntologyRegistry

26

27