We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byElijah McCabe
Modified over 2 years ago
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP Agenda Introduction Overview of using: 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
All rights reserved, Copyright © INTAP Introduction
All rights reserved, Copyright © INTAP Introduction Problems Objective Approach Open Standards used RM-ODP UML Profile for EDOC Introduction of Healthcare joint project
All rights reserved, Copyright © INTAP 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?
All rights reserved, Copyright © INTAP 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.
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP 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.
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP Five Viewpoints Enterprise 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
All rights reserved, Copyright © INTAP Target Enterprise Information Engineering Technology Computational Five Viewpoints
All rights reserved, Copyright © INTAP 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)
All rights reserved, Copyright © INTAP 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 companys system Customer management system within companys system Security systems Biomedical authentication system within security system … Therefore it is import to clarify which target you are specifying.
All rights reserved, Copyright © INTAP Application at various levels International industry consortium systems Participating companys system Customer management system Within a participating company Refinement
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP 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 Web Services User Web Services Provider Register Lookup Use Common diagram used to explain
All rights reserved, Copyright © INTAP 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.
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP What does it look like? Computational Viewpoint Model Component example Web Services Trader Component Lookup Register Link Proxy Admin Interfaces defined with IDL
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP App Server What does it look like? Technology Viewpoint Model Intra-net Web Server (Windows) Web App Firewall Client Internet Service Functions Legacy App WSDL Wrapper Intra-net Firewall Web Services Trader on Unix Firewall Stand-By Front End TP Monitor Web Services User Web Services Provider RDB
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP New System Enterprise View Information View Computational View Engineering View Technology View System X Divide and conquer with standard five viewpoints Model or Specification Refinements
All rights reserved, Copyright © INTAP System Integration System A System B Enterprise View Information View Computational View Engineering View Technology View refinements Think at the same granularity level
All rights reserved, Copyright © INTAP UML Profile for EDOC 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
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP Structure of UML Profile for EDOC Enterprise viewpoint (CCA, Processes, Entities, Relationships, Events) Technology viewpoint (UML for J2EE/EJB/JMS, CORBA 3/CCM, COM, SOAP, ebXML) Part I: Technology Specific Models Part II: Technology Mappings Part I: Enterprise Collaboration Architecture (ECA) (Technology abstraction: FCM) Engineering viewpoint Part I: Pattern can be applied to all viewpoints Information viewpointComputational viewpoint (CCA, Entities, Events)(Entities, Relationships)
All rights reserved, Copyright © INTAP 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
All rights reserved, Copyright © INTAP A Sample Process of Viewpoint Specification Development World of UML Profile for EDOC World of RM-ODP Enterprise Information Computational Engineering Technology Enterprise Information Computational Engineering Technology Focus of our current work
Copyright © 2008 Model Driven Solutions. Standards for Service Architectures SOA for e-Government Conference Cory Casanave cory-c (at) modeldriven.com.
Software Engineering Model Driven Architecture Software Engineering 2011 Department of Computer Science Ben-Gurion university Based on the book: MDA Explained:
The Model-Driven Semantic Web Emerging Technologies & Implementation Strategies Elisa Kendall Sandpiper Software September 8, 2005.
1 Computer Systems & Architecture Lesson 3 5. Designing the Architecture.
2/5/2014 4:51 PM SAEAF Education Series Session 1: Introduction and Overview September 2009 HL7 Services-Aware Enterprise Architecture Framework (SAEAF)
Architectural Design IS301 – Software Engineering Lecture # 14 – M. E. Kabay, PhD, CISSP Dept of Computer Information Systems Norwich University.
Tecnologia dei Servizi Grid e cloud computing - Lezione 003a 0 Lezione 3a - 20 ottobre 2009 Il materiale didattico usato in questo corso è stato mutuato.
Software Process Modeling with UML and SPEM Chris Armstrong Armstrong Process Group
Chapter 7 – Design and Implementation 1Chapter 7 Design and implementation Note: These are a modified version of Ch 7 slides available from the authors.
ITU-T X.906 | ISO/IEC 19793: UML for ODP system specification -- Current status -- Antonio Vallecillo Universidad de Málaga Dpto. Lenguajes y Ciencias.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Distributed Systems Architectures.
18 Copyright © 2005, Oracle. All rights reserved. Distributing Modular Applications: Introduction to Web Services.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Software Re-use IS301 – Software.
Chapter 7 – Design and Implementation Lecture 1 1Chapter 7 Design and implementation.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 10 Object-Oriented Analysis and Modeling Using the UML.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 10 Architectural Design.
Agent Based Software Development Michael Luck, Ronald Ashri and Mark dInverno Chapter 4: Methodologies and Modeling Languages.
1 Service Oriented Architecture Reference Model An informal SOA Ontology.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 14Slide 1 Chapter 14 Design with Reuse.
Page 1 R Copyright © 1997 by Rational Software Corporation Analysis and Design with UML.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Chapter 12 Object-Oriented Design.
1/23/2014 9:52 AM SOA4HL7: Defining Services based on HL7 Messaging Artifacts Alan Honey, Kaiser Permanente Enterprise Architect (Based on material initially.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 11Slide 1 Chapter 11 Distributed Systems Architectures.
Systems Analysis and Design 8 th Edition Chapter 7 Development Strategies.
7 February An Overview of the Systems Modeling (SysML) Specification Shana L. Lloyd Julie A. Street The Aerospace Corporation Systems Modeling Language.
Copyright © 2006 Data Access Technologies, Inc. Open Source eGovernment Reference Architecture Approach to Semantic Interoperability Cory Casanave, President.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
CS585 1/ Principals of Object Orientation OO Analysis Modeling with UML –UML Views User model view Structural view Behavioral view Implementation view.
© 2016 SlidePlayer.com Inc. All rights reserved.