DISCUSSION ABOUT REGISTRATION OF RM-ODP LIBRARY EXAMPLE BASED ON MFI

Yuan Lin, Wang Jian, Wang Chong, Liang Peng, Feng Zaiwen

Outline

Introduction to RM-ODP RM-ODP library example registration

Enterprise viewpoint registration Information viewpoint registration Computational viewpoint registration

3

What is ODP

RGPS will not cover all the aspects of information systems

RGPS provides a framework for the management, discovery and sharing of service-related models.

4

RM-ODP Viewpoints—Support different concerns( cited from Denise’s presentation )

Consider: These 3 represent the service Semantics

5

R

G

P

6

7

S

Important Definitions in RM-ODP from ISO/IEC:15414

Role Roles are used to decompose the behavior of the

community into parts that can each be performed by an enterprise object in the community

Actor Enterprise object fulfilling the role participates in the

action Objective

Practical advantage or intended effect, expressed as preferences about future states

Important Definitions in RM-ODP from ISO/IEC:15414 cont.

Process A collection of steps taking place in a prescribed

manner and leading to an objective A process identifies an abstraction of the community

behavior that includes only those actions that are related to achieving some particular sub-objective within the community

How to register specific part of RMODP to RGPS Enterprise Viewpoint Information Viewpoint Computation Viewpoint

Enterprise Specification Metamodel

System Concepts Community Concepts Policy Concepts Accountability Concepts

System Concepts

MFI-2:Context

Community Concepts

MFI-8:Role

MFI-8:Actor

MFI-8:Goal

MFI-8:Interaction

MFI-8:Organization

MFI-5:Process

MFI-5:Atomic Process/

Composite Process

MFI-5:Resource

MFI-2 MFI-8 MFI-5 RMODP

Context Field of application

Role Role

Community Organization

Actor Actor

Interaction Behavior

Goal Objective

Process Process

Process/Atomic Process

Step

Resource Artifact/Resource

Policy Concepts

MFI-8:Rule

MFI-8:Rule

Accountability Concepts

MFI-8:Role

MFI-8:Interaction

MFI-8 RMODP

Rule Rule/Policy

Role Party

Interaction Action

Library Example - EV

Building Enterprise Specification1. Identify community and its objectives2. Define Behavior fulfill roles

Could be processes Could be interactions between objects fulfilling roles

3. Identify Enterprise Objects in community4. Identify policy

Enterprise View of the Library System

MFI-8 :Organization

MFI-8 :Organization

MFI-8 RMODP E.g.

Community Organization Library, Academic

Library Community Spec

MFI-8:Goal

MFI-8 RMODP E.g.

Goal Objective Library objective

Process Specification

MFI-5:Process

MFI-5 RMODP E.g.

Process Process Borrow_Item, Add_member…

MFI-5:Process

MFI-5:Process

MFI-5:Process

MFI-5:Process

MFI-5:Process

MFI-5:Process

MFI-5:Process

MFI-5:Process

MFI-5:Process

MFI-5:Process

MFI-5:Process

Borrow Member Process

MFI-5:Atomic Process

MFI-8:Role

MFI-8:Role

MFI-8:Role

MFI-5:Atomic Process

MFI-5:Atomic Process

MFI-5:Atomic Process

MFI-5:Atomic Process

MFI-5:Atomic Process

MFI-5:Resource

MFI-5:Resource

MFI-5 MFI-8 RMODP E.g.

Role Role Borrower, Assistant, Library System

Resource Artifact Loan

Atomic Process Step State_loan_req, Check_req

MFI-5:Composite Process

Roles & Behavior

MFI-8:Role

MFI-8:Role

MFI-8:Role

MFI-8:Role

MFI-8:Role

MFI-8:Operational GoalMFI-8 RMODP E.g.

Role Role Libraian, Assistant, Assistant, …

Operational Goal

Behavior Create Member, Refuse new member, …

Interaction behavior

MFI-8 RMODP E.g.

Interaction Interaction Process Loan

Enterprise Object

MFI-8:Actor

MFI-8:Actor

MFI-8:Actor

MFI-8:Actor

MFI-8:Actor

MFI-8:Actor

MFI-8:Actor

MFI RMODP E.g.

Actor Enterprise Object Library System, Undergraduate

Policy

MFI-8:Rule

MFI-8:Rule

Lending limit policy

MFI-8:Rule

MFI RMODP E.g.

Rule Policy Lending Limit, Loan duration

Information Viewpoint

Concerning information modeling Semantics of information Information processing

Focus on Consistent interpretation of information by the

components of the ODP system Data and schemas

Information language metamodel

Three schemas

Predicates and specification of the data Invariant schema

expresses relationships between information objects which must always be true, for all valid behaviour of the system

Static schema expresses assertions which must be true at a single point in

time Dynamic schema

specifies how the information can evolve as the system operates

Could also constrain roles

Could relate to processes

Library Example - IV

Role

Role

Role

Invariant schema Example

There should be at most Librarian and at least one Assistant on duty while the library is open. This is a predicate on roles that always should be true Could be registered in MFI-8

Library Example - IV

Dynamic Schema

In a loan, undergraduate students can borrow N books provided that the total amount of books he/she borrows do not exceed 8. It is a constraint on the Borrow Item process Could be registered in MFI-5

Computational View

Concerning with functional decomposition Decompose the system into a few computational

objects Encapsulation Interact with other computational objects – through

interface

Building the computational view

3 steps: Identify the basic operations Group them into interfaces Identify the computational objects own the interfaces

The decomposition of the system provides the software architecture in an object-oriented way

Thus we face a significant difference between RM-ODP and RGPS Object-oriented vs. Service-oriented

Computational object is the closest element to the service ?

Computational view metamodel

Library Example – CV

Service

Service

Service