1. Overview: Guide for applying RM-ODP with UML Profile for EDOC
From Enterprise Model to Computational Model
and + alpha
July 24, 2002
INTAP ODP Technical Committee

2. Agenda Introduction Overview of using: Summary Q&A
RM-ODP Enterprise Viewpoint Language
UML Profile for EDOC – Enterprise Model
UML Profile for EDOC – Information Model
UML Profile for EDOC – Computational Model
Engineering and Technology Model
Summary
Q&A

3. Introduction

4. Introduction Problems Objective Approach Open Standards used
RM-ODP
UML Profile for EDOC
Introduction of Healthcare joint project

5. Problems Things which make enterprise system development more complex:
Endless development requests generated to meet a variety of requirements
Requirements for integrating heterogeneous systems and technologies
New requirements like enterprise collaboration and Web Services support pop up unexpectedly
System integration requirements by mergers and acquisitions
Understanding, development, and maintenance of enterprise systems are getting more difficult
Is there any way to better handle or organize this enterprise system development?

6. Objective We need something for enterprise systems that:
makes it easier to understand
makes it easier to communicate between subject matter experts
Some kind of guideline for users to achieve above is the objective.

7. Approach “Divide and conquer” is the approach to handle complexity
Utilize usable International Standards and OMG Specifications for this purpose
Develop guideline for using standards about:
How to divide complexity
Sample steps or process of thinking (development)
What should be described in each divided area
What pitfalls are
With examples

8. Standards utilized
RM-ODP (Reference Model for Open Distributed Processing) from ISO/IEC & ITU-T
Viewpoints
Fundamental concepts
UML Profile for EDOC (Enterprise Distributed Object Computing) from OMG
UML extensions based on RM-ODP viewpoint framework
Business process, event, entity, relationship, component, pattern, technology mappings etc.

9. RM-ODP Reference Model for Open Distributed Processing
ISO Standards & ITU-T Recommendations
Developed initially as reference standards for developing standards for open distributed systems
Better to consider now as vendor neutral distributed system description framework
Being adopted by OMG (OMA, Model Driven Architecture)
Object Oriented
Distinguishing feature: Five Standard Viewpoints defined for any system description

10. Five Viewpoints Enterprise Information Computational Engineering
Purpose, scope, and policies (not necessarily means “real enterprise”)
Could be considered as requirements specification
Information
Meaning and processing of information
Information model and schema
Computational
Functional decomposition (close to application objects)
Could be considered as object model or component models
Engineering
Infrastructure to enable interaction between computational objects
Could be considered as infrastructure/middleware for distributed processing systems
Technology
Choice of hardware and software, and conformance

11. Five Viewpoints Information Computational Enterprise Engineering
Target
Enterprise
Information
Engineering
Technology
Computational

12. Five Viewpoints Viewpoint specification for each viewpoint
For one target system, at most five set of viewpoint specifications will be developed
Those five set of specifications have correspondence among them, because those are the descriptions of the same target system (descriptions just from different viewpoints)

13. Application of viewpoints
Can start with any viewpoint, but it would be enterprise viewpoint if top-down approach for thinking and design is taken.
Can apply at any granularity level
For instance, at the level of:　
International industry systems
→　National industry systems
→　Participating company’s system
→　Customer management system within company’s system
→　Security systems
→　Biomedical authentication system within security system
→　…
Therefore it is import to clarify which target you are specifying.

14. Application at various levels
International industry consortium systems
Participating company’s system
Customer management system
Within a participating company
Refinement

15. Application of viewpoints
What is defined and NOT defined in RM-ODP Viewpoint Language:
Defined
Vocabulary to define viewpoint specifications
Structuring rules
NOT defined
Notation: Could be text or any language or technique like FDT, UML, etc.
Process or methodology: Could be anything.
This is the reason we are working on the guideline

16. What does it look like?
Take an example of basic model for Web Services
Web Services User
Web Services Provider
Web Services Trader　（Registry like UDDI and ebXML’s)
Web Services
Trader
Common diagram used to explain
Lookup
Register
Web Services
User
Web Services
Provider
Use

17. What does it look like? Enterprise Viewpoint Model
Community:　Web Services Community- Target domain, Objective
Roles/Objects – Participants in the community
Web Services Trader
Web Services Provider
Web Services User
Web Services Trader Administrator
Web Services Description
Behavior
Web Services export
Web Services import
Policy – Constraints and rules
Web Services Export Policy
Web Services Import Policy　etc.

18. What does it look like? Information Viewpoint Model
Information element examples
Web Services Type
Web Services Description …
Invariant schema example for Web Services system
Web Services Description is uniquely identifiable
Dynamic schema example
State transition of information elements within Web Services Trader
Static schema example
Initial state for Web Services Trader

19. What does it look like? Computational Viewpoint Model
Component example
Lookup
Register
Link
Proxy
Admin
Web Services
Trader Component
Interfaces defined with IDL

20. What does it look like? Engineering Viewpoint Model
Internet/Web Services Infrastructure
Distributed Object style communication
SOAP/XML
Distributed or federated naming
Various interceptors
security
management
Intra Enterprise CORBA Infrastructure
CORBA Core
CORBA Naming
CORBA Trading

21. What does it look like? Technology Viewpoint Model Internet
RDB
Web Services
Trader on Unix
Firewall
Front
End
Web App
Firewall
Internet
Stand-By
App Server
Web Server
(Windows)
Firewall
Intra-net TP
Monitor
Intra-net
WSDL Wrapper
Client
Service Functions
（Legacy App）
Web Services Provider
Web Services User

22. Systems to be built? If the target is to develop new system:
Five viewpoints applied to entire target system
If the target is to integrate existing systems:
Five viewpoints applied to each of the existing systems (legacy systems)
Try to think of integration at the same granularity level

23. New System Model or Specification System X
Refinements
Enterprise View
Information View
Computational View
Engineering View
Technology View
Divide and conquer with standard five viewpoints
System X

24. System Integration System A System B
Think at the same granularity level
refinements
Enterprise View
Information View
Computational View
Engineering View
Technology View
System A
System B

25. UML Profile for EDOC EDOC UML UML Profile UML Profile for EDOC
Enterprise Distributed Object Computing
RM-ODP applied to enterprise systems
UML
Unified Modeling Language（OMG）
UML Profile
Customized UML for specific domains
UML Profile for EDOC
UML customized for enterprise systems based on RM-ODP framework

26. Added value to RM-ODP In addition to “divide and conquer,”
Since viewpoint description will be in UML,
More precise description will be possible,
A variety of UML tools become available for model based system developments (e.g. use of stereotype etc.), and
Depending on functions provided by tools:
Skeleton code may be generated from UML models
Fast path to system development with tool-integrated IDE
One realization of OMG MDA

27. Structure of UML Profile for EDOC
Composed of the following sub-profiles
Component Collaboration Architecture (CCA)
Entity Profile
Event Profile
Business Process Profile
Relationship Profile
Pattern Profile

28. Structure of UML Profile for EDOC
Enterprise viewpoint
(CCA, Processes, Entities, Relationships, Events)
Part I:
Enterprise
Collaboration
Architecture
(ECA)
Information viewpoint
Computational viewpoint
(Entities, Relationships)
(CCA, Entities, Events)
Engineering viewpoint
Part II:
Technology
Mappings
Part I:　
Technology
Specific
Models
(Technology abstraction: FCM)
Technology viewpoint
(UML for J2EE/EJB/JMS, CORBA 3/CCM, COM, SOAP, ebXML)
Part I: Pattern can be applied to all viewpoints

29. A Project
A joint project experimentally utilizing RM-ODP and UML Profile for EDOC is underway.
Dealing with Healthcare area
Feedback is expected from participation/experience
The guide is also “work in progress” for revision to reflect the feedback

30. A Sample Process of Viewpoint Specification Development
World of RM-ODP
World of UML Profile for EDOC
Enterprise
Enterprise
Information
Information
Computational
Computational
Focus
of our
current
work
Engineering
Engineering
Technology
Technology