Document Management Reference Model

Slides:



Advertisements
Similar presentations
Document Management Reference Model
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Distributed Systems Architectures Slide 1 1 Chapter 9 Distributed Systems Architectures.
Chapters 14 & 15 Internet Databases. E-Commerce  Bringing new products, services, or ideas to market, supporting and enhancing business operations 
Middleware Fatemeh Hendijanifard 1 آزمايشگاه سيستم هاي هوشمند (
Chapter 17: Client/Server Computing Business Data Communications, 4e.
Distributed Systems Architectures
A brief look at CORBA. What is CORBA Common Object Request Broker Architecture developed by OMG Combine benefits of OO and distributed computing Distributed.
1. Introducing Java Computing  What is Java Computing?  Why Java Computing?  Enterprise Java Computing  Java and Internet Web Server.
Middleware Technologies compiled by: Thomas M. Cosley.
The Architecture of Transaction Processing Systems
Systems Architecture, Fourth Edition1 Internet and Distributed Application Services Chapter 13.
2 Systems Architecture, Fifth Edition Chapter Goals Describe client/server and multi-tier application architecture and discuss their advantages compared.
Chapter 9: Moving to Design
Distributed Systems: Client/Server Computing
Chapter 9 Elements of Systems Design
Quality Assurance for Component- Based Software Development Cai Xia (Mphil Term1) Supervisor: Prof. Michael R. Lyu 5 May, 2000.
Microsoft Active Directory(AD) A presentation by Robert, Jasmine, Val and Scott IMT546 December 11, 2004.
Java-Based Middleware IT 490 Stan Senesy IT Program NJIT.
第十四章 J2EE 入门 Introduction What is J2EE ?
Enterprise Java Beans Java for the Enterprise Server-based platform for Enterprise Applications Designed for “medium-to-large scale business, enterprise-wide.
1 Introduction to Middleware. 2 Outline What is middleware? Purpose and origin Why use it? What Middleware does? Technical details Middleware services.
SEMINOR. INTRODUCTION 1. Middleware is connectivity software that provides a mechanism for processes to interact with other processes running on multiple.
Lecture 22: Client-Server Software Engineering
Chapter 17: Client/Server Computing Business Data Communications, 4e.
CSC 480 Software Engineering Lecture 18 Nov 6, 2002.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
Presented By:- Sudipta Dhara Roll Table of Content Table of Content 1.Introduction 2.How it evolved 3.Need of Middleware 4.Middleware Basic 5.Categories.
CS 501: Software Engineering Fall 1999 Lecture 12 System Architecture III Distributed Objects.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
Active Directory Domain Services (AD DS). Identity and Access (IDA) – An IDA infrastructure should: Store information about users, groups, computers and.
Document Management Alliance (DMA)
E-commerce Architecture Ayşe Başar Bener. Client Server Architecture E-commerce is based on client/ server architecture –Client processes requesting service.
Information Networks. Internet It is a global system of interconnected computer networks that link several billion devices worldwide. It is an international.
9 Systems Analysis and Design in a Changing World, Fifth Edition.
CORBA Antonio Vasquez, John Shelton, Nidia, Ruben.
1 Distributed Systems Architectures Distributed object architectures Reference: ©Ian Sommerville 2000 Software Engineering, 6th edition.
Zoljargal.M  Introduction  Methods, approaches  Specifics of Web architecture  Typical components of architectures.
Successfully Implementing The Information System Systems Analysis and Design Kendall and Kendall Fifth Edition.
Database Principles: Fundamentals of Design, Implementation, and Management Chapter 1 The Database Approach.
Integrating CMS/DMS into OpenOffice Michael E. Bohn Consultant Office Migration Sun Microsystems GmbH.
E-Business Infrastructure PRESENTED BY IKA NOVITA DEWI, MCS.
Distributed OS.
Internet and Distributed Application Services
Chapter 12: Architecture
Systems Analysis and Design in a Changing World, Fourth Edition
Sabri Kızanlık Ural Emekçi
CHAPTER 3 Architectures for Distributed Systems
Database Architectures and the Web
University of Technology
#01 Client/Server Computing
Chapter 3: Windows7 Part 4.
Ch > 28.4.
Networking Computer network A collection of computing devices that are connected in various ways in order to communicate and share resources Usually,
Inventory of Distributed Computing Concepts and Web services
Component-Based Software Engineering: Technologies, Development Frameworks, and Quality Assurance Schemes X. Cai, M. R. Lyu, K.F. Wong, R. Ko.
Goals Introduce the Windows Server 2003 family of operating systems
Inventory of Distributed Computing Concepts
Service Oriented Architecture (SOA)
Chapter 17: Client/Server Computing
KNOWLEDGE MANAGEMENT (KM) Session # 34
Network+ Guide to Networks, Fourth Edition
Introduction of Week 11 Return assignment 9-1 Collect assignment 10-1
Scott Thorne & Chuck Shubert
Quality Assurance for Component-Based Software Development
Design.
#01 Client/Server Computing
Presentation transcript:

Document Management Reference Model Draft 05a, 2/19/99

Document Repository Interfaces Desktop Apps Authoring (WP, Web) Presentations Document Assembly Scan/Capture Image Editing Business Process Applications Repository Access Native DM Clients Web Browsers View/Search Tools Cross-repository Search Print Services Enterprise Apps Workflow Apps Data Merge Apps Managed Document Repository Managed Document Repository Databases Managed Document Repositories Message Stores Indexed Content Other Repositories LOB App Data Stores Access Control Data Repositories are Central to Key Applications 2/19/99

Scanning and Printing Interfaces Intranet Modem WAN Extranet LAN Production Printers Data Center Systems Transaction Printing AFP/Metacode Printers Imaging & COLD Systems Publishing Workgroups Production Scanning & Printing Document, Content, & Asset Management Systems Knowledge Workers Ad Hoc Scanning Personal/Workgroup Printers Messaging, Workgroup, & Web Repositories LAN 2/19/99

DM Reference Model - A Collaborative Effort Marilyn Wright, AIIM International Benny Ong, Boeing Corporation Fred Siegmund, Chevron Carl Frappaolo, The Delphi Group Diane Entner, Eastman SW/Black Forest Group Chuck Fay, FileNET Michael Leslie, General Motors Surendra Reddy, Oracle Corporation Jean Heminway, Xerox Corporation Toby Cobrin, XPLOR 2/19/99

Document Management Reference Model - Goals Provide a framework which shows how document management systems fit into a corporate information technology infrastructure Show how document repository integration and interoperability can be handled seamlessly with document management standards Illustrate how extensible services like security and directory services are provided through the existing enterprise infrastructure Give a consistent way to illustrate the differences between document management standards 2/19/99

Document Management in the Enterprise Architecture Corporate Information Technology Infrastructure Network Man. System & Management Object Security & Directory Other Services Workflow/ WfMC Network OS Services Presentation/ Application Layer Document-Related Applications Middleware/ API Layer Document Management Middleware and/or API Service Provider Layer Repository Services Repository Administration Services 2/19/99

DMA in the DM Reference Model Corporate Information Technology Infrastructure Network Man. System & Management Object Security & Directory Other Services Workflow/ WfMC Network OS Services Presentation/ Application Layer DMA Client Applications <DMA API> Middleware/ API Layer DMA Middleware <DMA API> Service Provider Layer DMA Service Provider 1 (DM Repository 1) DMA Service Provider 2 (DM Repository 2) 2/19/99

ODMA in the DM Reference Model Corporate Information Technology Infrastructure Network Man. System & Management Object Security & Directory Other Services Workflow/ WfMC Network OS Services Popular office applications Application integration for ODMA Presentation/ Application Layer ODMA Connection Manager DM Integration Native DM Client Application API Layer <Native DM API> Serv. Prov. Layer DM Repository 2/19/99

ODMA with Multiple Repositories Corporate Information Technology Infrastructure Network Man. System & Management Object Security & Directory Other Services Workflow/ WfMC Network OS Services Popular office applications Application integration for ODMA Presentation/ Application Layer ODMA Connection Manager DM Integration 1 DM Integration 2 DM Client App. 1 DM Client App. 2 API Layer <Native DM 1 API> <Native DM 2 API> Serv. Prov. Layer DM Repository 1 DM Repository 2 2/19/99

ODMA and DMA Interoperability Corporate IT Infrastructure Popular office applications Presentation/ Application Layer Application integration for ODMA ODMA Connection Manager ODMA-to-DMA Client Application <DMA API> Middleware/ API Layer DMA Middleware <DMA API> DMA Service Provider 1 (DM Repository 1) DMA Service Provider 2 (DM Repository 2) Serv. Prov. Layer 2/19/99

WebDAV in the DM Reference Model WebDAV Client WebDAV Client Application HTTP/WebDAV HTTP/WebDAV <Native HTTP API> WebDAV Service Provider WebDAV-enabled Web Server 2/19/99

Generic DMA Distributed Client DMA Client DMA Client Application Network Services Network Services DMA Client (skeleton) <DMA API> DMA Middleware DMA Repository <DMA API> 2/19/99 DMA Service Provider

WebDAV and DMA Interoperability WebDAV Client WebDAV Client Application HTTP/WebDAV HTTP/WebDAV WebDAV to DMA Translator <DMA API> DMA Middleware DMA Repository and Web Server <DMA API> DMA Service Provider 2/19/99

CORBA and DMA Interoperability CORBA Client Java Client Application CORBA ORB CORBA ORB CORBA IDL to DMA Translator <DMA API> DMA Middleware DMA Client & Repository <DMA API> 2/19/99 DMA Service Provider

CORBA and DMA Interoperability CORBA ORBs could also be used to distribute the middleware and/or service provider layers of the DM reference model CORBAservices and CORBAfacilities are additional infrastructure that could be leveraged in DMA service provider implementations 2/19/99

Generic DMA Distributed Middleware DMA Client DMA Client Application <DMA API> DMA Middleware Network Services Network Services DMA Middleware <DMA API> DMA Service Provider DMA Repository 2/19/99

Generic DMA Distributed Service Provider DMA Client Application DMA Client <DMA API> DMA Middleware <DMA API> DMA Service Provider Stub Network Services Network Services DMA Service Provider 2/19/99 DMA Repository

Reference Model Definitions

Presentation/Application Layer Document-related applications Desktop applications Enterprise applications Native document management clients Scan/Print services Presentation layer Provides user interface ODMA 1.0 providers and other extensible presentation frameworks are at this level 2/19/99

Middleware/API Layer Defines common interfaces for services provided by document repositories DMA and CORBA IDL for DM are examples Proprietary API in some cases (e.g., in ODMA model) Provides a uniform access model for document repositories Repository registration and location Cross-repository search 2/19/99

Middleware/API Layer May provide transparent object distribution across network boundaries (e.g., via CORBA or DCOM) Alternatively, may intercede only in limited ways, and otherwise allow client calls to pass through untouched E.g., non-distributed DMA middleware handles repository registration and location, and cross-repository search, but allows all other functions to pass directly from client to service provider 2/19/99

Service Provider Layer Provides services for repository usage and administration Different DM vendors can plug in their DM repositories within a standards-based enterprise-wide framework Administration distinguished from usage; administration currently not standardized 2/19/99

Corporate Information Technology Infrastructure DM model builds on existing enterprise IT infrastructure services -- transport, object management, network management, security, directory, database, work flow, OS E.g., DM vendors could build on CORBA or DCOM for distributed object management, rather than build a proprietary infrastructure 2/19/99

Network Services Network services provide for communicating with document repositories in a networked environment Allows clients to communicate with document repositories, and to request and receive information from service providers 2/19/99

Network Services Provides flexible transport mechanism by which documents are transferred from document repositories to clients Application-level protocols like WebDAV provide high-level functions like locking, property management, etc. on top of basic transport protocols 2/19/99

Object Management Services Provides transparent object distribution, e.g., via CORBA, DCOM, or RPC Gives the clients uniform access to distributed, heterogeneous information resources and services Supports object lifecycle management, transactions, etc. -- e.g. CORBAservices, MTS, COM IUnknown 2/19/99

System & Network Management System Management: Manages software installation, configuration, & upgrades across an enterprise Network Management: Monitors, manages, & controls network topology and nodes 2/19/99

Security & Directory Services Security Services: Enforces access controls and user authentication Directory Services: Provides service for locating network resources, nodes, users, groups, etc. 2/19/99

Operating System Services Provides fundamental services for memory allocation and management, file systems, device management, network connectivity, ... 2/19/99

Relationships Between Elements In the front document management plane, physical proximity of layers implies that those layers interact via objects and method calls. Likewise, the proximity of the document management plane to the IT infrastructure planes implies interaction. However, the positioning of the infrastructure layers in the diagram is arbitrary; juxtaposition does not necessarily imply a relationship between infrastructure layers. Interactions among the elements of the IT infrastructure are beyond the scope of this reference model. 2/19/99